Add support for communication channel to appliances
Today Nova enables to launch guests of different types. For real deployments we would need appliances from various vendors to run as instances. Appliances can be Loadbalancer, Firewall, IPsec, Routers or UTM etc.,
These appliances can be tied up with Neutron Services and would need configuration from various services like FWaaS, LBaaS, VPNaaS etc.,
One way to configure these appliances from Neutron Agents is by opening up the so needed virtio unix channel socket and reach the configuration daemon in the appliance.
Other approach is by having a separate network for management activities and having agent to communicate to a daemon in netns to reach out to appliance.
For us, it means additional daemon in the second approach. In case of first approach it is similar to Vmware way of configuring appliance.
Check this for reference http://
Blueprint information
- Status:
- Not started
- Approver:
- Russell Bryant
- Priority:
- Undefined
- Drafter:
- Ravi Chunduru
- Direction:
- Needs approval
- Assignee:
- balajipatnala
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Community working on other hypervisors like Xen, Hyper-V can also give comments/inputs on this BP, So that we can capture all the details in framework and collaborate.
Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)
