Need doc on how to enable tempest in DevStack

Bug #1291752 reported by Mike Spreitzer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
devstack
Invalid
Undecided
Unassigned

Bug Description

In the cases of Heat and Ceilometer (for example, http://devstack.org/lib/ceilometer.html) the DevStack doc about that project starts with a remark about how to configure DevStack to include that project. The same should be done for tempest. Apparently it is not as trivial as adding "tempest" to the enabled services. I am told I should also declare

HEAT_FETCHED_TEST_IMAGE=Fedora-i386-20-20131211.1-sda

Changed in devstack:
assignee: nobody → Talusani Mani Shanker (shanker-mani0)
Changed in devstack:
assignee: Talusani Mani Shanker (shanker-mani0) → nobody
Revision history for this message
Talusani Mani Shanker (shanker-mani0) wrote :

I would like to fix this bug. This is my first attempt for bug fixing. Can anyone help me how to fix this bug.

Changed in devstack:
assignee: nobody → Talusani Mani Shanker (shanker-mani0)
Revision history for this message
Mike Spreitzer (mike-spreitzer) wrote : Re: [Bug 1291752] Re: Need doc on how to enable tempest in DevStack

The first step of a documentation fix is to know the facts you propose to
write about. Have you got that down? I was told of an additional thing
to write, but do not understand what it means and why it must be written.
That should be included in the documentation.

If you follow the "contribute" link near the bottom of openstack.org you
will get to a page with useful pointers about contributing in general and
doc fixing in particular.

Revision history for this message
Mike Spreitzer (mike-spreitzer) wrote :

I may have put that a bit too strongly (my frustrations with Neutron are bleeding through). Even if you only add a remark like "here is a magic incantation that you might need" it would be an improvement. It would be even better to explain it. You can often get good information on IRC at fortuitous times of day. In this case I would suggest #openstack-qa and #openstack-infra.

Revision history for this message
Talusani Mani Shanker (shanker-mani0) wrote :
Revision history for this message
Mike Spreitzer (mike-spreitzer) wrote :

Actually, it now appears to me that it is not always necessary to add that line. I have experimentally verified this. It would be best to get an explanation from an expert about when that line is needed.

Changed in devstack:
assignee: Talusani Mani Shanker (shanker-mani0) → nobody
Revision history for this message
Lee Yarwood (lyarwood) wrote :

AFAICT Tempest is currently enabled by default and setting HEAT_FETCHED_TEST_IMAGE explicitly in localrc is not required. Testing locally it appears the only recommended localrc change is to disable API rate limiting with 'API_RATE_LIMIT=False'. I'll document this in a change now so we can close this out.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to devstack (master)

Fix proposed to branch: master
Review: https://review.openstack.org/107630

Changed in devstack:
assignee: nobody → Lee Yarwood (lyarwood)
status: New → In Progress
Revision history for this message
Robbie Harwood (rharwood) wrote :

.../docs/source/configuration.html already mentions that tempest needs `API_RATE_LIMIT=False`, so I think there is no need for additional documentation.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on devstack (master)

Change abandoned by Lee Yarwood (<email address hidden>) on branch: master
Review: https://review.openstack.org/107630
Reason: Fair comments, closing this out. Thanks all.

Changed in devstack:
assignee: Lee Yarwood (lyarwood) → nobody
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.