1a502b9151
Introduce the DataNetwork api, client, model to allow modelling of the
physical data network, with the following attributes:
datanetwork_name
mtu
datanetwork_type (flat, vlan, vxlan)
VxLAN specific attributes
- port_number
- multicast_group
- ttl
- mode ('dynamic' default, or 'static')
The system data network may then be assigned to interface.
This is part of the Story to "Move neutron provider network modelling
to system configuration".
The interface api is currently made compatible with current usage to
allow specifying datanetwork (formerly providernetwork).
The following new CLI commands and corresponding api are exposed:
datanetwork-add Add a datanetwork.
datanetwork-delete Delete a datanetwork.
datanetwork-list List datanetworks.
datanetwork-modify Modify a datanetwork.
datanetwork-show Show datanetwork details.
interface-datanetwork-assign
Assign a datanetwork to an interface.
interface-datanetwork-list
List datanetwork interfaces.
interface-datanetwork-remove
Remove an assigned datanetwork from an interface.
interface-datanetwork-show
Show interface datanetwork details.
'system datanetwork-add' must be run where
'neutron providernetwork-create'.
Tests Performed:
AIO Sanity
Sanity 2-controller, 2-compute
Sanity Storage lab
Interface Profile create and apply
Containers deployment
Change-Id: I630f90768647dbb414a60978bf8f8f641496afd5
Story: 2004455
Task: 28324
Signed-off-by: John Kung <john.kung@windriver.com>
|
||
|---|---|---|
| .. | ||
| cgtsclient | ||
| tools | ||
| .gitignore | ||
| .testr.conf | ||
| LICENSE | ||
| README.rst | ||
| pylint.rc | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||