Jump to: navigation, search

Difference between revisions of "Tacker/neutron-and-other-project-items"

Line 5: Line 5:
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
! Items !! contents !! requested by !! BP/assignee !! patch !! comment
+
! Items !! component !! contents !! requested by !! BP/assignee !! patch !! comment
 
|-
 
|-
 
| Disabling security group/anti-spoofing
 
| Disabling security group/anti-spoofing
 +
| Neutron
 
| Fix Security Groups to disable anti-spoofing mechanism to allow non VM IP/mac addresses in traffic from the Service VMs.
 
| Fix Security Groups to disable anti-spoofing mechanism to allow non VM IP/mac addresses in traffic from the Service VMs.
 
security group should be more flexible that allows the service VMs to spoof ip or MAC
 
security group should be more flexible that allows the service VMs to spoof ip or MAC
Line 17: Line 18:
 
|-
 
|-
 
| VM trunk port/l2-gateway support
 
| VM trunk port/l2-gateway support
 +
| Neutron
 
|  
 
|  
 
| Rick Masters, yisun, bmelande, hemanth.ravi
 
| Rick Masters, yisun, bmelande, hemanth.ravi
Line 24: Line 26:
 
|-
 
|-
 
| mulitple VIFs
 
| mulitple VIFs
 +
| Neutron
 
| multiple nova VM interface/VIFs on the same network with virtual MAC and VIP
 
| multiple nova VM interface/VIFs on the same network with virtual MAC and VIP
 
| hemanth.ravi, yisun, bmelande
 
| hemanth.ravi, yisun, bmelande
Line 31: Line 34:
 
|-
 
|-
 
| decouple vif creation/plugging
 
| 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  
 
| 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
 
| hemanth.ravi, bmelande
Line 38: Line 42:
 
|-
 
|-
 
| VM connecting to mulitple tenant
 
| VM connecting to mulitple tenant
 +
| Neutron
 
| allows same service VM instances to connect to the networks in different tenants
 
| allows same service VM instances to connect to the networks in different tenants
 
| yisun, natarajk
 
| yisun, natarajk
Line 45: Line 50:
 
|-
 
|-
 
| mgmt network interface on service vm
 
| 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.
 
| 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
 
| hemanth.rav
Line 52: Line 58:
 
|-
 
|-
 
| service insertion
 
| service insertion
 +
| Neutron
 
| service insertion with vm port, external port/traffic steering
 
| service insertion with vm port, external port/traffic steering
 
| bmelande
 
| bmelande
Line 59: Line 66:
 
|-
 
|-
 
| sharing mac/IP address
 
| sharing mac/IP address
 +
| Neutron
 
| share a (virtual) mac/IP address by multiple service VM instances or even the two ports on the same VM  
 
| share a (virtual) mac/IP address by multiple service VM instances or even the two ports on the same VM  
 
| bmelande
 
| bmelande
Line 66: Line 74:
 
|-
 
|-
 
| plugging driver
 
| plugging driver
 +
| Neutron/Nova?
 
|  
 
|  
 
| bmelande
 
| bmelande
Line 73: Line 82:
 
|-
 
|-
 
| oslo.messaging proxy
 
| oslo.messaging proxy
 +
| oslo.messaging
 
| implement oslo.messaging RPC proxy over Marconi with http proxy like instance metadata proxy
 
| implement oslo.messaging RPC proxy over Marconi with http proxy like instance metadata proxy
 
| yamahata
 
| yamahata

Revision as of 06:26, 3 June 2014

ServiceVM/Device manager https://wiki.openstack.org/wiki/ServiceVM

Items for other projects(Neutron, nova, oslo.messaging)

Items component contents requested by BP/assignee patch comment
Disabling security group/anti-spoofing Neutron Fix Security Groups to disable anti-spoofing mechanism to allow non VM IP/mac addresses in traffic from the Service VMs.

security group should be more flexible that allows the service VMs to spoof ip or MAC Ability to disable security groups on service VM port, at least ML2 OVS mechanism driver (e.g., by implementing the "port-security" extension

hemanth.ravi, masters, yisun, natarajk, bmelande
VM trunk port/l2-gateway support Neutron Rick Masters, yisun, bmelande, hemanth.ravi https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms, https://blueprints.launchpad.net/neutron/+spec/l2-gateway https://review.openstack.org/#/c/92541/
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
sharing mac/IP address Neutron share a (virtual) mac/IP address by multiple service VM instances or even the two ports on the same VM 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.