yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => juno-1

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

Title:
  disable nova-manage network + related cmds if using Quantum v2

Status in OpenStack Neutron (virtual network service):
  In Progress
Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  When using nova with quantum v2 API, all CRUD operations should be
  done directly against the quantum API, rather than using nova-manage.

  However, even when no nova-network is running (as is the case with
  Quantum v2), nova-manage calls to do things like create networks will
  still succeed, as nova-manage will simply load the default network
  manager, and make the calls, which will result in writing to the nova
  database.  These calls will appear to succeed, even though the
  networks, floating ips, fixed ips, etc. are irrelevant to the quantum
  deployment.

  We should add checks to nova (nova-manage?) to prevent this from
  happening.

  One option would be for the base NetworkManager class to check and
  make sure that a network manager will actually be used (i.e., check
  that the network_api_class is not set to
  "nova.network.quantumv2.api.API").

  Other options would be to modify nova-manage, but that seems less
  robust.

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