Thanks for the headsup Matt.
On Wed, Mar 7, 2018 at 4:57 PM, Matt Riedemann wrote:
> I just wanted to give a heads up to anyone thinking about upgrading to
> queens that nova has released a 17.0.1 patch release [1].
>
> There are some pretty important fixes in there that came up after the
> quee
I just wanted to give a heads up to anyone thinking about upgrading to
queens that nova has released a 17.0.1 patch release [1].
There are some pretty important fixes in there that came up after the
queens GA so if you haven't upgraded yet, I recommend going straight to
that one instead of 17.
On 03/07/2018 10:44 AM, Tim Bell wrote:
I think nested quotas would give the same thing, i.e. you have a parent project
for the group and child projects for the users. This would not need user/group
quotas but continue with the ‘project owns resources’ approach.
Agreed, I think that if we suppo
I think nested quotas would give the same thing, i.e. you have a parent project
for the group and child projects for the users. This would not need user/group
quotas but continue with the ‘project owns resources’ approach.
It can be generalised to other use cases like the value add partner or th
This is certainly a feature will make Public Cloud providers very happy :)
On Thu, Mar 8, 2018 at 12:33 AM, Tim Bell wrote:
> Sorry, I remember more detail now... it was using the 'owner' of the VM as
> part of the policy rather than quota.
>
> Is there a per-user/per-group quota in Nova?
>
> Ti
Hi!
On Tuesday afternoon of the PTG week we had a track of discussions to
brainstorm how to better align our release cycle and stable branch
maintenance with the OpenStack downstream consumption models.
I posted a summary at:
http://lists.openstack.org/pipermail/openstack-dev/2018-March/128005.h
