yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

Public bug reported:

It seems that this guide in openstack-manuals:

https://github.com/openstack/openstack-manuals/blob/stable/ocata/doc
/user-guide/source/cli-config-drive.rst

Was not migrated to the nova repo in pike.

The compute API reference refers to it though in the "config_drive"
parameter for the "Create Server" action:

https://developer.openstack.org/api-ref/compute/#create-server

"Read more in the OpenStack End User Guide."

Part of that guide is for end users and part of it is for operators, so
we should probably split it up when we migrate it into nova.

** Affects: nova
     Importance: High
         Status: Confirmed

** Affects: nova/pike
     Importance: High
         Status: Confirmed


** Tags: docs

** Summary changed:

- end user guide was not migrated from openstack-manuals
+ config drive guide was not migrated from openstack-manuals

** Also affects: nova/pike
   Importance: Undecided
       Status: New

** Changed in: nova/pike
       Status: New => Confirmed

** Changed in: nova/pike
   Importance: Undecided => High

-- 
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/1720873

Title:
  config drive guide was not migrated from openstack-manuals

Status in OpenStack Compute (nova):
  Confirmed
Status in OpenStack Compute (nova) pike series:
  Confirmed

Bug description:
  It seems that this guide in openstack-manuals:

  https://github.com/openstack/openstack-manuals/blob/stable/ocata/doc
  /user-guide/source/cli-config-drive.rst

  Was not migrated to the nova repo in pike.

  The compute API reference refers to it though in the "config_drive"
  parameter for the "Create Server" action:

  https://developer.openstack.org/api-ref/compute/#create-server

  "Read more in the OpenStack End User Guide."

  Part of that guide is for end users and part of it is for operators,
  so we should probably split it up when we migrate it into nova.

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