so, we can reference other platform-level services (like Trove and
>> Sahara) to see if they implemented an extra layer of quota management
>> system, and we could use it as a decision point.
>>
>>
>>
>> Best regards,
>>
>> Honbgin
>>
>>
>>
uota management
> system, and we could use it as a decision point.
>
>
>
> Best regards,
>
> Honbgin
>
>
>
> *From:* Adrian Otto [mailto:adrian.o...@rackspace.com]
> *Sent:* December-20-15 12:50 PM
> *To:* OpenStack Development Mailing List (not for usage questions)
ment system, and we could
use it as a decision point.
Best regards,
Honbgin
From: Adrian Otto [mailto:adrian.o...@rackspace.com]
Sent: December-20-15 12:50 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resour
Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources
Thanks Adrian and Tim, I saw that @Vilobh already uploaded a patch
https://review.openstack.org/#/c/259201/ here, perhaps we can first have a spec
and discuss there. ;-)
On Mon, Dec
a great help for operators.
>
>
>
> Tim
>
>
>
> *From:* Adrian Otto [mailto:adrian.o...@rackspace.com]
> *Sent:* 20 December 2015 18:50
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
>
error scenarios and
appropriate testing+documentation would be a great help for operators.
Tim
From: Adrian Otto [mailto:adrian.o...@rackspace.com]
Sent: 20 December 2015 18:50
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack][magn
;>
Subject: Re: [openstack-dev] [openstack][magnum] Quota for Magnum
Resources
Hi! Can I offer a counter point?
Quotas are for _real_ resources.
The CERN container specialist agrees with you ... it would be good to
reflect on the needs given that ironic, neutron and nova are policing the
gt; Lee
>
> On Dec 16, 2015, at 1:56 PM, Tim Bell wrote:
>
> -Original Message-
> From: Clint Byrum [mailto:cl...@fewbar.com ]
> Sent: 15 December 2015 22:40
> To: openstack-dev
> Subject: Re: [openstack-dev] [openstack][magnum] Quota for Magnum
> Resour
Excerpts from Adrian Otto's message of 2015-12-16 16:56:39 -0800:
> Clint,
>
> I think you are categorically dismissing a very real ops challenge of how to
> set correct system limits, and how to adjust them in a running system. I have
> been stung by this challenge repeatedly over the years. As
Clint,
I think you are categorically dismissing a very real ops challenge of how to
set correct system limits, and how to adjust them in a running system. I have
been stung by this challenge repeatedly over the years. As developers we
*guess* at what a sensible default for a value will be for a
esday, December 16, 2015 4:21 PM
To: openstack-dev
Subject: Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources
Excerpts from Fox, Kevin M's message of 2015-12-16 16:05:29 -0800:
> Yeah, as an op, I've run into a few things that need quota's that just have
> basi
Excerpts from Fox, Kevin M's message of 2015-12-16 16:05:29 -0800:
> Yeah, as an op, I've run into a few things that need quota's that just have
> basically hardcoded values. heat stacks for example. its a single global in
> /etc/heat/heat.conf:max_stacks_per_tenant=100. Instead of being able to
lopment Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources
On Dec 16, 2015, at 2:25 PM, James Bottomley
mailto:james.bottom...@hansenpartnership.com>>
wrote:
On Wed, 2015-12-16 at 20:35 +, Adrian Otto wrote:
Clint,
On Dec 16,
015 22:40
> >> To: openstack-dev
> >> Subject: Re: [openstack-dev] [openstack][magnum] Quota for Magnum
> >> Resources
> >>
> >> Hi! Can I offer a counter point?
> >>
> >> Quotas are for _real_ resources.
>
> No. Beyond billable resour
Dec 16, 2015, at 11:56 AM, Tim Bell tim.b...@cern.ch>> wrote:
>
> -Original Message-
> From: Clint Byrum [mailto:cl...@fewbar.com]
> Sent: 15 December 2015 22:40
> To: openstack-dev openstack-dev@lists.openstack.org>>
> Subject: Re: [openstack-dev] [openstack]
m [mailto:cl...@fewbar.com]
Sent: 15 December 2015 22:40
To: openstack-dev
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [openstack][magnum] Quota for Magnum
Resources
Hi! Can I offer a counter point?
Quotas are for _real_ resources.
No. Beyond billable resou
; To: openstack-dev
> > > Subject: Re: [openstack-dev] [openstack][magnum] Quota for Magnum
> > > Resources
> > >
> > > Hi! Can I offer a counter point?
> > >
> > > Quotas are for _real_ resources.
>
> No. Beyond billable resources
Excerpts from Fox, Kevin M's message of 2015-12-16 12:19:59 -0800:
> keypairs are real though. they consume database resource at the moment. You
> don't want a user blowing out your db. Quota's should be for things that ops
> will get sad over, if the users consume too many of them.
>
Limit ev
Clint,
> On Dec 16, 2015, at 11:56 AM, Tim Bell wrote:
>
>> -Original Message-
>> From: Clint Byrum [mailto:cl...@fewbar.com]
>> Sent: 15 December 2015 22:40
>> To: openstack-dev
>> Subject: Re: [openstack-dev] [openstack][magnum] Quota for Magnum
&
of them.
>
> Thanks,
> Kevin
>
> From: Tim Bell [tim.b...@cern.ch]
> Sent: Wednesday, December 16, 2015 11:56 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [openstack][magnum] Q
ell [tim.b...@cern.ch]
Sent: Wednesday, December 16, 2015 11:56 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources
> -Original Message-
> From: Clint Byrum [mailto:cl...@fewbar.com]
> Sent: 15
015 22:40
>> To: openstack-dev > <mailto:openstack-dev@lists.openstack.org>>
>> Subject: Re: [openstack-dev] [openstack][magnum] Quota for Magnum
>> Resources
>>
>> Hi! Can I offer a counter point?
>>
>> Quotas are for _real_ resources.
>>
>
> Th
> -Original Message-
> From: Clint Byrum [mailto:cl...@fewbar.com]
> Sent: 15 December 2015 22:40
> To: openstack-dev
> Subject: Re: [openstack-dev] [openstack][magnum] Quota for Magnum
> Resources
>
> Hi! Can I offer a counter point?
>
> Quotas are for
Hi! Can I offer a counter point?
Quotas are for _real_ resources.
Memory, CPU, disk, bandwidth. These are all _closely_ tied to things
that cost real money and cannot be conjured from thin air. As such, the
user being able to allocate 1 billion or 2 containers is not limited by
Magnum, but by rea
"OpenStack Mailing List (not for usage questions)"
mailto:openst...@lists.openstack.org>>, Belmiro
Moreira mailto:belmiro.more...@cern.ch>>
Subject: Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources
IMHO for Magnum and Nested Quota we need more discussio
enStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Cc:* OpenStack Mailing List (not for usage questions) <
> openst...@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [openstack][magnum] Quota for Magnum
> Resources
questions)
Cc: OpenStack Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources
Vilobh,
Thanks for advancing this important topic. I took a look at what Tim referenced
how Nova is implementing nested quotas, and it seems to me
Vilobh,
Thanks for advancing this important topic. I took a look at what Tim referenced
how Nova is implementing nested quotas, and it seems to me that’s something we
could fold in as well to our design. Do you agree?
Adrian
On Dec 14, 2015, at 10:22 PM, Tim Bell
mailto:tim.b...@cern.ch>> wro
Can we have nested project quotas in from the beginning ? Nested projects are
in Keystone V3 from Kilo onwards and retrofitting this is hard work.
For details, see the Nova functions at
https://review.openstack.org/#/c/242626/. Cinder now also has similar
functions.
Tim
From: Vilobh Mes
29 matches
Mail list logo
