openstack/openstack-ansible
Code Issues Proposed changes

docs: update information about OSA

Browse Source 
Change-Id: If25b66c5d6e9122f42b6aa1a342a4938357a602c
This commit is contained in:
Ivan Anfimov
2025-05-04 08:52:57 +00:00
parent 4952ff51fb
commit c83bcb4a10
1 changed files with 12 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
doc/source/reference/aboutosa.rst
View File

@@ -1,21 +1,19 @@
.. _app-aboutosa:
=======================
About OpenStack-Ansible
=======================
OpenStack-Ansible (OSA) uses the `Ansible <https://www.ansible.com/how-ansible-works>`_
OpenStack-Ansible (OSA) uses the `Ansible <https://docs.ansible.com/ansible/latest/getting_started/index.html>`_
IT automation engine to deploy an OpenStack environment on Ubuntu, Debian
and CentOS Stream (including derivatives like Rocky Linux)
and CentOS Stream (including derivatives like Rocky Linux).
For isolation and ease of maintenance, all OpenStack services are installed by
default from source code into python virtual environments.
The services are further isolated via the use of LXC containers, but these are
optional and a bare metal based installation is also possible.
optional and a bare-metal-based installation is also possible.
The OpenStack-Ansible manifesto
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
OpenStack-Ansible Manifesto
~~~~~~~~~~~~~~~~~~~~~~~~~~~
All the design considerations (the container architecture, the ability to
override any code, the network considerations, etc.) of this project are
@@ -24,14 +22,15 @@ listed in our :dev_docs:`architecture reference <reference/architecture/index.ht
Why choose OpenStack-Ansible?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* Supports the major Linux distributions Ubuntu, CentOS/Rocky, Debian.
* Supports the major Linux distributions Ubuntu, CentOS Stream, Rocky Linux
and Debian.
* 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
extra wiring and optimized 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.
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
@@ -42,9 +41,9 @@ Why choose OpenStack-Ansible?
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
* If your company is already invested in other configuration management
system (Puppet) and does not want to use Ansible we recommend
building on your existing knowledge and experimenting with a different
OpenStack deployment project.
* You want to deploy OpenStack with 100% application containers.
We currently support LXC containers, if you want to go 100% Docker,