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

Latest revision as of 17:20, 29 May 2015

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	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

@@ Line 1: / Line 1: @@
 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)
 {| class="wikitable"
 |-
-! Items !! contents !! requested by !! BP/assignee !! patch !! comment
+! Items !! component !! contents !! requested by !! BP/assignee !! patch !! comment
-|-
-| Disabling security group/anti-spoofing
-| 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
-|
-| 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
@@ Line 31: / Line 17: @@
 |-
 | 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
@@ Line 38: / Line 25: @@
 |-
 | VM connecting to mulitple tenant
+| Neutron
 | allows same service VM instances to connect to the networks in different tenants
 | yisun, natarajk
@@ Line 45: / Line 33: @@
 |-
 | 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
@@ Line 52: / Line 41: @@
 |-
 | service insertion
+| Neutron
 | service insertion with vm port, external port/traffic steering
-| bmelande
-|
-|
-|
-|-
-| sharing mac/IP address
-| share a (virtual) mac/IP address by multiple service VM instances or even the two ports on the same VM
 | bmelande
 |
@@ Line 66: / Line 49: @@
 |-
 | plugging driver
+| Neutron/Nova?
 |
 | bmelande
@@ Line 71: / Line 55: @@
 |
 |
-|-
-| oslo.messaging proxy
-| 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.
 |}