openstack/openstack-manuals
Code Issues Proposed changes

Fix whitespace problems

Browse Source 
Since we have now a niceness gate, let's remove the known failures.

Change-Id: I01684aee61e18e76f6523a466e28b8252e577f6f
This commit is contained in:
Andreas Jaeger
2013-10-08 14:18:12 +02:00
parent f9cc649ce8
commit fac23cb047
51 changed files with 174 additions and 193 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -1002,7 +1002,7 @@ header: Date: Thu, 13 Sep 2012 20:27:36 GMT
avoid raising an error. Compute nodes have
iptables/ebtables entries created for each project and instance
to protect against IP/MAC address spoofing and ARP
poisoning. </para>
poisoning.</para>
<note>
<para>In single-host Flat DHCP mode you <emphasis
role="italic">will</emphasis> be able to ping VMs
@@ -2124,7 +2124,7 @@ HostC p2 5 10240 150
<command>live-migration</command>,
under the default Compute
configuration options the instances
are suspended before migration.</para>
are suspended before migration.</para>
<para>See <link xlink:href="http://docs.openstack.org/trunk/config-reference/content/configuring-openstack-compute-basics.html#section_configuring-compute-migrations">Configure migrations</link> in <citetitle>OpenStack Configuration Reference</citetitle> for more details.</para>
</note>
</para>
@@ -2137,7 +2137,7 @@ HostC p2 5 10240 150
from a failed compute node. Of the two methods covered in the following sections,
the evacuate API is the preferred method even in the absence of shared storage. The
evacuate API provides many benefits over manual recovery, such as re-attachment of
volumes and floating IPs. </para>
volumes and floating IPs.</para>
<xi:include href="../common/section_nova_cli_evacuate.xml"/>
<section xml:id="nova-compute-node-down-manual-recovery">
<title>Manual recovery</title>

4
doc/admin-guide-cloud/section_troubleshoot-cinder.xml
View File

