Bug 1459469 - [Docs][Rally] Review OpenStack Benchmarking Service guide
Summary: [Docs][Rally] Review OpenStack Benchmarking Service guide
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Linux
Target Milestone: ---
: ---
Assignee: RHOS Documentation Team
QA Contact: RHOS Documentation Team
Depends On:
TreeView+ depends on / blocked
Reported: 2017-06-07 08:58 UTC by Francisco Javier Lopez Y Grueber
Modified: 2019-03-29 16:19 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-03-29 16:19:56 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Francisco Javier Lopez Y Grueber 2017-06-07 08:58:56 UTC
Description of problem:

The Red Hat OpenStack Platform 10 Benchmarking Service Guide is not correct in delivering installation instructions of Rally within the Rally 0.7.0 rpm shipped with RHOS10 release. 

Instead of providing information on the RHOS10 rally rpm we give very basic information on how to install via installation script as done within the upstream git repository. 

This should be fixed immediately as it is the impression that there was no QA verifying this. [ install_rally.sh is not included in the package] 

Also note, that the creation of venv is not possible when using the rpm this way. 

Additionally the "rally deployment create" routine should have a dedicated explanation. 

As it forms the base for the successfull usage of the package. 

Version-Release number of selected component (if applicable):


How reproducible:

Always -> Chapter Two -> Installing Benchmarking Service 

Steps to Reproduce:
1. rpm -ql openstack-rally |grep install_rally.sh 


Actual results:

No Information provided 

Expected results:

Detailed instructions on how to use the product 

Additional info:

Comment 1 Lucy Bopf 2017-08-25 05:20:24 UTC
Moving to 'NEW' to allow for triage.

Changing summary to suggest a whole guide review.

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