yahoo-eng-team team mailing list archive

[Armando Migliaccio <1237807@xxxxxxxxxxxxxxxxxx>]

@Yair: from comment #14 I sense that you are making wrong assumptions as
to what a real world data center or cloud environment actually works.

A resource like 'network' has two status attributes: admin_status_up and
status; these are not to be confused. As of now, flipping the
admin_status_up from True to False has no effect in most plugins, it's
just a toggle operation on the DB, and some plugins do not even support
it (ie. barf at the update operation when/if tried, like the NSX
plugin).

In my opinion this is the semantic:

admin_status_up: it's the management state of the resource. An admin can
choose to disable/enable this resource for management purposes.
Management plane downtime, must not cause a data plane loss. If we want
to mirror this to the compute world, it's like when I put a hypervisor
in maintenance mode: perhaps I need to evacuate the host and I cannot
allow for more vm's to get spawned, or I need to do some sort of
reactive maintenance and I don't want the management framework to fiddle
with it while I am on it. If you think that management downtime == data
plane downtime, you clearly have a wrong view of the real world!!

status: this is the status of the fabric, the data plane status if you
will. Following the analogy with compute, this means that your host is
either hosed, not feeling well, and something is broken; it pleas for
troubleshooting!

Now, as for a Neutron network, the admin_status_up may not be entirely
useful, but deprecating it or marking for removal is wrong. And even
worse, forcing admin_status_up=False to cause a data plane loss.

** Changed in: neutron
       Status: Incomplete => Won't Fix

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

Title:
  Network admin_state _up is not working

Status in OpenStack Neutron (virtual network service):
  Won't Fix

Bug description:
  By default network is created with admin_statue_up True

  Network will not be deactivated  when user issue update to
  admin_statue_up False , traffic from VMs still works and the network
  STAUS is still Active

  
  [root@puma04 ~(keystone_admin_tenant1)]$neutron net-list
  +--------------------------------------+-------------+----------------------------------------------------+
  | id                                   | name        | subnets                                            |
  +--------------------------------------+-------------+----------------------------------------------------+
  | 62e4a6ac-970e-49fe-81c1-1115dee7f800 | ext_net     | 6dd43d99-e226-4e85-9471-89091c3ad031               |
  | 78c1f62e-22c0-42e0-9377-e9d247862da4 | net-vlan201 | 534d328d-441b-4fe6-b4ba-3c397391bea2 89.66.66.0/24 |
  +--------------------------------------+-------------+----------------------------------------------------+

  [root@puma04 ~(keystone_admin_tenant1)]$neutron net-update 78c1f62e-22c0-42e0-9377-e9d247862da4 --admin_state_up False  <<<<<<<<<<< 
  Updated network: 78c1f62e-22c0-42e0-9377-e9d247862da4
  [root@puma04 ~(keystone_admin_tenant1)]$neutron net-show 78c1f62e-22c0-42e0-9377-e9d247862da4
  +-----------------+--------------------------------------+
  | Field           | Value                                |
  +-----------------+--------------------------------------+
  | admin_state_up  | False                                | <<<<<<
  | id              | 78c1f62e-22c0-42e0-9377-e9d247862da4 |
  | name            | net-vlan201                          |
  | router:external | False                                |
  | shared          | False                                |
  | status          | ACTIVE                               | <<<<<<<<<< Still ACTIVE 
  | subnets         | 534d328d-441b-4fe6-b4ba-3c397391bea2 |
  | tenant_id       | c7431cff351542c28427028d9befe1fb     |
  +-----------------+--------------------------------------+
  [root@puma04 ~(keystone_admin_tenant1)]$neutron net-update 78c1f62e-22c0-42e0-9377-e9d247862da4 --admin_state_up True <<<<<<<<<< 
  Updated network: 78c1f62e-22c0-42e0-9377-e9d247862da4
  [root@puma04 ~(keystone_admin_tenant1)]$neutron net-show 78c1f62e-22c0-42e0-9377-e9d247862da4
  +-----------------+--------------------------------------+
  | Field           | Value                                |
  +-----------------+--------------------------------------+
  | admin_state_up  | True                                 |
  | id              | 78c1f62e-22c0-42e0-9377-e9d247862da4 |
  | name            | net-vlan201                          |
  | router:external | False                                |
  | shared          | False                                |
  | status          | ACTIVE                               | <<<<<<<<<<<<
  | subnets         | 534d328d-441b-4fe6-b4ba-3c397391bea2 |
  | tenant_id       | c7431cff351542c28427028d9befe1fb     |
  +-----------------+--------------------------------------+

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