@@ -61,7 +61,7 @@
<para>This is most likely going to be a minor adjustment to your
<filename>nova.conf</filename> file. Make sure that your
<filename>nova.conf</filename> has the following
entry:<programlisting>volume_api_class=nova.volume.cinder.API </programlisting></para>
entry:<programlisting>volume_api_class=nova.volume.cinder.API</programlisting></para>
<para>Make certain that you explicitly set
<option>enabled_apis</option> because the default includes
<option>osapi_volume</option>:<programlisting>enabled_apis=ec2,osapi_compute,metadata</programlisting></para>
@@ -70,7 +70,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. </para>
create a volume that is 1 GB.</para>
<para>To fix this issue, change the content of the
<filename>/etc/tgt/targets.conf</filename> from
<literal>include /etc/tgt/conf.d/*.conf</literal> to

2
doc/common/section_baremetal.xml
View File

@@ -14,7 +14,7 @@ xml:id="baremetal">
hardware via OpenStack's API, using pluggable sub-drivers to deliver
machine imaging (PXE) and power control (IPMI). With this, provisioning
and management of physical hardware is accomplished using common cloud
APIs and tools, such as OpenStack Orchestration or salt-cloud.
APIs and tools, such as OpenStack Orchestration or salt-cloud.
However, due to this unique
situation, using the baremetal driver requires some additional
preparation of its environment, the details of which are beyond the

12
doc/common/section_config_keystone_ldap.xml
View File

@@ -5,9 +5,9 @@
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
xml:id="configuring-keystone-for-ldap-backend">
<title>Configuring OpenStack Identity for an LDAP backend</title>
<para> As an alternative to the SQL Database backing store, Identity can use
<para>As an alternative to the SQL Database backing store, Identity can use
a directory server to provide the Identity service. An example schema
for AcmeExample would look like this: </para>
for AcmeExample would look like this:</para>
<screen>
dn: dc=AcmeExample,dc=org
dc: AcmeExample
@@ -30,7 +30,7 @@ objectClass: top
objectClass: organizationalUnit
ou: roles
</screen>
<para> The corresponding entries in the <filename>keystone.conf</filename>
<para>The corresponding entries in the <filename>keystone.conf</filename>
configuration file are:</para>
<programlisting language="ini">
[ldap]
@@ -60,7 +60,7 @@ role_objectclass = organizationalRole
<emphasis>uidNumber</emphasis> and <emphasis>username</emphasis>
field either <emphasis>uid</emphasis> or <emphasis>cn</emphasis>. To
change these two fields, the corresponding entries in the Keystone
configuration file are: </para>
configuration file are:</para>
<programlisting language="ini">
[ldap]
user_id_attribute = uidNumber
@@ -69,7 +69,7 @@ user_name_attribute = cn
<para>There is a set of allowed actions per object type that you can modify
depending on your specific deployment. For example, the users are
managed by another tool and you have only read access, in such case the
configuration is: </para>
configuration is:</para>
<programlisting language="ini">
[ldap]
user_allow_create = False
@@ -86,7 +86,7 @@ role_allow_delete = True
</programlisting>
<para>There are some configuration options for filtering users, tenants and
roles, if the backend is providing too much output, in such case the
configuration will look like: </para>
configuration will look like:</para>
<programlisting language="ini">
[ldap]
user_filter = (memberof=CN=acme-users,OU=workgroups,DC=AcmeExample,DC=com)

6
doc/common/section_dashboard-configure-https.xml
View File

@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<section xml:id="dashboard-config-https" 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"><title>Configure the dashboard for HTTPS</title>
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"><title>Configure the dashboard for HTTPS</title>
<para>You can configure the dashboard for a secured HTTPS deployment. While the standard installation
uses a non-encrypted HTTP channel, you can enable SSL support
for the dashboard.</para>
@@ -29,7 +29,7 @@ SESSION_COOKIE_HTTPONLY = True</programlisting>
<step>
<para>Edit
<filename>/etc/apache2/conf.d/openstack-dashboard.conf:</filename></para>
<para>Before:</para>
<programlisting><?db-font-size 65%?>WSGIScriptAlias / /usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi
WSGIDaemonProcess horizon user=www-data group=www-data processes=3 threads=10
@@ -38,7 +38,7 @@ Alias /static /usr/share/openstack-dashboard/openstack_dashboard/static/
Order allow,deny
Allow from all
&lt;/Directory&gt;</programlisting>
<para>After:</para>
<programlisting><?db-font-size 65%?>&lt;VirtualHost *:80&gt;
ServerName openstack.example.com

2
doc/common/section_dashboard-configure-vnc-window.xml
View File

@@ -7,7 +7,7 @@
<para>The <filename>_detail_vnc.html</filename> file defines
the size of the VNC window. To change the window size, edit
this file.</para>
<procedure xml:id="adjust-vnc-window">
<procedure xml:id="adjust-vnc-window">
<step>
<para>Edit
<filename>/usr/share/pyshared/horizon/dashboards/nova/instances/templates/instances/_detail_vnc.html.</filename></para>

4
doc/common/section_dashboard-configure.xml
View File

@@ -6,13 +6,13 @@
<title>Configure the dashboard</title>
<?dbhtml stop-chunking?>
<para>You can configure the dashboard for a simple HTTP
deployment. </para>
deployment.</para>
<para>You can configure the dashboard for a secured HTTPS
deployment. While the standard installation uses a
non-encrypted HTTP channel, you can enable SSL support for the
dashboard.</para>
<para>Also, you can configure the size of the VNC window in the
dashboard. </para>
dashboard.</para>
<xi:include href="section_dashboard-configure-http.xml"/>
<xi:include href="section_dashboard-configure-https.xml"/>
<xi:include href="section_dashboard-configure-vnc-window.xml"/>

2
doc/common/section_networking-quotas.xml
View File

@@ -10,7 +10,7 @@
<screen><prompt>$</prompt> <userinput>neutron net-create test_net</userinput>
<computeroutput>Quota exceeded for resources: ['network']</computeroutput></screen>
<para>Per-tenant quota configuration is also supported by the quota extension API. See <link
linkend="cfg_quotas_per_tenant"> Per-tenant quota configuration</link> for details. </para>
linkend="cfg_quotas_per_tenant"> Per-tenant quota configuration</link> for details.</para>
<section xml:id="cfg_quotas_common">
<title>Basic quota configuration</title>
<para>In the Networking default quota mechanism, all tenants have the same quota value, such

2
doc/common/section_nova_cli_commands.xml
View File

@@ -212,7 +212,7 @@
x509-create-cert Create x509 cert for a user in tenant.
x509-get-root-cert Fetches the x509 root cert.
bash-completion Prints out a list of all possible commands and flags
that the nova command can accept. Can be used by bash
that the nova command can accept. Can be used by bash
for tab-completion of commands.
help Display help about this program or one of its
subcommands.

4
doc/common/section_nova_cli_quotas.xml
View File

@@ -110,7 +110,7 @@
<para>
<systemitem>instances</systemitem>
</para>
</td>
</td>
<td>
<para>
Number of instances allowed per tenant.
@@ -356,4 +356,4 @@
</step>
</procedure>
</section>
</section>
</section>

2
doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml
View File

@@ -59,7 +59,7 @@
<literal>gpfs_mount_point_base</literal> and
<literal>gpfs_images_dir</literal> flags must both
reside in the same GPFS file system and in the same
GPFS file set. </para>
GPFS file set.</para>
</note>
</section>
<section xml:id="GPFS-volume-options">

66
doc/config-reference/networking/section_networking-config-identity.xml
View File

@@ -15,13 +15,13 @@
<substeps>
<step>
<para>Add the following function to your
<filename>.bashrc</filename> file: </para>
<filename>.bashrc</filename> file:</para>
<screen><prompt>$</prompt> <userinput>function get_id () {
echo `"$@" | awk '/ id / { print $4 }'`
}</userinput></screen>
</step>
<step>
<para>Source the <filename>.bashrc</filename> file: </para>
<para>Source the <filename>.bashrc</filename> file:</para>
<screen><prompt>$</prompt> <userinput>source .bashrc</userinput></screen>
</step>
</substeps>
@@ -29,7 +29,7 @@ echo `"$@" | awk '/ id / { print $4 }'`
<step>
<title>Create the OpenStack Networking Service Entry</title>
<para>OpenStack Networking must be available in the OpenStack
Compute service catalog. Create the service, as follows: </para>
Compute service catalog. Create the service, as follows:</para>
<screen><prompt>$</prompt> <userinput>NEUTRON_SERVICE_ID=$(get_id keystone service-create --name neutron --type network --description 'OpenStack Networking Service')</userinput></screen>
</step>
<step>
@@ -37,7 +37,7 @@ echo `"$@" | awk '/ id / { print $4 }'`
Entry</title>
<para>The way that you create an OpenStack Networking endpoint
entry depends on whether you are using the SQL catalog driver
or the template catalog driver: </para>
or the template catalog driver:</para>
<para>
<itemizedlist>
<listitem>
@@ -58,7 +58,7 @@ echo `"$@" | awk '/ id / { print $4 }'`
OpenStack Compute catalog template file
(default_catalog.templates), using these parameters:
given region ($REGION) and IP address of the OpenStack
Networking server ($IP). </para>
Networking server ($IP).</para>
<programlisting language="bash">catalog.$REGION.network.publicURL = http://$IP:9696
catalog.$REGION.network.adminURL = http://$IP:9696
catalog.$REGION.network.internalURL = http://$IP:9696
@@ -80,32 +80,32 @@ catalog.$Region.network.internalURL = http://10.211.55.17:9696
approach is to create a special <literal>service</literal>
tenant, create a <literal>neutron</literal> user within this
tenant, and to assign this user an <literal>admin</literal>
role. </para>
role.</para>
<substeps>
<step>
<para>Create the <literal>admin</literal> role: </para>
<para>Create the <literal>admin</literal> role:</para>
<screen><prompt>$</prompt> <userinput>ADMIN_ROLE=$(get_id keystone role-create --name=admin)
</userinput></screen>
</step>
<step>
<para> Create the <literal>neutron</literal> user: </para>
<para>Create the <literal>neutron</literal> user:</para>
<screen><prompt>$</prompt> <userinput>NEUTRON_USER=$(get_id keystone user-create --name=neutron --pass="$NEUTRON_PASSWORD" --email=demo@example.com --tenant-id service)
</userinput></screen>
</step>
<step>
<para>Create the <literal>service</literal> tenant: </para>
<para>Create the <literal>service</literal> tenant:</para>
<screen><prompt>$</prompt> <userinput>SERVICE_TENANT=$(get_id keystone tenant-create --name service --description "Services Tenant")</userinput></screen>
</step>
<step>
<para>Establish the relationship among the tenant, user, and
role: </para>
role:</para>
<screen><prompt>$</prompt> <userinput>keystone user-role-add --user_id $NEUTRON_USER --role_id $ADMIN_ROLE --tenant_id $SERVICE_TENANT</userinput></screen>
</step>
</substeps>
</step>
</procedure>
<para>See the OpenStack Installation Guides for more details about
creating service entries and service users. </para>
creating service entries and service users.</para>
<section xml:id="nova_with_neutron">
<title>OpenStack Compute</title>
@@ -118,7 +118,7 @@ catalog.$Region.network.internalURL = http://10.211.55.17:9696
IPs are proxied by OpenStack Compute to OpenStack Network APIs.
However, operator-facing tools (for example, <systemitem
class="service">nova-manage</systemitem>) are not proxied and
should not be used. </para>
should not be used.</para>
<warning>
<para>When you
configure networking, you must use this guide. Do not rely on OpenStack
@@ -144,11 +144,11 @@ catalog.$Region.network.internalURL = http://10.211.55.17:9696
<systemitem class="service">nova-network</systemitem>.
</para>
</note>
<para> To ensure that OpenStack Compute works properly with
<para>To ensure that OpenStack Compute works properly with
OpenStack Networking (rather than the legacy <systemitem
class="service">nova-network</systemitem> mechanism), you must
adjust settings in the <filename>nova.conf</filename>
configuration file. </para>
configuration file.</para>
</section>
<section xml:id="nova_with_neutron_api">
<title>Networking API &amp; and Credential Configuration</title>
@@ -158,7 +158,7 @@ catalog.$Region.network.internalURL = http://10.211.55.17:9696
standard API. For this to happen, you must configure the
following items in the <filename>nova.conf</filename> file (used
by each <systemitem class="service">nova-compute</systemitem>
and <systemitem class="service">nova-api</systemitem> instance). </para>
and <systemitem class="service">nova-api</systemitem> instance).</para>
<table rules="all">
<caption>nova.conf API and Credential Settings</caption>
<col width="20%"/>
@@ -184,18 +184,18 @@ catalog.$Region.network.internalURL = http://10.211.55.17:9696
<td><para>Update to the hostname/IP and port of the
<systemitem class="service"
>neutron-server</systemitem> instance for this
deployment. </para></td>
deployment.</para></td>
</tr>
<tr>
<td><para><literal>neutron_auth_strategy</literal></para></td>
<td><para>Keep the default <literal>keystone</literal> value
for all production deployments. </para></td>
for all production deployments.</para></td>
</tr>
<tr>
<td><para><literal>neutron_admin_tenant_name</literal></para></td>
<td><para>Update to the name of the service tenant created
in the above section on OpenStack Identity
configuration. </para></td>
configuration.</para></td>
</tr>
<tr>
<td><para><literal>neutron_admin_username</literal></para></td>
@@ -214,7 +214,7 @@ catalog.$Region.network.internalURL = http://10.211.55.17:9696
<td><para>Update to the OpenStack Identity server IP and
port. This is the Identity (keystone) admin API server
IP and port value, and not the Identity service API IP
and port. </para></td>
and port.</para></td>
</tr>
</tbody>
</table>
@@ -228,10 +228,10 @@ catalog.$Region.network.internalURL = http://10.211.55.17:9696
you should always disable built-in security groups and proxy all
security group calls to the OpenStack Networking API . If you do
not, security policies will conflict by being simultaneously
applied by both services. </para>
applied by both services.</para>
<para>To proxy security groups to OpenStack Networking, use the
following configuration values in
<filename>nova.conf</filename>: </para>
<filename>nova.conf</filename>:</para>
<table rules="all">
<caption>nova.conf Security Group Settings</caption>
<col width="20%"/>
@@ -255,7 +255,7 @@ catalog.$Region.network.internalURL = http://10.211.55.17:9696
<td><para><literal>security_group_api</literal></para></td>
<td><para>Update to <literal>neutron</literal>, so that all
security group requests are proxied to the OpenStack
Network Service. </para></td>
Network Service.</para></td>
</tr>
</tbody>
</table>
@@ -268,9 +268,9 @@ catalog.$Region.network.internalURL = http://10.211.55.17:9696
those requests to <systemitem class="service"
>nova-api</systemitem>, even when the requests are made from
isolated networks, or from multiple networks that use
overlapping IP addresses. </para>
overlapping IP addresses.</para>
<para>To enable proxying the requests, you must update the
following fields in <filename>nova.conf</filename>. </para>
following fields in <filename>nova.conf</filename>.</para>
<table rules="all">
<caption>nova.conf Metadata Settings</caption>
<col width="20%"/>
@@ -297,12 +297,12 @@ catalog.$Region.network.internalURL = http://10.211.55.17:9696
<td><para>Update to a string "password" value. You must also
configure the same value in the
<filename>metadata_agent.ini</filename> file, to
authenticate requests made for metadata. </para>
authenticate requests made for metadata.</para>
<para>The default value of an empty string in both files
will allow metadata to function, but will not be secure
if any non-trusted entities have access to the metadata
APIs exposed by <systemitem class="service"
>nova-api</systemitem>. </para></td>
>nova-api</systemitem>.</para></td>
</tr>
</tbody>
</table>
@@ -318,7 +318,7 @@ catalog.$Region.network.internalURL = http://10.211.55.17:9696
class="service">nova-api</systemitem> instance exposes
metadata APIs is determined by the value of
<literal>enabled_apis</literal> in its
<filename>nova.conf</filename>. </para>
<filename>nova.conf</filename>.</para>
</note>
</section>
<section xml:id="nova_with_neutron_vifplugging">
@@ -330,8 +330,8 @@ catalog.$Region.network.internalURL = http://10.211.55.17:9696
Networking plugins may require different types of vif-plugging.
You must specify the type of vif-plugging to be used for each
<systemitem class="service">nova-compute</systemitem> instance
in the <filename>nova.conf</filename> file. </para>
<para> The following plugins support the "port bindings" API
in the <filename>nova.conf</filename> file.</para>
<para>The following plugins support the "port bindings" API
extension that allows Nova to query for the type of vif-plugging
required: <itemizedlist>
<listitem>
@@ -357,19 +357,19 @@ catalog.$Region.network.internalURL = http://10.211.55.17:9696
<para>For these plugins, the default values in
<filename>nova.conf</filename> are sufficient. For other
plugins, see the sub-sections below for vif-plugging
configuration, or consult external plugin documentation. </para>
configuration, or consult external plugin documentation.</para>
<note>
<para>The vif-plugging configuration required for <systemitem
class="service">nova-compute</systemitem> might vary even
within a single deployment if your deployment includes
heterogeneous compute platforms (for example, some Compute
hosts are KVM while others are ESX). </para>
hosts are KVM while others are ESX).</para>
</note>
<section xml:id="nova_with_neutron_vifplugging_nvp">
<title>Vif-plugging with Nicira NVP Plugin</title>
<para>The choice of vif-plugging for the NVP Plugin depends on
which version of libvirt you use. To check your libvirt
version, use: </para>
version, use:</para>
<screen><prompt>$</prompt> <userinput>libvirtd version</userinput></screen>
<para>In the <filename>nova.conf</filename> file, update the
<literal>libvirt_vif_driver</literal> value, depending on
@@ -412,7 +412,7 @@ catalog.$Region.network.internalURL = http://10.211.55.17:9696
<filename>/etc/libvirt/qemu.conf</filename>, uncomment the
entry for 'cgroup_device_acl', add the value '/dev/net/tun'
to the list of items for the configuration entry, and then
restart libvirtd. </para>
restart libvirtd.</para>
</note>
</section>
</section>

2
doc/install-guide/section_networking-provider-router-with-private_networks.xml
View File

@@ -20,7 +20,7 @@
<note>
<para>Because you run the DHCP agent and L3 agent on one node, you must set
<literal>use_namespaces</literal> to <literal>True</literal> (which is the default)
in both agents' configuration files. </para>
in both agents' configuration files.</para>
</note>
<informalfigure>
<mediaobject>

2
doc/install-guide/section_networking-single-flat.xml
View File

@@ -1,6 +1,6 @@
<?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"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
xml:id="section_network-single-flat">
<title>Single Flat Network</title>
<para>This section describes how to install the OpenStack Networking service and its components

2
doc/training-guide/associate-horizon-cli-operations.xml
View File

@@ -5,7 +5,7 @@
version="5.0"
xml:id="using-horizon-cli">
<title>Using Horizon and the CLI for Operations Tasks</title>
<xi:include href="module001-ch006-overview-horizon-cli.xml"
<xi:include href="module001-ch006-overview-horizon-cli.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(/*/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback></xi:include>
<para><link xlink:href="https://blueprints.launchpad.net/openstack-manuals/+filebug" xlink:show="new">Submit a bug on

