-
Type: Story
-
Status: Closed (View Workflow)
-
Priority: Blocker
-
Resolution: Done
-
Affects Version/s: 1.7.0
-
Fix Version/s: 1.8.0
-
Component/s: None
-
Labels:
-
Story Points:3
-
Epic Link:
-
Sprint:Hummingbird sprint 3, Ibis Sprint 2 - Deployment
Currently VPLS doesn't have any CLI, even if the network interface configuration CLI might be used to change the configuration.
The new VPLS (currently WIP) assumes we will have this new configuration in the network-cfg.json file.
An example of the expected configuration is reported below.
The goal is to follow the model used in org.onosproject.bgprouter (ref of their config in the sdnip user-guide on the wiki).
There are already CLI commands to add, modify and remove interfaces.
What is missed and desired are the following commands:
- vpls-add-new-network NETWORK_NAME -> creates an empty network and gives it a name
- vpls-add-intf NETWORK_NAME INTF_NAME (we assume that interfaces must have a name!) -> adds an interface to an existing network
- vpls-del-intf NETWORK_NAME INTF_NAME -> deletes the interface INTF_NAME from an existing network
- vpls-list-networks -> returns the list of networks configured (empty or with interfaces). In this case just a list of network names is returned.
- vpls-show-network -> shows details about an existing network - basically the name of the network and the interfaces associated to it.
NETWORK CONFIG EXAMPLE:
{
"ports" : {
"of:0000000000000001/1" : {
"interfaces" : [
,
,
]
},
"of:0000000000000001/2" : {
"interfaces" : [
,
,
]
},
"of:0000000000000002/1" : {
"interfaces" : [
]
}
},
"apps" : {
"org.onosproject.vpls" : {
"networks": [
,
{ "name": "net2", "interfaces": ["inf3", "intf4", "intf5"] } ]
}
}
}