- Related issues: #2841 [FEATURE] Reorganize the networkconfigs UI
Category:
- Network
Verification Steps
-
Go to Cluster Networks/Configs
-
Create a cluster network and provide the name
-
Create a Network Config
-
Given the NICs that not been used by mgmt-bo (eg.
ens1f1
)
-
Use default
active-backup
mode -
Check the cluster network config in
Active
status -
Go to Networks
-
Create a VLAN network
-
Given the name and vlan id
-
Select the cluster network from drop down list
-
Check the vlan route activity
-
Check the NIC
ens1f1
can bind to the cnetwork-boharvester-r2rpc:~ # ip a | grep cnetwork-bo 3: ens1f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master cnetwork-bo state UP group default qlen 1000 109: cnetwork-bo: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master cnetwork-br state UP group default qlen 1000
-
Delete the created VLAN network
-
Delete the network config from cluster network
-
Delete the cluster network
-
Create another cluster network
cnetwork2
without network config setup on it -
Go to create VLAN network page
-
Provide vlan name and id
-
Click the dropdown list and find the no config cluster network
Expected Results
-
Can create a new custom cluster network
-
Can create network config based on available NICs ( for non
mgmt-bo
) -
Can create VLAN network with valid id based on cluster network and config
-
Can create custom VLAN network and route correctly in
active
status -
Can delete created custom VLAN network
-
Can delete network config from cluster network
-
Can delete created cluster network
-
Cluster network without any network config will display with
Not ready
on the VLAN creation drop down list