Testing Installation

At this point, you have both the Front End and one Node installed. In principle this is a fully functional installation. To ensure this is the case, we’ll run the standard battery of tests on the cloud infrastructure as a normal user.

Cloud User

We will create a new StratusLab cloud user account. Note that StratusLab accounts are independent of the Unix accounts on the machine itself.

Add the following line to the end of the file /etc/stratuslab/authn/login-pswd.properties:

$ cat >> /etc/stratuslab/authn/login-pswd.properties

This creates a new StratusLab user ‘sluser’ with a password ‘slpass’. The group ‘cloud-access’ is mandatory for the user to have access to the cloud services. (Crypted or hashed password values are also allowed in the configuration.)

The StratusLab distribution supports other authentication methods (LDAP, X509 certificates, X509 proxies, etc.), but a username/password pair is the simplest for this tutorial.

StratusLab Client

Now we will test that the cloud functions correctly by starting a new virtual machine instance and logging into it. We’ll test the cloud service from a normal Unix user account on the Front End.

First, ensure that the StratusLab user client is installed on the machine. Do the following as root:

$ yum install -y stratuslab-cli-user

This will do a system-wide installation of the StratusLab client from the RPM package.


For normal client installations, it is strongly recommended to use pip for the client installation. See the User Tutorial or User Guide for more information.


The RPM and pip installations are incompatible. Use only one method for installing the client!

Unix Account

Now create a normal Unix user for testing:

$ adduser sluser

We’ve chosen the same name as the cloud user, but the unix and cloud user accounts are distinct.

Now log in as the user and setup the account for using StratusLab. An SSH key pair is required to log into your virtual machines and the client requires that a complete client configuration file.

Log in as the user and create an SSH key pair. This is similar to the process used for the root account on the machine:

$ su - sluser
$ ssh-keygen -q

You can create a passphrase for this SSH key if you want. If you do, you’ll need to provide the passphrase when logging into virtual machines.

Now copy the reference configuration file into place and edit the parameters:

$ stratus-copy-config
$ vi $HOME/.stratuslab/stratuslab-user.cfg

You will need to set the “endpoint”, “username”, and “password” parameters in this file. For the “endpoint” use the hostname or IP address of your Front End. For the “username” and “password” use “sluser” and “slpass”, respectively.

Hello Cloud

Everything should be setup now. So just “ping” the services to ensure that they are running and accessible.

$ stratus-describe-volumes
No disk to show

$ stratus-describe-instance
id  state     vcpu memory    cpu% host/ip                 name

If the services do not respond, verify that the services are running and accessible through the nginx proxy. You may need to restart the nginx server after the server configuration.

Storage Check

Because the virtual machine management infrastructure depends on the storage system. We should first verify that the storage system works.

Run through the complete lifecycle of a persistent disk:

$ stratus-create-volume --size 1 --tag HELLO
DISK 87955437-1baa-412b-87ed-71e59e45e0f4

$ stratus-describe-volumes
:: DISK 87955437-1baa-412b-87ed-71e59e45e0f4
   count: 0
   owner: sluser
   tag: HELLO
   size: 1

$ stratus-delete-volume 87955437-1baa-412b-87ed-71e59e45e0f4
DELETED 87955437-1baa-412b-87ed-71e59e45e0f4

$ stratus-describe-volumes
No disk to show

If the full lifecycle works, then you’re ready to try to deploy a virtual machine.

Virtual Machine Check

You installed manually the package which provides the load information for the cloud. Check that the Node you configured is visible and not showing any errors:

$ curl -k https://${FRONTEND_HOST}/load.txt
 0        0      0      0    100     0K     0K     0K  err

If there are no machines listed or there is an error, you will need to correct this before going on.

$ stratus-run-instance KhGzWhB9ZZv5ZkLSZqm6pkWx7ZF

 :: Starting machine(s) ::
 :: Starting 1 machine
 :: Machine 1 (vm ID: 1)
 Public ip:
 :: Done!

Check the status of the machine as it starts:

# Check its status.  Pending -> not yet assigned to a Node
$ stratus-describe-instance
id  state     vcpu memory    cpu% host/ip                 name
1   Pending   1    0         0    vm-42.lal.stratuslab.eu one-1

# Check again.  Prolog -> resources for VM are being initialized
$ stratus-describe-instance
id  state     vcpu memory    cpu% host/ip                 name
1   Prolog    1    0         0    vm-42.lal.stratuslab.eu one-1

# Check again. Running -> hypervisor has started machine
$ stratus-describe-instance
id  state     vcpu memory    cpu% host/ip                 name
1   Running   1    0         0    vm-42.lal.stratuslab.eu one-1

When the machine reaches the ‘running’ status, the virtual machine is running in the hypervisor on the Node. It will probably take some additional time for the operating system to boot.

Verify that the machine has fully booted and is accessible from the network:

# Ping the virtual machine to see if it is accessible.
$ ping vm-42.lal.stratuslab.eu
PING vm-42.lal.stratuslab.eu ( 56(84) bytes of data.
From onehost-5.lal.in2p3.fr ( icmp_seq=2 Destination Host
From onehost-5.lal.in2p3.fr ( icmp_seq=8 Destination Host
64 bytes from vm-42.lal.stratuslab.eu ( icmp_seq=9
 ttl=64 time=1.44 ms

# Now login to the machine as root.
$ ssh root@vm-42.lal.stratuslab.eu

The authenticity of host 'vm-42.lal.stratuslab.eu ('
 can't be established.
RSA key fingerprint is
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'vm-42.lal.stratuslab.eu,'
 (RSA) to the list of known hosts.

#       # <- we're logged into the virtual machine
# exit  # just logout of the session
Connection to vm-42.lal.stratuslab.eu closed.

Now the machine can be terminated:

$ stratus-kill-instance 1

Going through the full lifecycle of a machine shows that all of the services are working.