Re: [ovs-dev] Neutron Container integration.

eal solution to implement for container support. Best, Aaron From: Gurucharan Shetty Sent: Wednesday, April 22, 2015 10:01 AM To: Thomas Graf Cc: Russell Bryant; dev; Aaron Rosen; Armando Migliaccio Subject: Re: [ovs-dev] Neutron Container inte

Re: [ovs-dev] Neutron Container integration.

> The connectivity test could include reaching a link local address > on the host bridge or even a remote endpoint. Listening to all the complications being involved over Neutron, using a IP address in the same logical network for connectivity test seems better. > > In theory this sounds more sca

Re: [ovs-dev] Neutron Container integration.

On 22 April 2015 at 08:27, Russell Bryant wrote: > On 04/22/2015 11:18 AM, Thomas Graf wrote: > > On 04/22/15 at 10:56am, Russell Bryant wrote: > >> Cool stuff. It looks like it will help. To be clear though, what I > >> think we need is an HTTP callback. Neutron needs to be able to notify > >

Re: [ovs-dev] Neutron Container integration.

On 04/22/2015 11:18 AM, Thomas Graf wrote: > On 04/22/15 at 10:56am, Russell Bryant wrote: >> Cool stuff. It looks like it will help. To be clear though, what I >> think we need is an HTTP callback. Neutron needs to be able to notify >> an arbitrary system instead of specifically Nova that a por

Re: [ovs-dev] Neutron Container integration.

On 04/22/15 at 10:56am, Russell Bryant wrote: > Cool stuff. It looks like it will help. To be clear though, what I > think we need is an HTTP callback. Neutron needs to be able to notify > an arbitrary system instead of specifically Nova that a port is ready. > > Another way to go about this wo

Re: [ovs-dev] Neutron Container integration.

On 04/22/2015 09:57 AM, Kyle Mestery wrote: > On Wed, Apr 22, 2015 at 8:28 AM, Russell Bryant > wrote: > > On 04/22/2015 09:21 AM, Salvatore Orlando wrote: > > Polling for port status is the easiest solution. > > In some cases excessive polling does not scal

Re: [ovs-dev] Neutron Container integration.

On Wed, Apr 22, 2015 at 8:28 AM, Russell Bryant wrote: > On 04/22/2015 09:21 AM, Salvatore Orlando wrote: > > Polling for port status is the easiest solution. > > In some cases excessive polling does not scale very well. > > For instance in large cloud with 1000s of compute nodes, this will put a

Re: [ovs-dev] Neutron Container integration.

On 04/22/2015 09:21 AM, Salvatore Orlando wrote: > Polling for port status is the easiest solution. > In some cases excessive polling does not scale very well. > For instance in large cloud with 1000s of compute nodes, this will put a > bit of a strain on the neutron server. > > This why Aaron a w

Re: [ovs-dev] Neutron Container integration.

Polling for port status is the easiest solution. In some cases excessive polling does not scale very well. For instance in large cloud with 1000s of compute nodes, this will put a bit of a strain on the neutron server. This why Aaron a while ago implemented [1] for interfacing neutron with nova. B

Re: [ovs-dev] Neutron Container integration.

> > I was expecting that once the port status made it up to Neutron from > OVN, that we would update the port state in the Neutron db, as well. > That would be reflected in the neutron API for getting the port details > that you reference. Yes, that would work. > > -- > Russell Bryant

Re: [ovs-dev] Neutron Container integration.

On 04/21/2015 08:49 PM, Gurucharan Shetty wrote: > 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 contai

Re: [ovs-dev] Neutron Container integration.

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 contai