Difference between revisions of "Rally/ArchitectureForDevelopers"

Latest revision as of 05:56, 12 December 2013

The way the Rally benchmark engine is launches benchmark scenario is visualized on the sequence diagram below.

@@ Line 1: / Line 1: @@
-=Rally architecture for developers=
+==Rally architecture for developers==
-==Class diagram==
+===Sequence diagram for benchmark engine===
-The UML class diagram shown below demostrates the core classes in Rally as well as the relationships between them.
+The way the Rally benchmark engine is launches benchmark scenario is visualized on the sequence diagram below.
-[[File:RallyClassDiagram.png|Rally class diagram]]
+[[File:RallySequenceDiagramBenchmarkEngine.png|Rally sequence diagram for benchmark engine]]
-The ''Orchestrator'' class, which is responsible for launching the entire system working cycle, uses ''Task'' to register a benchmarking task and ''EngineFactory'' to choose an appropriate ''DeployEngine'' subclass (which deploys OpenStack according to the user configuration). Finally, the ''Orchestrator'' then uses a ''TestEngine'' instance to initiate the cloud verification and benchmarking process. ''DeployEngine'' subclasses also may use ''ProviderFactory'' to get a ''ServerProvider'' instance which allows to deploy OpenStack properly on a (virtual) server.
-==Sequence diagram==
-The relationships described above are also visualized on a sequence diagram.
-[[File:RallySequenceDiagram.png|Rally class diagram]]