
The OpenStack Ansible Deployment manifesto [1] was lost in times in pages long forgotten of the wiki. Instead, it should be part of the documentation, in our reference section. The reference is a great place because it's where we explain WHY we are doing things. To increase visibility of this page, the design decisions are directly linked from the deploy guide appendix about "Why OpenStack-Ansible". Change-Id: Ifb3ef041c773ee6dbe6606e2e5efc0542776dfc5
20 lines
385 B
ReStructuredText
20 lines
385 B
ReStructuredText
============
|
|
Architecture
|
|
============
|
|
|
|
Many operational requirements have been taken into consideration for
|
|
the design of the OpenStack-Ansible project.
|
|
|
|
In this chapter, you can find details about `why` OpenStack-Ansible
|
|
was architected in this way.
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
|
|
manifesto.rst
|
|
security.rst
|
|
service-arch.rst
|
|
storage-arch.rst
|
|
container-networking.rst
|
|
|