Alexis Lee 5ac9e6b189 Add an overview diagram to the userguide

The diagram covers the tools used to configure the base image for use as
a TripleO instance, both pre and post build time. It mentions
diskimage-builder, tripleo-image-elements, os-collect-config,
os-refresh-config, os-apply-config and Heat.

Change-Id: I68b8f90efd0f92a8a35baa53733bbc2a7145cefc

2014-05-30 16:42:30 +01:00

1.2 KiB

Raw Blame History

Using TripleO

Learning

Learning how TripleO all works is essential. Working through devtest is highly recommended.

Overview

Setup

The script install-dependencies from incubator will install the basic tools needed to build and deploy images via TripleO. What it won't do is larger scale tasks like configuring a Ubuntu/Fedora/etc mirror, a pypi mirror, squid or similar HTTP caches etc. If you are deploying rarely, these things are optional.

However, if you are building lots of images, having a local mirror of the things you are installing can be extremely advantageous.

Operating

The general design of TripleO is intended to produce small unix-like tools that can be used to drive arbitrary cloud deployments. It is expected that you will either wrap them in higher order tools (such as CM tools, custom UI's or even just targeted scripts). TripleO is building a dedicated API to unify all these small tools for common case deployments, called Tuskar, but that is not yet ready for prime time. We'll start using it ourselves as it becomes ready.

Take the time to learn the plumbing - nova, nova-bm or ironic, glance, keystone etc.

1.2 KiB Raw Blame History