4
doc/training-guide/card006.xml
View File

@@ -6,11 +6,11 @@
xml:id="configure-virtualbox">
<title>VirtualBox Basics</title>
<!-- this maps to user story "Card008 - As an associate trainee I need to be able to understand the architecture of the RefStack architecture described in the Basic Install Guide" -->
<xi:include href="lab000-virtualbox-basics.xml"
<xi:include href="lab000-virtualbox-basics.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(/*/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback>
</xi:include>
<para><link xlink:href="https://blueprints.launchpad.net/openstack-manuals/+filebug" xlink:show="new">Submit a bug on
the section above. Short description for the bug summary. Paragraph for the description and
then tag with training-manuals.</link></para>
</section>
</section>

4
doc/training-guide/card007-core-overview.xml
View File

@@ -6,11 +6,11 @@
xml:id="card007-core-overview">
<title>Core Project Overview</title>
<!-- this maps to card007 user story title "Overview Core Project" -->
<xi:include href="../install-guide/basic-install-files/basic-install_architecture.xml"
<xi:include href="../install-guide/basic-install-files/basic-install_architecture.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(/*/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback>
</xi:include>
<para><link xlink:href="https://blueprints.launchpad.net/openstack-manuals/+filebug" xlink:show="new">Submit a bug on
the section above. Short description for the bug summary. Paragraph for the description and
then tag with training-manuals.</link></para>
</section>
</section>

