dparalen / devstack-gate-test

Table of Contents

• devstack-gate-test
  • Running on a VM, without Vagrant
  • Pre-requisites
  • Git Cache

devstack-gate-test

Please create the directory /opt/git and have it owned by the user that will be running Vagrant. It is highly recommended to setup a cache of files here. Please see Git Cache for information on setting up the git cache.

I recommend if on Ubuntu 14.04 to get the latest version of Vagrant from https://www.vagrantup.com/downloads.html and download the Debian 64-bit flavor.

Inside the created Virtual Machine a 'backdoor' user is created and is able sudo to root. The user's SSH public key is copied to the 'backdoor' and the 'jenkins' user. This is because the puppet script will remove the ability to SSH as root. This is a problem if you decide to use just the ansible portion to run on an OpenStack VM, as you would not be able to login.

Running on a VM, without Vagrant

For those users who want to run this on a VM without using Vagrant, it can be done. This is not yet fully documented though. I am assuming a good knowledge of how to use Ansible.

There is a fairly simple bash script to do the work. It is vm-setup.sh. It takes care of installing the required dependencies and runs the devstack-gate VM setup to the point where it is ready to be snapshotted.

If not using the vm-setup.sh script then the following will apply.

In the directory ansible/ there is a playbook ansible/playbook.yml. Change into the directory ansible. Create an inventory file in the directory, for example hosts and put the name of the host you want to run the ansible playbook against.

Then you can do:

$ ansible-playbook -vvv -i hosts playbook.yml

Note

Ansible 2.0 or higher is required on the target VM. You can use Ansible 1.5.4 on the system that connects to the VM. But if the target and the host are the same, please install Ansible 2.0 or higher.

Note

There is an assumption that the sudo can happen without needing a password. So you may need to use the -K flag if you require a password to sudo.

Note

The puppet scripts that get run effectively lock down the root user. They also change the SSH host key on the system. Because of this the Ansible scripts create a user called 'backdoor' and copy the authorized_keys file that existed for the root user. You can SSH in as the 'backdoor' user and then sudo.

Pre-requisites

Pre-requisites needed for running devstack-gate (assuming Ubuntu 14.04):

1. Vagrant - latest version can be downloaded from www.vagrantup.com/downloads.html), Debian 64-bit flavor
2. VirtualBox - latest version. Can be done by running sudo apt-get install virtualbox. Once you have it installed you probably want to install guest additions in the guest OS. And you probably also want the extension pack which you can get from here: www.virtualbox.org/wiki/Downloads.
3. NFS server - /opt/git is synced with the VM via NFS. On Ubuntu, may be installed by running sudo apt-get install nfs-kernel-server.

The two important scripts:

ironic-grenade.sh - This file clones the devstack-gate into your workspace. References the update-projects.sh in an export statement. It exports all local modules grenade things, and runs baremetal tests.

update-projects.sh - This file is used to do various updates after the /opt/stack/old and /opt/stack/new are set up. Again, this file is referenced and sourced into ironic-grenade.sh.

To run the tests:

1. Create the guest VM:

   $ vagrant up

2. SSH into the vm using vagrant.

   $ vagrant ssh

3. Switch to the jenkins user, and run the ironic-grenade.sh script.

   $ sudo su - jenkins

   $ ./ironic-grenade.sh

Running takes about 30-40 mins unfortunately. After the run, you can see the logs in /home/jenkins/workspace/testing/logs/. Specifically, grenade.sh.txt.gz.

Any time major changes are made to files, the image for the VM box needs to be recreated as follows:

Pull the latest changes. Create a package.box by doing:

$ vagrant package

This will create a package.box in your current directory. You must now add this box so that vagrant can find it and use it:

$ vagrant box add --name devstack-gate package.box

After this you should have your directory called devstack-gate-test with everything, and also a Vagrantfile.package file in it.

To avoid doing a rebuild every single time any minor changes are made, create a new directory devstack-gate-packaged, copy the Vagrantfile.package and rename it to Vagrantfile. In this file, update the name of the box to whatever you named when you created add the box with the "vagrant box add" command. This way you would only be dealing with two directories, devstack-gate devstack-gate-packaged.

Git Cache

Use the script setup_git_cache.sh to populate your /opt/git/ directory.