Fix some wrong UTF-8 characters
Replace UTF-8 characters with normal characters or entities as appropriate. Change-Id: I28f932506fbaff738c3490151ffdcf3d5dc5ae33 Note: The repo still contains UTF-8 characters but those are fine.
This commit is contained in:
parent
85b63ccded
commit
c633f2878c
@ -6,7 +6,7 @@
|
||||
<title>Problem</title>
|
||||
<para>This error may be caused by a volume being exported outside of OpenStack using a
|
||||
host name different from the system name that OpenStack expects. This error could be displayed with the IQN if the host was exported using iSCSI.</para>
|
||||
<programlisting>Duplicate3PARHost: 3PAR Host already exists: Host wwn 50014380242B9750 already used by host cld4b5ubuntuW(id = 68. The hostname must be called 'cld4b5ubuntu‘.</programlisting>
|
||||
<programlisting>Duplicate3PARHost: 3PAR Host already exists: Host wwn 50014380242B9750 already used by host cld4b5ubuntuW(id = 68. The hostname must be called 'cld4b5ubuntu'.</programlisting>
|
||||
</section>
|
||||
<section xml:id="section_ts_duplicate_3PAR_host_solution">
|
||||
<title>Solution</title>
|
||||
|
@ -50,8 +50,8 @@
|
||||
</para>
|
||||
<para>To quickly enable an interface to be used as a Virtual Interface the following
|
||||
PowerShell may be used:</para>
|
||||
<screen><prompt>PS C:\></prompt><userinput>$if = Get-NetIPAddress –IPAddress 192* | Get-NetIPInterface</userinput>
|
||||
<prompt>PS C:\></prompt><userinput>New-VMSwitch -NetAdapterName $if.ifAlias -Name yourbridgename –AllowManagementOS $false</userinput></screen>
|
||||
<screen><prompt>PS C:\></prompt><userinput>$if = Get-NetIPAddress -IPAddress 192* | Get-NetIPInterface</userinput>
|
||||
<prompt>PS C:\></prompt><userinput>New-VMSwitch -NetAdapterName $if.ifAlias -Name yourbridgename -AllowManagementOS $false</userinput></screen>
|
||||
</section>
|
||||
<section xml:id="enable-iscsi-services-hyper-v">
|
||||
<title>Enable iSCSI initiator service</title>
|
||||
@ -137,7 +137,7 @@
|
||||
each Hyper-V host:</para>
|
||||
<screen><prompt>PS C:\></prompt><userinput>Enable-VMMigration</userinput>
|
||||
<prompt>PS C:\></prompt><userinput>Set-VMMigrationNetwork <replaceable>IP_ADDRESS</replaceable></userinput>
|
||||
<prompt>PS C:\></prompt><userinput>Set-VMHost –VirtualMachineMigrationAuthenticationTypeKerberos</userinput></screen>
|
||||
<prompt>PS C:\></prompt><userinput>Set-VMHost -VirtualMachineMigrationAuthenticationTypeKerberos</userinput></screen>
|
||||
<note>
|
||||
<para>Please replace the IP_ADDRESS with the address of the interface which will provide
|
||||
the virtual switching for nova-network.</para>
|
||||
@ -204,7 +204,7 @@
|
||||
<para><link xlink:href="http://www.lfd.uci.edu/~gohlke/pythonlibs/"
|
||||
>http://www.lfd.uci.edu/~gohlke/pythonlibs/</link></para>
|
||||
<para>You must scroll to the greenlet section for the following file:
|
||||
greenlet-0.4.0.win32-py2.7.exe</para>
|
||||
greenlet-0.4.0.win32-py2.7.exe</para>
|
||||
<para>Click on the file, to initiate the download. Once the download is complete,
|
||||
run the installer.</para>
|
||||
</listitem>
|
||||
|
@ -1994,7 +1994,7 @@
|
||||
|
||||
<glossdef>
|
||||
<para>The process of finding duplicate data at the disk block, file,
|
||||
and/or object level to minimize storage use—currently unsupported
|
||||
and/or object level to minimize storage use—currently unsupported
|
||||
within OpenStack.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -2722,7 +2722,7 @@
|
||||
</indexterm></glossterm>
|
||||
|
||||
<glossdef>
|
||||
<para>Connected to by a direct consumer in RabbitMQ—Compute, the
|
||||
<para>Connected to by a direct consumer in RabbitMQ—Compute, the
|
||||
message can be consumed only by the current connection.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
@ -1,7 +1,12 @@
|
||||
<section xmlns="http://docbook.org/ns/docbook"
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink"
|
||||
xmlns:xi="http://www.w3.org/2001/XInclude"
|
||||
version="5.0" xml:id="s-mysql">
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<!DOCTYPE section [
|
||||
<!ENTITY % openstack SYSTEM "../../common/entities/openstack.ent">
|
||||
%openstack;
|
||||
]>
|
||||
<section xmlns="http://docbook.org/ns/docbook"
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink"
|
||||
xmlns:xi="http://www.w3.org/2001/XInclude"
|
||||
version="5.0" xml:id="s-mysql">
|
||||
<info>
|
||||
<title>Highly available MySQL</title>
|
||||
</info>
|
||||
@ -233,7 +238,7 @@ service, and its dependent resources, on one of your nodes.</simpara>
|
||||
<title>Configure OpenStack services for highly available MySQL</title>
|
||||
</info>
|
||||
<simpara>Your OpenStack services must now point their MySQL configuration to
|
||||
the highly available, virtual cluster IP address — rather than a
|
||||
the highly available, virtual cluster IP address—rather than a
|
||||
MySQL server’s physical IP address as you normally would.</simpara>
|
||||
<simpara>For OpenStack Image, for example, if your MySQL service IP address is
|
||||
192.168.42.101 as in the configuration explained here, you would use
|
||||
|
@ -1,7 +1,12 @@
|
||||
<section xmlns="http://docbook.org/ns/docbook"
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink"
|
||||
xmlns:xi="http://www.w3.org/2001/XInclude"
|
||||
version="5.0" xml:id="s-rabbitmq">
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<!DOCTYPE section [
|
||||
<!ENTITY % openstack SYSTEM "../../common/entities/openstack.ent">
|
||||
%openstack;
|
||||
]>
|
||||
<section xmlns="http://docbook.org/ns/docbook"
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink"
|
||||
xmlns:xi="http://www.w3.org/2001/XInclude"
|
||||
version="5.0" xml:id="s-rabbitmq">
|
||||
<info>
|
||||
<title>Highly available RabbitMQ</title>
|
||||
</info>
|
||||
@ -41,7 +46,7 @@ managing all resources, including the RabbitMQ daemon itself, with
|
||||
<simpara>There is an alternative method of configuring RabbitMQ for high
|
||||
availability. That approach, known as
|
||||
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.rabbitmq.com/ha.html">active-active mirrored queues</link>,
|
||||
happens to be the one preferred by the RabbitMQ developers — however
|
||||
happens to be the one preferred by the RabbitMQ developers—however
|
||||
it has shown less than ideal consistency and reliability in OpenStack
|
||||
clusters. Thus, at the time of writing, the Pacemaker/DRBD based
|
||||
approach remains the recommended one for OpenStack environments,
|
||||
@ -221,7 +226,7 @@ service, and its dependent resources, on one of your nodes.</simpara>
|
||||
<title>Configure OpenStack services for highly available RabbitMQ</title>
|
||||
</info>
|
||||
<simpara>Your OpenStack services must now point their RabbitMQ configuration to
|
||||
the highly available, virtual cluster IP address — rather than a
|
||||
the highly available, virtual cluster IP address—rather than a
|
||||
RabbitMQ server’s physical IP address as you normally would.</simpara>
|
||||
<simpara>For OpenStack Image, for example, if your RabbitMQ service IP address is
|
||||
192.168.42.100 as in the configuration explained here, you would use
|
||||
|
@ -9,7 +9,7 @@
|
||||
<para>The swift client is simple to use, scalable, and flexible.</para><para>Use the swift client <option>-o</option> or
|
||||
<option>-output</option> option to get short answers to
|
||||
questions about logs,</para>
|
||||
<para>You can use the <option>-o —output</option> option with a
|
||||
<para>You can use the <option>-o</option> or <option>--output</option> option with a
|
||||
single object download to redirect the command output to a
|
||||
specific file or to STDOUT (<literal>-</literal>). The ability
|
||||
to redirect the output to STDOUT enables you to pipe
|
||||
@ -61,7 +61,7 @@ Write ACL:</computeroutput></screen></step>
|
||||
2010-11-16-22_access.log</computeroutput></screen></step></procedure></section>
|
||||
<section xml:id="swift_upload_files"><title>Download and analyze an object</title>
|
||||
<procedure>
|
||||
<para>This example uses the <option>-o —output</option>
|
||||
<para>This example uses the <option>-o</option>
|
||||
option and a hyphen (<literal>-</literal>) to get
|
||||
information about an object.</para>
|
||||
<para>Use the swift <command>download</command> command to
|
||||
@ -79,7 +79,7 @@ Write ACL:</computeroutput></screen></step>
|
||||
<step>
|
||||
<para>Download an object:</para>
|
||||
<screen><prompt>$</prompt> <userinput>swift -A http://swift-auth.com:11000/v1.0 -U test:tester -K testing \
|
||||
download -o - logtest 2010-11-16-22_access.log | awk ‘{ print $9”-“$12}’ | sort | uniq -c</userinput> </screen>
|
||||
download -o - logtest 2010-11-16-22_access.log | awk '{ print $9"-"$12}' | sort | uniq -c</userinput> </screen>
|
||||
<screen><computeroutput>805 DELETE-204
|
||||
12 DELETE-404
|
||||
2 DELETE-409
|
||||
@ -112,7 +112,7 @@ Write ACL:</computeroutput></screen></step>
|
||||
8 PUT-499</computeroutput></screen></step>
|
||||
<step><para>Discover how many PUT requests are in each log file.</para>
|
||||
<para>Use a bash for loop with awk and swift with
|
||||
the <option>-o —output</option> option and a
|
||||
the <option>-o</option> or <option>--output</option> option and a
|
||||
hyphen (<literal>-</literal>) to discover how many
|
||||
PUT requests are in each log file.</para>
|
||||
|
||||
@ -124,7 +124,7 @@ Write ACL:</computeroutput></screen></step>
|
||||
Finally, pipe into <command>wc -l</command> to
|
||||
count the lines.</para>
|
||||
<screen><prompt>$</prompt> <userinput>for f in `swift -A http://swift-auth.com:11000/v1.0 -U test:tester -K testing list logtest` ; \
|
||||
do echo -ne “PUTS - ” ; swift -A http://swift-auth.com:11000/v1.0 -U test:tester -K testing download -o - logtest $f | grep PUT | wc -l ; \
|
||||
do echo -ne "PUTS - " ; swift -A http://swift-auth.com:11000/v1.0 -U test:tester -K testing download -o - logtest $f | grep PUT | wc -l ; \
|
||||
done</userinput></screen>
|
||||
<screen><computeroutput>2010-11-15-21_access.log - PUTS - 402
|
||||
2010-11-15-22_access.log - PUTS - 1091
|
||||
@ -145,7 +145,7 @@ Write ACL:</computeroutput></screen></step>
|
||||
object name.</para>
|
||||
|
||||
<screen><prompt>$</prompt> <userinput>for f in `swift -A http://swift-auth.com:11000/v1.0 -U test:tester -K testing list -p 2010-11-15 logtest` ; \
|
||||
do echo -ne “$f - PUTS - ” ; swift -A http://127.0.0.1:11000/v1.0 -U test:tester \
|
||||
do echo -ne "$f - PUTS - " ; swift -A http://127.0.0.1:11000/v1.0 -U test:tester \
|
||||
-K testing download -o - logtest $f | grep PUT | wc -l ; \
|
||||
done</userinput></screen>
|
||||
<screen><computeroutput>2010-11-15-21_access.log - PUTS - 402
|
||||
|
@ -106,7 +106,7 @@
|
||||
<tr>
|
||||
<td>RAM image</td>
|
||||
<td>
|
||||
<screen><prompt>$</prompt> <userinput>glance image-create -—name "cirros-threepart-ramdisk" \
|
||||
<screen><prompt>$</prompt> <userinput>glance image-create --name "cirros-threepart-ramdisk" \
|
||||
--disk-format ari --container-format ari --is-public False \
|
||||
--file ~/images/cirros-0.3.1~pre4-x86_64-initrd</userinput></screen>
|
||||
</td>
|
||||
@ -116,7 +116,7 @@
|
||||
<td>
|
||||
<screen><prompt>$</prompt> <userinput>glance image-create --name "cirros-threepart" --disk-format ami \
|
||||
--container-format ami --is-public False \
|
||||
--property kernel_id=$KID—property ramdisk_id=$RID \
|
||||
--property kernel_id=$KID-property ramdisk_id=$RID \
|
||||
--file ~/images/cirros-0.3.1~pre4-x86_64-blank.img</userinput></screen>
|
||||
</td>
|
||||
</tr>
|
||||
|
@ -1,4 +1,4 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE chapter [
|
||||
]>
|
||||
<chapter xmlns="http://docbook.org/ns/docbook"
|
||||
|
@ -1,4 +1,4 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<section xmlns="http://docbook.org/ns/docbook"
|
||||
xmlns:xi="http://www.w3.org/2001/XInclude"
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
|
||||
|
Loading…
Reference in New Issue
Block a user