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&gt; 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 >

that is correct: project a seperate. think of them as mini virtual datacenters if you like have you tried to set up a GRE tunnel between the two projects? i recommend you search the internet for a good blog post or walkthrough. other than https://www.rdoproject.org/Using_GRE_Tenant_Networks i unfortunately do not have one i can recommend .also note that you will be doing fundamental changes to your networking if you go the GRE way however, if you have 2 separate teams why not have them communicate via the public ip? On Wed, Apr 29, 2015 at 7:46 PM, Steve Poe <steve.poe(a)gmail.com&gt; wrote: > 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&gt; 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 >>> >> > -- <https://candidate.peoplecert.org/ReportsLink.aspx?argType=1&id=13D642... *805010942448935* <https://www.redhat.com/wapps/training/certification/verify.html?certNumbe... *GR750055912MA* <https://candidate.peoplecert.org/ReportsLink.aspx?argType=1&id=13D642... *Link to me on LinkedIn <http://www.linkedin.com/in/mohammedarafa>*

On 04/29/2015 04:24 PM, Steve Poe 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 > Have you tried creating a shared network? I haven't tried to share a network between projects, but this works for creating one network that multiple tenants can use: neutron net-create --shared my-network You would need to run that with admin credentials. Please let the list know if this works for you. -- Dan Sneddon | Principal OpenStack Engineer dsneddon(a)redhat.com | redhat.com/openstack 650.254.4025 | dsneddon:irc @dxs:twitter _______________________________________________ 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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/29/2015 05:18 PM, Steve Poe wrote: > I'll try it again, but the shared network did not seem to help > me. Maybe a little pseudo example of adding projects DevTeamA and > DevTeamB to your "my-network" would help me? I understand you > don't have the tenat-ids but let's assume id: 1234 for DevTeamA > and tenant-id for 5678. Feel free to fill-in the pieces if my > logic is off. > > Thanks. > > Steve > > > On Wed, Apr 29, 2015 at 5:10 PM, Dan Sneddon <dsneddon(a)redhat.com > <mailto:dsneddon@redhat.com>> wrote: > > On 04/29/2015 04:24 PM, Steve Poe 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 >> > > Have you tried creating a shared network? I haven't tried to share > a network between projects, but this works for creating one > network that multiple tenants can use: > > neutron net-create --shared my-network > > You would need to run that with admin credentials. Please let the > list know if this works for you. > > -- Dan Sneddon | Principal OpenStack Engineer > dsneddon(a)redhat.com <mailto:dsneddon@redhat.com> | > redhat.com/openstack <http://redhat.com/openstack> 650.254.4025 > <tel:650.254.4025> | dsneddon:irc @dxs:twitter > If the shared networks in Neutron work the way I think they do, then you don't have to associate the project with the network. A shared network should appear for all tenants and all projects. - -- Dan Sneddon | Principal OpenStack Engineer dsneddon(a)redhat.com | redhat.com/openstack 650.254.4025 | dsneddon:irc @dxs:twitter