2
doc/training-guide/card008.xml
View File

@@ -6,7 +6,7 @@
xml:id="card008-Understand_refstack_architecture">
<title>Understanding the RefStack Architecture</title>
<!-- this maps to user story "Card008 - As an associate trainee I need to be able to understand the architecture of the RefStack architecture described in the Basic Install Guide" -->
<xi:include href="module001-ch004-openstack-architecture.xml"
<xi:include href="module001-ch004-openstack-architecture.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(/*/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback>
</xi:include>

6
doc/training-guide/card009.xml
View File

@@ -5,15 +5,15 @@
xml:id="install-ubuntu">
<title>Install Ubuntu</title>
<!-- this maps to user story "Card009 - As a trainee I need to be able to understand how to install Ubuntu 12.04 (or 13.04 in later versions) -->
<!-- <xi:include href="../install-guide/basic-install-files/basic-install_controller-common.xml"
<!-- <xi:include href="../install-guide/basic-install-files/basic-install_controller-common.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(//*[@xml:id = 'controller-os']/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback>
</xi:include> ../install-guide/basic-install-files/basic-install_controller-common.xml
line 30
line 30
Severity: error
Description: IDREF "basic-install_common_repo" without matching ID
-->
<para><link xlink:href="https://blueprints.launchpad.net/openstack-manuals/+filebug" xlink:show="new">Submit a bug on
the section above. Short description for the bug summary. Paragraph for the description and
then tag with training-manuals.</link></para>
</section>
</section>

2
doc/training-guide/card011.xml
View File

@@ -5,7 +5,7 @@
version="5.0"
xml:id="card011-Installing_MySQL_Database_service">
<title>Installing MySQL</title>
<xi:include href="../install-guide/basic-install-files/basic-install_controller-common.xml"
<xi:include href="../install-guide/basic-install-files/basic-install_controller-common.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(//*[@xml:id = 'controller-mysql']/*[not(self::db:info)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback>
</xi:include>

4
doc/training-guide/card025.xml
View File

@@ -5,11 +5,11 @@
xml:id="role-controller-node">
<title>Role of the Controller Node</title>
<!-- this maps to user story "Card025 - As an associate trainee I need to be able to understand the role of the Controller Node in The RefStack architecture described in the basic install guide -->
<xi:include href="../install-guide/basic-install-files/basic-install_architecture.xml"
<xi:include href="../install-guide/basic-install-files/basic-install_architecture.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(/*/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback>
</xi:include>
<para><link xlink:href="https://blueprints.launchpad.net/openstack-manuals/+filebug" xlink:show="new">Submit a bug on
the section above. Short description for the bug summary. Paragraph for the description and
then tag with training-manuals.</link></para>
</section>
</section>

4
doc/training-guide/card037-rabbitmq.xml
View File

@@ -6,11 +6,11 @@
xml:id="card037-installing-rabbitMQ">
<title>Installing RabbitMQ</title>
<!-- this maps to card037 user story title "rabbit-mq" -->
<xi:include href="../install-guide/basic-install-files/basic-install_controller-common.xml"
<xi:include href="../install-guide/basic-install-files/basic-install_controller-common.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(//*[@xml:id = 'controller-rabbitmq']/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback>
</xi:include>
<para><link xlink:href="https://blueprints.launchpad.net/openstack-manuals/+filebug" xlink:show="new">Submit a bug on
the section above. Short description for the bug summary. Paragraph for the description and
then tag with training-manuals.</link></para>
</section>
</section>

2
doc/training-guide/card038.xml
View File

@@ -5,7 +5,7 @@
version="5.0"
xml:id="card038-Install-and-configure-OpenStack-Identity-Service-in-the-Controller-Node">
<title>Install and configure OpenStack Identity Service in the Controller Node</title>
<xi:include href="../install-guide/basic-install-files/basic-install_controller-keystone.xml"
<xi:include href="../install-guide/basic-install-files/basic-install_controller-keystone.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(/*/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback>
</xi:include>

2
doc/training-guide/card039-nova.xml
View File

@@ -6,7 +6,7 @@
xml:id="configure-nova">
<title>Install Nova</title>
<!-- this maps to user story "Card039 - As an associate trainee I need to be able to install and configure OpenStack Compute (Cloud Controller Services) in the Controller Node -->
<xi:include href="../install-guide/basic-install-files/basic-install_controller-nova.xml"
<xi:include href="../install-guide/basic-install-files/basic-install_controller-nova.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(/*/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback>
</xi:include>

2
doc/training-guide/card040-cinder.xml
View File

@@ -6,7 +6,7 @@
xml:id="configure-block-storage">
<title>Install Cinder</title>
<!-- this maps to user story "Card040 - As an associate trainee I need to be able to install and configure OpenStack Block Storage Service in the Controller Node -->
<xi:include href="../install-guide/basic-install-files/basic-install_controller-cinder.xml"
<xi:include href="../install-guide/basic-install-files/basic-install_controller-cinder.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(/*/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback>
</xi:include>

4
doc/training-guide/card041-neutron.xml
View File

@@ -8,12 +8,12 @@
<!-- this maps to user story "Card041 - As an associate trainee I need to be able to install and configure OpenStack Network Service (cloud controller) in the Controller Node -->
<para><emphasis role="bold">Install OpenVSwitch</emphasis></para>
<para>OpenVSwitch is one of many options, but for now we will stick with OVS.</para>
<xi:include href="../install-guide/basic-install-files/basic-install_compute-neutron.xml"
<xi:include href="../install-guide/basic-install-files/basic-install_compute-neutron.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(//*[@xml:id = 'compute-ovs']/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback>
</xi:include>
<para><emphasis role="bold">Install Neutron</emphasis></para>
<xi:include href="../install-guide/basic-install-files/basic-install_compute-neutron.xml"
<xi:include href="../install-guide/basic-install-files/basic-install_compute-neutron.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(//*[@xml:id = 'compute-neutron']/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback>
</xi:include>

