Difference between revisions of "Rally/ArchitectureForDevelopers"
< Rally
(→Sequence diagram) |
Aovchinnikov (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | =Rally architecture for developers= | + | ==Rally architecture for developers== |
| − | ==Class diagram== | + | ===Class diagram=== |
The UML class diagram shown below demostrates the core classes in Rally as well as the relationships between them. | The UML class diagram shown below demostrates the core classes in Rally as well as the relationships between them. | ||
| Line 8: | Line 8: | ||
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. | 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== | + | ===Sequence diagram=== |
The relationships described above are also visualized on a sequence diagram. | The relationships described above are also visualized on a sequence diagram. | ||
[[File:RallySequenceDiagram.png|Rally sequence diagram]] | [[File:RallySequenceDiagram.png|Rally sequence diagram]] | ||
Revision as of 08:59, 24 October 2013
Rally architecture for developers
Class diagram
The UML class diagram shown below demostrates the core classes in Rally as well as the relationships between them.
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.
