Take full network details (addresses, bounds etc.) from the network_data.json file first, then fallback to network_config content
Due to blueprint and patches related here: https:/
This way, the baseopenstack metadata service will be updated to handle such new JSON information, if present, usually found into the "network_data.json" (like meta_data and vendor_data), thing which will be included for sure into the Liberty OpenStack freeze. Missing information (or extra if any) will be taken using the old method: by parsing the debian-like content addressed by the network_config file path.
The second part of this blueprint will cover the extra configuration due to such new/extra found networking information (ex. NICs bounds) through new utilities and additional calls in the networkconfig plugin (features).
First, take and adapt all the content found and parsed in the JSON form and if is not present, then fall back to the network_config content. Only if special cases are discovered and required, then check and merge both of the possiblities.
Blueprint information
- Status:
- Complete
- Approver:
- Alessandro Pilotti
- Priority:
- Medium
- Drafter:
- Cosmin Poieana
- Direction:
- Approved
- Assignee:
- Alessandro Pilotti
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Alessandro Pilotti
- Completed by
- Alessandro Pilotti
Related branches
Related bugs
Sprints
Whiteboard
From Alessandro:
1. The new format supersedes the old "interfaces" template one, so the metadata provider can transparently deal with this passing the data to the plugin in the current way (with additional info of course). The actual data structure returned by the metadata provider can be refactored.
2. Important features that will be added here: teamed interfaces, VLAN
Gerrit topic: https:/
Addressed by: https:/
Add a new layer of abstractization over the network metadata
Addressed by: https:/
Update the processing of the network information in metadata services
Addressed by: https:/
Add support for MAAS json network metadata
Addressed by: https:/
Add support for OpenStack json network metadata
Addressed by: https:/
Add network details builder for the Open Nebula service
Addressed by: https:/
Update the processing of the network information
Addressed by: https:/
Add base data model in order to improve data representation
Addressed by: https:/
Added advanced networking structure
Addressed by: https:/
Added base L2/L3 network implementation
Addressed by: https:/
Added base L4 network implementation
Addressed by: https:/
Use new network data structures for Openstack and NetworkConfigPlugin
Gerrit topic: https:/
Addressed by: https:/
Move NetworkDetails to a separate module
Addressed by: https:/
Add new networking model
Addressed by: https:/
Return NetConnectionID instead of Name
Addressed by: https:/
Add rename_
Addressed by: https:/
Use the interface name when setting the MTU
Addressed by: https:/
Add PyMI as requirement
Addressed by: https:/
Add get_network_
Addressed by: https:/
Add NetLBFO network teaming
Addressed by: https:/
Use MSFT_NetIPAddress in static network config
Addressed by: https:/
Support get_network_
Addressed by: https:/
Add get_network_
Gerrit topic: https:/
Addressed by: https:/
Include the NIC names in get_dhcp_
Addressed by: https:/
Add get_network_
Addressed by: https:/
Add enable_
Work Items
Dependency tree
* Blueprints in grey have been implemented.
