> -Original Message-
> From: Robert Collins [mailto:robe...@robertcollins.net]
> Sent: 10 January 2014 08:54
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [nova] where to expose network quota
>
> On 8 January 20
On 8 January 2014 03:01, Christopher Yeoh wrote:
> On Mon, Jan 6, 2014 at 4:47 PM, Yaguang Tang
...
>
> For the V3 API clients should access neutron directly for quota information.
> The V3 API will no longer proxy quota related information for neutron. Also
> novaclient will not get the quota in
On Mon, Jan 6, 2014 at 4:47 PM, Yaguang Tang wrote:
> Hi all,
>
> Now Neutron has its own quota management API for network related
> items(floating ips, security groups .etc) which are also manged by Nova.
> when using nova with neutron as network service, the network related quota
> items are st
On Jan 6, 2014, at 12:47 AM, Yaguang Tang wrote:
> Hi all,
>
> Now Neutron has its own quota management API for network related
> items(floating ips, security groups .etc) which are also manged by Nova.
> when using nova with neutron as network service, the network related quota
> items are
On 2014?01?06? 16:47, Yaguang Tang wrote:
Hi all,
Now Neutron has its own quota management API for network related
items(floating ips, security groups .etc) which are also manged by
Nova. when using nova with neutron as network service, the network
related quota items are stored in two diffe
Hi all,
Now Neutron has its own quota management API for network related
items(floating ips, security groups .etc) which are also manged by Nova.
when using nova with neutron as network service, the network related quota
items are stored in two different databases and managed by different APIs.
