Revision as of 20:00, 15 January 2014

Deploy engines: Introduction

One of the core entities in Rally architecture are the Deploy engines. The task of a deploy engine is to control the process of deploying some OpenStack distribution like DevStack or FUEL before any benchmarking procedures take place. Every deploy engine should implement the following fairly simple interface:

• constuctor, which takes a deployment entity as its only parameter;
• deploy(), which should deploy the appropriate OpenStack distribution given the cloud config from the deployment object the engine was initialized with (possibly using one of available server providers). The method should also return a dictionary with endpoints of the deployed OpenStack distribution;
• cleanup(), which should clean up the OpenStack deployment (again, possibly using one of available server providers).

Below you will find a short but informative description of deploy engines implemented in Rally.

Available Deploy engines

DummyEngine

Description

This engine does not deploy anything, but uses an existing OpenStack deployment. It may be useful in case you have a preconfigured OpenStack deployment ready for benchmark scenarios launching.

Configuration Example

   {
       "name": "DummyEngine",
       "endpoint": {
               "auth_url": "http://192.168.122.22:5000/v2.0/",
               "username": "admin",
               "password": "password",
               "tenant_name": "admin"
       }
   }

All you should specify in the config are the OpenStack cloud endpoints: the uri and also admin credentials, including tenant name. Rally will use the specified admin account to manage temporary non-admin tenants and users exploited while launching benchmark scenarios.

DevstackEngine

Description

This engine deploys a Devstack cloud using the given Devstack repository.

Configuration Example

   {
       "name": "DevstackEngine",
       "localrc": {
           "ADMIN_PASSWORD": "secret",
           "NOVA_REPO": "git://example.com/nova/",
           ...
       },
       "devstack_repo": "git://example.com/devstack/",
       "provider": {
           "name": "${PROVIDER_NAME}",
           ...
       }
   }

The localrc field of the Devstack engine configuration will be used to initialize the Devstack's localrc file. As this deploy engine is not a dummy one, it also needs a concrete server provider specification: the name of the used provider (${PROVIDER_NAME}), followed by provider-specific fields configuration.

Note

More Deploy engines are to come in future releases, namely deploy engines for FUEL, Tripple-O etc. Stay tuned.