Why wouldn't you separate you dev/test/productiion via tenants as well? That's what we encourage our users to do. This would let you create flavors that give dev/test less resources under exhaustion conditions and production more resources. You could even pin dev/test to specific hypervisors/areas of the cloud and let production have the rest via those flavors. ____________________________________________
Kris Lindgren Senior Linux Systems Engineer GoDaddy, LLC. From: Daniel Comnea <[email protected]<mailto:[email protected]>> Date: Wednesday, April 8, 2015 at 3:32 AM To: Daniel Comnea <[email protected]<mailto:[email protected]>> Cc: "OpenStack Development Mailing List (not for usage questions)" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [Openstack-operators] [Openstack-dev] resource quotas limit per stacks within a project + operators Hard to believe nobody is facing this problems, even on small shops you end up with multiple stacks part of the same tenant/ project. Thanks, Dani On Wed, Apr 1, 2015 at 8:10 PM, Daniel Comnea <[email protected]<mailto:[email protected]>> wrote: Any ideas/ thoughts please? In VMware world is basically the same feature provided by the resource pool. Thanks, Dani On Tue, Mar 31, 2015 at 10:37 PM, Daniel Comnea <[email protected]<mailto:[email protected]>> wrote: Hi all, I'm trying to understand what options i have for the below use case... Having multiple stacks (various number of instances) deployed within 1 Openstack project (tenant), how can i guarantee that there will be no race after the project resources. E.g - say i have few stacks like stack 1 = production stack 2 = development stack 3 = integration i don't want to be in a situation where stack 3 (because of a need to run some heavy tests) will use all of the resources for a short while while production will suffer from it. Any ideas? Thanks, Dani P.S - i'm aware of the heavy work being put into improving the quotas or the CPU pinning however that is at the project level
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
