openstack/openstack-manuals
Code Issues Proposed changes

Edits for TB/GB/MB/KB usage

Browse Source 
Improve some wording and introduce non-breaking spaces.

Change-Id: I315968c155f6707b4ae57b00cf96a26b453e1d23
Co-Authored-By: Diane Fleming <diane.fleming@rackspace.com>
This commit is contained in:
Andreas Jaeger 2014-03-18 18:52:11 +01:00
parent 4e26cc9667
commit 8df08851d7
22 changed files with 169 additions and 81 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/admin-guide-cloud/ch_blockstorage.xml
View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<chapter 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"
@ -91,7 +95,7 @@
<literal>cinder-*</literal> services. Two additional
compute nodes run <systemitem class="service"
>nova-compute</systemitem>. The walk through uses a
custom partitioning scheme that carves out 60 GB of space
custom partitioning scheme that carves out 60&nbsp;GB of space
and labels it as LVM. The network uses the
<literal>FlatManager</literal> and
<literal>NetworkManager</literal> settings for

6
doc/admin-guide-cloud/ch_compute.xml
View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<chapter xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:xi="http://www.w3.org/2001/XInclude"
@ -327,7 +331,7 @@
<para>In addition to the ephemeral root volume, all flavors
except the smallest, <filename>m1.tiny</filename>, also
provide an additional ephemeral block device of between 20
and 160GB. These sizes can be configured to suit your
and 160&nbsp;GB. These sizes can be configured to suit your
environment. This is presented as a raw block device with
no partition table or file system. Cloud-aware operating
system images can discover, format, and mount these

12
doc/admin-guide-cloud/section_backup-block-storage-disks.xml
View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<section xml:id="backup-block-storage-disks"
xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
@ -25,10 +29,10 @@
much space as the potential snapshot size. If insufficient
space is available, the snapshot might become
corrupted.</para>
<para>For this example, assume that a 100 GB volume named
<para>For this example, assume that a 100&nbsp;GB volume named
<literal>volume-00000001</literal> was created for an
instance while only 4 GB are used. This example uses these
commands to back up only those 4 GB:</para>
instance while only 4&nbsp;GB are used. This example uses these
commands to back up only those 4&nbsp;GB:</para>
<itemizedlist>
<listitem>
<para><command>lvm2</command> command. Directly
@ -204,7 +208,7 @@ Block device 251:14</programlisting>
carefully because the time it takes to complete
the calculation is directly proportional to the
size of the file.</para>
<para>For files larger than around 4 to 6 GB, and
<para>For files larger than around 4 to 6&nbsp;GB, and
depending on your CPU, the process might take a
long time.</para>
</note>

6
doc/admin-guide-cloud/section_ts_cinder_config.xml
View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<section xml:id="section_ts_cinder_config"
xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
@ -165,7 +169,7 @@
<programlisting language="bash">2013-03-12 01:35:43 1248 TRACE cinder.openstack.common.rpc.amqp ISCSITargetCreateFailed: Failed to create iscsi target for volume volume-137641b2-af72-4a2f-b243-65fdccd38780.</programlisting>
<para>You might see this error in
<filename>cinder-volume.log</filename> after
trying to create a volume that is 1 GB. To fix this
trying to create a volume that is 1&nbsp;GB. To fix this
issue:</para>
<para>Change content of the
<filename>/etc/tgt/targets.conf</filename> from

5
doc/common/section_cli_cinder_manage_volumes.xml
View File

@ -1,4 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section [
<!ENTITY nbsp "&#160;">
]>
<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"
@ -83,7 +86,7 @@
+-----------------------+----------------------------------------+</computeroutput></screen>
</step>
<step>
<para>Create a volume with 8 GBs of space. Specify the
<para>Create a volume with 8&nbsp;GB of space. Specify the
availability zone and image:</para>
<screen><prompt>$</prompt> <userinput>cinder create 8 --display-name my-new-volume --image-id 397e713c-b95b-4186-ad46-6126863ea0a9 --availability-zone nova</userinput></screen>
<screen><?db-font-size 65%?><computeroutput>+---------------------+--------------------------------------+

