openstack/openstack-ansible
Code Issues Proposed changes

docs: add a decision help

Browse Source 
There are a lot of different approaches to deploy OpenStack to your
environment. Namely Puppet, Chef, Helm, Juju, Fuel, TripleO, Kolla
and probably more. The designated OpenStack operators would benefit
from high-level decision help when and when not to chose openstack-
ansible. This does not imply that one project is "better" than the
others.
This change adds a few bullet points to the docs which might help
designated operators to make their decision, because switching that
decision when the OpenStack cloud is in production might not be that
easy.

Change-Id: I26e1b22010f56b1fb6eda7a02f9f31f79c3adc15
This commit is contained in:
Markus Zoeller 2017-09-14 09:41:02 -06:00 committed by Alexandra Settle
parent bf1835b919
commit c3ce038737
1 changed files with 33 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
deploy-guide/source/overview-osa.rst
View File

@ -7,6 +7,39 @@ IT automation engine to deploy an OpenStack environment on Ubuntu Linux.
For isolation and ease of maintenance, you can install OpenStack components
into Linux containers (LXC).
Why choose OpenStack-Ansible?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* Supports the major Linux distributions Ubuntu, CentOS (WIP) and OpenSUSE
(WIP).
* Supports the major CPU architectures x86, ppc64, s390x (WIP).
* Offers automation for upgrades between major OpenStack releases.
* Uses OpenStack defaults for each of the project roles, and provides
extra wiring and optimised configuration when combining projects
together.
* Does not implement its own DSL, and uses wherever possible Ansible
directly. All the experience acquired using Ansible can be used in
openstack-ansible, and the other way around.
* You like to use reliable, proven technology. We try to run OpenStack
with a minimum amount of packages that are not provided by distributions
or the OpenStack community. Less dependencies and distribution tested
software make the project more reliable.
* You want to be able to select how to deploy on your hardware: deploy
partially on metal, fully on metal, or fully in machine containers.
When **not** to choose OpenStack-Ansible?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* If your company is already invested with other configuration management
systems, Puppet or Chef, and does not want to use Ansible we recommend
re-using your knowledge and experimenting with a different
OpenStack deployment project.
* You want to deploy OpenStack with 100% application containers.
We currently support machine containers, with lxc and we will support
*systemd-nspawn* in the future (WIP). If you want to go 100% Docker,
there are other projects in the OpenStack community that can
help you.
Ansible
~~~~~~~