Re: [Rdo-list] OpenStack Juno: best way to implement quotas?
Mohammed,
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.
Steve
On Wed, Apr 29, 2015 at 4:29 PM, Mohammed Arafa <mohammed.arafa(a)gmail.com>
wrote:
Unless I am missing something that sounds like the perfect use case
for
quotas.
Project Quotas are on virtual resources like cpu ram and storage
On Apr 29, 2015 7:26 PM, "Steve Poe" <steve.poe(a)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?
>
> Thanks.
>
> Steve
>
>
> _______________________________________________
> Rdo-list mailing list
> Rdo-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
>
> To unsubscribe: rdo-list-unsubscribe(a)redhat.com
>
Attachments:
- attachment.html (text/html — 2.5 KB)