4
doc/training-guide/card043-ovs-in-network-node.xml
View File

@@ -7,11 +7,11 @@
<title>OVS Installation and Configuration in Network node</title>
<!-- this maps to card043 ovs in the network node -->
<xi:include href="../install-guide/basic-install-files/basic-install_network-services.xml"
<xi:include href="../install-guide/basic-install-files/basic-install_network-services.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(//*[@xml:id = 'network-ovs']/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback>
</xi:include>
<para><link xlink:href="https://blueprints.launchpad.net/openstack-manuals/+filebug" xlink:show="new">Submit a bug on
the section above. Short description for the bug summary. Paragraph for the description and
then tag with training-manuals.</link></para>
</section>
</section>

4
doc/training-guide/card046-L3_Configuration_in_the_Network_Node.xml
View File

@@ -4,9 +4,9 @@
xmlns:xlink="http://www.w3.org/1999/xlink"
version="5.0"
xml:id="card046-L3_Configuration_in_the_Network_Node">
<title>L3 Configuration in the Network Node</title>
<title>L3 Configuration in the Network Node</title>
<!-- this maps to card046 L3_Configuration_in_the_Network_Node -->
<xi:include href="../install-guide/basic-install-files/basic-install_network-operating.xml"
<xi:include href="../install-guide/basic-install-files/basic-install_network-operating.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(//*[@xml:id = 'configure-l3']/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback>
</xi:include>

2
doc/training-guide/card047-install-nova-compute.xml
View File

@@ -6,7 +6,7 @@
xml:id="card047-install_nova_compute">
<title>Installing Nova</title>
<!-- This maps to card047 Install Nova Compute -->
<xi:include href="../install-guide/basic-install-files/basic-install_compute-nova.xml"
<xi:include href="../install-guide/basic-install-files/basic-install_compute-nova.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(/*/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback>
</xi:include>

4
doc/training-guide/card074-horizon-snapshots.xml
View File

@@ -7,11 +7,11 @@
<title>Creating Snapshots</title>
<para><emphasis role="bold">Creating image snapshots using Horizon</emphasis></para>
<!-- this maps to user story "Card074 - As an associate trainee I need to be able to Take a snapshot using OpenStack Dashboard (Horizon) -->
<xi:include href="../user-guide-admin/section_dashboard_admin_manage_instances.xml"
<xi:include href="../user-guide-admin/section_dashboard_admin_manage_instances.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(//*[@xml:id = 'dashboard_instance_snapshots']/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback>
</xi:include>
<para><link xlink:href="https://blueprints.launchpad.net/openstack-manuals/+filebug" xlink:show="new">Submit a bug on
the section above. Short description for the bug summary. Paragraph for the description and
then tag with training-manuals.</link></para>
</section>
</section>

2
doc/training-guide/card126-horizon.xml
View File

@@ -6,7 +6,7 @@
xml:id="configure-dashboard">
<title>Install Horizon</title>
<!-- this maps to user story "Card126 - As an associate trainee I need to be able to install OpenStack Dashboard (Horizon) in the Controller node -->
<xi:include href="../install-guide/basic-install-files/basic-install_controller-dashboard.xml"
<xi:include href="../install-guide/basic-install-files/basic-install_controller-dashboard.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(/*/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback></xi:include>
<para><link xlink:href="https://blueprints.launchpad.net/openstack-manuals/+filebug" xlink:show="new">Submit a bug on

4
doc/training-guide/card127-glance.xml
View File

@@ -6,11 +6,11 @@
xml:id="configure-image">
<title>Install Glance</title>
<!-- this maps to user story "Card127 - As an associate trainee I need to be able to install OpenStack the Image service (Glance) on the controller node -->
<xi:include href="../install-guide/basic-install-files/basic-install_controller-glance.xml"
<xi:include href="../install-guide/basic-install-files/basic-install_controller-glance.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(/*/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback>
</xi:include>
<para><link xlink:href="https://blueprints.launchpad.net/openstack-manuals/+filebug" xlink:show="new">Submit a bug on
the section above. Short description for the bug summary. Paragraph for the description and
then tag with training-manuals.</link></para>
</section>
</section>

2
doc/training-guide/card128-swift.xml
View File

@@ -6,7 +6,7 @@
xml:id="configure-swift">
<title>Install Swift</title>
<!-- this maps to user story "Card128 - As an associate trainee I need to be able to install and configure OpenStack Object Storage (swift) in the Controller Node -->
<xi:include href="../install-guide/section_object-storage-install-ubuntu.xml"
<xi:include href="../install-guide/section_object-storage-install-ubuntu.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(//*[@xml:id = 'general-installation-steps-swift']/*[not(self::db:title)])">
<xi:fallback><para><mediaobject><imageobject><imagedata fileref="figures/openstack-training-remote-content-not-available.png" format="PNG"/></imageobject></mediaobject>Remote content not available</para><para>image source</para><para><link xlink:href="https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing">https://docs.google.com/drawings/d/1J2LZSxmc06xKyxMgPjv5fC0blV7qK6956-AeTmFOZD4/edit?usp=sharing</link></para></xi:fallback>
</xi:include>

27
doc/training-guide/lab000-virtualbox-basics.xml
View File

