yahoo-eng-team team mailing list archive

[OpenStack Infra <1670419@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/442035
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7439e9473617a871c032107ab85b1b623369975f
Submitter: Jenkins
Branch:    master

commit 7439e9473617a871c032107ab85b1b623369975f
Author: Matt Riedemann <mriedem.os@xxxxxxxxx>
Date:   Mon Mar 6 20:25:55 2017 -0500

    Remove unused placement_database config options
    
    The placement_database config options were added in Newton
    but the actual code to use the options was reverted and is
    not used. The help text actually has a typo (Ocata was 15.0.0,
    not 14.0.0) and, more importantly, the help text makes it sound
    like you should really be setting up a separate database for the
    placement service but we don't actually use these options, we use
    the api_database options for all of the placement data models.
    
    To avoid confusion until this is actually supported, let's just
    remove the options which should have been cleaned up as part of
    39fb302fd9c8fc57d3e4bea1c60a02ad5067163f anyway.
    
    Change-Id: I31293ac4689630e4113588ab2c6373cf572b8f38
    Closes-Bug: #1670419


** Changed in: nova
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1670419

Title:
  placement_database config option help is wrong

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) newton series:
  New
Status in OpenStack Compute (nova) ocata series:
  In Progress

Bug description:
  The help on the [placement_database] config options is wrong, it
  mentions Ocata 14.0.0 but 14.0.0 is actually Newton, Ocata was 15.0.0:

  "# The *Placement API Database* is a separate database which is used for the new
  # placement-api service. In Ocata release (14.0.0) this database is optional:"

  It also has some scary words about configuring it with a separate
  database so you don't have to deal with data migration issues later to
  migrate data from the nova_api database to a separate placement
  database, but the placement_database options are not actually used in
  code. They will be when this blueprint is complete:

  https://blueprints.launchpad.net/nova/+spec/optional-placement-
  database

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