[Rdo-list] OpenStack Juno: best way to implement quotas?
steve.poe at gmail.com
Wed Apr 29 23:46:28 UTC 2015
I think so too, but when I create a new projects (DevTeam_A and DevTeam B),
I cannot figure it out how to create one network that both will use. I
maybe smart enough to route myself into a corner (pun intended). When login
as admin, go to Networking, and try associate a new project to the same
network name that is shared.
On Wed, Apr 29, 2015 at 4:29 PM, Mohammed Arafa <mohammed.arafa at gmail.com>
> Unless I am missing something that sounds like the perfect use case for
> Project Quotas are on virtual resources like cpu ram and storage
> On Apr 29, 2015 7:26 PM, "Steve Poe" <steve.poe at gmail.com> wrote:
>> My colleagues and I are looking at using OpenStack Juno internally using
>> in various install methods (pre-packaged enterprise offering, manual via
>> packages, etc. I picked RDO. I am responsible for evaluating quota usage.
>> We'll have different development teams using our environment in one
>> network. Each development team may have their own project where quotas can
>> be adjusted when necessary. However, each project/tenant gets its own
>> network. I wish I could associate multiple projects with one network.
>> I was hoping to use projects in managing/implementing quotas (instances,
>> cores, ram, storage, etc.) for the dev teams, but maybe I am approaching
>> incorrectly. Any suggestions?
>> Rdo-list mailing list
>> Rdo-list at redhat.com
>> To unsubscribe: rdo-list-unsubscribe at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dev