@@ -32,7 +32,7 @@
<para><emphasis role="bold">OpenStack:</emphasis>OpenStack
Official Documentation (docs.openstack.org)</para>
<para><emphasis role="bold">Networking:</emphasis>Computer
Networks (5th Edition) by Andrew S. Tanenbaum </para>
Networks (5th Edition) by Andrew S. Tanenbaum</para>
<para><emphasis role="bold">VirtualBox:</emphasis>Virtual Box
Manual (http://www.virtualbox.org/manual/UserManual.html)</para>
<para><emphasis role="bold">Requirements :</emphasis></para>
@@ -144,7 +144,7 @@
<para><guilabel>Setup Your VM Environment</guilabel></para>
<para>Before you can start configuring your Environment you need to
download some of the following stuff:</para>
<orderedlist>
<listitem>
<para><link xlink:href="https://www.virtualbox.org/wiki/Downloads">
@@ -216,8 +216,7 @@
</listitem>
</itemizedlist>
<para><emphasis role="bold">Vboxnet0</emphasis></para>
<informaltable class="c25">
<tbody>
<tr>
@@ -251,8 +250,8 @@
</mediaobject>
</figure>
<para><emphasis role="bold">Vboxnet1</emphasis></para>
<informaltable class="c25">
<tbody>
<tr>
@@ -286,8 +285,7 @@
</mediaobject>
</figure>
<para><emphasis role="bold">Vboxnet2</emphasis></para>
<informaltable class="c25">
<tbody>
<tr>
@@ -375,8 +373,7 @@
<para>Configure the networks</para>
<para>(Ignore the IP Address for now, you will set it up from
inside the VM)</para>
<informaltable class="c25">
<tbody>
<tr>
@@ -450,8 +447,7 @@
<para>Configure the networks</para>
<para>(Ignore the IP Address for now, you will set it up from
inside the VM)</para>
<informaltable class="c25">
<tbody>
<tr>
@@ -538,8 +534,7 @@
<para>Configure the networks</para>
<para>(Ignore the IP Address for now, you will set it up from
inside the VM)</para>
<informaltable class="c25">
<tbody>
<tr>
@@ -648,5 +643,5 @@ $ping www.google.com</programlisting>
Ubuntu Server on the above setup Virtual Box Instances. In the
next section we will go through deploying OpenStack using the
above created Virtual Box instances.</para>
</chapter>
</chapter>

10
doc/training-guide/lab001-compute-node.xml
View File

@@ -26,7 +26,7 @@
used by virtual box VM’s for OpenStack networks, so that
OpenStack’s services can communicate with each other.</para>
<para><guilabel>Compute Node</guilabel></para>
<para> Start your Controller Node the one you setup in previous
<para>Start your Controller Node the one you setup in previous
section.</para>
<para><emphasis role="bold">Preparing Ubuntu
13.04/12.04</emphasis></para>
@@ -39,15 +39,15 @@
</listitem>
<listitem>
<para>Add Grizzly repositories:</para>
<para><programlisting>#apt-get install ubuntu-cloud-keyring python-software-properties software-properties-common python-keyring
# echo deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly main >> /etc/apt/sources.list.d/grizzly.list </programlisting></para>
<para><programlisting>#apt-get install ubuntu-cloud-keyring python-software-properties software-properties-common python-keyring
# echo deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly main >> /etc/apt/sources.list.d/grizzly.list</programlisting></para>
</listitem>
<listitem>
<para> Update your system: </para>
<para>Update your system:</para>
<para><programlisting>#apt-get update
#apt-get upgrade
#apt-get dist-upgrade</programlisting></para>
</listitem>
</itemizedlist>
<para>More Content To be Added soon.</para>
</chapter>
</chapter>

10
doc/training-guide/lab001-control-node.xml
View File

@@ -22,7 +22,7 @@
used by virtual box VM’s for OpenStack networks, so that
OpenStack’s services can communicate with each other.</para>
<para><guilabel>Controller Node</guilabel></para>
<para> Start your Controller Node the one you setup in previous
<para>Start your Controller Node the one you setup in previous
section.</para>
<para><emphasis role="bold">Preparing Ubuntu
13.04/12.04</emphasis></para>
@@ -35,15 +35,15 @@
</listitem>
<listitem>
<para>Add Grizzly repositories:</para>
<para><programlisting>#apt-get install ubuntu-cloud-keyring python-software-properties software-properties-common python-keyring
# echo deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly main >> /etc/apt/sources.list.d/grizzly.list </programlisting></para>
<para><programlisting>#apt-get install ubuntu-cloud-keyring python-software-properties software-properties-common python-keyring
# echo deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly main >> /etc/apt/sources.list.d/grizzly.list</programlisting></para>
</listitem>
<listitem>
<para> Update your system: </para>
<para>Update your system:</para>
<para><programlisting>#apt-get update
#apt-get upgrade
#apt-get dist-upgrade</programlisting></para>
</listitem>
</itemizedlist>
<para>More Content To be Added soon.</para>
</chapter>
</chapter>

10
doc/training-guide/lab002-network-node.xml
View File

@@ -26,7 +26,7 @@
used by virtual box VM’s for OpenStack networks, so that
OpenStack’s services can communicate with each other.</para>
<para><guilabel>Network Node</guilabel></para>
<para> Start your Controller Node the one you setup in previous
<para>Start your Controller Node the one you setup in previous
section.</para>
<para><emphasis role="bold">Preparing Ubuntu
13.04/12.04</emphasis></para>
@@ -39,15 +39,15 @@
</listitem>
<listitem>
<para>Add Grizzly repositories:</para>
<para><programlisting>#apt-get install ubuntu-cloud-keyring python-software-properties software-properties-common python-keyring
# echo deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly main >> /etc/apt/sources.list.d/grizzly.list </programlisting></para>
<para><programlisting>#apt-get install ubuntu-cloud-keyring python-software-properties software-properties-common python-keyring
# echo deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly main >> /etc/apt/sources.list.d/grizzly.list</programlisting></para>
</listitem>
<listitem>
<para> Update your system: </para>
<para>Update your system:</para>
<para><programlisting>#apt-get update
#apt-get upgrade
#apt-get dist-upgrade</programlisting></para>
</listitem>
</itemizedlist>
<para>More Content To be Added soon.</para>
</chapter>
</chapter>

6
doc/training-guide/module001-ch001-intro-text.xml
View File

@@ -25,7 +25,7 @@
education and expanding its possibilities. Being open in nature,
these resources are free to use and modify, tailor them at no cost,
shape them as per your requirements and let the cloud do all the
hard work. </para>
hard work.</para>
<para>In data centers today, many computers suffer under-utilization
in computing power and networking bandwidth. For example, projects
may need a large amount of computing capacity to complete a
@@ -90,7 +90,7 @@
operates for a single organization, but can be managed on-premise
or off-premise. A public cloud has an infrastructure that is
available to the general public or a large industry group and is
likely owned by a cloud services company. </para>
likely owned by a cloud services company.</para>
<para>Clouds can also be described as hybrid. A hybrid cloud can be
a deployment model, as a composition of both public and private
clouds, or a hybrid model for cloud computing may involve both
@@ -110,7 +110,7 @@
technically, its reach and its impact on the entire world.</para>
<para>OpenStack is an Open source software for building private and
public clouds which delivers a massively scalable cloud operating
system. </para>
system.</para>
<informaltable class="c20">
<tbody>
<tr>

2
doc/training-guide/module001-ch002-brief-overview.xml
View File

@@ -80,7 +80,7 @@
<para><guilabel>Who it's for:</guilabel></para>
<para>Enterprises, service providers, government and academic
institutions with physical hardware that would like to build a
public or private cloud. </para>
public or private cloud.</para>
<para><guilabel>How it's being used today:</guilabel></para>
<para>Organizations like CERN, Cisco WebEx, DreamHost, eBay, the
Gap, HP, MercadoLibre, NASA, PayPal, Rackspace and University of

4
doc/training-guide/module001-ch005-vm-provisioning-walk-through.xml
View File

@@ -24,7 +24,7 @@
based on budget and resource constraints as well as the
inevitable list of supported features and required technical
specifications. The majority of development is done with the KVM
and Xen-based hypervisors. Refer to
and Xen-based hypervisors. Refer to
<link xlink:href="http://wiki.openstack.org/HypervisorSupportMatrix"></link>
<link xlink:href="http://goo.gl/n7AXnC">
http://goo.gl/n7AXnC</link>
@@ -236,4 +236,4 @@
VM provisioning. For launching a VM, you can either use
Command Line Interface or the OpenStack Horizon Dashboard.
</para>
</chapter>
</chapter>

22
doc/training-guide/module001-ch006-overview-horizon-cli.xml
View File

@@ -610,7 +610,7 @@
</listitem>
</orderedlist>
<para>To SSH into your instance, you use the downloaded keypair
file. </para>
file.</para>
<para>To SSH into your instance</para>
<orderedlist>
<listitem>
@@ -1080,7 +1080,7 @@
<para>You can upload images through the glance client or the Image
Service API. You can also use the nova client to list images,
set and delete image metadata, delete images, and take a
snapshot of a running instance to create an image. </para>
snapshot of a running instance to create an image.</para>
<para><guilabel>Manage images with the glance client</guilabel></para>
<para>To list or get details for images</para>
<orderedlist>
@@ -1241,7 +1241,7 @@
<para>You can also assign a floating IP address to a running
instance to make it accessible from outside the cloud. You
assign a floating IP address to an instance and attach a block
storage device, or volume, for persistent storage. </para>
storage device, or volume, for persistent storage.</para>
<para><guilabel>Set up access and security for instances</guilabel></para>
<para>When you launch a virtual machine, you can inject a key
pair, which provides SSH access to your instance. For this to
@@ -1295,7 +1295,7 @@
<para>You can also assign a floating IP address to a running
instance to make it accessible from outside the cloud. You
assign a floating IP address to an instance and attach a block
storage device, or volume, for persistent storage. </para>
storage device, or volume, for persistent storage.</para>
<para><guilabel>Add or import keypairs</guilabel></para>
<para>To add a key</para>
<para>You can generate a keypair or upload an existing public
@@ -1619,7 +1619,7 @@
<para>To gather the parameters to launch an instance</para>
<orderedlist>
<listitem>
<para>On a shell, source the OpenStack RC file. </para>
<para>On a shell, source the OpenStack RC file.</para>
</listitem>
<listitem>
<para>List the available flavors:</para>
@@ -1704,7 +1704,7 @@
</listitem>
<listitem>
<para>$ nova boot --flavor FLAVOR_ID --image IMAGE_ID
--key_name KEY_NAME --user-data mydata.file \
--key_name KEY_NAME --user-data mydata.file \
--security_group SEC_GROUP NAME_FOR_INSTANCE --meta
KEY=VALUE --meta KEY=VALUE</para>
</listitem>
@@ -1778,7 +1778,7 @@
<listitem>
<para># cinder create --image-id
397e713c-b95b-4186-ad46-6126863ea0a9 --display-name
my-bootable-vol 8 </para>
my-bootable-vol 8</para>
</listitem>
<listitem>
<para>Optionally, to configure your volume, see the
@@ -2047,7 +2047,7 @@
<para>$ nova resize myCirrosServer 4 --poll</para>
</listitem>
<listitem>
<para>Instance resizing... 100% completeFinished </para>
<para>Instance resizing... 100% completeFinished</para>
</listitem>
<listitem>
<para>Show the status for your server:</para>
@@ -2191,7 +2191,7 @@
</listitem>
<listitem>
<para>$ nova evacuate evacuated_server_name host_b
--on-shared-storage </para>
--on-shared-storage</para>
</listitem>
</orderedlist>
<para><guilabel>Delete an instance</guilabel></para>
@@ -2315,7 +2315,7 @@
my-baremetal-flavor test</para>
</listitem>
<listitem>
<para>|... wait for instance to become active ... </para>
<para>|... wait for instance to become active ...</para>
</listitem>
<listitem>
<para>You can list bare metal nodes and interfaces. When a
@@ -2426,7 +2426,7 @@
local</para>
</listitem>
<listitem>
<para>Created a new network: </para>
<para>Created a new network:</para>
</listitem>
<listitem>
<para>Just as shown previous, the unknown option

39
doc/training-guide/module001-ch007-keystone-arch.xml
View File

@@ -6,7 +6,7 @@
xml:id="module001-ch007-keystone-arch">
<title>Ketstone Architecture</title>
<para>More Content To be Added ...</para>
<para><guilabel>Identity Service Concepts</guilabel></para>
<para>The Identity service performs the following
functions:</para>
@@ -22,7 +22,7 @@
</itemizedlist>
<para>To understand the Identity Service, you must understand the
following concepts:</para>
<para><guilabel>User</guilabel></para>
<para>Digital representation of a person, system, or service who
uses OpenStack cloud services. Identity authentication
@@ -31,8 +31,7 @@
and may be assigned tokens to access resources. Users may be
directly assigned to a particular tenant and behave as if they
are contained in that tenant.</para>
<para><guilabel><anchor xml:id="h.i1npk4aiu35h"/>Credentials</guilabel></para>
<para>Data that is known only by a user that proves who they
are. In the Identity Service, examples are:</para>
@@ -48,8 +47,7 @@
Service</para>
</listitem>
</itemizedlist>
<para><guilabel><anchor xml:id="h.aa29gdlbf7qa"/>Authentication</guilabel></para>
<para>The act of confirming the identity of a user. The Identity
Service confirms an incoming request by validating a set of
@@ -58,8 +56,7 @@
In response to these credentials, the Identity Service issues
the user an authentication token, which the user provides in
subsequent requests.</para>
<para><guilabel><anchor xml:id="h.grqljkbnx8fs"/>Token</guilabel></para>
<para>An arbitrary bit of text that is used to access resources.
Each token has a scope which describes which resources are
@@ -70,30 +67,26 @@
support additional protocols in the future. The intent is for
it to be an integration service foremost, and not aspire to be
a full-fledged identity store and management solution.</para>
<para><guilabel><anchor xml:id="h.qz798xvt751f"/>Tenant</guilabel></para>
<para>A container used to group or isolate resources and/or
identity objects. Depending on the service operator, a tenant
may map to a customer, account, organization, or
project.</para>
<para><guilabel><anchor xml:id="h.ayp97sn984my"/>Service</guilabel></para>
<para>An OpenStack service, such as Compute (Nova), Object
Storage (Swift), or Image Service (Glance). Provides one or
more endpoints through which users can access resources and
perform operations.</para>
<para><guilabel><anchor xml:id="h.74y77xwdnwlm"/>Endpoint</guilabel></para>
<para>An network-accessible address, usually described by URL,
from where you access a service. If using an extension for
templates, you can create an endpoint template, which
represents the templates of all the consumable services that
are available across the regions.</para>
<para><guilabel><anchor xml:id="h.r7samiog05in"/>Role</guilabel></para>
<para>A personality that a user assumes that enables them to
perform a specific set of operations. A role includes a set of
@@ -112,9 +105,7 @@
</imageobject>
</mediaobject>
</figure>
<para><guilabel><anchor xml:id="h.rdpcpnbvn06w"/>User management</guilabel></para>
<para>The main components of Identity user management are:</para>
<itemizedlist>
@@ -148,7 +139,7 @@
user the "compute-user" role in the "acme" tenant:</para>
<para>$ keystone user-list</para>
<para>$ keystone user-role-add --user=892585 --role=9a764e
--tenant-id=6b8fd2 </para>
--tenant-id=6b8fd2</para>
<para>A user can be assigned different roles in different tenants:
for example, Alice may also have the "admin" role in the
"Cyberdyne" tenant. A user can also be assigned multiple roles
@@ -171,11 +162,9 @@
that there are no restrictions on which users can create
volumes: if the user has any role in a tenant, they will be able
to create volumes in that tenant.</para>
<para><guilabel><anchor xml:id="h.f5989v85c3fd"/></guilabel></para>
<para><guilabel><anchor xml:id="h.1rrjgvz0nkwh"/>Service
management</guilabel></para>
<para>The Identity Service provides the following service
@@ -194,5 +183,5 @@
service.</para>
<para>The commands for creating services and endpoints are
described in a later section.</para>
</chapter>

27
doc/training-guide/module001-ch009-vm-placement.xml
View File

@@ -44,13 +44,12 @@
(ComputeFilter).</para>
</listitem>
</itemizedlist>
<para><guilabel>Filter Scheduler</guilabel></para>
<para>The Filter Scheduler supports filtering and weighting to
make informed decisions on where a new instance should be created.
This Scheduler supports only working with Compute Nodes.</para>
<para><guilabel>Filtering</guilabel></para>
<figure>
<title>Filtering</title>
@@ -124,16 +123,16 @@
these)Examples are: "&gt;= 5", "s== 2.1.0", "&lt;in&gt; gcc",
and "&lt;or&gt; fpu &lt;or&gt; gpu"</para>
<programlisting>class RamFilter(filters.BaseHostFilter):
"""Ram Filter with over subscription flag"""
def host_passes(self, host_state, filter_properties):
"""Only return hosts with sufficient available RAM."""
"""Ram Filter with over subscription flag"""
instance_type = filter_properties.get('instance_type')
requested_ram = instance_type['memory_mb']
free_ram_mb = host_state.free_ram_mb
total_usable_ram_mb = host_state.total_usable_ram_mb
used_ram_mb = total_usable_ram_mb - free_ram_mb
def host_passes(self, host_state, filter_properties):
"""Only return hosts with sufficient available RAM."""
instance_type = filter_properties.get('instance_type')
requested_ram = instance_type['memory_mb']
free_ram_mb = host_state.free_ram_mb
total_usable_ram_mb = host_state.total_usable_ram_mb
used_ram_mb = total_usable_ram_mb - free_ram_mb
return total_usable_ram_mb * FLAGS.ram_allocation_ratio - used_ram_mb >= requested_ram</programlisting>
<para>Here ram_allocation_ratio means the virtual RAM to
physical RAM allocation ratio (it is 1.5 by default). Really,
@@ -177,9 +176,7 @@
are also called isolated. This Scheduler checks if
image_isolated flag named in instance specifications is the
same that the host has.</para>
<para><guilabel>Weights</guilabel></para>
<para>Filter Scheduler uses so-called weightsduring its
work.</para>

