+1 to Dash (Dan + Vish) :p Lean@mercadolibre On Mar 28, 2012 7:50 PM, "Dan Wendlandt" <[email protected]> wrote:
> > > On Wed, Mar 28, 2012 at 3:25 PM, Vishvananda Ishaya <[email protected] > > wrote: > >> >> >> So that explains where we are. Here is the plan (as I understand) for >> the future: >> >> a) move the quantum plugin to the api layer >> (At this point we could move validation into the api if necessary.) >> >> b) define a more complete network api which includes all of the necessary >> features that are currently compute extensions >> >> c) make a client to talk to the api >> >> d) make compute talk through the client to the api instead of using >> rabbit messages >> > > Agreed, this is what I've been thinking as well. Moving forward, > configuration of floating IPs would be done using the Quantum API. For > people who want to drive network config via Nova (e.g., using euca-api, or > using os-api extensions for backward compat), these calls would effectively > be proxied to Quantum. If someone using the proxied APIs make a request > that results in an error, the Quantum API would generate an error, and the > proxy would essentially pass this error on to the user. > > >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openstack >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> >> > > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Dan Wendlandt > Nicira Networks: www.nicira.com > twitter: danwendlandt > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
