minor doc changes coordinated with Nick
This commit is contained in:
parent
e4a7d1986d
commit
c20a48cfc8
@ -1,7 +1,7 @@
|
|||||||
.. _Create-Cluster:
|
.. _Create-Cluster:
|
||||||
|
|
||||||
Create an example multi-node OpenStack cluster using Fuel
|
Create a multi-node OpenStack cluster using Fuel
|
||||||
=========================================================
|
================================================
|
||||||
|
|
||||||
.. contents:: :local:
|
.. contents:: :local:
|
||||||
|
|
||||||
|
@ -232,7 +232,7 @@ These values don't actually relate to Quantum; they are used by nova-network. I
|
|||||||
|
|
||||||
#Which IP have Quantum network node?
|
#Which IP have Quantum network node?
|
||||||
$quantum_net_node_hostname = 'fuel-controller-03'
|
$quantum_net_node_hostname = 'fuel-controller-03'
|
||||||
$quantum_host = $controller_internal_addresses[$quantum_hostname]
|
$quantum_net_node_address = $controller_internal_addresses[$quantum_net_node_hostname]
|
||||||
|
|
||||||
If you are installing Quantum in non-HA mode, you will need to specify which single controller controls Quantum. ::
|
If you are installing Quantum in non-HA mode, you will need to specify which single controller controls Quantum. ::
|
||||||
|
|
||||||
@ -324,7 +324,7 @@ Fuel enables you to control multiple deployments simultaneously by setting an in
|
|||||||
|
|
||||||
# This parameter specifies the the identifier of the current cluster. This is needed in case of multiple environments.
|
# This parameter specifies the the identifier of the current cluster. This is needed in case of multiple environments.
|
||||||
# installation. Each cluster requires a unique integer value.
|
# installation. Each cluster requires a unique integer value.
|
||||||
# Valid identifier range is 1 to 254
|
# Valid identifier range is 0 to 254
|
||||||
$deployment_id = '79'
|
$deployment_id = '79'
|
||||||
|
|
||||||
Enabling Cinder
|
Enabling Cinder
|
||||||
@ -461,13 +461,13 @@ Configuring OpenStack to use syslog
|
|||||||
To use the syslog server, adjust the corresponding variables in the ``if $use_syslog`` clause::
|
To use the syslog server, adjust the corresponding variables in the ``if $use_syslog`` clause::
|
||||||
|
|
||||||
$use_syslog = true
|
$use_syslog = true
|
||||||
if $use_syslog {
|
if $use_syslog {
|
||||||
class { "::rsyslog::client":
|
class { "::rsyslog::client":
|
||||||
log_local => true,
|
log_local => true,
|
||||||
log_auth_local => true,
|
log_auth_local => true,
|
||||||
server => '127.0.0.1',
|
server => '127.0.0.1',
|
||||||
port => '514'
|
port => '514'
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
||||||
@ -508,7 +508,7 @@ To tell Fuel to download packages from external repos provided by Mirantis and y
|
|||||||
$enable_test_repo = false
|
$enable_test_repo = false
|
||||||
$repo_proxy = 'http://10.20.0.100:3128'
|
$repo_proxy = 'http://10.20.0.100:3128'
|
||||||
|
|
||||||
Once again, the ``$mirror_tyoe`` **must** be set to ``default``. If you set it correctly in ``config.yaml`` and ran ``openstack_system`` this will already be taken care of. Otherwise, **make sure** to set this value yourself.
|
Once again, the ``$mirror_type`` **must** be set to ``default``. If you set it correctly in ``config.yaml`` and ran ``openstack_system`` this will already be taken care of. Otherwise, **make sure** to set this value yourself.
|
||||||
|
|
||||||
Future versions of Fuel will enable you to use your own internal repositories.
|
Future versions of Fuel will enable you to use your own internal repositories.
|
||||||
|
|
||||||
@ -555,8 +555,6 @@ Using the ``$horizon_use_ssl`` variable, you have the option to decide whether t
|
|||||||
# 'custom': require fileserver static mount point [ssl_certs] and hostname based certificate existence
|
# 'custom': require fileserver static mount point [ssl_certs] and hostname based certificate existence
|
||||||
$horizon_use_ssl = false
|
$horizon_use_ssl = false
|
||||||
|
|
||||||
class compact_controller (
|
|
||||||
|
|
||||||
This variable accepts the following values:
|
This variable accepts the following values:
|
||||||
|
|
||||||
* ``false``: In this mode, the dashboard uses HTTP with no encryption.
|
* ``false``: In this mode, the dashboard uses HTTP with no encryption.
|
||||||
|
@ -22,7 +22,7 @@ The Fuel User's Guide is organized as follows:
|
|||||||
|
|
||||||
* Section 2, :ref:`Reference Architecture <Reference-Archiecture>`, provides a general look at the components that make up OpenStack, and describes the reference architecture to be instantiated in Section 3.
|
* Section 2, :ref:`Reference Architecture <Reference-Archiecture>`, provides a general look at the components that make up OpenStack, and describes the reference architecture to be instantiated in Section 3.
|
||||||
|
|
||||||
* Section 3, :ref:`Create an example multi-node OpenStack cluster using Fuel <Create-Cluster>`, takes you step-by-step through the process of creating a high-availability OpenStack cluster.
|
* Section 3, :ref:`Create a multi-node OpenStack cluster using Fuel <Create-Cluster>`, takes you step-by-step through the process of creating a high-availability OpenStack cluster.
|
||||||
|
|
||||||
* Section 4, :ref:`Production Considerations <Production>`, looks at the real-world questions and problems involved in creating an OpenStack cluster for production use. It discusses issues such as network layout and hardware requirements, and provides tips and tricks for creating a cluster of up to 100 nodes.
|
* Section 4, :ref:`Production Considerations <Production>`, looks at the real-world questions and problems involved in creating an OpenStack cluster for production use. It discusses issues such as network layout and hardware requirements, and provides tips and tricks for creating a cluster of up to 100 nodes.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user