yahoo-eng-team team mailing list archive

[Shivakumar M <1422629@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Consider scenario, where ml2 plugin is configured with following segment ranges.
network_vlan_ranges=physnet1:1000:1999
vni_ranges=500:999

Now, if I create a Network specifying a segmentation id which is not in
the range specified in the configuration file, the resource is getting
created.

neutron net-create net1 --provider:network_type=vlan --provider:physical_network=physnet1 --provider:segmentation_id=100
Created a new network:
+---------------------------+--------------------------------------+
| Field                     | Value                                |
+---------------------------+--------------------------------------+
| admin_state_up            | True                                 |
| id                        | dbe747f5-9d45-403d-97b2-6f4dd82aef47 |
| name                      | net1                               |
| provider:network_type     | vlan                                 |
| provider:physical_network | physnet1                             |
| provider:segmentation_id  | 100                                  |
| router:external           | False                                |
| shared                    | False                                |
| status                    | ACTIVE                               |
| subnets                   |                                      |
| tenant_id                 | e7897ad9e9f84826a0a7bfe6086e9278     |
+---------------------------+--------------------------------------+


neutron net-create net2 --provider:network_type=vxlan --provider:segmentation_id=10000
Created a new network:
+---------------------------+--------------------------------------+
| Field                     | Value                                |
+---------------------------+--------------------------------------+
| admin_state_up            | True                                 |
| id                        | ec9dd22a-ae53-41f0-9c78-348e77508dff |
| name                      | net2                               |
| provider:network_type     | vxlan                                |
| provider:physical_network |                                      |
| provider:segmentation_id  | 10000                                |
| router:external           | False                                |
| shared                    | False                                |
| status                    | ACTIVE                               |
| subnets                   |                                      |
| tenant_id                 | e7897ad9e9f84826a0a7bfe6086e9278     |
+---------------------------+--------------------------------------+

** Affects: neutron
     Importance: Undecided
     Assignee: Shivakumar M (shiva-m)
         Status: New


** Tags: ml2 neutron-core

** Changed in: neutron
     Assignee: (unassigned) => Shivakumar M (shiva-m)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1422629

Title:
  Creating a network with explicitly specified segmentation id must
  fail, if that id is not confiured

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Consider scenario, where ml2 plugin is configured with following segment ranges.
  network_vlan_ranges=physnet1:1000:1999
  vni_ranges=500:999

  Now, if I create a Network specifying a segmentation id which is not
  in the range specified in the configuration file, the resource is
  getting created.

  neutron net-create net1 --provider:network_type=vlan --provider:physical_network=physnet1 --provider:segmentation_id=100
  Created a new network:
  +---------------------------+--------------------------------------+
  | Field                     | Value                                |
  +---------------------------+--------------------------------------+
  | admin_state_up            | True                                 |
  | id                        | dbe747f5-9d45-403d-97b2-6f4dd82aef47 |
  | name                      | net1                               |
  | provider:network_type     | vlan                                 |
  | provider:physical_network | physnet1                             |
  | provider:segmentation_id  | 100                                  |
  | router:external           | False                                |
  | shared                    | False                                |
  | status                    | ACTIVE                               |
  | subnets                   |                                      |
  | tenant_id                 | e7897ad9e9f84826a0a7bfe6086e9278     |
  +---------------------------+--------------------------------------+

  
  neutron net-create net2 --provider:network_type=vxlan --provider:segmentation_id=10000
  Created a new network:
  +---------------------------+--------------------------------------+
  | Field                     | Value                                |
  +---------------------------+--------------------------------------+
  | admin_state_up            | True                                 |
  | id                        | ec9dd22a-ae53-41f0-9c78-348e77508dff |
  | name                      | net2                               |
  | provider:network_type     | vxlan                                |
  | provider:physical_network |                                      |
  | provider:segmentation_id  | 10000                                |
  | router:external           | False                                |
  | shared                    | False                                |
  | status                    | ACTIVE                               |
  | subnets                   |                                      |
  | tenant_id                 | e7897ad9e9f84826a0a7bfe6086e9278     |
  +---------------------------+--------------------------------------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1422629/+subscriptions