4
doc/training-guide/module001-ch010-vm-provisioning-indepth.xml
View File

@@ -81,13 +81,13 @@
upload image from image storage.</para>
</listitem>
<listitem>
<para>glance-api validates the auth-token with keystone. </para>
<para>glance-api validates the auth-token with keystone.</para>
</listitem>
</orderedlist>
<para>nova-compute get the image metadata.</para>
<para>nova-compute does the REST-call by passing auth-token to
Network API to allocate and configure the network such that
instance gets the IP address. </para>
instance gets the IP address.</para>
<orderedlist>
<listitem>
<para>quantum-server validates the auth-token with

2
doc/training-guide/module002-ch003-neutron-use-cases.xml
View File

@@ -6,7 +6,7 @@
xml:id="module002-ch003-neutron-use-cases">
<title>Neutron Use Cases</title>
<para>As of now you must be wondering, how to use these awesome
features that OpenStack Networking has given to us. </para>
features that OpenStack Networking has given to us.</para>
<para><guilabel><anchor xml:id="h.lrsgdytf1mh5"/>Use Case: Single Flat
Network</guilabel></para>
<para>In the simplest use case, a single OpenStack Networking

4
doc/training-guide/module002-ch004-security-in-neutron.xml
View File

@@ -28,7 +28,7 @@
restart nova-api and nova-compute in order to pick up this
change. After this change is made one will be able to use
both the OpenStack Compute and OpenStack Network security
group API at the same time.</para>
group API at the same time.</para>
<para><guilabel>Authentication and Authorization</guilabel></para>
<para>OpenStack Networking uses the OpenStack Identity service
(project name keystone) as the default authentication
@@ -137,4 +137,4 @@
identifier of the user submitting the request.</para>
</listitem>
</itemizedlist>
</chapter>
</chapter>

