Document how to install tempest without devstack

Bug #1201201 reported by Attila Fazekas
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
tempest
Invalid
Wishlist
Ankur

Bug Description

Add an rst file and an install helper script, which expected to configure and prepare a tempest run against any dev/test system.

summary: - Document how to installation tempest without devstack
+ Document how to install tempest without devstack
Changed in tempest:
status: New → Confirmed
importance: Undecided → Low
Sean Dague (sdague)
tags: added: low-hanging-fruit
Changed in tempest:
assignee: nobody → chandankumar (chandankumar-093047)
Revision history for this message
chandan kumar (chkumar246) wrote :

Hello,
What is the link for the helper script to install tempest.
So that i can work on it.

Thanks,
Chandan Kumar

Sean Dague (sdague)
Changed in tempest:
importance: Low → Wishlist
Changed in tempest:
assignee: chandankumar (chandankumar-093047) → nobody
Changed in tempest:
assignee: nobody → Pradnya Patankar (pradnya-patankar)
assignee: Pradnya Patankar (pradnya-patankar) → nobody
Changed in tempest:
assignee: nobody → Hemanth Nakkina (hemanth-n)
Revision history for this message
naggappan (naggappan) wrote :

Hi Hemanth,

I am new to tempest and currently i am trying tempest in openstack environment. So i can prepare a clean document and instllation scripts. I just wanted to know if you are working on this bug still. If not please assign it to me so that i can proceed with this low priority bugs.

Changed in tempest:
assignee: Hemanth Nakkina (hemanth-n) → nobody
naggappan (naggappan)
Changed in tempest:
assignee: nobody → naggappan (naggappan)
Revision history for this message
naggappan (naggappan) wrote :

==============================
Tempest Execution Guide
==============================

step 1:
*Clone the tempest code to your openstack environment
*git clone https://github.com/openstack/tempest.git

step 2:
*You should do basic configuration according to your environment
*By default an example configuration file would be present copy that to tempest.conf
*cp $Tempest_root/etc/tempest.conf.sample $Tempest_root/etc/tempest.conf
*If you are running devstack a non-admin user demo and non-admin tenant demo would have been created automatically during instllation
*But if you are running under openstack environment please create a not admin user eg: demo. Also create a non-admin-tenant eg: demo.
*Open the tempest.conf and configure the following in [identity] and [dashboard] session

[identity]
uri=http://127.0.0.1:5000/v2.0/
uri_v3 = http://127.0.0.1:5000/v3/
auth_version=v2
admin_domain_name = Default
admin_tenant_name = admin
admin_password = {your_openstack_admin_login_password}
admin_username = admin
tenant_name = {non-admin-tenant-eg-demo}
username = {non-admin-user-eg-demo}
password = {non-admin-user-password}

[dashboard]

login_url=http://127.0.0.1/auth/login/
uri_v3 = http://127.0.0.1:5000/v3/

Note:
In the above example i have configured dashboard and identity url as 127.0.0.1. In case if keystone service is installed in different machine, please use that machines IP address

Executing the tempest:(below example only execute identity api tempest)
cd $Tempest_root/
pip install -r requirements.txt
nosetests -v tempest.api.identity

Note:
*Still You may require to configure the tempest.conf with image_ref to execute all test as below

To execute complete tempest:
nosetests -v tempest.

++++++++++++++++++++++++++++++
I have given basic configurations details for identity api test.
If this is ok i will create a new configruation.rts file and specify the above details
++++++++++++++++++++++++++++++++++++++

Revision history for this message
David Kranz (david-kranz) wrote :

So doing this right with an arbitrarily configured cloud is really hard. That is why https://review.openstack.org/94473 is badly needed so that documentation like this can be made really usable. Note also that before you can do pip install -r requirements.txt you need to install a bunch of other native packages depending on what os you are using. This is not really documented either and is another thing that devstack does on the machine where it is run.

Revision history for this message
naggappan (naggappan) wrote :

*I have install openstack in readhat using "packstack --allinone"
*Then i have cloned the tempest.
*Also i have installed the below dependencies to run nosetests

pip install testrepository
pip install testscenarios
pip install discover
pip install testresources
pip install unittest2
pip install testtools
pip install fixtures

*Yes installing requirements.txt has lots of issues most of the time. But since i have used packstack and installed openstack already. I did not try that.

*I have gone through the blueprint, so this should be specify to configuration and not on dependencies which needs to be installed. Because this is going to be executed against the openstack/devstack where already the required things are installed and configured.

* Please let me know in which os it has to be tested. So that first i can may the configuration only for identity api and verify it in my end before submitting.
*Also this has to be tested under devstack or openstack environment. If openstack means there are lots of instillation process so it may be differ according to the users.
*I am confused with details about configuration in yamal/json file. So it means that that yamal file should contain basic configuration for each service and it should take from there and write it in tempest.conf

*Also please let me know when this will be discussed in IRC Meeting. so that i can login at that time and know what is happening on this issue and how to proceed

Revision history for this message
David Kranz (david-kranz) wrote :

Tempest should not be assumed to be running on the controller node for a cloud, even though that is what we do with devstack in the gate jobs.

Revision history for this message
naggappan (naggappan) wrote :

ok so i guess the following should be the proper steps,

*A separate machine which has no connection with our cloud environment. Except that it can contact the controller node
*clone the tempest code in this machine
*Install all dependencies without any failure
*do the basic configuration in tempest.conf where URL and URI other settings should be related to their cloud environment
*Then start the tempest.

Revision history for this message
naggappan (naggappan) wrote :

Hi,

Is it possible to do in the following way,

* Install devstack with tempest
* Now in the tempest config lets modify the URL to point the actual openstack controller node
* Now run the tempest , so it will execute the tempest agains the actual openstack cloud from a devstack machine. In this way we don't find any dependencies issue.

Revision history for this message
Albert (albert-vico) wrote :

What's wrong with:

git clone <tempest>

configure the proper tempest.conf pointing to your deployment

./run_tempest.sh

if fails install any missing dependencies, like ggc, python-dev, etc.

naggappan (naggappan)
Changed in tempest:
assignee: naggappan (naggappan) → nobody
Changed in tempest:
assignee: nobody → Pramod (pramod-raghavendra-jayathirth)
Ankur (ankur-gupta-f)
Changed in tempest:
assignee: Pramod (pramod-raghavendra-jayathirth) → Ankur (ankur-gupta-f)
Revision history for this message
Ankur (ankur-gupta-f) wrote :

Is this bug still viable. Should an .rst still be created to provide users step by step for full tempest install in a non-devstack environment?

Revision history for this message
Steve Heyman (sheyman) wrote :

Ankur - seems to be this would be valuable. Are you working on it?

Revision history for this message
Ankur (ankur-gupta-f) wrote :

I had put it on hold until I got some feedback on whether it was still necessary.

In order to complete I would need more details on what is expected and how it should be implemented.

Thank you Steve.

Revision history for this message
Anthony Washington (anthony-washington) wrote :

Refer to the link: http://docs.openstack.org/developer/tempest/

Quickstart section will show you how to run and configure tempest w/o
a devstack environment.

Will have to config that will tell Tempest where to find the various
OpenStack services and other testing behavior switches.

Is this the solution you were looking for?

Changed in tempest:
status: Confirmed → 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.