Merge "Removed mentioning of CentOS" into stable/7.0

contents/contents-planning-guide.rst

@@ -2,7 +2,6 @@
 .. include:: /pages/planning-guide/0020-system-requirements.rst
 .. include:: /pages/planning-guide/4000-planning-summary.rst
 .. include:: /pages/planning-guide/4200-net-topology.rst
-.. include:: /pages/planning-guide/4300-linux-distro.rst
 .. include:: /pages/planning-guide/4360-storage-plan.rst
 .. include:: /pages/planning-guide/4400-nodes-roles.rst
 .. include:: /pages/planning-guide/4450-monitoring.rst

pages/planning-guide/0020-system-requirements.rst

@@ -38,7 +38,6 @@ Some general remarks:
 - Select peripheral hardware that is supported
   by the operating system distribution
   that you are using for the target nodes
-  (see :ref:`linux-distro-plan`)
   and for the VM instances that will be deployed.
 
   Integrating new hardware drivers

pages/planning-guide/4000-planning-summary.rst

@@ -21,9 +21,6 @@ complete to plan the Mirantis OpenStack deployment.
 | Select a network topology  | See :ref:`net-topology-plan`              |
 |                            |                                           |
 +----------------------------+-------------------------------------------+
-| Choose the Linux distro    | See :ref:`linux-distro-plan`              |
-| to use on your nodes       |                                           |
-+----------------------------+-------------------------------------------+
 | Determine how many nodes   | See :ref:`nodes-roles-plan`               |
 | to deploy and which roles  |                                           |
 | to assign to each and      |                                           |

pages/planning-guide/4300-linux-distro.rst

@@ -1,24 +0,0 @@
-
-.. _linux-distro-plan:
-
-Linux Distribution for Nodes
-============================
-
-Fuel allows you to deploy either the CentOS or Ubuntu
-Linux distribution as the Host O/S on the nodes.
-All nodes in the environment must run the same Linux distribution.
-Often, the choice is made based on personal preference;
-many administrative tasks on the nodes
-must be performed at shell level
-and many people choose the distribution
-with which they are most comfortable.
-
-Some specific considerations:
-
-- Each distribution has some hardware support issues.
-  See :ref:`release-notes` for details about known issues.
-- In particular, the CentOS version used for OpenStack
-  does not include native support for VLANs
-  while the Ubuntu version does.
-- CentOS supports .rpm packages; Ubuntu supports .deb packages.
-

pages/reference-architecture/9000-fuel-provision.rst

@@ -30,10 +30,6 @@ repositories in a directory which is then packed into the operating system
 image. The build script is run once no matter how many nodes one is going
 to deploy.
 
-Currently, the CentOS image is built at the development stage and then
-this image is put into Mirantis OpenStack ISO and used for all CentOS
-based environments.
-
 Ubuntu images are built on the master node, one operating system image
 per environment. We need to build different images for each environment
 because each environment has its own set of repositories. In order to

pages/user-guide/7300-vcenter.rst

@@ -29,12 +29,11 @@ to launch the wizard that creates a new OpenStack environment.
 
 .. _vcenter-start-create-env-ug:
 
-Create Environment and Choose Distribution for vCenter
-++++++++++++++++++++++++++++++++++++++++++++++++++++++
+Create Environment
+++++++++++++++++++
 
-Either the CentOS or Ubuntu distro
-can be used as the host operating system on the Slave nodes
-for environments that support integration with vSphere:
+Select an OpenStack release and type a name for the OpenStack
+environment:
 
 .. image:: /_images/user_screen_shots/vcenter-create-env.png
 

pages/user-guide/initialize-fuel/0600-boot-nodes.rst

@@ -20,9 +20,8 @@ Master Node.
 #. Each node sends out DHCP discovery requests and gets the response from
    the Fuel Master node that runs the DHCP server.
 #. When a node receives the response from the Fuel Master node,
-   it fetches the pxelinux bootloader
-   and then the bootstrap image (CentOS based Linux in memory)
-   from the Fuel Master node's TFTP server and boots into it.
+   it fetches the pxelinux bootloader and then the bootstrap image from the
+   Fuel Master node's TFTP server and boots into it.
 #. When this image is loaded,
    it reports the node's readiness and configuration to the Fuel Master.
    This can take a few minutes.