24272bbe95
Here we enhance the rst docs (used for readthedocs): * Simplify its index structure by reducing it to only 5 points: 1. Deploy (engines & server providers) 2. Verify 3. Benchmark (scenarios, engine, contexts, plugins) 4. Command Line Interface 5. Implementation (all source docs moved here) * Extend the 'Benchmark' page with info from the "Main concepts" page from Wiki * Add some introductory text on Deploy & Verify parts based on that from Wiki * Simplify headings by removing "The" and "Layer" Change-Id: I04bb553aba04009634272a88a757baa8f2c8c359
2.5 KiB
2.5 KiB
Deploy
Deployment engines
One of the core entities in Rally architecture are the Deploy engines. The main 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).
Server Providers
Server providers in Rally are typically used by deploy engines to manage virtual machines necessary for OpenStack deployment and its following benchmarking. The key feature of server providers is that they provide a unified interface for interacting with different virtualization technologies (LXS, Virsh etc.) and cloud suppliers (like Amazon).
Every server provider should implement the following basic interface:
- constructor, which should take the deployment entity the provider should bind to and a config dictionary as its parameters;
- create_servers(image_uuid, type_id, amount), which should create the requested number of virtual machines of the given type using a specific image. The method should also return the list of created servers wrapped in special Server entities.
- destroy_servers(), which should destroy all virtual machines previously created by the same server provider.