[ovs-dev] Neutron Container integration.

[Gurucharan Shetty]

Adding ovs-dev.

One design decision that I would like to be discussed for OVN
integration with Containers and OpenStack is - how does a container
plugin in the VM know that OVN has completed the wiring and that it is
OK to let the container application start. A straight forward way from
the container plugin's point of view is to call a "neutron port-show".
If this command could query the details from the OVN plugin, then the
container plugin could simply poll for the data to be ready.

Aaron,
Does that look feasible?



On Tue, Apr 21, 2015 at 4:47 PM, Russell Bryant <rbryant at redhat.com> wrote:
> Thanks for checking in.
>
> I have a python-neutronclient patch and 2 patches to networking-ovn.  It
> should be close to done.  I need to finish testing and fix whatever I
> missed.  Here are the 3 patches I have in flight:
>
>   https://review.openstack.org/#/c/174098/
>
> and the top 2 patches here:
>
>   https://github.com/russellb/networking-ovn/commits/containers
>
> If you have ideas on a different way to accomplish it, I'd be interested
> to hear it.  I went with an approach that didn't require any changes to
> Neutron to get it working without having to get held up by Neutron.  See
> the commit messages and such for more detail.  I'd be interested in a
> more general and official API approach longer term, though.
>
> Regarding coordination and avoiding overlap of work, I'd prefer to avoid
> private emails like this.  We've got a few places where coordination has
> been happening:
>
> 1) ovs-dev mailing list for OVN itself
>
> 2) #openstack-neutron-ovn and the openstack-dev mailing list for the
> Neutron integration
>
> 3) A weekly IRC meeting in #openvswitch to cover both OVN and the
> Neutron integration.
>
> We've also got a TODO document for the Neutron integration where I've
> been trying to keep record of who was working on which pieces:
>
> http://git.openstack.org/cgit/stackforge/networking-ovn/tree/doc/source/todo.rst
>
> --
> Russell Bryant
>
> On 04/21/2015 06:34 PM, Aaron Rosen wrote:
>> Hi Russell,
>>
>> Yup, I was planning on integrating the work that Guru has done in OVN to interface that with neutron. I'm planning on writing up a spec on this based on: http://openvswitch.org/pipermail/dev/2015-March/052060.html which I see you have reviewed.
>>
>> I believe to support this in neutron the easiest route will be to leverage the port_bindings extension that neutron already has in order to specify the parent_name (neutron port_id of vm that docker container is running on top of) and tag  (vlan tag that a containers traffic will be sent out on and ovs in the hypervisor will know which virtual network to put that traffic on) which ovn needs.
>>
>> Let me know if you've already started working on this. Otherwise I'm hoping to have a patch for this up on review before the end of the week.
>>
>> Best,
>>
>> Aaron
>>
>> ________________________________________
>> From: Gurucharan Shetty <shettyg at nicira.com>
>> Sent: Tuesday, April 21, 2015 1:56 PM
>> To: Russell Bryant; Aaron Rosen; Salvatore Orlando
>> Subject: Neutron Container integration.
>>
>> Hello Russell,
>>  I saw in your blog post at [1] that you are working on getting
>> changes done in Neutron for containers too. Aaron was planning to work
>> on it this week. So to avoid duplicated effort, I thought it is best
>> to get in sync here to know the design.
>>
>> About the UP state of the logical port, I was thinking that we should
>> somehow be able to query that from the container VM. I was thinking
>> that we should get this information by running 'neutron port-show''s
>> 'status' column (or a new column, if 'status' has some other
>> meaning.).
>>
>> About the container network plugin, I am working to create a piece for
>> both docker and rkt.
>>
>>
>> [1]: https://urldefense.proofpoint.com/v2/url?u=http-3A__blog.russellbryant.net_2015_04_21_ovn-2Dand-2Dopenstack-2Dstatus-2D2015-2D04-2D21_&d=AwIBaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=hwWOe6tnWamV5Up5MRhjgrrG84KhriNQORyVOM1w8AM&m=JXTcE6lUMlFeFIfnY-KAWS8ler42qj6_KRQ7GCoH4MI&s=xoPtVcay4zChTz3Yp4zUyoZMRYqngWNo3l37z8CFbzI&e=
>>
>>
>> Thanks,
>> Guru
>>
>