Re: [openstack-dev] [nova][neutron] VIF event callbacks implementation

2014-05-07 Thread Dan Smith
> I have additional concern that API is something that's user facing > so basically now Nova is exposing some internal synchronization > detail to the outside world. We have lots of admin-only APIs. > Does it make sense that the user would now be able to send messages > to this API? Potentially.

Re: [openstack-dev] [nova][neutron] VIF event callbacks implementation

2014-05-07 Thread Duncan Thomas
On 7 May 2014 13:04, Mike Kolesnik wrote: > - Original Message - >> Yeah, we've already got plans in place to get Cinder to use the >> interface to provide us more detailed information and eliminate some >> polling. We also have a very purpose-built notification scheme between >> nova and

Re: [openstack-dev] [nova][neutron] VIF event callbacks implementation

2014-05-07 Thread Mike Kolesnik
Hi, Sorry for late reply, please see replies inline. I have additional concern that API is something that's user facing so basically now Nova is exposing some internal synchronization detail to the outside world. Does it make sense that the user would now be able to send messages to this API? --

Re: [openstack-dev] [nova][neutron] VIF event callbacks implementation

2014-05-01 Thread Adam Gandelman
On Tue, Apr 29, 2014 at 12:23 PM, Dan Smith wrote: > > Yeah, we've already got plans in place to get Cinder to use the > interface to provide us more detailed information and eliminate some > polling. We also have a very purpose-built notification scheme between > nova and cinder that facilitates

Re: [openstack-dev] [nova][neutron] VIF event callbacks implementation

2014-05-01 Thread Duncan Thomas
On 29 April 2014 20:23, Dan Smith wrote: > Yeah, we've already got plans in place to get Cinder to use the > interface to provide us more detailed information and eliminate some > polling. We also have a very purpose-built notification scheme between > nova and cinder that facilitates a callback f

Re: [openstack-dev] [nova][neutron] VIF event callbacks implementation

2014-04-29 Thread Dan Smith
> Aside from creating a sort of cyclic dependency between the two, it > is my understanding that Neutron is meant to be a "stand alone" > service capable of being consumed by other compute managers (i.e. > oVirt). This breaks that paradigm. > So my question is: Why use API and not RPC? > > I

Re: [openstack-dev] [nova][neutron] VIF event callbacks implementation

2014-04-29 Thread Aaron Rosen
Hi Mike, Comments inline: On Mon, Apr 28, 2014 at 1:57 AM, Mike Kolesnik wrote: > Hi, > > I came across the implementation of > https://blueprints.launchpad.net/neutron/+spec/nova-event-callback > and have a question about the way it was implemented. > > I notice that now Neutron has a depende

[openstack-dev] [nova][neutron] VIF event callbacks implementation

2014-04-28 Thread Mike Kolesnik
Hi, I came across the implementation of https://blueprints.launchpad.net/neutron/+spec/nova-event-callback and have a question about the way it was implemented. I notice that now Neutron has a dependency on Nova and needs to be configured to have nova details (API endpoint, user, password, tena