Re: [Openstack] Provider networks and manual ip management

2013-02-13 Thread tra26
Alright so the proposed patch (on the abandoned review) doesn't fix the problem either, so I guess I take a look at Grizzly. If I were to want to test this out is Grizzly is the best option to just grab the code from git and deploy it that way or is there a snapshot that passes the tests? Basicall

Re: [Openstack] Provider networks and manual ip management

2013-02-11 Thread tra26
Salvatore, Thanks for your reply, ok that makes sense. I tried to create the network without a subnet and as the bug (https://bugs.launchpad.net/nova/+bug/1039665) lists it brings it up with no vif. I will just put a shim in or something and see if that solves my problem (assign a random ip) since

Re: [Openstack] Provider networks and manual ip management

2013-02-11 Thread Robert Kukura
On 02/08/2013 10:14 AM, tr...@cs.drexel.edu wrote: > Anyone? I haven't tried this myself, but, before booting the instance, you should be able create the port, passing the desired IP on the subnet as fixed_ips. Then pass this port's ID to nova when you boot the instance. You may also want to speci

Re: [Openstack] Provider networks and manual ip management

2013-02-10 Thread Salvatore Orlando
Hi Trevor, sorry for the delay in the response. It seems you want a L2-only network. In theory, all you should do to achieve this is to not create a subnet on your network. Disabling DHCP on the subnet won't make any difference, since the --enable-dhcp option only controls the IP address delivery

Re: [Openstack] Provider networks and manual ip management

2013-02-08 Thread tra26
Anyone? Thanks, -Trevor > Again, is there a better place to ask these types of questions? > > I am trying to get a provider network working where I have full control of > the ip allocations. What I need is to be able to have 2 (or more public ip > addresses, or really to our private network). I