nsx_edge¶
NSX Management API — edge nodes.
Edge NODES are individual transport nodes of type EdgeNode (as opposed to
saltext.vcf.clients.nsx_edge_cluster, which manages the containing
CLUSTERS). Edge nodes are managed through the shared transport-node API
(/api/v1/transport-nodes) filtered on node_types=EdgeNode.
Single-node reads (get / get_or_none) delegate to
saltext.vcf.clients.nsx_transport_node so the 404 handling and endpoint
shape stay in one place. Only the edge-specific behaviour lives here:
list_ (adds the node_types=EdgeNode filter), write endpoints
(create/update/delete — transport_node has no CRUD), plus
redeploy / state / cluster_allocation_status.
- saltext.vcf.clients.nsx_edge.list_(opts, profile=None)[source]¶
List all edge transport nodes (
node_types=EdgeNode).
- saltext.vcf.clients.nsx_edge.get(opts, node_id, profile=None)[source]¶
Get a single edge transport node by id.
- saltext.vcf.clients.nsx_edge.get_or_none(opts, node_id, profile=None)[source]¶
Return the edge node, or
Noneif the API responds 404.
- saltext.vcf.clients.nsx_edge.create(opts, body, profile=None)[source]¶
Create an edge transport node. body is the TransportNode spec dict.
- saltext.vcf.clients.nsx_edge.update(opts, node_id, body, profile=None)[source]¶
Update an existing edge transport node.
- saltext.vcf.clients.nsx_edge.delete(opts, node_id, profile=None)[source]¶
Delete an edge transport node.
- saltext.vcf.clients.nsx_edge.redeploy(opts, node_id, body=None, profile=None)[source]¶
Redeploy an edge transport node (POST with
?action=redeploy).