6
doc/common/section_cli_nova_boot_from_volume.xml
View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<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"
@ -268,7 +272,7 @@
<parameter>--ephemeral</parameter> parameter to attach an
ephemeral disk on boot. When you terminate the instance, both
disks are deleted.</para>
<para>Boot an instance with a 512 MB swap disk and 2 GB ephemeral
<para>Boot an instance with a 512&nbsp;MB swap disk and 2&nbsp;GB ephemeral
disk:</para>
<screen><prompt>$</prompt> <userinput>nova boot --flavor <replaceable>FLAVOR</replaceable> --image <replaceable>IMAGE_ID</replaceable> --swap 512 --ephemeral size=2 <replaceable>NAME</replaceable></userinput></screen>
<note>

6
doc/common/section_cli_nova_host_aggregates.xml
View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE section [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<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"
@ -200,7 +204,7 @@
</screen>
<para>Use the <command>nova flavor-create</command> command to
create the <literal>ssd.large</literal> flavor called with
an ID of 6, 8GB of RAM, 80GB root disk, and 4
an ID of 6, 8&nbsp;GB of RAM, 80&nbsp;GB root disk, and 4
vCPUs.</para>
<screen><prompt>$</prompt> <userinput>nova flavor-create ssd.large 6 8192 80 4</userinput>
<computeroutput>+----+-----------+-----------+------+-----------+------+-------+-------------+-----------+-------------+

11
doc/common/section_objectstorage-arch.xml
View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE section [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<section xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink"
@ -58,9 +62,10 @@
</imageobject>
</mediaobject>
</figure>
<para>Currently, 2 TB or 3 TB SATA disks deliver good price/performance value. You can use
desktop-grade drives if you have responsive remote hands in the datacenter and
enterprise-grade drives if you don't.</para>
<para>Currently, a 2&nbsp;TB or 3&nbsp;TB SATA disk delivers
good performance for the price. You can use desktop-grade
drives if you have responsive remote hands in the datacenter
and enterprise-grade drives if you don't.</para>
<section xml:id="section_storage-nodes-considerations">
<title>Factors to consider</title>
<para>You should keep in mind the desired I/O performance for single-threaded requests .

8
doc/common/section_storage-concepts.xml
View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE section [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<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"
@ -48,8 +52,8 @@
<td>Easily scalable for future growth</td>
</tr>
<tr>
<td>Example: 10 GB first disk, 30 GB/core second disk</td>
<td>Example: 1 TB "extra hard drive"</td>
<td>Example: 10&nbsp;GB first disk, 30&nbsp;GB/core second disk</td>
<td>Example: 1&nbsp;TB "extra hard drive"</td>
<td>Example: 10s of TBs of data set storage</td>
</tr>
</tbody>

13
doc/config-reference/compute/section_compute-scheduler.xml
View File

@ -1,3 +1,8 @@
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE section [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<section xml:id="section_compute-scheduler"
xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
@ -411,10 +416,10 @@ isolated_images=342b492c-128f-4a42-8d3a-c5088cf27d13,ebd267a6-ca86-4d6c-9a0e-bd1
configuration option in
<filename>nova.conf</filename>. The default setting
is:</para>
<programlisting language="ini">ram_allocation_ratio=1.5</programlisting>
<para>With this setting, if there is 1 GB of free RAM, the
scheduler allows instances up to size 1.5 GB to be run
on that instance.</para>
<programlisting
language="ini">ram_allocation_ratio=1.5</programlisting>
<para>This setting enables 1.5&nbsp;GB instances to run on
any compute node with 1&nbsp;GB of free RAM.</para>
</section>
<section xml:id="retryfilter">
<title>RetryFilter</title>

17
doc/config-reference/compute/section_hypervisor_vmware.xml
View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE chapter [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<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"
@ -104,7 +108,7 @@
<listitem>
<para><emphasis role="bold">Copying VMDK files (vSphere 5.1
only).</emphasis> In vSphere 5.1, copying large image files
(for example, 12 GB and greater) from Glance can take a long
(for example, 12&nbsp;GB and greater) from Glance can take a long
time. To improve performance, VMware recommends that you
upgrade to VMware vCenter Server 5.1 Update 1 or later. For
more information, see the <link xlink:href="https://www.vmware.com/support/vsphere5/doc/vsphere-vcenter-server-51u1-release-notes.html#resolvedissuescimapi">Release Notes</link>.</para>
@ -231,11 +235,12 @@ datastore_regex=&lt;optional datastore regex&gt;</programlisting>
data stores that are not intended for OpenStack.</para>
</listitem>
<listitem>
<para>Reserved host memory:
The <option>reserved_host_memory_mb</option> setting is set
to 512 MB by default. However, VMware recommends setting
this value to 0 MB because the vCenter driver reports
the effective memory available to the virtual machines.</para>
<para>Reserved host memory: The
<option>reserved_host_memory_mb</option> option value is
512&nbsp;MB by default. However, VMware recommends that
you set this option to 0&nbsp;MB because the vCenter
driver reports the effective memory available to the
virtual machines.</para>
</listitem>
</itemizedlist>
</note>

7
doc/glossary/glossary-terms.xml
View File

@ -2,6 +2,7 @@
<!DOCTYPE chapter [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY mdash "&#x2014;">
<!ENTITY nbsp "&#160;">
]>
<glossary xmlns="http://docbook.org/ns/docbook"
@ -2703,8 +2704,10 @@
<glossentry>
<glossterm>large object</glossterm>
<glossdef>
<para>An object within Object Storage that is larger than 5
GBs.</para>
<para>
An object within Object Storage that is larger than
5&nbsp;GB.
</para>
</glossdef>
</glossentry>
<glossentry>

36
doc/image-guide/ch_creating_images_manually.xml
View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE chapter [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<chapter 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"
@ -130,14 +134,16 @@ Starting install...
Creating domain... | 0 B 00:00
Domain installation still in progress. You can reconnect to
the console to complete the installation process.</computeroutput></screen>
<para>This uses the KVM hypervisor to start up a virtual
machine with the libvirt name of
<literal>centos-6.4</literal> with 1024MB of RAM, with
a virtual CD-ROM drive associated with the
<filename>/data/CentOS-6.4-x86_64-netinstall.iso</filename>
file, and a local hard disk which is stored in the host at
<filename>/data/centos-6.4.qcow2</filename> that is
10GB in size in qcow2 format. It configures networking to
<para>
The KVM hypervisor starts the virtual machine with the
libvirt name, <literal>centos-6.4</literal>, with
1024&nbsp;MB of RAM. The virtual machine also has a virtual
CD-ROM drive associated with the
<filename>/data/CentOS-6.4-x86_64-netinstall.iso</filename>
file and a local 10&nbsp;GB hard disk in qcow2 format that is
stored in the host at
<filename>/data/centos-6.4.qcow2</filename>.
It configures networking to
use libvirt's default network. There is a VNC server that
is listening on all interfaces, and libvirt will not
attempt to launch a VNC client automatically nor try to
@ -146,13 +152,13 @@ the console to complete the installation process.</computeroutput></screen>
libvirt will attempt to optimize the configuration for a
Linux guest running a RHEL 6.x distribution.<note>
<para>When using the libvirt
<literal>default</literal> network, libvirt
will connect the virtual machine's interface to a
bridge called <literal>virbr0</literal>. There is
a dnsmasq process managed by libvirt that will
hand out an IP address on the 192.168.122.0/24
subnet, and libvirt has iptables rules for doing
NAT for IP addresses on this subnet.</para>
<literal>default</literal> network, libvirt will
connect the virtual machine's interface to a bridge
called <literal>virbr0</literal>. There is a dnsmasq
process managed by libvirt that will hand out an IP
address on the 192.168.122.0/24 subnet, and libvirt
has iptables rules for doing NAT for IP addresses on
this subnet.</para>
</note></para>
<para>Run the <command>virt-install --os-variant
list</command> command to see a range of allowed

8
doc/image-guide/ch_modifying_images.xml
View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE chapter [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<chapter 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"
@ -210,8 +214,8 @@ Type: 'help' for help on commands
<title>Resize an image</title>
<para>Here's a simple of example of how to use
<command>virt-resize</command> to resize an image.
Assume we have a 16GB Windows image in qcow2 format
that we want to resize to 50GB. First, we use
Assume we have a 16&nbsp;GB Windows image in qcow2 format
that we want to resize to 50&nbsp;GB. First, we use
<command>virt-filesystems</command> to identify
the
partitions:<screen><prompt>#</prompt> <userinput>virt-filesystems --long --parts --blkdevs -h -a /data/images/win2012.qcow2</userinput>

12
doc/install-guide/object-storage/section_object-storage-sys-requirements.xml
View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE chapter [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<section xml:id="object-storage-system-requirements"
xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
@ -30,9 +34,9 @@
<td><para>Object Storage object servers</para></td>
<td>
<para>Processor: dual quad
core</para><para>Memory: 8 or 12 GB RAM</para>
core</para><para>Memory: 8 or 12&nbsp;GB RAM</para>
<para>Disk space: optimized for cost per GB</para>
<para>Network: one 1 GB Network Interface Card
<para>Network: one 1&nbsp;GB Network Interface Card
(NIC)</para></td>
<td><para>The amount of disk space depends on how much
you can fit into the rack efficiently. You
@ -59,8 +63,8 @@
servers</para></td>
<td>
<para>Processor: dual quad core</para>
<para>Memory: 8 or 12 GB RAM</para>
<para>Network: one 1 GB Network Interface Card
<para>Memory: 8 or 12&nbsp;GB RAM</para>
<para>Network: one 1&nbsp;GB Network Interface Card
(NIC)</para></td>
<td><para>Optimized for IOPS due to tracking with
SQLite databases.</para></td>

17
doc/install-guide/section_ceilometer-install.xml
View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE chapter [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<section xml:id="ceilometer-install"
xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
@ -37,16 +41,17 @@
<screen os="ubuntu;debian"><prompt>#</prompt> <userinput>apt-get install mongodb</userinput></screen>
<note>
<para>
By default MongoDB is configured to create several 1 GB files
By default MongoDB is configured to create several 1&nbsp;GB files
in the <filename>/var/lib/mongodb/journal/</filename> directory
to support database journaling.
</para>
<para>
If you need to minimize the space allocated to support database
journaling then set the <option>smallfiles</option> configuration
key to <literal>true</literal> in the <filename>/etc/mongodb.conf</filename>
configuration file. This will reduce the size of each journaling file
to 512 MB.
If you need to minimize the space allocated to support
database journaling then set the <option>smallfiles</option>
configuration key to <literal>true</literal> in the
<filename>/etc/mongodb.conf</filename> configuration
file. This configuration reduces the size of each journaling
file to 512&nbsp;MB.
</para>
<para os="ubuntu;debian">
As the files are created the first time the MongoDB service starts

22
doc/training-guides/lab000-virtualbox-basics.xml
View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE chapter [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<chapter xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink"
@ -50,10 +54,10 @@
<tbody>
<tr>
<td rowspan="1" colspan="1">VT Enabled PC:</td>
<td rowspan="1" colspan="1">Intel ix or Amd QuadCore</td>
<td rowspan="1" colspan="1">Intel ix or AMD QuadCore</td>
</tr>
<tr>
<td rowspan="1" colspan="1">4GB Ram:</td>
<td rowspan="1" colspan="1">4&nbsp;GB RAM:</td>
<td rowspan="1" colspan="1">DDR2/DDR3</td>
</tr>
</tbody>
@ -372,9 +376,9 @@
</imageobject>
</mediaobject>
</figure>
<para>Select appropriate RAM, minimum 512 MB of RAM for Control
Node. Rest all can be default settings. The hard disk size can
be 8GB as default.</para>
<para>Select the appropriate amount of RAM. For the control node,
the minimum is 512&nbsp;MB of RAM. For other settings, use the
defaults. The hard disk size can be 8&nbsp;GB as default.</para>
<para>Configure the networks</para>
<para>(Ignore the IP Address for now, you will set it up from
inside the VM)</para>
@ -439,8 +443,8 @@
are doing.</para>
<para><guilabel>Network Node:</guilabel></para>
<para>Create a new Virtual Machine,</para>
<para>Minimum RAM is 512MB. Rest all can be left default. Minimum
HDD space 8GB.</para>
<para>Minimum RAM is 512&nbsp;MB. Rest all can be left default. Minimum
HDD space 8&nbsp;GB.</para>
<figure>
<title>Create New Virtual Machine</title>
<mediaobject>
@ -526,8 +530,8 @@
like DNS servers etc. (not necessary). Unless you know what you
are doing.</para>
<para><guilabel>Compute Node:</guilabel></para>
<para>Create a new virtual machine, give it atleast 1,000 MB RAM.
Rest all can be left as defaults. Give atleast 8GB HDD.</para>
<para>Create a virtual machine with at least 1,000&nbsp;MB RAM and
8&nbsp;GB HDD. For other settings, use the defaults.</para>
<figure>
<title>Create New Virtual Machine</title>
<mediaobject>

14
doc/training-guides/module003-ch006-more-concepts.xml
View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE chapter [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<chapter xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink"
@ -41,13 +45,13 @@
encoded as C%2B%2Bfinal%28v2%29.txt and therefore be 24
bytes in length rather than the expected 16.</para>
<para>The maximum allowable size for a storage object upon
upload is 5 gigabytes (GB) and the minimum is zero bytes.
upload is 5&nbsp;GB and the minimum is zero bytes.
You can use the built-in large object support and the
swift utility to retrieve objects larger than 5 GB.</para>
swift utility to retrieve objects larger than 5&nbsp;GB.</para>
<para>For metadata, you should not exceed 90 individual
key/value pairs for any one object and the total byte
length of all key/value pairs should not exceed 4KB (4096
bytes).</para>
length of all key/value pairs should not exceed 4&nbsp;KB
(4096&nbsp;bytes).</para>
<para><guilabel>Language-Specific API
Bindings</guilabel></para>
<para>A set of supported API bindings in several popular
@ -217,4 +221,4 @@
other errors are found they are logged. For example,
an object’s listing cannot be found on any container
server it should be.</para>
</chapter>
</chapter>

16
doc/training-guides/module003-ch007-swift-cluster-architecture.xml
View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE section [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<chapter xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink"
@ -69,12 +73,12 @@
provisioned with single gigabit or 10 gigabit network
interface depending on expected workload and desired
performance.</para>
<para>Currently 2 TB or 3 TB SATA disks deliver good
price/performance value. Desktop-grade drives can be used
where there are responsive remote hands in the datacenter,
and enterprise-grade drives can be used where this is not
the case.</para>
<para><guilabel>Factors to Consider</guilabel></para>
<para>Currently, a 2&nbsp;TB or 3&nbsp;TB SATA disk delivers
good performance for the price. Desktop-grade drives can
be used where there are responsive remote hands in the
datacenter, and enterprise-grade drives can be used where
this is not the case.</para>
<para><guilabel>Factors to Consider</guilabel></para>
<para>Desired I/O performance for single-threaded requests
should be kept in mind. This system does not use RAID,
so each request for an object is handled by a single

7
doc/user-guide-admin/section_cli_keystone_set_quotas.xml
View File

@ -5,6 +5,7 @@
<!ENTITY mdash "&#x2014;">
<!ENTITY hellip "&#x2026;">
<!ENTITY plusmn "&#xB1;">
<!ENTITY nbsp "&#160;">
]>
<section xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
@ -21,8 +22,10 @@
<para>Using the command-line interface, you can manage quotas for
the OpenStack Compute service, the OpenStack Block Storage service,
and the OpenStack Networking service.</para>
<para>Typically, default values are changed because a tenant
requires more than 10 volumes, or more than 1 TB on a compute node.</para>
<para>The cloud operator typically changes default values because a
tenant requires more than ten volumes or 1&nbsp;TB on a compute
node.
</para>
<note>
<para>To view all tenants (projects), run:
<screen><prompt>$</prompt> <userinput>keystone tenant-list</userinput>

7
doc/user-guide-admin/section_dashboard_admin_set_quotas.xml
View File

@ -1,10 +1,11 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section [
<!-- Some useful entities bortred from HTML -->
<!-- Some useful entities borrowed from HTML -->
<!ENTITY ndash "&#x2013;">
<!ENTITY mdash "&#x2014;">
<!ENTITY hellip "&#x2026;">
<!ENTITY plusmn "&#xB1;">
<!ENTITY nbsp "&#160;">
]>
<section xmlns="http://docbook.org/ns/docbook" version="5.0"
xmlns:xi="http://www.w3.org/2001/XInclude"
@ -17,8 +18,8 @@
number of gigabytes allowed for each tenant can be controlled so that
cloud resources are optimized. Quotas can be enforced at both the tenant
(or project) and the tenant-user level.</para>
<para>Typically, you change quotas when a project needs more than 10
volumes or 1 TB on a compute node.</para>
<para>Typically, you change quotas when a project needs more than ten
volumes or 1&nbsp;TB on a compute node.</para>
<para>Using the Dashboard, you can view default Compute and Block Storage
quotas for new tenants, as well as update quotas for existing tenants.</para>
<note>

8
doc/user-guide/section_cli_nova_config-drive.xml
View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE chapter [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY nbsp "&#160;">
]>
<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"
@ -256,8 +260,8 @@ openstack/latest/user_data</computeroutput></screen>
<filename>/etc/nova/nova.conf</filename>
file:</para>
<programlisting language="ini">config_drive_format=vfat</programlisting>
<para>If you choose VFAT, the configuration drive is 64
MBs.</para>
<para>If you choose VFAT, the configuration drive is
64&nbsp;MB.</para>
</simplesect>
</section>
<section xml:id="config_reference">