← Back to team overview

openstack team mailing list archive

Re: public net with single ip cannot be uplinked[QUANTUM]

 

I believe a minimum of 2 IP addresses is required (1 for the bridge port, and 1 to allocate).

From: Openstack [mailto:openstack-bounces+eric_e_smith=dell.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Ramprasad Velavarthipati
Sent: Thursday, May 02, 2013 2:00 AM
To: openstack@xxxxxxxxxxxxxxxxxxx
Subject: [Openstack] public net with single ip cannot be uplinked[QUANTUM]

Hello,
Im trying to create a public network(in a test lab where we get the ip addresses through DHCP.,
hence I limited the public network to /32 cidr range)
Im trying to map this public network to my router in quantum Im getting the following error
"root@ubuntu-ram:/home/ramprasvm# quantum router-gateway-set router1 public-net
No more IP addresses available on network fca44fe9-0afb-4458-985e-12ae876b5494.
"
"root@ubuntu-ram:/home/ramprasvm# quantum net-list
+--------------------------------------+-------------+-------------------------------------------------------+
| id                                   | name        | subnets                                               |
+--------------------------------------+-------------+-------------------------------------------------------+
| 5b5ea7cf-ea08-4007-9f6e-0c2c6a93455a | private-net | 7100a8ef-e204-43f2-8fdd-e0bb697bf610 172.16.8.0/24<http://172.16.8.0/24>    |
| fca44fe9-0afb-4458-985e-12ae876b5494 | public-net  | b0c23146-63ea-4758-8b22-f0602bce0378 10.232.91.108/32<http://10.232.91.108/32> |
+--------------------------------------+-------------+-------------------------------------------------------+
root@ubuntu-ram:/home/ramprasvm# quantum subnet-list
+--------------------------------------+----------------+------------------+------------------------------------------------+
| id                                   | name           | cidr             | allocation_pools                               |
+--------------------------------------+----------------+------------------+------------------------------------------------+
| b0c23146-63ea-4758-8b22-f0602bce0378 | public-subnet  | 10.232.91.108/32<http://10.232.91.108/32> |                                                |
| 7100a8ef-e204-43f2-8fdd-e0bb697bf610 | private-subnet | 172.16.8.0/24<http://172.16.8.0/24>    | {"start": "172.16.8.2", "end": "172.16.8.254"} |
"
Kindly help me out how to proceed further
--
Thanks,
-Ram

Follow ups

References