[Rdo-list] Adding another public subnet in RDO

Sun Jun 29 15:36:27 UTC 2014

----- Original Message -----
> Hi Assaf,
> 
> Thank you for responding.
> 
> This was a single node install (packstack --allinone) with only 1 eth
> (eth0). So eth0 is already assigned a public ip address (which is later
> moved to br-ex as required during Openstack installation). The initial IP
> range allotted by Datacenter was: 173.xxx.xxx.144/29, so 173.xxx.xxx.146 is
> eth0.
> 
> Now, the free ips that can be assigned are: 173.xxx.xxx.147-.150. These ips
> were used up by the few VMs (and a ovs router). So next, the DC assigned
> another block of ips which is of an entirely different subnet, **and making
> the second ip range work in a single node install was a pain for me**
> 
> I asked about this particular error in the OpenStack list with no response,
> so maybe I was doing something really stupid.
> 
> http://lists.openstack.org/pipermail/openstack/2014-June/007987.html    ..
> and..
> http://lists.openstack.org/pipermail/openstack/2014-June/007992.html
> 
> Even after adding another public subnet (neutron subnet-create ..), I was
> unable to "interface-attach", with error saying that no free IPs are
> available, where as in reality: 1. private network has lot of ips available
> 2. First public subnet is full 3. Second subnet is already added in public
> net, and it has free ips available.
> 
> From logs it was evident that "Interface-attach" action was complaining
> about a public subnet being full (Shouldn't it simply create eth1 and
> assign a private IP? Why the heck should it complain about a public subnet
> being full?)
> 
> I was hitting some kind of port-limit there but I do not recollect what I
> did to fix it (apparently I spent a couple of days testing things out so
> not sure what eventually fixed it).
> 
> I finally added one ip from the second public subnet to br-ex, and then
> created a public subnet with the rest of the ips on that range with gateway
> set to this ip on br-ex and it worked. I hope this is how it can be done.
> 

I'm glad it works now.

> Also, your blog on Openvswitch and Openstack networking is undoubtedly the
> best ever explanation of how networking works in OpenStack. I noted down
> every word and pic from your blog (on topics: ovs & gre) in my notebook,
> read and re-read them some 10-15 times and I can confidently say I have a
> better understanding on these things now than when I posted this query (a
> week ago, that is). Do keep writing, please!
> 

Wow, thank you :) I hope I can keep writing around a post a month.

> I successfully tested out a 3-node OpenStack install earlier today, and
> your notes on GRE helped me in troubleshooting like a pro :-)
> 
> Regards,
> Vimal
> 
> On Sun, Jun 29, 2014 at 2:58 PM, Assaf Muller <amuller at redhat.com> wrote:
> 
> > Hi Vimal,
> >
> > Answers inline.
> >
> > ----- Original Message -----
> > > Hi,
> > >
> > > I have a dedicated server which has 2 public ip ranges allotted to it by
> > the
> > > DC. I am trying out OpenStack RDO on this server (allinone install), and
> > I
> > > was able to assign one of the mentioned ranges (let's say
> > > 173.xxx.xxx.144/29) and managed to use up all the available ips in this
> > > range for a few vms. This floating-ip range is now accessible from
> > outside,
> > > and everything is fine.
> > >
> > > [root at mycloud ~(keystone_admin)]# neutron net-list
> > >
> > +--------------------------------------+---------+---------------------------------------------------------+
> > > | id | name | subnets |
> > >
> > +--------------------------------------+---------+---------------------------------------------------------+
> > > | 09c8da8e-79d7-49e1-9af8-c2a13a032040 | private |
> > > | b7eeae38-682a-4397-8b3c-e3dee88527ab 10.0.0.0/24 |
> > > | 31956556-c540-4676-9cd4-e618a4f93fc8 | public |
> > > | 14d4b197-1121-4a4b-80b3-b8d80115f734 173.xxx.xxx.144/29 |
> > >
> > +--------------------------------------+---------+---------------------------------------------------------+
> > >
> > > [root at yocloud ~(keystone_admin)]# neutron subnet-list
> > >
> > +--------------------------------------+----------------+--------------------+--------------------------------------------------------+
> > > | id | name | cidr | allocation_pools |
> > >
> > +--------------------------------------+----------------+--------------------+--------------------------------------------------------+
> > > | b7eeae38-682a-4397-8b3c-e3dee88527ab | private_subnet | 10.0.0.0/24 |
> > > | {"start": "10.0.0.2", "end": "10.0.0.254"} |
> > > | 14d4b197-1121-4a4b-80b3-b8d80115f734 | public_subnet |
> > 173.xxx.xxx.144/29 |
> > > | {"start": "173.xxx.xxx.147", "end": "173.xxx.xxx.150"} |
> > >
> > +--------------------------------------+----------------+--------------------+--------------------------------------------------------+
> > >
> > > I am now looking to use the second public ip range for next vms and I am
> > not
> > > sure how to proceed.
> > >
> > > I tried to create a subnet (public_subnet2) inside "public" net for the
> > new
> > > ip block but fail to get it working. Neutron does not appear to know
> > that it
> > > has a few more free floating-ips available, and throws 'No more IP
> > addresses
> > > available on network'.
> > >
> > > Can someone point to the right direction? Is it not possible to add
> > multiple
> > > subnets inside a public network?
> >
> > When exactly do you fail? When I run neutron floatingip-create <public
> > network>
> > it successfully creates floating IPs from the first subnet, then when that
> > runs
> > out it starts creating FIPs on the second subnet.
> >
> > >
> > > Regards,
> > > Vimal
> > >
> > > _______________________________________________
> > > Rdo-list mailing list
> > > Rdo-list at redhat.com
> > > https://www.redhat.com/mailman/listinfo/rdo-list
> > >
> >
> 