----
To: Trey Morris From: Dan Wendlandt
Date: 05/30/2012 12:46AMCc: Yong Sheng Gong/China/IBM@IBMCN, netstack@lists.launchpad.netSubject: Re: [Netstack] About quantum api v2.0
On Tue, May 29, 2012 at 9:07 AM, Trey Morris <trey.mor...@rackspace.com> wrote:
Mr. Gong, we've go
allowed_address_pairs=pairs
> )
>
> Here we called two methods by webservice, It will cause:
> 1. transaction problem,
> They are not in one transaction context, So we have to be careful to maintain
> the consistency of our system.
>
> 2. performance.
>
Hi Dan and tr3buchet,I see some things in branch https://github.com/tr3buchet/nova/tree/quantum_api:1. compute manager is using a configurable network_api, i.e.self.network_api = utils.import_object(FLAGS.network_api_class)instead of self.network_api = network.API().I think, to use new quantum netw
On Tue, May 29, 2012 at 9:07 AM, Trey Morris wrote:
> Mr. Gong, we've got a lot of work going on in this area and it's rapidly
> changing at the moment. We've already written a new network manager that we
> use and I'm in the process of removing the network manager piece all
> together when using
Mr. Gong, we've got a lot of work going on in this area and it's rapidly
changing at the moment. We've already written a new network manager that we
use and I'm in the process of removing the network manager piece all
together when using nova with quantum. This work is planned for upstream as
a par
Hi,We have planned to replace quantum network manager in nova project with quantum api v2.0 calls.I have found that nova will call following 34 network api methods:class API(base.Base): # called in compute manager def get_instance_nw_info(self, context, instance): pass def add_
6 matches
Mail list logo
