Public bug reported:

The values for default_ipv4_subnet_pool and default_ipv6_subnet_pool
currently have to be defined as the UUID of the desired subnetpool. This
leads to a chicken & egg situation where the admin has to somehow enter
the UUID into the conf file before neutron is initialised, and therefore
before the UUID can be generated.

These values should instead be defined by the name of the desired
subnetpool, so the admin can create it after neutron is started.

** Affects: neutron
     Importance: Undecided
     Assignee: John Davidge (john-davidge)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => John Davidge (john-davidge)

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

Title:
  Default subnetpools cannot be defined by name

Status in neutron:
  New

Bug description:
  The values for default_ipv4_subnet_pool and default_ipv6_subnet_pool
  currently have to be defined as the UUID of the desired subnetpool.
  This leads to a chicken & egg situation where the admin has to somehow
  enter the UUID into the conf file before neutron is initialised, and
  therefore before the UUID can be generated.

  These values should instead be defined by the name of the desired
  subnetpool, so the admin can create it after neutron is started.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to