Jump to: navigation, search

Difference between revisions of "Rally/HowToExtendRally"

(DevstackEngine)
(Rewritten)
Line 1: Line 1:
=Available Deploy Engines=
+
=Extend Rally functionality=
  
==DummyEngine==
+
==Add Server providers==
 +
Stay tuned.
  
===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",
 
        "cloud_config": {
 
            ''(specify here the cloud endpoints)''
 
            "identity": {
 
                "url": "http://192.168.122.22/",
 
                "uri": "http://192.168.122.22:5000/v2.0/",
 
                "admin_username": "admin",
 
                "admin_password": "password",
 
                "admin_tenant_name": "demo"
 
            }
 
        }
 
    }
 
  
 +
==Add Deploy engines==
 +
Stay tuned.
  
  
==DevstackEngine==
+
==Add Benchmark scenarios==
 
+
Stay tuned.
===Description===
 
This engine deploys a DevStack cloud using the given DevStack repository. As this deploy engine is not a dummy one, it also needs a concrete [[ServerProviders|Server Provider]] to be specified in the config.
 
 
 
===Configuration Example===
 
    {
 
        "name": "DevstackEngine",
 
        "localrc": {
 
            "ADMIN_PASSWORD": "secret",
 
            ...
 
        },
 
        "devstack_repo": "git://example.com/devstack/",
 
        "provider": {
 
            "name": "''%PROVIDER_NAME''",
 
          ...
 
        }
 
    }
 
 
 
=Note=
 
More Deploy engines are to come in future releases, namely deploy engines for FUEL, Tripple-O etc. Stay tuned.
 

Revision as of 17:33, 14 October 2013

Extend Rally functionality

Add Server providers

Stay tuned.


Add Deploy engines

Stay tuned.


Add Benchmark scenarios

Stay tuned.