Management of Associations between Networks and Projects fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
François Charlier | ||
Diablo |
Fix Released
|
Undecided
|
Mark McLoughlin |
Bug Description
http://
I have a question regarding the nova-manage network create statement. We assumed, that every project / tenant should get its own virtual network segment out of the defined range of ip nets in the fixed-range flag in nova.conf.
When I create a new network with, e.g.
Code: Select all
nova-manage network create projnet 192.168.5.0/24 2 128
: How does Open Stack knows, that it should belong to the previously created project??
I used "nova-manage network create --help" to find out, that there are some additional options available for the nova-manage network create statement (e.g.):
Code: Select all
-
-
Whenever I used them in one of my statements the appropriate project field is still empty.
Code: Select all
root@
root@
root@
id IPv4 IPv6 start address DNS1 DNS2 VlanID project uuid
1 192.168.4.0/24 None 192.168.4.2 8.8.4.4 None None None None
2 192.168.5.0/25 None 192.168.5.2 8.8.4.4 None None None None
3 192.168.5.128/25 None 192.168.5.130 8.8.4.4 None None None None
4 192.168.6.0/25 None 192.168.6.2 8.8.4.4 None None None None
5 192.168.7.0/25 None 192.168.7.2 8.8.4.4 None None None None
Also the corresponding fields in the table "networks" are empty.
So how does Openstack manage associations between network and different projects?
Thank you for answering my question in advance.
-------
Answer by: mjfork » Thu Dec 08, 2011 7:58 pm
I tried this a few separate ways and it did not work for me as well. I traced the code and, while I see nova-manage passing on project_id to the create_networks call, I do not see where create_networks makes use of it. I would suggest opening a bug report in launchpad. Please post the link if you do in case others with a similar problem come across this.
As a workaround, you could go into the mysql database and do
mysql> SELECT id, vlan from networks;
mysql> UPDATE networks SET project_
Where to get the project_id will depend on if you are using keystone or nova authentication. I believe this will only work if the network has not been previously used.
Michael Fork
description: | updated |
Changed in nova: | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in nova: | |
assignee: | nobody → François Charlier (francois-charlier) |
status: | Confirmed → In Progress |
Changed in nova: | |
milestone: | none → essex-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-3 → 2012.1 |
This also affects me - project_id is being ignored when specifying creation of a fixed IP range.
Ubuntu 11.10, Diablo.
sudo nova-manage project create development kevinj id=development --fixed_ range_v4= 10.0.1. 0/26 --bridge_ interface= eth1 --vlan=101
sudo nova-manage network create --label=development --project_
sudo nova-manage network list
id IPv4 IPv6 start address DNS1 DNS2 VlanID project uuid
1 10.0.0.0/26 None 10.0.0.3 None None 100 example None
4 10.0.1.0/26 None 10.0.1.3 None None 101 None None