Difference between revisions of "Tacker/neutron-and-other-project-items"
< Tacker
Line 7: | Line 7: | ||
|- | |- | ||
! Items !! component !! contents !! requested by !! BP/assignee !! patch !! comment | ! Items !! component !! contents !! requested by !! BP/assignee !! patch !! comment | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
| mulitple VIFs | | mulitple VIFs | ||
Line 61: | Line 43: | ||
| Neutron | | Neutron | ||
| service insertion with vm port, external port/traffic steering | | service insertion with vm port, external port/traffic steering | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
| bmelande | | bmelande | ||
| | | |
Revision as of 06:28, 11 June 2014
ServiceVM/Device manager https://wiki.openstack.org/wiki/ServiceVM For neutron port related things, please refer to https://wiki.openstack.org/wiki/ServiceVM/neutron-port-attributes
Items for other projects(Neutron, nova, oslo.messaging)
Items | component | contents | requested by | BP/assignee | patch | comment |
---|---|---|---|---|---|---|
mulitple VIFs | Neutron | multiple nova VM interface/VIFs on the same network with virtual MAC and VIP | hemanth.ravi, yisun, bmelande | |||
decouple vif creation/plugging | Nova? | Capability to decouple the following 2 operations: a. creation of interface on a VM and b. plugging of the interface into a neutron network | hemanth.ravi, bmelande | |||
VM connecting to mulitple tenant | Neutron | allows same service VM instances to connect to the networks in different tenants | yisun, natarajk | |||
mgmt network interface on service vm | Neutron | Mgmt Network interface on Service VM to manage the VM. The mgmt network needs to be visible to both Agents running on the OS mgmt network as well as potentially be exposed to tenant networks. | hemanth.rav | The assumed deployment is not clear. Can VMs/services be trusted? If yes, provider network that is connected to OpenStack mgmt network can be used. If no, oslo.messaging proxy approach is needed | ||
service insertion | Neutron | service insertion with vm port, external port/traffic steering | bmelande | |||
plugging driver | Neutron/Nova? | bmelande | ||||
oslo.messaging proxy | oslo.messaging | implement oslo.messaging RPC proxy over Marconi with http proxy like instance metadata proxy | yamahata | https://blueprints.launchpad.net/oslo.messaging/+spec/message-proxy-server | discussed in Atlanta. |