<commit_before>---
title: RDO Manager Architecture Overview
authors: athomas, chrisw
wiki_title: RDO Manager Architecture Overview
wiki_revision_count: 16
wiki_last_updated: 2015-04-08
---

# RDO Manager Architecture Overview

RDO Manager Architecture Overview

QuickStart

This document lists the main components of RDO Manager, and gives some description of how each component is used. There are links to additional sources of information throughout the document. For those wishing to start actually using RDO Manager, the current installation documentation is here - <https://repos.fedorapeople.org/repos/openstack-m/instack-undercloud/html/index.html>

RDO Manager is a set of tools from deploying, and managing OpenStack which is built upon the TripleO project.

The name TripleO refers to three related things:

A design pattern, where an underlying OpenStack instance is used to deploy and then to manage another, usually more complex, OpenStack instance. A set of configuration files and scripts which contain OS image building rules and service configuration rules The upstream program within the OpenStack project which develops the various scripts and utilities which are combined to deliver the complete software solution.

The design pattern, where a sophisticated, general-purpose OpenStack instance is created by, and then runs on top of, a simpler, single-purpose deployment instance of OpenStack, is what gives TripleO its name. It is short for OpenStack On OpenStack.

Benefits

Using RDO Manager’s combination of OpenStack components, and their APIs, as the infrastructure to deploy and operate OpenStack itself delivers several benefits:

RDO Manager’s APIs \*are\* the OpenStack APIs. They’re well maintained, well documented, and come with client libraries and command line tools. Users who invest time in learning about RDO manager’s APIs are also learning about OpenStack itself, and users who are already familiar with OpenStack will find a great deal in RDO Manager that they already understand. Using the OpenStack components allows more rapid feature development of RDO Manager than might otherwise be the case; RDO Manager automatically inherits all the new features which are added to Glance, Heat etc., even when the developer of the new feature didn’t explicitly have TripleO and RDO Manager in mind. The same applies to bug fixes and security updates. When OpenStack developers fix bugs in the common components, those fixes are inherited by RDO Manager Users’ can invest time in integrating their own scripts and utilities with RDO Manager’s APIs with some confidence. Those APIs are cooperatively maintained and developed by the OpenStack community. They’re not at risk of being suddenly changed or retired by a single controlling vendor. For developers, tight integration with the openstack APIs provides a solid architecture, which has gone through extensive community review.

It should be noted that not everything in RDO Manager is a reused OpenStack element. The Tuskar API, for example (which lets users design the workload cloud that they want to deploy), is found in RDO Manager but not, so far at least, in a typical Openstack instance. The Tuskar API is described in more detail below.

Deploying the workload cloud with RDO Manager
<commit_msg>Updated RDO Manager Architecture Overview<commit_after>---
title: RDO Manager Architecture Overview
authors: athomas, chrisw
wiki_title: RDO Manager Architecture Overview
wiki_revision_count: 16
wiki_last_updated: 2015-04-08
---

# RDO Manager Architecture Overview

RDO Manager Architecture Overview

## QuickStart

This document lists the main components of RDO Manager, and gives some description of how each component is used. There are links to additional sources of information throughout the document. For those wishing to start actually using RDO Manager, the current installation documentation is here - <https://repos.fedorapeople.org/repos/openstack-m/instack-undercloud/html/index.html>

RDO Manager is a set of tools from deploying, and managing OpenStack which is built upon the TripleO project.

The name TripleO refers to three related things:

A design pattern, where an underlying OpenStack instance is used to deploy and then to manage another, usually more complex, OpenStack instance. A set of configuration files and scripts which contain OS image building rules and service configuration rules The upstream program within the OpenStack project which develops the various scripts and utilities which are combined to deliver the complete software solution.

The design pattern, where a sophisticated, general-purpose OpenStack instance is created by, and then runs on top of, a simpler, single-purpose deployment instance of OpenStack, is what gives TripleO its name. It is short for OpenStack On OpenStack.

Benefits

Using RDO Manager’s combination of OpenStack components, and their APIs, as the infrastructure to deploy and operate OpenStack itself delivers several benefits:

RDO Manager’s APIs \*are\* the OpenStack APIs. They’re well maintained, well documented, and come with client libraries and command line tools. Users who invest time in learning about RDO manager’s APIs are also learning about OpenStack itself, and users who are already familiar with OpenStack will find a great deal in RDO Manager that they already understand. Using the OpenStack components allows more rapid feature development of RDO Manager than might otherwise be the case; RDO Manager automatically inherits all the new features which are added to Glance, Heat etc., even when the developer of the new feature didn’t explicitly have TripleO and RDO Manager in mind. The same applies to bug fixes and security updates. When OpenStack developers fix bugs in the common components, those fixes are inherited by RDO Manager Users’ can invest time in integrating their own scripts and utilities with RDO Manager’s APIs with some confidence. Those APIs are cooperatively maintained and developed by the OpenStack community. They’re not at risk of being suddenly changed or retired by a single controlling vendor. For developers, tight integration with the openstack APIs provides a solid architecture, which has gone through extensive community review.

It should be noted that not everything in RDO Manager is a reused OpenStack element. The Tuskar API, for example (which lets users design the workload cloud that they want to deploy), is found in RDO Manager but not, so far at least, in a typical Openstack instance. The Tuskar API is described in more detail below.

Deploying the workload cloud with RDO Manager

{'fraction_non_alphanumeric': 0.030243459851807045, 'fraction_numerical': 0.0030243459851807047, 'mean_word_length': 5.056776556776557, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3955045', 'n_tokens_mistral': 1511, 'n_tokens_neox': 1412, 'n_words': 968}