Bug 913281 - RHOS Command Line Interface Guide
Summary: RHOS Command Line Interface Guide
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: distribution
Version: 3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: beta
: 3.0
Assignee: RHOS Documentation Team
QA Contact:
URL:
Whiteboard:
Depends On: 919474 919481 919486 953675
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-20 20:00 UTC by Stephen Gordon
Modified: 2013-06-26 14:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-26 14:40:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1130868 0 None None None Never

Description Stephen Gordon 2013-02-20 20:00:25 UTC
Description of problem:

Deliver a command line interface guide based on the upstream equivalent located here:

    http://docs.openstack.org/cli/quick-start/content/index.html

Initial tasks are to:

    - Work with upstream to ensure that the guide is up to date and accurate for all Fedora/EL derived distributions.
    - Work with upstream to add OS specific conditionals to the guide (stretch goal).
    - Work with upstream to ensure content exists for all supported Grizzly CLIs.

Delivery tasks are to:

    - Create a build process capable of either building the DocBook 5 source or converting it to DocBook 4.5 at build time.
    - Ensure process for maintaining and updating rhos-openstack-manuals repository tracking upstream is well defined and works.

This bug is to act as the tracker for these efforts.

Comment 1 Stephen Gordon 2013-03-08 15:48:05 UTC
Added some Publican RFEs I have raised which would help with this effort. These are not strictly required if we use a pre-build script but would help minimize the amount of XML transformation it needs to do.

Comment 2 Lon Hohberger 2013-06-26 14:40:58 UTC
Closing based on talking with Stephen.  The upstream direction is primarily to place the CLI guide within the user guide; a separate guide is not necessary.


Note You need to log in before you can comment on or make changes to this bug.