>>I'd maybe just hide it by default, and do a single api call on
>>GET /nodes/NODE/sdn
yes, good idea !
pvesh get /cluster/sdn
┌─────────────┐
│ id │
╞═════════════╡
│ controllers │
├─────────────┤
│ vnets │
├─────────────┤
│ zones │
└─────────────┘
(Could also be used to filtering specific sub-section, if later we want to
extend it with dhcp,... or others beta things)
>>if this does not errors out (e.g., with "no such resource") then we know that
>>SDN is available and can save that in a PVE. object for caching, e.g.,:
>>PVE.FeatureInfo = { sdn: true }
>>and depending on that show the whole panel entries in datacenter section.
Ok, I'll have a look a this.
----- Mail original -----
De: "Thomas Lamprecht" <t.lampre...@proxmox.com>
À: "aderumier" <aderum...@odiso.com>
Cc: "pve-devel" <pve-devel@pve.proxmox.com>
Envoyé: Lundi 17 Février 2020 16:24:52
Objet: Re: [pve-devel] working on ifupdown2 openvswitch addon
On 2/17/20 4:13 PM, Alexandre DERUMIER wrote:
>>> As said, I'm open to integrate the gui also, with a "experimental" title
>>> and if only shown once pve-network is installed. This way you'd reach a
>>> lot more people open for testing easier, as it does not requires them to
>>> apply patches and build packages them self or download unsigned packages :)
>
> Yes :) I don't known if I could add some kind of api in pve-network package,
> to display or not the sdn section in datacenter ?
>
I'd maybe just hide it by default, and do a single api call on
GET /nodes/NODE/sdn
if this does not errors out (e.g., with "no such resource") then we know that
SDN is available and can save that in a PVE. object for caching, e.g.,:
PVE.FeatureInfo = { sdn: true }
and depending on that show the whole panel entries in datacenter section.
_______________________________________________
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
