Distributed datapath for metadata
When instances are booting, they will try to retrieve metadata from Nova by the path of Neutron virtual switches(bridges), virtual devices, namespaces and metadata-agents. After that, metadata agent has no other functionalities. In large-scale scenarios, a large number of deployed metadata agents will cause a waste of resources for hosts and message queue. Because metadata agents will start tons of external processes based on the number of users' resources, report state to Neutron server for keepalive.
We are going to implement an agent extension for Neutron openvswitch agent to make the metadata datapath distributed.
Blueprint information
- Status:
- Started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- LIU Yulong
- Direction:
- Needs approval
- Assignee:
- LIU Yulong
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Good progress
- Milestone target:
-
next
- Started by
- Rodolfo Alonso
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Approved RFE:
https:/
Approved spec:
https:/
Code series:
https:/
Gerrit topic: https:/
Addressed by: https:/
Add host metadata haproxy manager
Addressed by: https:/
Pass physical bridge informations to OVS agent extension API
Addressed by: https:/
Add basical functionalities for metadata path extension
Gerrit topic: https:/
Addressed by: https:/
Code move for metadata haproxy
Gerrit topic: https:/
Addressed by: https:/
Add metadata path extension openflows
Addressed by: https:/
Add devstack plugin to enable ovs metadata_path
