[pve-devel] [PATCH v2 pve-network 04/15] update documentation.txt
Alexandre Derumier
aderumier at odiso.com
Tue Nov 26 10:00:19 CET 2019
Signed-off-by: Alexandre Derumier <aderumier at odiso.com>
---
test/documentation.txt | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/test/documentation.txt b/test/documentation.txt
index 3f70987..8b78d46 100644
--- a/test/documentation.txt
+++ b/test/documentation.txt
@@ -2,31 +2,31 @@ Here a sample of command with pvesh to manage the sdn.
#create a vlan transportzone
-pvesh create /cluster/sdn/ --sdn vlanzone --type vlan --uplink-id 1
+pvesh create /cluster/sdn/zones/ --zone vlanzone --type vlan --uplink-id 1
#create a layer2 vxlan multicast transportzone
-pvesh create /cluster/sdn/ --sdn vxlanmulticastzone --type vxlan --uplink-id 1 --multicast-address 239.192.114.23
+pvesh create /cluster/sdn/zones/ --zone vxlanmulticastzone --type vxlan --uplink-id 1 --multicast-address 239.192.114.23
#create a layer2 vxlan unicast transportzone
-pvesh create /cluster/sdn/ --sdn vxlanunicastzone --type vxlan --uplink-id 1 --unicast-address 192.168.0.1,192.168.0.2,192.168.0.3
+pvesh create /cluster/sdn/zones/ --zone vxlanunicastzone --type vxlan --uplink-id 1 --unicast-address 192.168.0.1,192.168.0.2,192.168.0.3
#create an controller
-pvesh create /cluster/sdn/ --sdn frrrouter1 --type evpncontroller --uplink-id 1 --peers 192.168.0.1,192.168.0.2,192.168.0.3 --asn 1234 --gateway-nodes pxnode1,pxnode2 --gateway-external-peers 192.168.0.253,192.168.0.254
+pvesh create /cluster/sdn/controllers/ --controller frrrouter1 --type frrevpn --uplink-id 1 --peers 192.168.0.1,192.168.0.2,192.168.0.3 --asn 1234 --gateway-nodes pxnode1,pxnode2 --gateway-external-peers 192.168.0.253,192.168.0.254
#create a layer2 vxlan bgpevpn transportzone
-pvesh create /cluster/sdn/ --sdn layer2evpnzone --type evpn --uplink-id 1 --controller frrrouter1
+pvesh create /cluster/sdn/zones/ --zone layer2evpnzone --type evpn --uplink-id 1 --controller frrrouter1
#create a layer3 routable vxlan bgpevpn transportzone
-pvesh create /cluster/sdn/ --sdn layer3evpnzone --type evpn --uplink-id 1 --controller frrrouter1 --vrf vrf1 --vrf-vxlan 4000
+pvesh create /cluster/sdn/zones/ --zone layer3evpnzone --type evpn --uplink-id 1 --controller frrrouter1 --vrf vrf1 --vrf-vxlan 4000
#create a vnet in the transportzone
-pvesh create /cluster/sdn/ --sdn vnet10 --type vnet --transportzone vlanzone --tag 10
+pvesh create /cluster/sdn/vnets/ --vnet vnet10 --type vnet --transportzone vlanzone --tag 10
#create a vnet in the transportzone with ip for evpn routing
-pvesh create /cluster/sdn/ --sdn vnet11 --type vnet --transportzone layer3evpnzone --tag 11 --ipv4 10.0.0.1/24 --mac c8:1f:66:f8:62:8d
-pvesh create /cluster/sdn/ --sdn vnet12 --type vnet --transportzone layer3evpnzone --tag 12 --ipv4 10.0.1.1/24 --mac c8:1f:66:f8:62:8e
+pvesh create /cluster/sdn/vnets/ --vnet vnet11 --type vnet --transportzone layer3evpnzone --tag 11 --ipv4 10.0.0.1/24 --mac c8:1f:66:f8:62:8d
+pvesh create /cluster/sdn/vnets/ --vnet vnet12 --type vnet --transportzone layer3evpnzone --tag 12 --ipv4 10.0.1.1/24 --mac c8:1f:66:f8:62:8e
#apply changes from /etc/pve/sdn.cfg.new to /etc/pve/sdn.cfg
@@ -53,7 +53,7 @@ display transporzone status on all cluster nodes
#list all transport zones of a node
-pvesh get /nodes/<node>/sdn/
+pvesh get /nodes/<node>/sdn/zones/
┌─────────────────┬───────────┐
│ sdn │ status │
├─────────────────┼───────────┤
@@ -67,7 +67,7 @@ pvesh get /nodes/<node>/sdn/
#list all vnet status from a node transportzone
-pveset get /nodes/<node>/sdn/<transportzone>/content
+pveset get /nodes/<node>/sdn/zones/<transportzone>/content
┌─────────┬────────┐
│ vnet │ status │
--
2.20.1
More information about the pve-devel
mailing list