dashbord/horizon create network for vlan without choosing segmentation ID
Bug #1223360 reported by
Roey Dekel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Medium
|
Justin Pomeroy |
Bug Description
When creating a new network, it's segmentation ID is being choosed by the lowest aviable. This could cause problems when creating vlan.
I configurated 2 segmentations for vlans: one internal-237, one external-232 with GW (gateway). I tried to use the dashbord (horizon) in order to first create the internal and afterwards the external, and I reliezied that I don't have the oppurtunity to choose the segmentation ID for each of them. In my example I had to do first the external because it's number is lower. I think that in much complicated example the option to choose the segmentation ID will be welcomed.
affects: | openstack-manuals → horizon |
Changed in horizon: | |
importance: | Undecided → Medium |
milestone: | none → icehouse-1 |
status: | New → Confirmed |
Changed in horizon: | |
milestone: | icehouse-1 → icehouse-2 |
Changed in horizon: | |
milestone: | icehouse-2 → icehouse-3 |
Changed in horizon: | |
status: | Confirmed → In Progress |
Changed in horizon: | |
milestone: | icehouse-3 → icehouse-rc1 |
Changed in horizon: | |
milestone: | icehouse-rc1 → next |
Changed in horizon: | |
milestone: | next → juno-3 |
Changed in horizon: | |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | juno-3 → 2014.2 |
To post a comment you must log in.
I think you are talking about the provider network feature in Neutron.
At now network creation form does not support provider network feature in Neutron. The blueprint is proposed to allow admin to specify the segmentation ID, but I don't see any progress.
The segmentation ID depends on the network type of the network, so it is not simple to validate user input. If we can pass the parameters to Neutron without any cross-field validation, it can be implemented. However, it is not user-friendly.
I would like to know your thought on in for better implementation.
If it is small, we can consider a fix in Havana-RC1.