I'm also interested in providing multiple floating IP pools. Is this something that is achievable or conceived?
My use case is as follows: Each tenant gets its own private VLAN and address space, so intercommunication between each tenant is able to be segregated. On assignment of public floating IPs though this segregation breaks down. To put this into context, I'd like to be able to have, say, a "Production" tenant and a "Development" tenant. Inter-communication between the two should be prohibited. As soon as I assign a floating IP address, this model breaks down. I noticed that nova-manage floating create has a ' --pool=<pool> Optional pool ' option. How is this used? Does this help solve my problem? Cheers, Kev On 6 February 2012 18:46, Xu (Simon) Chen <xche...@gmail.com> wrote: > Hi all, > > I am running devstack and got a dev instance of OpenStack running. > > I am happy to see the concept of multiple floating IP pools, and the > per-floating-ip interface in the trunk, which I consider a very good basis > for my blueprint proposal here: > https://blueprints.launchpad.net/nova/+spec/multi-network-without-multi-nic > > I have a quick question. Is there a plan (or maybe it's already there) for > access control whether a project is allowed to take floating IPs from a > pool? > > Thanks! > -Simon > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > -- Kevin Jackson @itarchitectkev
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