8
doc/training-guide/module003-ch004-swift-building-blocks.xml
View File

@@ -260,7 +260,7 @@
through a few scenarios and introduce the components.</para>
<para><guilabel>Bird-eye View</guilabel></para>
<para><emphasis role="bold">Upload</emphasis></para>
<para>A client uses the REST API to make a HTTP request to PUT
an object into an existing Container. The cluster receives
the request. First, the system must figure out where the
@@ -284,12 +284,12 @@
</imageobject>
</mediaobject>
</figure>
<para><emphasis role="bold">Download</emphasis></para>
<para><emphasis role="bold">Download</emphasis></para>
<para>A request comes in for an Account/Container/object.
Using the same consistent hashing, the Partition name is
generated. A lookup in the Ring reveals which storage
nodes contain that Partition. A request is made to one of
the storage nodes to fetch the object and if that fails,
requests are made to the other nodes.</para>
</chapter>
</chapter>

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

@@ -144,7 +144,7 @@
</tr>
</tbody>
</table>
<section xml:id="dashboard_view_quotas_procedure">
<title>View default project quotas</title>
<procedure>

6
doc/user-guide-admin/section_nova_specify_host.xml
View File

@@ -6,13 +6,13 @@
<title>Select on which host instances are launched</title>
<para>With the appropriate permissions, you can select on which
host instances are launched and which roles can boot instances
on this host. </para>
on this host.</para>
<procedure><step><para>To select the host where instances are launched, use the
<literal>--availability_zone
<replaceable>zone</replaceable>:<replaceable>host</replaceable></literal>
parameter on n the <command>nova boot</command>
parameter on the <command>nova boot</command>
command, </para>
<para>For example:</para>
<para>For example:</para>
<screen><prompt>$</prompt> <userinput>nova boot --image &lt;uuid&gt; --flavor m1.tiny --key_name test --availability-zone nova:server2</userinput></screen>
</step><step><para>To specify which roles can launch an instance on a specified
host, enable the <literal>create:forced_host</literal>

4
doc/user-guide/section_heat_cli.xml
View File

@@ -7,7 +7,7 @@
xml:id="heat-stack-create">
<title>Create and manage stacks</title>
<section xml:id="create_stacks_proc"> <title>Create a stack from an example template file</title>
<procedure>
<procedure>
<step>
<para>To create a stack, or template, from an <link
xlink:href="https://github.com/openstack/heat-templates">example template
@@ -54,7 +54,7 @@
+--------------------------------------+---------------+-----------------+----------------------+</computeroutput></screen></para>
</step>
<step>
<para>To show the details of a stack, run the following
command:</para>
<screen><prompt>$</prompt> <userinput>heat stack-show mystack</userinput></screen></step>

4
doc/user-guide/section_swift_cli_howto.xml
View File

@@ -13,10 +13,10 @@
library, <literal>client.py</literal>, which seamlessly
re-authenticates if the current token expires during
processing, retries operations multiple times, and provides a
processing concurrency of 10. </para>
processing concurrency of 10.</para>
<para>Users have roles on accounts. For example, the admin
role enables full access to all containers and objects in an
account. </para>
account.</para>
<para>You can set access control lists (ACLs) are set at the container level
and support lists for read and write access, which are set
with the <literal>X-Container-Read</literal> and