Remove duplicate spaces
Change-Id: Icc70c9c3b19701f103ceb46fb04f76a82d83a4f7
This commit is contained in:
Christian Berendt
parent
d74779e10f
commit
f31a39ea52
@ -15,7 +15,7 @@
|
||||
<para>The Block Storage API service is named
|
||||
<literal>openstack-cinder-api</literal> on the following
|
||||
distributions: CentOS, Fedora, openSUSE, Red Hat Enterprise
|
||||
Linux, and SUSE Linux Enterprise. In Ubuntu and Debian
|
||||
Linux, and SUSE Linux Enterprise. In Ubuntu and Debian
|
||||
distributions, the Block Storage API service is named
|
||||
<literal>cinder-api</literal>.</para>
|
||||
</note>
|
||||
|
||||
@ -342,7 +342,7 @@ external_network_bridge = br-ex-2</programlisting>
|
||||
configuration.</para>
|
||||
<note>
|
||||
<para>If the Linux installation does not support network namespaces, you must
|
||||
disable network namespaces in the L3 metering configuration file. The default
|
||||
disable network namespaces in the L3 metering configuration file. The default
|
||||
value of the <option>use_namespaces</option> option is <code>True</code>.</para>
|
||||
</note>
|
||||
<para><programlisting language="ini">use_namespaces = False</programlisting></para>
|
||||
|
||||
@ -85,7 +85,7 @@
|
||||
aid in recovery and resiliency of services in order to meet
|
||||
strict SLAs.</para>
|
||||
</section>
|
||||
<section xml:id="capacity-planning-operational">
|
||||
<section xml:id="capacity-planning-operational">
|
||||
<title>Capacity planning</title>
|
||||
<para>Adding extra capacity to an OpenStack cloud is an easy
|
||||
horizontally scaling process, as consistently configured nodes
|
||||
|
||||
@ -364,7 +364,7 @@
|
||||
<listitem>
|
||||
<para>
|
||||
Where instances and images will be stored will influence
|
||||
the architecture. For example, instances can be stored
|
||||
the architecture. For example, instances can be stored
|
||||
in a number of options. OpenStack Block Storage is a
|
||||
good location for instances because it is persistent
|
||||
block storage, however, OpenStack Object Storage can be
|
||||
@ -626,7 +626,7 @@
|
||||
system and hypervisor combination. Finally, it is important to
|
||||
ensure that the networking hardware selection and topology will
|
||||
work with the chosen operating system and hypervisor
|
||||
combination. For example, if the design uses Link Aggregation
|
||||
combination. For example, if the design uses Link Aggregation
|
||||
Control Protocol (LACP), the OS and hypervisor both need to
|
||||
support it.</para>
|
||||
<para>Some areas that could be impacted by the selection of OS and
|
||||
|
||||
@ -50,7 +50,7 @@
|
||||
cloud instances using cloud orchestration or configuration
|
||||
management tools, driven by the CMP, for more specific
|
||||
templating. Another more expensive option is to use a
|
||||
commercial image migration tool. The issue of image
|
||||
commercial image migration tool. The issue of image
|
||||
portability is not just for a one time migration. If the
|
||||
intention is to use the multiple cloud for disaster recovery,
|
||||
application diversity or high availability, the images and
|
||||
|
||||
@ -127,7 +127,7 @@
|
||||
networks, or GPU cards.</para>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata contentwidth="4in"
|
||||
<imagedata contentwidth="4in"
|
||||
fileref="../images/Massively_Scalable_Cells_+_regions_+_azs.png"
|
||||
/>
|
||||
</imageobject>
|
||||
|
||||
@ -49,7 +49,7 @@
|
||||
<para>
|
||||
There are a number of commercial products available today that
|
||||
provide such a broker solution but nothing that is native in
|
||||
the OpenStack project. Not providing a broker is also
|
||||
the OpenStack project. Not providing a broker is also
|
||||
an option, but managing this manually would not suffice as a
|
||||
large scale, enterprise solution.
|
||||
</para>
|
||||
|
||||
@ -24,7 +24,7 @@
|
||||
<para>In order to provide cryptography offloading to a set of
|
||||
instances, it is possible to use Image Service configuration
|
||||
options to assign the cryptography chip to a device node in
|
||||
the guest. The <citetitle>OpenStack Command Line
|
||||
the guest. The <citetitle>OpenStack Command Line
|
||||
Reference</citetitle> contains further information on
|
||||
configuring this solution in the chapter <link
|
||||
xlink:href="http://docs.openstack.org/cli-reference/content/chapter_cli-glance-property.html">Image
|
||||
|
||||
@ -14,7 +14,7 @@
|
||||
specifies options as <literal>key=value</literal> pairs,
|
||||
grouped into sections. The <literal>DEFAULT</literal> section
|
||||
contains most of the configuration options. Lines starting with a
|
||||
hash sign (<literal>#</literal>) are comment lines. For example:
|
||||
hash sign (<literal>#</literal>) are comment lines. For example:
|
||||
</para>
|
||||
<programlisting language="ini">[DEFAULT]
|
||||
# Print debugging output (set logging level to DEBUG instead
|
||||
@ -159,7 +159,7 @@ instance_format = "[instance: %(uuid)s] "</programlisting>
|
||||
<title>Substitution</title>
|
||||
|
||||
<para>
|
||||
The configuration file supports variable substitution. After
|
||||
The configuration file supports variable substitution. After
|
||||
you set a configuration option, it can be referenced in later
|
||||
configuration values when you precede it with a
|
||||
<literal>$</literal>, like
|
||||
@ -185,7 +185,7 @@ rabbit_hosts = $rabbit_host:$rabbit_port</programlisting>
|
||||
|
||||
<para>
|
||||
To avoid substitution, use <literal>$$</literal>, it is replaced
|
||||
by a single <literal>$</literal>. For example, if your LDAP DNS
|
||||
by a single <literal>$</literal>. For example, if your LDAP DNS
|
||||
password is <literal>$xkj432</literal>, specify it, as follows:
|
||||
<programlisting language="ini">ldap_dns_password = $$xkj432</programlisting>
|
||||
</para>
|
||||
|
||||
@ -15,7 +15,7 @@ options. For installation prerequisites and step-by-step walkthroughs, see the
|
||||
<section xml:id="section_keystone-cache">
|
||||
<title>Caching layer</title>
|
||||
<para>Identity supports a caching layer that is above the
|
||||
configurable subsystems, such as token or assignment. The
|
||||
configurable subsystems, such as token or assignment. The
|
||||
majority of the caching configuration options are set in the
|
||||
<literal>[cache]</literal> section. However, each section that
|
||||
has the capability to be cached usually has a
|
||||
|
||||
@ -129,7 +129,7 @@ name=api</programlisting></para>
|
||||
replacing <replaceable>cell1</replaceable> with the name
|
||||
of each
|
||||
cell:<programlisting language="ini">[DEFAULT]
|
||||
# Disable quota checking in child cells. Let API cell do it exclusively.
|
||||
# Disable quota checking in child cells. Let API cell do it exclusively.
|
||||
quota_driver=nova.quota.NoopQuotaDriver
|
||||
|
||||
[cells]
|
||||
|
||||
@ -22,7 +22,7 @@ xenapi_connection_password = your_password</programlisting>
|
||||
console, to your XenServer or XCP box.</para>
|
||||
<note><para>
|
||||
The <literal>xenapi_connection_url</literal> is generally the management
|
||||
network IP address of the XenServer. Though it is possible to use the
|
||||
network IP address of the XenServer. Though it is possible to use the
|
||||
internal network IP Address (169.250.0.1) to contact XenAPI, this does not
|
||||
allow live migration between hosts. Other functionalities such as host aggregates,
|
||||
do not work.
|
||||
|
||||
@ -19,7 +19,7 @@
|
||||
preparation of its environment, the details of which are beyond the
|
||||
scope of this guide.</para>
|
||||
<note><para>Some OpenStack Compute features are not implemented by
|
||||
the baremetal hypervisor driver. See the <link
|
||||
the baremetal hypervisor driver. See the <link
|
||||
xlink:href="http://wiki.openstack.org/HypervisorSupportMatrix">
|
||||
hypervisor support matrix</link> for details.</para></note>
|
||||
<para>For the Baremetal driver to be loaded and function properly,
|
||||
@ -33,8 +33,8 @@ scheduler_host_manager=nova.scheduler.baremetal_host_manager.BaremetalHostManage
|
||||
ram_allocation_ratio=1.0
|
||||
reserved_host_memory_mb=0</programlisting>
|
||||
<para>Many configuration options are specific to the
|
||||
Baremetal driver. Also, some additional steps are
|
||||
required, such as building the baremetal deploy ramdisk. See
|
||||
Baremetal driver. Also, some additional steps are
|
||||
required, such as building the baremetal deploy ramdisk. See
|
||||
the <link
|
||||
xlink:href="https://wiki.openstack.org/wiki/Baremetal">main wiki page</link> for details and implementation suggestions.
|
||||
</para>
|
||||
|
||||
@ -541,7 +541,7 @@ X-Trans-Id: tx602634cf478546a39b1be-0051e6bc7a</computeroutput></screen>
|
||||
<para>If all files are successfully deleted (or did not
|
||||
exist), the operation returns <code>HTTPOk</code>. If any
|
||||
files failed to delete, the operation returns
|
||||
<code>HTTPBadGateway</code>. In both cases, the response body
|
||||
<code>HTTPBadGateway</code>. In both cases, the response body
|
||||
is a JSON dictionary that shows the number of files that were
|
||||
successfully deleted or not found. The files that failed are
|
||||
listed.</para>
|
||||
|
||||
@ -5578,7 +5578,7 @@
|
||||
<para>
|
||||
Each OpenStack release has a code name. Code names ascend in
|
||||
alphabetical order: Austin, Bexar, Cactus, Diablo, Essex,
|
||||
Folsom, Grizzly, Havana, Icehouse, Juno, and Kilo. Code names are
|
||||
Folsom, Grizzly, Havana, Icehouse, Juno, and Kilo. Code names are
|
||||
cities or counties near where the corresponding OpenStack
|
||||
design summit took place. An exception, called the Waldon
|
||||
exception, is granted to elements of the state flag that
|
||||
|
||||
@ -7,7 +7,7 @@
|
||||
<title>Highly available Telemetry central agent</title>
|
||||
|
||||
<para>Telemetry (ceilometer) is the metering and monitoring service in
|
||||
OpenStack. The Central agent polls for resource utilization
|
||||
OpenStack. The Central agent polls for resource utilization
|
||||
statistics for resources not tied to instances or compute nodes.</para>
|
||||
<note>
|
||||
<para>Due to limitations of a polling model, a single instance of this agent
|
||||
|
||||
@ -8,11 +8,11 @@
|
||||
<title>Database</title>
|
||||
|
||||
<para>The first step is installing the database that sits at the heart of the
|
||||
cluster. When we talk about High Availability, we talk about several databases (for redundancy) and a
|
||||
means to keep them synchronized. In this case, we must choose the
|
||||
cluster. When we talk about High Availability, we talk about several databases (for redundancy) and a
|
||||
means to keep them synchronized. In this case, we must choose the
|
||||
MySQL database, along with Galera for synchronous multi-master replication.</para>
|
||||
<para>The choice of database isn’t a foregone conclusion; you’re not required
|
||||
to use MySQL. It is, however, a fairly common choice in OpenStack
|
||||
to use MySQL. It is, however, a fairly common choice in OpenStack
|
||||
installations, so we’ll cover it here.</para>
|
||||
|
||||
<xi:include href="ha_aa_db/section_ha_aa_db_mysql_galera.xml"/>
|
||||
|
||||
@ -115,7 +115,7 @@ address of that node, as in:
|
||||
</orderedlist>
|
||||
<screen><prompt>#</prompt> <userinput>service mysql start wsrep_cluster_address=gcomm://10.0.0.10</userinput></screen>
|
||||
<para>You also have the option to set the <literal>wsrep_cluster_address</literal> in the
|
||||
<filename>/etc/mysql/conf.d/wsrep.cnf</filename> file, or within the client itself. (In
|
||||
<filename>/etc/mysql/conf.d/wsrep.cnf</filename> file, or within the client itself. (In
|
||||
fact, for some systems, such as MariaDB or Percona, this may be your
|
||||
only option.)</para>
|
||||
<orderedlist numeration="arabic" inheritnum="ignore" continuation="restarts">
|
||||
|
||||
@ -93,7 +93,7 @@
|
||||
<title>Rackspace Cloud Builders (multiple distros)
|
||||
images</title>
|
||||
<para>Rackspace Cloud Builders maintains a list of pre-built images from various
|
||||
distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can be found at
|
||||
distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can be found at
|
||||
<link xlink:href="https://github.com/rackerjoe/oz-image-build"
|
||||
>rackerjoe/oz-image-build on Github</link>.</para>
|
||||
</section>
|
||||
|
||||
@ -147,7 +147,7 @@ use = egg:swift#proxy_logging
|
||||
</note>
|
||||
<para>For example, if a storage node
|
||||
has a partition in Zone 1 on IP 10.0.0.1, the storage node has
|
||||
address 10.0.1.1 from replication network. The mount point of
|
||||
address 10.0.1.1 from replication network. The mount point of
|
||||
this partition is <filename>/srv/node/sdb1</filename>, and the
|
||||
path in <filename>/etc/rsyncd.conf</filename> is
|
||||
<filename>/srv/node/</filename>, the DEVICE would be sdb1 and
|
||||
|
||||
@ -660,7 +660,7 @@
|
||||
<option>sync_binlog</option> option is configured on your database. Replace the
|
||||
following sample connection values with values that connect to your database:</para>
|
||||
<screen><prompt>$</prompt> <userinput>mysql -u user7 -ppassword -h 172.16.200.2 myDB7</userinput>
|
||||
<computeroutput>Welcome to the MySQL monitor. Commands end with ; or \g.
|
||||
<computeroutput>Welcome to the MySQL monitor. Commands end with ; or \g.
|
||||
...</computeroutput>
|
||||
<prompt>mysql></prompt> <userinput>show variables like 'sync_binlog';</userinput>
|
||||
<computeroutput>+---------------+-------+
|
||||
|
||||
Loading…
Reference in New Issue
Block a user