openstack/fuel-library
Code Issues Proposed changes

unification docs arrangement

Browse Source
This commit is contained in:
Alexey Abashkin 2012-12-25 14:41:35 +04:00
parent 406e4c65e2
commit 88fb1ea031
8 changed files with 48 additions and 38 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/pages/0010-package-contents.rst
View File

@ -3,12 +3,5 @@ Package Contents
.. contents:: :local:
Fuel package contains the following items:
#. Puppet and Cobbler automation
* resides in Fuel distribution under /deployment directory
#. Access to Mirantis repository of OpenStack packages
* all packages are installed from http://download.mirantis.com
#. Configuration guide
* available online through Fuel portal http://fuel.mirantis.com
.. include:: package-contents/0010-package-contents.rst

11
docs/pages/0020-how-it-works.rst
View File

@ -3,13 +3,4 @@ How It Works
.. contents:: :local:
Fuel provides the following important bits in order to streamline the process of installing and managing OpenStack:
* Automation & instructions to install master node with Puppet Master and Cobbler
* Snippets, kickstart and preseed files for Cobbler
* Puppet manifests for all OpenStack components
In order to use Fuel, one should create a master node first. Then a configuration should be supplied for an OpenStack installation -- the description of physical nodes, layout of OpenStack components, as well as desired OpenStack settings. After that Fuel automatically performs the deployment procedure according to the reference architecture with built-in high availability for OpenStack components. It performs bare metal provisioning of hardware nodes first, and then does the installation and setup of an OpenStack cloud:
.. image:: https://docs.google.com/drawings/pub?id=15vTTG2_575M7-kOzwsYyDmQrMgCPT2joLF2Cgiyzv7Q&w=678&h=617
.. include:: how-it-works/0010-how-it-works.rst

16
docs/pages/0030-supported-software-versions.rst
View File

@ -3,19 +3,5 @@ Supported Software & Versions
.. contents:: :local:
Fuel has been tested and is guaranteed to work with the following software components:
.. include:: supported-software-versions/0010-supported-software-versions.rst
* Operating Systems
* CentOS 6.3 (x86_64 architecture only)
* RHEL 6.3 (x86_64 architecture only)
* Ubuntu 12.04 (x86_64 architecture only)
* Puppet (IT automation tool)
* 2.7.19
* 3.0.0
* Cobbler (bare metal provisioning tool)
* 2.2.3
* OpenStack
* Folsom release

6
docs/pages/0060-frequently-asked-questions.rst
View File

@ -3,8 +3,4 @@ FAQ (Frequently Asked Questions)
.. contents:: :local:
#. **[Q]** Why did you decide to provide OpenStack packages through your own repository at http://download.mirantis.com?
**[A]** We are fully committed to providing our customers with working and stable bits and pieces in order to make successful OpenStack deployments. It is important to mention that we do not distribute our own version of OpenStack, we rather provide a plain vanilla distribution. So there is no vendor lock-in, and our repository just keeps the history of OpenStack packages certified to work with our Puppet manifests.
The benefit is that at any moment in time you can install any OpenStack version you want. If you are running Essex, you just need to use Puppet manifests which reference OpenStack packages for Essex from our repository. Once Folsom came out, we added new OpenStack packages for Folsom to our repository and created a separate branch with the corresponding Puppet manifests (which, in turn, reference these packages). With EPEL it would not be possible, as it only keeps the latest version for OpenStack packages.
.. include:: frequently-asked-questions/0010-frequently-asked-questions.rst

6
docs/pages/frequently-asked-questions/0010-frequently-asked-questions.rst Normal file
View File

@ -0,0 +1,6 @@
#. **[Q]** Why did you decide to provide OpenStack packages through your own repository at http://download.mirantis.com?
**[A]** We are fully committed to providing our customers with working and stable bits and pieces in order to make successful OpenStack deployments. It is important to mention that we do not distribute our own version of OpenStack, we rather provide a plain vanilla distribution. So there is no vendor lock-in, and our repository just keeps the history of OpenStack packages certified to work with our Puppet manifests.
The benefit is that at any moment in time you can install any OpenStack version you want. If you are running Essex, you just need to use Puppet manifests which reference OpenStack packages for Essex from our repository. Once Folsom came out, we added new OpenStack packages for Folsom to our repository and created a separate branch with the corresponding Puppet manifests (which, in turn, reference these packages). With EPEL it would not be possible, as it only keeps the latest version for OpenStack packages.

11
docs/pages/how-it-works/0010-how-it-works.rst Normal file
View File

@ -0,0 +1,11 @@
Fuel provides the following important bits in order to streamline the process of installing and managing OpenStack:
* Automation & instructions to install master node with Puppet Master and Cobbler
* Snippets, kickstart and preseed files for Cobbler
* Puppet manifests for all OpenStack components
In order to use Fuel, one should create a master node first. Then a configuration should be supplied for an OpenStack installation -- the description of physical nodes, layout of OpenStack components, as well as desired OpenStack settings. After that Fuel automatically performs the deployment procedure according to the reference architecture with built-in high availability for OpenStack components. It performs bare metal provisioning of hardware nodes first, and then does the installation and setup of an OpenStack cloud:
.. image:: https://docs.google.com/drawings/pub?id=15vTTG2_575M7-kOzwsYyDmQrMgCPT2joLF2Cgiyzv7Q&w=678&h=617

10
docs/pages/package-contents/0010-package-contents.rst Normal file
View File

@ -0,0 +1,10 @@
Fuel package contains the following items:
#. Puppet and Cobbler automation
* resides in Fuel distribution under /deployment directory
#. Access to Mirantis repository of OpenStack packages
* all packages are installed from http://download.mirantis.com
#. Configuration guide
* available online through Fuel portal http://fuel.mirantis.com

17
docs/pages/supported-software-versions/0010-supported-software-versions.rst Normal file
View File

@ -0,0 +1,17 @@
Fuel has been tested and is guaranteed to work with the following software components:
* Operating Systems
* CentOS 6.3 (x86_64 architecture only)
* RHEL 6.3 (x86_64 architecture only)
* Ubuntu 12.04 (x86_64 architecture only)
* Puppet (IT automation tool)
* 2.7.19
* 3.0.0
* Cobbler (bare-metal provisioning tool)
* 2.2.3
* OpenStack
* Folsom release