openstack/openstack-manuals
Code Issues Proposed changes

cleaning up whitespaces

Browse Source 
Removing more whitespaces found by the new validation method.
https://review.openstack.org/#/c/40414/ is workable after merging
this change.

Patchset fixes missing periods.

Change-Id: I95b866cc3dfdd7fd71afb98f9b4f78a3e484504a
This commit is contained in:
Christian Berendt 2013-08-07 08:58:27 +02:00 committed by annegentle
parent 2387fc040f
commit 588d397e8f
66 changed files with 689 additions and 690 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/src/docbkx/common/ch_getstart.xml
View File

@ -461,7 +461,7 @@
installations that need to support euca2ools. The
euca2ools tools talk to nova-objectore in “S3 language”
and <systemitem class="service">nova-objectstore</systemitem> translates S3 requests into glance
requests </para>
requests.</para>
</listitem>
<listitem>
<para>The <code>euca2ools</code> client is not an

16
doc/src/docbkx/common/ch_support-compute.xml
View File

@ -4,13 +4,15 @@
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="troubleshooting-openstack-compute">
<title>Troubleshooting OpenStack Compute</title>
<para>Common problems for Compute typically involve misconfigured networking or credentials that are not sourced properly in the environment. Also, most flat networking configurations do not enable ping or ssh from a compute node to the instances running on that node. Another common problem is trying to run 32-bit images on a 64-bit compute node. This section offers more information about how to troubleshoot Compute.</para>
<section xml:id="log-files-for-openstack-compute"><title>Log files for OpenStack Compute</title><para>Log files are stored in /var/log/nova and there is a log file for each service, for example
nova-compute.log. You can format the log strings using options for the nova.log
module. The options used to set format strings are: logging_context_format_string
and logging_default_format_string. If the log level is set to debug, you can also
specify logging_debug_format_suffix to append extra formatting. For information
about what variables are available for the formatter see:
http://docs.python.org/library/logging.html#formatter </para>
<section xml:id="log-files-for-openstack-compute"><title>Log files for OpenStack Compute</title><para>Log files are stored in /var/log/nova and there is a log file for each
service, for example nova-compute.log. You can format the log
strings using options for the nova.log module. The options used to
set format strings are: logging_context_format_string and
logging_default_format_string. If the log level is set to debug, you
can also specify logging_debug_format_suffix to append extra
formatting. For information about what variables are available for
the formatter see:
http://docs.python.org/library/logging.html#formatter.</para>
<para>You have two options for logging for OpenStack Compute based on configuration
settings. In nova.conf, include the logfile option to enable logging. Alternatively
you can set use_syslog=1, and then the nova daemon logs to syslog.</para></section>

6
doc/src/docbkx/common/ch_support.xml
View File

@ -40,7 +40,7 @@
additional mailing lists is available at
<link
xlink:href="http://wiki.openstack.org/MailingLists">http://wiki.openstack.org/MailingLists</link>.</para></simplesect><simplesect>
<title>The OpenStack Wiki search </title>
<title>The OpenStack Wiki search</title>
<para>The <link xlink:href="http://wiki.openstack.org/">OpenStack wiki</link> contains content
on a broad range of topics, but some of it sits a bit below the surface. Fortunately, the wiki
search feature is very powerful in that it can do both searches by title and by content. If
@ -48,7 +48,7 @@
find lots of content using the search feature. More is being added all the time, so be sure to
check back often. You can find the search box in the upper right hand corner of any OpenStack wiki
page.</para></simplesect>
<simplesect><title>The Launchpad Bugs area </title>
<simplesect><title>The Launchpad Bugs area</title>
<para>So you think you've found a bug. That's great! Seriously, it is. The OpenStack community
values your setup and testing efforts and wants your feedback. To log a bug you must
have a Launchpad account, so sign up at https://launchpad.net/+login if you do not
@ -92,7 +92,7 @@
</simplesect>
<simplesect>
<title>The OpenStack IRC channel </title>
<title>The OpenStack IRC channel</title>
<para>The OpenStack community lives and breathes in the
#openstack IRC channel on the Freenode network. You
can come by to hang out, ask questions, or get

2
doc/src/docbkx/common/glossary/glossary-terms.xml
View File

@ -8,7 +8,7 @@
<para>Licensed under the Apache License, Version 2.0 (the
"License"); you may not use this file except in
compliance with the License. You may obtain a copy of
the License at </para>
the License at</para>
<para>
<link
xlink:href="http://www.apache.org/licenses/LICENSE-2.0"

2
doc/src/docbkx/common/section_compute-configure-console.xml
View File

@ -20,7 +20,7 @@
video streaming and more. SPICE is a new protocol which aims to
address all the limitations in VNC, to provide good remote
desktop support.</para>
<para> SPICE support in OpenStack Compute shares a similar
<para>SPICE support in OpenStack Compute shares a similar
architecture to the VNC implementation. The OpenStack Dashboard
uses a SPICE-HTML5 widget in its console tab, that communicates
to the <literal>nova-spicehtml5proxy</literal> service using

2
doc/src/docbkx/common/section_fibrechannel.xml
View File

@ -20,7 +20,7 @@
</para>
</section>
<section xml:id="fibre-channel-reqs">
<title>Requirements for KVM Hosts </title>
<title>Requirements for KVM Hosts</title>
<para>The KVM host must have the following system packages installed:</para>
<para>
<itemizedlist>

2
doc/src/docbkx/common/section_glance_cli_manage_images.xml
View File

@ -20,7 +20,7 @@
><citetitle>Virtual Machine Image
Guide</citetitle></link>.</para>
<section xml:id="glance-image-list">
<title>Manage images with the glance client </title>
<title>Manage images with the glance client</title>
<procedure>
<title>To list images</title>
<step>

4
doc/src/docbkx/common/section_keystone-concepts.xml
View File

@ -39,10 +39,10 @@
are: </para>
<itemizedlist>
<listitem>
<para>Username and password </para>
<para>Username and password</para>
</listitem>
<listitem>
<para>Username and API key </para>
<para>Username and API key</para>
</listitem>
<listitem>
<para>An authentication token provided by the

16
doc/src/docbkx/common/section_keystone_certificates-for-pki.xml
View File

@ -113,11 +113,11 @@ SrWY8lF3HrTcJT23sZIleg==</screen></para>
<itemizedlist>
<listitem>
<para>all certificate and key files must be in
Privacy Enhanced Mail (PEM) format </para>
Privacy Enhanced Mail (PEM) format</para>
</listitem>
<listitem>
<para>private key files must not be protected by a
password </para>
password</para>
</listitem>
</itemizedlist>
<para>When using signing certificate issued by an external
@ -135,10 +135,10 @@ SrWY8lF3HrTcJT23sZIleg==</screen></para>
</listitem>
<listitem>
<para>Convert certificate and private key to PEM if
needed </para>
needed</para>
</listitem>
<listitem>
<para>Install External Signing Certificate </para>
<para>Install External Signing Certificate</para>
</listitem>
</orderedlist>
</section>
@ -191,21 +191,21 @@ openssl req -newkey rsa:1024 -keyout signing_key.pem -keyform PEM -out signing_c
<listitem>
<para>
<literal>signing_cert.pem</literal> - (Keystone
token) signing certificate in PEM format </para>
token) signing certificate in PEM format</para>
</listitem>
<listitem>
<para>
<literal>signing_key.pem</literal> - corresponding
(non-encrypted) private key in PEM format </para>
(non-encrypted) private key in PEM format</para>
</listitem>
<listitem>
<para>
<literal>cacert.pem</literal> - trust CA
certificate chain in PEM format </para>
certificate chain in PEM format</para>
</listitem>
</itemizedlist>
<para>Copy the above to your certificate directory. For
example: </para>
example:</para>
<screen>
mkdir -p /etc/keystone/ssl/certs
cp signing_cert.pem /etc/keystone/ssl/certs/

2
doc/src/docbkx/common/section_kvm.xml
View File

@ -112,7 +112,7 @@ KVM acceleration can NOT be used</computeroutput></screen></para>
<section xml:id="enabling-kvm">
<title>Enabling KVM</title>
<para>KVM requires the <literal>kvm </literal>and either <literal>kvm-intel</literal> or
<para>KVM requires the <literal>kvm</literal> and either <literal>kvm-intel</literal> or
<literal>kvm-amd</literal> modules to be loaded. This may have been configured
automatically on your distribution when KVM is installed.</para>
<para>You can check that they have been loaded using <command>lsmod</command>, as follows,

2
doc/src/docbkx/common/section_moosefs.xml
View File

@ -77,7 +77,7 @@
</figure>
</para>
<section xml:id="installing-moosefs-metadata-metalogger-servers">
<title> Installing the MooseFS metadata and metalogger servers</title>
<title>Installing the MooseFS metadata and metalogger servers</title>
<para>Both components could be run anywhere , as long as the MooseFS chunkservers can reach
the MooseFS master server.</para>
<para>In our deployment, both MooseFS master and slave run their services inside a virtual

2
doc/src/docbkx/common/section_storage-concepts.xml
View File

@ -13,7 +13,7 @@
<col width="33%"/>
<thead>
<tr>
<td>On-instance / ephemeral </td>
<td>On-instance / ephemeral</td>
<td>Volumes block storage (Cinder)</td>
<td>Object Storage (Swift)</td>
</tr>

2
doc/src/docbkx/common/section_using-vnc-console.xml
View File

@ -6,7 +6,7 @@
<title>Using VNC Console</title>
<para>There are several methods to interact with the VNC console,
using a VNC client directly, a special java client, or through the
web browser. For information about configuring the console,
web browser. For information about configuring the console,
see <xref linkend="installing-openstack-dashboard"/>.
</para>

2
doc/src/docbkx/common/section_xen-install.xml
View File

@ -65,7 +65,7 @@
selected by choosing "XenDesktop Optimized" option. In
case you are using an answer file, make sure you use
<literal>srtype="ext"</literal> within the
<literal> installation</literal> tag of the answer
<literal>installation</literal> tag of the answer
file.</para>
</important></para>
<section xml:id="xenapi-post-install">

6
doc/src/docbkx/common/tables/ldap-keystone-conf.xml
View File

@ -18,16 +18,16 @@
</tr>
<tr>
<td>
user = dc=Manager,dc=example,dc=com </td>
user = dc=Manager,dc=example,dc=com</td>
<td>(StrOpt) User for the LDAP server to use as default.</td>
</tr>
<tr>
<td>password = None </td>
<td>password = None</td>
<td>(StrOpt) Password for LDAP server to connect to.</td>
</tr>
<tr>
<td>
suffix = cn=example,cn=com </td>
suffix = cn=example,cn=com</td>
<td>(StrOpt) Default suffix for your LDAP server.</td>
</tr>
<tr><td>use_dumb_member = False</td>

2
doc/src/docbkx/openstack-admin-user/src/ch_cli.xml
View File

@ -9,7 +9,7 @@
<info>
<title>OpenStack command-line clients</title>
</info>
<xi:include href="../../openstack-user/src/section_cli_overview.xml"/>
<xi:include href="../../openstack-user/src/section_cli_overview.xml"/>
<xi:include href="../../openstack-user/src/section_cli_install.xml"/>
<xi:include href="../../openstack-user/src/section_cli_version.xml"/>
<xi:include href="../../openstack-user/src/section_cli_openrc.xml"/>

2
doc/src/docbkx/openstack-admin-user/src/section_cli_manage_images.xml
View File

@ -20,7 +20,7 @@
><citetitle>Virtual Machine Image
Guide</citetitle></link>.</para>
<section xml:id="glance-image-list">
<title>Manage images with the glance client </title>
<title>Manage images with the glance client</title>
<procedure>
<title>To list images</title>
<step>

4
doc/src/docbkx/openstack-admin-user/src/section_dashboard_prereqs.xml
View File

@ -1,9 +1,9 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section [
<!DOCTYPE section [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY ndash "&#x2013;">
<!ENTITY mdash "&#x2014;">
<!ENTITY hellip "&#x2026;">
<!ENTITY hellip "&#x2026;">
]>
<section xml:id="dashboard-overview"
xmlns="http://docbook.org/ns/docbook"

6
doc/src/docbkx/openstack-block-storage-admin/backup-block-storage-disks.xml
View File

@ -24,11 +24,11 @@
</listitem>
<listitem>
<para><command>tar</command> creates a
minimum-sized backup </para>
minimum-sized backup</para>
</listitem>
<listitem>
<para><command>sha1sum</command> calculates the
backup checksum, to check its consistency </para>
backup checksum, to check its consistency</para>
</listitem>
</orderedlist>
<para>
@ -191,7 +191,7 @@
<para><itemizedlist>
<listitem>
<para>You didn't allocate enough
space for the snapshot </para>
space for the snapshot</para>
</listitem>
<listitem>
<para>

8
doc/src/docbkx/openstack-block-storage-admin/drivers/hds-volume-driver.xml
View File

@ -52,7 +52,7 @@
<para>
HDS driver supports the concept of differentiated services,
<footnote xml:id='hds-fn-svc-1'><para>Not to be confused with
Cinder volume service </para> </footnote> where <link
Cinder volume service</para></footnote> where <link
linkend="multi_backend">volume type</link> can be associated
with the fine tuned performance characteristics of HDP -- the
dynamic pool where volumes shall be created. For instance an HDP
@ -147,7 +147,7 @@
<literal>hds_cinder_config_file</literal> option is used to
point to an unique configuration file for each block. Set
<literal>volume_driver</literal> for each backend to
<literal> cinder.volume.drivers.hds.hds.HUSDriver</literal>
<literal>cinder.volume.drivers.hds.hds.HUSDriver</literal>
<programlisting>
enabled_backends=hus1,hus2
[hus1]
@ -222,7 +222,7 @@
</orderedlist>
</simplesect>
<simplesect>
<title> Type extra specs: volume_backend and volume type</title>
<title>Type extra specs: volume_backend and volume type</title>
<para>
If <link linkend="multi_backend">volume type</link> are used,
they should be configured in the configuration file as
@ -238,7 +238,7 @@
</para>
</simplesect>
<simplesect>
<title> Non differentiated deployment of HUS arrays </title>
<title>Non differentiated deployment of HUS arrays</title>
<para>
Multiple cinder instances, each controlling a separate HUS
array and with no volume type being associated with any of

2
doc/src/docbkx/openstack-block-storage-admin/drivers/huawei-storage-driver.xml
View File

@ -4,7 +4,7 @@
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
xml:id="huawei-storage-driver">
<title> Huawei Storage Driver</title>
<title>Huawei Storage Driver</title>
<para>Huawei storage drivers integrate OceanStor T series unified storage with OceanStor
Dorado high-performance storage to provide block storage services for
OpenStack.</para>

4
doc/src/docbkx/openstack-block-storage-admin/drivers/ibm-storwize-svc-driver.xml
View File

@ -9,7 +9,7 @@
instances with access to IBM Storwize family or SVC
storage systems.</para>
<section xml:id="ibm-storwize-svc-driver1">
<title>Configuring the Storwize Family and SVC System </title>
<title>Configuring the Storwize Family and SVC System</title>
<simplesect>
<title>Network Configuration</title>
@ -191,7 +191,7 @@ ssh-keygen -t rsa
</simplesect>
</section>
<section xml:id="ibm-storwize-svc-driver2">
<title>Configuring the Storwize Family and SVC Driver </title>
<title>Configuring the Storwize Family and SVC Driver</title>
<simplesect>
<title>Enabling the Storwize family and SVC driver
</title>

6
doc/src/docbkx/openstack-block-storage-admin/drivers/netapp-volume-driver.xml
View File

@ -174,7 +174,7 @@
driver on OpenStack.</para>
<simplesect>
<title>Configuration options for the clustered
Data ONTAP driver </title>
Data ONTAP driver</title>
<para>Set the volume driver to the clustered
Data ONTAP driver by setting the
<literal>volume_driver</literal>
@ -409,7 +409,7 @@
</simplesect>
</section>
<section xml:id="netapp-iscsi-driver-direct-cluster">
<title>NetApp iSCSI direct driver for clustered Data ONTAP </title>
<title>NetApp iSCSI direct driver for clustered Data ONTAP</title>
<para>The NetApp iSCSI direct driver for clustered Data ONTAP is
a driver interface from OpenStack to clustered Data
ONTAP storage systems for provisioning and managing the
@ -654,7 +654,7 @@
</simplesect>
</section>
<section xml:id="netapp-nfs-driver-cluster">
<title>NetApp NFS driver for clustered Data ONTAP </title>
<title>NetApp NFS driver for clustered Data ONTAP</title>
<para>The NetApp NFS driver for clustered Data ONTAP is a driver
interface from OpenStack to clustered Data ONTAP systems
for provisioning and managing OpenStack

2
doc/src/docbkx/openstack-block-storage-admin/drivers/xen-sm-driver.xml
View File

@ -193,7 +193,7 @@ Note: SR type and config connection parameters are in keeping with the XenAPI Co
</itemizedlist>
</simplesect>
<simplesect>
<title>Creating and Accessing the volumes from VMs </title>
<title>Creating and Accessing the volumes from VMs</title>
<para>Currently, the flavors have not been tied to
the volume types API. As a result, we simply
end up creating volumes in a "first fit" order

36
doc/src/docbkx/openstack-compute-admin/adding-images.xml
View File

@ -387,7 +387,7 @@
<varlistentry>
<term><literal>arch</literal></term>
<listitem>
<para>This is: Arch Linux </para>
<para>This is: Arch Linux</para>
<para>Do not use:
<literal>archlinux</literal>, or
<literal>org.archlinux</literal>
@ -398,7 +398,7 @@
<term><literal>centos</literal></term>
<listitem>
<para>This is: Community Enterprise
Operating System </para>
Operating System</para>
<para>Do not use:
<literal>org.centos</literal>
<literal>CentOS</literal>
@ -408,7 +408,7 @@
<varlistentry>
<term><literal>debian</literal></term>
<listitem>
<para>This is: Debian </para>
<para>This is: Debian</para>
<para>Do not use:
<literal>Debian</literal>, or
<literal>org.debian</literal>
@ -418,7 +418,7 @@
<varlistentry>
<term><literal>fedora</literal></term>
<listitem>
<para>This is: Fedora </para>
<para>This is: Fedora</para>
<para>Do not use:
<literal>Fedora</literal>,
<literal>org.fedora</literal>, or
@ -429,7 +429,7 @@
<varlistentry>
<term><literal>freebsd</literal></term>
<listitem>
<para>This is: FreeBSD </para>
<para>This is: FreeBSD</para>
<para>Do not use:
<literal>org.freebsd</literal>,
<literal>freeBSD</literal>, or
@ -440,7 +440,7 @@
<varlistentry>
<term><literal>gentoo</literal></term>
<listitem>
<para>This is: Gentoo Linux </para>
<para>This is: Gentoo Linux</para>
<para>Do not use:
<literal>Gentoo</literal>, or
<literal>org.gentoo</literal>
@ -450,7 +450,7 @@
<varlistentry>
<term><literal>mandrake</literal></term>
<listitem>
<para>This is: Mandrakelinux (MandrakeSoft) </para>
<para>This is: Mandrakelinux (MandrakeSoft)</para>
<para>Do not use:
<literal>mandrakelinux</literal>, or
<literal>MandrakeLinux</literal>
@ -460,7 +460,7 @@
<varlistentry>
<term><literal>mandriva</literal></term>
<listitem>
<para>This is: Mandriva Linux </para>
<para>This is: Mandriva Linux</para>
<para>Do not use:
<literal>mandrivalinux</literal>
</para>
@ -469,7 +469,7 @@
<varlistentry>
<term><literal>mes</literal></term>
<listitem>
<para>This is: Mandriva Enterprise Server </para>
<para>This is: Mandriva Enterprise Server</para>
<para>Do not use:
<literal>mandrivaent</literal>, or
<literal>mandrivaES</literal>
@ -480,7 +480,7 @@
<term><literal>msdos</literal></term>
<listitem>
<para>This is: Microsoft Disc Operating
System </para>
System</para>
<para>Do not use: <literal>ms-dos</literal>
</para>
</listitem>
@ -488,7 +488,7 @@
<varlistentry>
<term><literal>netbsd</literal></term>
<listitem>
<para>This is: NetBSD </para>
<para>This is: NetBSD</para>
<para>Do not use:
<literal>NetBSD</literal>, or
<literal>org.netbsd</literal>
@ -498,7 +498,7 @@
<varlistentry>
<term><literal>netware</literal></term>
<listitem>
<para>This is: Novell NetWare </para>
<para>This is: Novell NetWare</para>
<para>Do not use:
<literal>novell</literal>, or
<literal>NetWare</literal>
@ -508,7 +508,7 @@
<varlistentry>
<term><literal>openbsd</literal></term>
<listitem>
<para>This is: OpenBSD </para>
<para>This is: OpenBSD</para>
<para>Do not use:
<literal>OpenBSD</literal>, or
<literal>org.openbsd</literal>
@ -527,7 +527,7 @@
<varlistentry>
<term><literal>opensuse</literal></term>
<listitem>
<para>This is: openSUSE </para>
<para>This is: openSUSE</para>
<para>Do not use: <literal>suse</literal>,
<literal>SuSE</literal>, or
<literal>org.opensuse</literal>
@ -537,7 +537,7 @@
<varlistentry>
<term><literal>rhel</literal></term>
<listitem>
<para>This is: Red Hat Enterprise Linux </para>
<para>This is: Red Hat Enterprise Linux</para>
<para>Do not use:
<literal>redhat</literal>,
<literal>RedHat</literal>, or
@ -549,7 +549,7 @@
<term><literal>sled</literal></term>
<listitem>
<para>This is: SUSE Linux Enterprise
Desktop </para>
Desktop</para>
<para>Do not use:
<literal>com.suse</literal>
</para>
@ -558,7 +558,7 @@
<varlistentry>
<term><literal>ubuntu</literal></term>
<listitem>
<para>This is: Ubuntu </para>
<para>This is: Ubuntu</para>
<para>Do not use:
<literal>Ubuntu</literal>,
<literal>com.ubuntu</literal>,
@ -570,7 +570,7 @@
<varlistentry>
<term><literal>windows</literal></term>
<listitem>
<para>This is: Microsoft Windows </para>
<para>This is: Microsoft Windows</para>
<para>Do not use:
<literal>com.microsoft.server</literal>,
or <literal>windoze</literal>

156
doc/src/docbkx/openstack-compute-admin/ch_identity_mgmt.xml
View File

@ -150,7 +150,7 @@ pipeline = [...] json_body stats_reporting ec2_extension [...] admin_service
<screen>$ curl -H 'X-Auth-Token: ADMIN' -X DELETE http://localhost:35357/v2.0/OS-STATS/stats</screen>
</section>
<xi:include href="../common/section_keystone_certificates-for-pki.xml"/>
<xi:include href="../common/section_keystone-sample-conf-files.xml"/>
<xi:include href="../common/section_keystone-sample-conf-files.xml"/>
<section xml:id="running-keystone">
<title>Running the Identity Service</title>
<para>
@ -233,7 +233,7 @@ keystone-manage db_sync
<listitem>
<para>
<literal>--password OS_PASSWORD</literal>. The administrator
password </para>
password</para>
</listitem>
<listitem>
<para>
@ -307,16 +307,16 @@ keystone --username=admin --password=secrete --tenant_name=admin tenant-create -
it.</para>
<section xml:id="tenant-create">
<title><literal>tenant-create</literal></title>
<para>keyword arguments </para>
<para>keyword arguments</para>
<itemizedlist>
<listitem>
<para>name </para>
<para>name</para>
</listitem>
<listitem>
<para>description (optional, defaults to None) </para>
<para>description (optional, defaults to None)</para>
</listitem>
<listitem>
<para>enabled (optional, defaults to True) </para>
<para>enabled (optional, defaults to True)</para>
</listitem>
</itemizedlist>
<para>The following command creates a tenant named
@ -325,39 +325,39 @@ keystone --username=admin --password=secrete --tenant_name=admin tenant-create -
</section>
<section xml:id="tenant-delete">
<title><literal>tenant-delete</literal></title>
<para>arguments </para>
<para>arguments</para>
<itemizedlist>
<listitem>
<para>tenant_id </para>
<para>tenant_id</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone tenant-delete f2b7b39c860840dfa47d9ee4adffa0b3
</screen>
</section>
<section xml:id="tenant-enable">
<title><literal>tenant-enable</literal></title>
<para>arguments </para>
<para>arguments</para>
<itemizedlist>
<listitem>
<para>tenant_id </para>
<para>tenant_id</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone tenant-enable f2b7b39c860840dfa47d9ee4adffa0b3
</screen>
</section>
<section xml:id="tenant-disable">
<title><literal>tenant-disable</literal></title>
<para>arguments </para>
<para>arguments</para>
<itemizedlist>
<listitem>
<para>tenant_id </para>
<para>tenant_id</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone tenant-disable f2b7b39c860840dfa47d9ee4adffa0b3
</screen>
@ -367,25 +367,25 @@ keystone tenant-disable f2b7b39c860840dfa47d9ee4adffa0b3
<title>Users</title>
<section xml:id="user-create">
<title><literal>user-create</literal></title>
<para>keyword arguments: </para>
<para>keyword arguments:</para>
<itemizedlist>
<listitem>
<para>name </para>
<para>name</para>
</listitem>
<listitem>
<para>pass </para>
<para>pass</para>
</listitem>
<listitem>
<para>email </para>
<para>email</para>
</listitem>
<listitem>
<para>default_tenant (optional, defaults to None) </para>
<para>default_tenant (optional, defaults to None)</para>
</listitem>
<listitem>
<para>enabled (optional, defaults to True) </para>
<para>enabled (optional, defaults to True)</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone user-create
--name=admin \
@ -395,13 +395,13 @@ keystone user-create
</section>
<section xml:id="user-delete">
<title><literal>user-delete</literal></title>
<para>keyword arguments: </para>
<para>keyword arguments:</para>
<itemizedlist>
<listitem>
<para>user </para>
<para>user</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone user-delete f2b7b39c860840dfa47d9ee4adffa0b3
</screen>
@ -409,74 +409,74 @@ keystone user-delete f2b7b39c860840dfa47d9ee4adffa0b3
<section xml:id="user-list">
<title><literal>user-list</literal></title>
<para>list users in the system, optionally by a specific tenant
(identified by tenant_id) </para>
<para>arguments </para>
(identified by tenant_id)</para>
<para>arguments</para>
<itemizedlist>
<listitem>
<para>tenant_id (optional, defaults to None) </para>
<para>tenant_id (optional, defaults to None)</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone user-list
</screen>
</section>
<section xml:id="user-update-email">
<title><literal>user-update --email</literal></title>
<para>arguments </para>
<para>arguments</para>
<itemizedlist>
<listitem>
<para>user_id </para>
<para>user_id</para>
</listitem>
<listitem>
<para>email </para>
<para>email</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone user-update --email 03c84b51574841ba9a0d8db7882ac645 &quot;someone@somewhere.com&quot;
</screen>
</section>
<section xml:id="user-enable">
<title><literal>user-enable</literal></title>
<para>arguments </para>
<para>arguments</para>
<itemizedlist>
<listitem>
<para>user_id </para>
<para>user_id</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone user-enable 03c84b51574841ba9a0d8db7882ac645
</screen>
</section>
<section xml:id="user-disable">
<title><literal>user-disable</literal></title>
<para>arguments </para>
<para>arguments</para>
<itemizedlist>
<listitem>
<para>user_id </para>
<para>user_id</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone user-disable 03c84b51574841ba9a0d8db7882ac645
</screen>
</section>
<section xml:id="user-update-password">
<title><literal>user-update --password</literal></title>
<para>arguments </para>
<para>arguments</para>
<itemizedlist>
<listitem>
<para>user_id </para>
<para>user_id</para>
</listitem>
<listitem>
<para>password </para>
<para>password</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone user-update --password 03c84b51574841ba9a0d8db7882ac645 foo
</screen>
@ -486,65 +486,65 @@ keystone user-update --password 03c84b51574841ba9a0d8db7882ac645 foo
<title>Roles</title>
<section xml:id="role-create">
<title><literal>role-create</literal></title>
<para>arguments </para>
<para>arguments</para>
<itemizedlist>
<listitem>
<para>name </para>
<para>name</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone role-create --name=demo
</screen>
</section>
<section xml:id="role-delete">
<title><literal>role-delete</literal></title>
<para>arguments </para>
<para>arguments</para>
<itemizedlist>
<listitem>
<para>role_id </para>
<para>role_id</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone role-delete 19d1d3344873464d819c45f521ff9890
</screen>
</section>
<section xml:id="role-list">
<title><literal>role-list</literal></title>
<para>example: </para>
<para>example:</para>
<screen>
keystone role-list
</screen>
</section>
<section xml:id="role-get">
<title><literal>role-get</literal></title>
<para>arguments </para>
<para>arguments</para>
<itemizedlist>
<listitem>
<para>role_id </para>
<para>role_id</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone role-get role=19d1d3344873464d819c45f521ff9890
</screen>
</section>
<section xml:id="add-user-role">
<title><literal>add-user-role</literal></title>
<para>arguments </para>
<para>arguments</para>
<itemizedlist>
<listitem>
<para>role_id </para>
<para>role_id</para>
</listitem>
<listitem>
<para>user_id </para>
<para>user_id</para>
</listitem>
<listitem>
<para>tenant_id </para>
<para>tenant_id</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone add-user-role \
3a751f78ef4c412b827540b829e2d7dd \
@ -554,19 +554,19 @@ keystone add-user-role \
</section>
<section xml:id="remove-user-role">
<title><literal>remove-user-role</literal></title>
<para>arguments </para>
<para>arguments</para>
<itemizedlist>
<listitem>
<para>role_id </para>
<para>role_id</para>
</listitem>
<listitem>
<para>user_id </para>
<para>user_id</para>
</listitem>
<listitem>
<para>tenant_id </para>
<para>tenant_id</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone remove-user-role \
19d1d3344873464d819c45f521ff9890 \
@ -579,19 +579,19 @@ keystone remove-user-role \
<title>Services</title>
<section xml:id="service-create">
<title><literal>service-create</literal></title>
<para>keyword arguments </para>
<para>keyword arguments</para>
<itemizedlist>
<listitem>
<para>name </para>
<para>name</para>
</listitem>
<listitem>
<para>type </para>
<para>type</para>
</listitem>
<listitem>
<para>description </para>
<para>description</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone service create \
--name=nova \
@ -601,39 +601,39 @@ keystone service create \
</section>
<section xml:id="service-list">
<title><literal>service-list</literal></title>
<para>arguments </para>
<para>arguments</para>
<itemizedlist>
<listitem>
<para>service_id </para>
<para>service_id</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone service-list
</screen>
</section>
<section xml:id="service-get">
<title><literal>service-get</literal></title>
<para>arguments </para>
<para>arguments</para>
<itemizedlist>
<listitem>
<para>service_id </para>
<para>service_id</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone service-get 08741d8ed88242ca88d1f61484a0fe3b
</screen>
</section>
<section xml:id="service-delete">
<title><literal>service-delete</literal></title>
<para>arguments </para>
<para>arguments</para>
<itemizedlist>
<listitem>
<para>service_id </para>
<para>service_id</para>
</listitem>
</itemizedlist>
<para>example: </para>
<para>example:</para>
<screen>
keystone service-delete 08741d8ed88242ca88d1f61484a0fe3b
</screen>
@ -690,7 +690,7 @@ keystone service-delete 08741d8ed88242ca88d1f61484a0fe3b
This is configured in <filename>keystone.conf</filename> file
under the section <literal>[DEFAULT]</literal>. In the
sample file provided with the keystone project, the line
defining this token is </para>
defining this token is</para>
<blockquote>
<para>
[DEFAULT] admin_token = ADMIN

4
doc/src/docbkx/openstack-compute-admin/ch_image_mgmt.xml
View File

@ -265,7 +265,7 @@
within <filename>policy.json</filename> on the desired roles. By default, only the admin
role has this setting enabled.</para>
<para>You can view the list of valid compute hosts by using the <command>nova
hypervisor-list </command>command, for
hypervisor-list</command> command, for
example:<screen><prompt>$</prompt> <userinput>nova hypervisor-list</userinput>
<computeroutput>+----+---------------------+
| ID | Hypervisor hostname |
@ -291,7 +291,7 @@
</section>
<section xml:id="replicating-images">
<title>Replicating images across multiple data centers </title>
<title>Replicating images across multiple data centers</title>
<para>The image service comes with a tool called
<command>glance-replicator</command> that can be used
to populate a new glance server using the images stored in

2
doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml
View File

@ -323,7 +323,7 @@ header: Date: Thu, 13 Sep 2012 20:27:36 GMT
<para>Flavors define a number of elements <itemizedlist>
<listitem>
<para><literal>ID</literal>: a unique numeric id </para>
<para><literal>ID</literal>: a unique numeric id</para>
</listitem>
<listitem>
<para><literal>Name</literal>: a descriptive name.

2
doc/src/docbkx/openstack-compute-admin/computeautomation.xml
View File

@ -269,7 +269,7 @@ format="SVG" scale="60"/>
<simplesect><title>Notes</title>
<orderedlist>
<listitem>
<para>SSH login nova instance after test of nova </para>
<para>SSH login nova instance after test of nova</para>
<para>An instance will be started during the test of nova. After the test,
you can login the instance by executing the following commands.</para>
<para>For openstack nova folsom,</para>

130
doc/src/docbkx/openstack-compute-admin/computenetworking.xml
View File

@ -607,7 +607,7 @@ iface br100 inet dhcp
<para><figure>
<title>Flat network, all-in-one server
installation </title>
installation</title>
<mediaobject>
<imageobject>
<imagedata scale="80"
@ -1196,21 +1196,22 @@ firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver</programlis
services. As with before
<literal>public_interface</literal> refers to
the network interfce on the VM running the
OpenStack services. </para>
OpenStack services.</para>
<para>With VLAN networking and the XenAPI driver, the
following things happen when you start a VM: <itemizedlist>
following things happen when you start a VM:
<itemizedlist>
<listitem>
<para> First the XenServer network is
<para>First the XenServer network is
attached to the appropriate physical
interface (PIF) and VLAN unless the
network already exists. </para>
network already exists.</para>
</listitem>
<listitem>
<para> When the VM is created, its VIF is
attached to the above network. </para>
<para>When the VM is created, its VIF is
attached to the above network.</para>
</listitem>
<listitem>
<para> The 'Openstack domU', i.e. where
<para>The 'Openstack domU', i.e. where
nova-network is running, acts as a
gateway and DHCP for this instance.
The DomU does this for multiple VLAN
@ -1218,15 +1219,16 @@ firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver</programlis
a VLAN trunk. For this reason it must
have an interface on the parent bridge
of the VLAN bridge where VM instances
are plugged. </para>
are plugged.</para>
</listitem>
</itemizedlist>
</para>
<para>To help understand VLAN networking with the
XenAPI further, here are some important things to
note: <itemizedlist>
note:
<itemizedlist>
<listitem>
<para> A physical interface (PIF)
<para>A physical interface (PIF)
identified either by (A) the
vlan_interface flag or (B) the
bridge_interface column in the
@ -1234,16 +1236,16 @@ firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver</programlis
creating a XenServer VLAN network. The
VLAN tag is found in the vlan column,
still in the networks table, and by
default the first tag is 100. </para>
default the first tag is 100.</para>
</listitem>
<listitem>
<para> VIF for VM instances within this
<para>VIF for VM instances within this
network will be plugged in this VLAN
network. You won't see the bridge
until a VIF is plugged in it. </para>
until a VIF is plugged in it.</para>
</listitem>
<listitem>
<para> The 'Openstack domU', i.e. the VM
<para>The 'Openstack domU', i.e. the VM
running the nova network node, instead
will not be plugged into this network;
since it acts as a gateway for
@ -1255,10 +1257,10 @@ firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver</programlis
example, if
<literal>vlan_interface</literal>
is eth0 it must be plugged in xenbr1,
eth1 --> xenbr1, etc. </para>
eth1 --> xenbr1, etc.</para>
</listitem>
<listitem>
<para> Within the Openstack domU, 'ip
<para>Within the Openstack domU, 'ip
link' is then used to configure VLAN
interfaces on the 'trunk' port. Each
of this vlan interfaces is associated
@ -1268,7 +1270,7 @@ firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver</programlis
constantly updated by nova-network,
thus ensuring VMs get the IP address
specified by the layer3 network driver
(nova IPAM or Melange). </para>
(nova IPAM or Melange).</para>
</listitem>
</itemizedlist>
</para>
@ -1277,7 +1279,7 @@ firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver</programlis
the appropriate dnsmasq instance, and should be
able to communicate without any problem with other
VMs on the same network and with the their
gateway. </para>
gateway.</para>
<para>The above point (3) probably needs some more
explanations. With Open vSwitch, we don't really
have distinct bridges for different VLANs; even if
@ -1286,7 +1288,7 @@ firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver</programlis
instance, which runs a distinct 'fake-bridge' for
each VLAN. The 'real' bridge is the 'parent' of
the fake one. You can easily navigate fake and
real bridges with ovs-vsctl. </para>
real bridges with ovs-vsctl.</para>
<para>As you can see I am referring to Openvswitch
only. This is for a specific reason: the
fake-parent mechanism automatically imply that
@ -1304,7 +1306,7 @@ firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver</programlis
node on a VM on a XenServer that does not host any
<systemitem class="service"
>nova-compute</systemitem> controlled
instances. </para>
instances.</para>
</section>
<section xml:id="vlan-known-issues">
<title>Known issue with failed DHCP leases in VLAN
@ -1348,7 +1350,7 @@ firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver</programlis
xlink:href="http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=9380ba70d67db6b69f817d8e318de5ba1e990b12"
>has integrated a fix</link> for the issue in
dnsmaq version 2.61. </para>
dnsmaq version 2.61.</para>
<para>If upgrading dnsmasq is out of the question, a
possible workaround is to minimize lease renewals
with something like the following combination of
@ -1365,10 +1367,9 @@ fixed_ip_disassociate_timeout=1209600</programlisting></para>
<section xml:id="cloudpipe-per-project-vpns">
<title>Cloudpipe — Per Project Vpns</title>
<para> Cloudpipe is a method for connecting end users to
their project instances in VLAN networking mode. </para>
<para> The support code for cloudpipe implements admin
<para>Cloudpipe is a method for connecting end users to
their project instances in VLAN networking mode.</para>
<para>The support code for cloudpipe implements admin
commands (through an extension) to automatically
create a VM for a project that allows users to VPN
into the private network of their project. Access to
@ -1376,16 +1377,14 @@ fixed_ip_disassociate_timeout=1209600</programlisting></para>
network host for the project. This allows users to
have free access to the virtual machines in their
project without exposing those machines to the public
internet. </para>
<para> The cloudpipe image is basically just a Linux
internet.</para>
<para>The cloudpipe image is basically just a Linux
instance with openvpn installed. It needs a simple
script to grab user data from the metadata server, b64
decode it into a zip file, and run the autorun.sh
script from inside the zip. The autorun script will
configure and run openvpn to run using the data from
nova. </para>
nova.</para>
<para>It is also useful to have a cron script that will
periodically re download the metadata and copy the new
Certificate Revocation List (CRL). This list is
@ -1410,17 +1409,17 @@ fixed_ip_disassociate_timeout=1209600</programlisting></para>
<listitem>
<para>Installing the required packages</para>
<para> We start by installing the required
<para>We start by installing the required
packages on our instance:
<screen><prompt>#</prompt> <userinput>apt-get update &amp;&amp; apt-get upgrade &amp;&amp; apt-get install openvpn bridge-utils unzip -y</userinput></screen></para>
</listitem>
<listitem>
<para> Creating the server configuration
<para>Creating the server configuration
template</para>
<para> Create a configuration for Openvpn, and
<para>Create a configuration for Openvpn, and
save it under
<filename>/etc/openvpn/server.conf</filename>
: </para>
:</para>
<para>
<programlisting>port 1194
@ -1463,7 +1462,7 @@ mute 20</programlisting>
<listitem>
<para>Create the network scripts</para>
<para> The next step is to create both scripts
<para>The next step is to create both scripts
that will be used when the network
components will start up and shut down.
The scripts will be respectively saved
@ -1500,7 +1499,7 @@ DEV=$2
<para>Edit the network interface configuration
file</para>
<para> Update the
<para>Update the
<filename>/etc/network/interfaces</filename>
accordingly (We tear down the main
interface and enable the bridged
@ -1526,7 +1525,7 @@ bridge_ports eth0 </programlisting>
<listitem>
<para>Edit the rc.local file</para>
<para> The next step consists in updating the
<para>The next step consists in updating the
<filename>/etc/rc.local</filename>
file. We will ask our image to retrieve
the payload, decrypt it, and use both key
@ -1586,11 +1585,11 @@ exit 0 </programlisting>
<section xml:id="cloudpipe-upload-image">
<title>Upload your instance to Glance</title>
<para> We will make use of the <systemitem
<para>We will make use of the <systemitem
class="service">nova</systemitem> snapshot
feature in order to create an image from our
running instance. We start by retrieving the
instance ID: </para>
instance ID:</para>
<para>
<screen><prompt>$</prompt> <userinput>nova list</userinput></screen>
@ -1603,7 +1602,7 @@ exit 0 </programlisting>
+--------------------------------------+------------+--------+---------------------+
</programlisting>
<para> We create an image with, using the instance ID
<para>We create an image with, using the instance ID
:
<screen><prompt>$</prompt> <userinput>nova image-create 739079a-b-0f8e-404a-ae6e-a91f4fe99c94</userinput></screen>
@ -1641,7 +1640,7 @@ cnt_vpn_clients=5
<section xml:id="cloudpipe-start-instance">
<title>Power-up your instance</title>
<para> Use the <systemitem class="service">nova
<para>Use the <systemitem class="service">nova
cloudpipe</systemitem> feature the following
way:
@ -1722,9 +1721,8 @@ ALLOW -1:-1 from 0.0.0.0/0
nova-manage, a new Certificate Revocation List
(crl) is generated. As long as cloudpipe has an
updated crl, it will block revoked users from
connecting to the vpn. </para>
<para> The user data for cloudpipe isn't currently
connecting to the vpn.</para>
<para>The user data for cloudpipe isn't currently
updated when certs are revoked, so it is necessary
to restart the cloudpipe instance if a user's
credentials are revoked.</para>
@ -1766,9 +1764,9 @@ ALLOW -1:-1 from 0.0.0.0/0
</section>
<section xml:id="cloudpipe-remote-acceess">
<title> Remote access to your cloudpipe instance from
<title>Remote access to your cloudpipe instance from
an OpenVPN client</title>
<para> Now your cloudpipe instance is running, you can
<para>Now your cloudpipe instance is running, you can
use your favorite OpenVPN client in order to
access your instances within their private network
cloudpipe is connected to. In these sections we
@ -1782,7 +1780,7 @@ ALLOW -1:-1 from 0.0.0.0/0
<orderedlist>
<listitem>
<para>Generate your certificates</para>
<para> Start by generating a private key and a
<para>Start by generating a private key and a
certificate for your project:
<screen><prompt>$</prompt> <userinput>nova x509-create-cert</userinput></screen>
@ -1792,7 +1790,7 @@ ALLOW -1:-1 from 0.0.0.0/0
<para>Create the openvpn configuration
file</para>
<para> The following template, which can be
<para>The following template, which can be
found under
<filename>nova/cloudpipe/client.ovpn.template</filename>
contains the necessary instructions for
@ -1826,7 +1824,7 @@ ping-timer-rem
persist-tun
persist-key </programlisting>
<para> Update the file accordingly. In order
<para>Update the file accordingly. In order
to get the public IP and port of your
cloudpipe instance, you can run the
following command:
@ -1840,8 +1838,8 @@ persist-key </programlisting>
</para>
</listitem>
<listitem>
<para> Start your OpenVPN client </para>
<para> Depending on the client you are using,
<para>Start your OpenVPN client</para>
<para>Depending on the client you are using,
make sure to save the configuration file
under the directory it should be, so the
certificate file and the private key.
@ -1855,13 +1853,13 @@ persist-key </programlisting>
instance using an interface</emphasis><orderedlist>
<listitem>
<para> Download an OpenVPN client </para>
<para> In order to connect to the
<para>Download an OpenVPN client</para>
<para>In order to connect to the
project's network, you will need an
OpenVPN client for your computer. Here
are several clients <itemizedlist>
<listitem>
<para> For Ubuntu: </para>
<para>For Ubuntu:</para>
<para><link
xlink:href="apt://openvpn"
>OpenVPN</link>
@ -1879,7 +1877,7 @@ persist-key </programlisting>
>gopenvpn</link></para>
</listitem>
<listitem>
<para> For Mac OsX: </para>
<para>For Mac OsX:</para>
<para>
<link
xlink:href="http://openvpn.net/"
@ -1897,7 +1895,7 @@ persist-key </programlisting>
</para>
</listitem>
<listitem>
<para> For Windows: </para>
<para>For Windows:</para>
<para>
<link
xlink:href="http://openvpn.net/"
@ -1907,8 +1905,8 @@ persist-key </programlisting>
</itemizedlist></para>
</listitem>
<listitem>
<para> Configure your client </para>
<para> In this example we will use
<para>Configure your client</para>
<para>In this example we will use
Viscosity, but the same settings apply
to any client. Start by filling the
public ip and the public port of the
@ -1947,9 +1945,9 @@ persist-key </programlisting>
</mediaobject>
<itemizedlist>
<listitem>
<para> Certificate: The generated
<para>Certificate: The generated
certificate</para>
<para>Key: The private key </para>
<para>Key: The private key</para>
</listitem>
</itemizedlist>
<mediaobject>
@ -2002,7 +2000,7 @@ persist-key </programlisting>
<listitem>
<para><emphasis role="bold">Troubleshoot your
cloudpipe instance</emphasis></para>
<para> A periodic task disassociates the fixed
<para>A periodic task disassociates the fixed
ip address for the cloudpipe instance.
Into
<filename>/var/log/nova/nova-network.log</filename>,
@ -2057,7 +2055,7 @@ persist-key </programlisting>
<para><emphasis role="bold">Automate the
cloudpipe image
installation</emphasis></para>
<para> You can automate the image creation by
<para>You can automate the image creation by
download that script and running it from
inside the instance: <link
xlink:href="https://github.com/leseb/cloudpipe-image-auto-creation/blob/master/cloudpipeconf.sh"
@ -2162,7 +2160,7 @@ public_interface=vlan100
running the nova-network service.</para>
</note>
</para>
<para> you can check if the forwarding is enabled by
<para>you can check if the forwarding is enabled by
running the following command: <screen><prompt>$</prompt> <userinput>cat /proc/sys/net/ipv4/ip_forward</userinput></screen>
<screen><computeroutput>0</computeroutput></screen></para>
<para>Or using sysctl<screen><prompt>$</prompt> <userinput> sysctl net.ipv4.ip_forward</userinput></screen>
@ -2317,7 +2315,7 @@ auto_assign_floating_ip=True
<section xml:id="using-multiple-nics-usage">
<title>Using the multinic feature</title>
<para> In order to use the multinic feature, first create
<para>In order to use the multinic feature, first create
two networks, and attach them to your project:
<screen><prompt>$</prompt> <userinput>nova network-create first-net --fixed-range-v4=20.20.0.0/24 --project-id=$your-project</userinput>
<prompt>$</prompt> <userinput>nova network-create second-net --fixed-range-v4=20.20.10.0/24 --project-id=$your-project</userinput> </screen>
@ -2419,7 +2417,7 @@ iface eth1 inet dhcp </programlisting></para>
compute host requires a connection to the public
internet and each host is also assigned an address
from the VM network where it listens for DHCP traffic.
The <systemitem class="service">nova-api</systemitem> service
The <systemitem class="service">nova-api</systemitem> service
is needed so that it can act as a
metadata server for the instances.</para>
<para>To run in HA mode, each compute host must run the

22
doc/src/docbkx/openstack-compute-admin/computescheduler.xml
View File

@ -137,7 +137,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
</section>
<section xml:id="aggregate-ram-filter">
<title>AggregateRamFilter </title>
<title>AggregateRamFilter</title>
<para>Implements blueprint
<literal>per-aggregate-resource-ratio</literal>.
Supports per-aggregate
@ -153,7 +153,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
</section>
<section xml:id="availabilityzonefilter">
<title> AvailabilityZoneFilter </title>
<title>AvailabilityZoneFilter</title>
<para>Filters hosts by availability zone. This filter must
be enabled for the scheduler to respect availability
@ -179,9 +179,9 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
</section>
<section xml:id="computefilter">
<title> ComputeFilter </title>
<title>ComputeFilter</title>
<para> Passes all hosts that are operational and
<para>Passes all hosts that are operational and
enabled.</para>
<para>In general, this filter should always be enabled.
@ -189,7 +189,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
</section>
<section xml:id="corefilter">
<title> CoreFilter </title>
<title>CoreFilter</title>
<para>Only schedule instances on hosts if there are
sufficient CPU cores available. If this filter is not
set, the scheduler may over provision a host based on
@ -197,7 +197,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
may exceed the physical cores).</para>
<para>This filter can be configured to allow a fixed
amount of vCPU overcommitment by using the
<literal>cpu_allocation_ratio </literal>
<literal>cpu_allocation_ratio</literal>
Configuration option in
<filename>nova.conf</filename>. The default setting
is:
@ -251,7 +251,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
sufficient disk space available for root and ephemeral storage.</para>
<para>This filter can be configured to allow a fixed
amount of disk overcommitment by using the
<literal>disk_allocation_ratio </literal>
<literal>disk_allocation_ratio</literal>
Configuration option in
<filename>nova.conf</filename>. The default setting
is:
@ -291,7 +291,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
these properties using
<programlisting>glance image-update img-uuid --property architecture=arm --property hypervisor_type=qemu</programlisting>
</para>
<para> The image properties that the filter checks for
<para>The image properties that the filter checks for
are:</para>
<itemizedlist>
<listitem>
@ -318,7 +318,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
</itemizedlist>
</section>
<section xml:id="isolatedhostsfilter">
<title> IsolatedHostsFilter </title>
<title>IsolatedHostsFilter</title>
<para>Allows the admin to define a special (isolated) set
of images and a special (isolated) set of hosts, such
that the isolated images can only run on the isolated
@ -533,10 +533,10 @@ ram_allocation_ratio=1.5
scheduler_weight_classes=nova.scheduler.weights.all_weighers
ram_weight_multiplier=1.0
</programlisting>
<para> The default is to spread instances across all hosts
<para>The default is to spread instances across all hosts
evenly. Set the <literal>ram_weight_multiplier</literal>
option to a negative number if you prefer stacking instead
of spreading. </para>
of spreading.</para>
</section>

2
doc/src/docbkx/openstack-compute-admin/computetutorials.xml
View File

@ -69,7 +69,7 @@ export NOVA_VERSION=1.1
II!</para>
</section>
<section xml:id="part-ii-getting-virtual-machines">
<title>Part II: Starting Virtual Machines </title>
<title>Part II: Starting Virtual Machines</title>
<para>Understanding what you can do with cloud computing
means you should have a grasp on the concept of
virtualization. With virtualization, you can run

2
doc/src/docbkx/openstack-compute-admin/moosefsbackend.xml
View File

@ -76,7 +76,7 @@
</figure>
</para>
<section xml:id="installing-moosefs-metadata-metalogger-servers">
<title> Installing the MooseFS metadata and metalogger servers</title>
<title>Installing the MooseFS metadata and metalogger servers</title>
<para>You can run these components anywhere as long as the MooseFS chunkservers can reach
the MooseFS master server.</para>
<para>In our deployment, both MooseFS master and slave run their services inside a virtual

4
doc/src/docbkx/openstack-config/ch_computeconfigure.xml
View File

@ -451,7 +451,7 @@ $ <userinput>sudo service nova-compute restart</userinput></screen>
<section xml:id="sample-nova-configuration-files">
<title>Example <filename>nova.conf</filename> Configuration
Files</title>
<para> The following sections describe many of the configuration
<para>The following sections describe many of the configuration
option settings that can go into the
<filename>nova.conf</filename> files. Copies of each
<filename>nova.conf</filename> file need to be copied to each
@ -586,7 +586,7 @@ xenapi_remap_vbd_dev=true
<title>Configuring the Compute API</title>
<simplesect>
<title>Configuring Compute API password handling</title>
<para> The OpenStack Compute API allows the user to specify an
<para>The OpenStack Compute API allows the user to specify an
admin password when creating (or rebuilding) a server
instance. If no password is specified, a randomly generated
password is used. The password is returned in the API

22
doc/src/docbkx/openstack-config/ch_computescheduler.xml
View File

@ -145,7 +145,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
</section>
<section xml:id="availabilityzonefilter">
<title> AvailabilityZoneFilter </title>
<title>AvailabilityZoneFilter</title>
<para>Filters hosts by availability zone. This filter
must be enabled for the scheduler to respect
availability zones in requests.</para>
@ -169,9 +169,9 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
</section>
<section xml:id="computefilter">
<title> ComputeFilter </title>
<title>ComputeFilter</title>
<para> Passes all hosts that are operational and
<para>Passes all hosts that are operational and
enabled.</para>
<para>In general, this filter should always be enabled.
@ -179,7 +179,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
</section>
<section xml:id="corefilter">
<title> CoreFilter </title>
<title>CoreFilter</title>
<para>Only schedule instances on hosts if there are
sufficient CPU cores available. If this filter is not
set, the scheduler may over provision a host based on
@ -187,7 +187,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
may exceed the physical cores).</para>
<para>This filter can be configured to allow a fixed
amount of vCPU overcommitment by using the
<literal>cpu_allocation_ratio </literal>
<literal>cpu_allocation_ratio</literal>
Configuration option in
<filename>nova.conf</filename>. The default setting
is:
@ -237,18 +237,18 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
<section xml:id="diskfilter">
<title>DiskFilter</title>
<para> Only schedule instances on hosts if there is
<para>Only schedule instances on hosts if there is
sufficient disk space available for root and ephemeral
storage.</para>
<para>This filter can be configured to allow a fixed
amount of disk overcommitment by using the
<literal>disk_allocation_ratio </literal>
<literal>disk_allocation_ratio</literal>
Configuration option in
<filename>nova.conf</filename>. The default setting
is:</para>
<programlisting>disk_allocation_ratio=1.0</programlisting>
<para>Adjusting this value to be greater than 1.0 will
allow scheduling instances while over committing disk
resources on the node. This may be desirable if you
@ -258,7 +258,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
</section>
<section xml:id="groupantiaffinityfilter">
<title>GroupAntiAffinityFilter</title>
<para> The GroupAntiAffinityFilter ensures that each
<para>The GroupAntiAffinityFilter ensures that each
instance in a group is on a different host. To take
advantage of this filter, the requester must pass a
scheduler hint, using <literal>group</literal> as the
@ -282,7 +282,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
these properties using
<programlisting>glance image-update img-uuid --property architecture=arm --property hypervisor_type=qemu</programlisting>
</para>
<para> The image properties that the filter checks for
<para>The image properties that the filter checks for
are:</para>
<itemizedlist>
<listitem>
@ -311,7 +311,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
<section xml:id="isolatedhostsfilter">
<title> IsolatedHostsFilter </title>
<title>IsolatedHostsFilter</title>
<para>Allows the admin to define a special (isolated) set
of images and a special (isolated) set of hosts, such
that the isolated images can only run on the isolated

2
doc/src/docbkx/openstack-config/ch_identityconfigure.xml
View File

@ -25,5 +25,5 @@
<xi:include href="../common/section_identity-configure.xml"/>
<xi:include href="../common/section_keystone-sample-conf-files.xml"/>
<xi:include href="../common/section_keystone_certificates-for-pki.xml"/>
<xi:include href="../common/section_keystone-ssl-config.xml"/>
<xi:include href="../common/section_keystone-ssl-config.xml"/>
</chapter>

2
doc/src/docbkx/openstack-config/compute-configure-migrations.xml
View File

@ -158,7 +158,7 @@
<prompt>$</prompt> <userinput>/etc/init.d/idmapd restart</userinput></screen>
</listitem>
<listitem>
<para>Set the 'execute/search' bit on your shared directory </para>
<para>Set the 'execute/search' bit on your shared directory.</para>
<para>On both compute nodes, make sure to enable the
'execute/search' bit to allow qemu to be able to use the images
within the directories. On all hosts, execute the

2
doc/src/docbkx/openstack-image/ch_converting.xml
View File

@ -40,7 +40,7 @@
</tr>
</tbody>
</table>
<para>This example will convert a raw image file named centos63.dsk to a qcow2 image file </para>
<para>This example will convert a raw image file named centos63.dsk to a qcow2 image file.</para>
<para>
<screen><prompt>$</prompt> <userinput>qemu-img convert -f raw -O qcow2 centos64.dsk centos64.qcow2</userinput></screen>
</para>

2
doc/src/docbkx/openstack-image/ch_modifying_images.xml
View File

@ -208,7 +208,7 @@ disk, carefully check that the resized disk boots and works correctly.
<simplesect>
<title>Mounting a raw image (without LVM)</title>
<para>If you have a raw virtual machine image that is not using LVM to manage its
partitions. First, use the <command>losetup </command>command to find an unused loop
partitions. First, use the <command>losetup</command> command to find an unused loop
device.
<screen><prompt>#</prompt> <userinput>losetup -f</userinput>
<computeroutput>/dev/loop0</computeroutput></screen></para>

4
doc/src/docbkx/openstack-install/ap_installingfolsom.xml
View File

@ -351,7 +351,7 @@ flavor = keystone</programlisting></para>
</section>
<section xml:id="osfolubuntu-computesevice">
<title> Installing and configuring Compute</title>
<title>Installing and configuring Compute</title>
<para>Install the
packages.<screen><prompt>$</prompt> <userinput>sudo apt-get install nova-api nova-cert nova-compute nova-compute-qemu nova-doc nova-network nova-objectstore nova-scheduler nova-volume rabbitmq-server novnc nova-consoleauth </userinput></screen>Update
@ -470,7 +470,7 @@ nova-cert ubuntu-precise nova enabled :-) 2012-09-1
LOGIN_REDIRECT_URL='/horizon'</screen>
<para>Restart the
services.<screen><prompt>$</prompt> <userinput>sudo service apache2 restart; sudo service memcached restart</userinput></screen></para>
<para>Logging into the dashboard with browser </para>
<para>Logging into the dashboard with browser</para>
<programlisting>http://127.0.0.1/horizon</programlisting>
</section>
<xi:include href="cinder-install.xml"></xi:include>

2
doc/src/docbkx/openstack-install/ch_installidentity.xml
View File

@ -3,7 +3,7 @@
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
xml:id="ch_installing-openstack-identity-service">
<title>Installing OpenStack Identity Service </title>
<title>Installing OpenStack Identity Service</title>
<para>The OpenStack Identity Service manages users, tenants
(accounts or projects) and offers a common identity system for
all the OpenStack components.</para>

2
doc/src/docbkx/openstack-install/ch_installobjectstorage.xml
View File

@ -3,7 +3,7 @@
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
xml:id="ch_installing-openstack-object-storage">
<title>Installing OpenStack Object Storage </title>
<title>Installing OpenStack Object Storage</title>
<para>The OpenStack Object Storage services work together to provide object storage and retrieval through a REST API.</para>
<xi:include href="object-storage-sys-requirements.xml" />

2
doc/src/docbkx/openstack-install/ch_terminology.xml
View File

@ -6,7 +6,7 @@
<title>OpenStack Terminology</title>
<section xml:id="version">
<title> Version Names and Release Notes</title>
<title>Version Names and Release Notes</title>
<para>Each OpenStack release has a name, in increasing alphabetical order (e.g., Havana
follows Grizzly). There are also version numbers corresponding to these releases,
as shown in the table below. Click on a release name in the table (e.g., Grizzly) for

2
doc/src/docbkx/openstack-install/compute-db-sync.xml
View File

@ -14,7 +14,7 @@
response means the command completed correctly and your
nova database is now populated.</para>
<note><title>Deprecation warnings</title>
<para>Note that if while running this command you see warnings such as <literal> SADeprecationWarning: The 'listeners' argument to Pool (and create_engine()) is deprecated. Use event.listen().</literal>, these will be fixed in future version of the libraries and can be safely ignored.</para></note>
<para>Note that if while running this command you see warnings such as <literal>SADeprecationWarning: The 'listeners' argument to Pool (and create_engine()) is deprecated. Use event.listen().</literal>, these will be fixed in future version of the libraries and can be safely ignored.</para></note>
<para>Restart all services in total, just to cover the entire spectrum. On the controller node
run:</para>

4
doc/src/docbkx/openstack-install/compute-sys-requirements.xml
View File

@ -30,10 +30,10 @@
services) </td>
<td>
<para>Processor: 64-bit x86</para>
<para>Memory: 12 GB RAM </para>
<para>Memory: 12 GB RAM</para>
<para>Disk space: 30 GB (SATA, SAS or SSD) </para>
<para>Volume storage: two disks with 2 TB (SATA) for volumes attached to the
compute nodes </para>
compute nodes</para>
<para>Network: one 1 Gbps Network Interface Card (NIC)</para>
</td>
<td>

2
doc/src/docbkx/openstack-install/install-config-glance.xml
View File

@ -45,7 +45,7 @@
determines which row in the user table it uses when authenticating connections.</para>
</note>
<para>Enter <literal>quit </literal>at the
<para>Enter <literal>quit</literal> at the
<literal>mysql></literal> prompt to exit MySQL.</para>
<para><screen><prompt>mysql></prompt> <userinput>quit</userinput></screen></para>

2
doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml
View File

@ -41,7 +41,7 @@
</note>
</section>
<section xml:id="general-installation-steps-swift">
<title>General Installation Steps </title>
<title>General Installation Steps</title>
<orderedlist>
<listitem>
<para>Install the baseline operating system, such as

2
doc/src/docbkx/openstack-install/object-storage-verifying-install.xml
View File

@ -28,7 +28,7 @@
</note>
</step>
<step>
<para> Export the ADMINPASS environment variable: </para>
<para>Export the ADMINPASS environment variable:</para>
<screen><prompt>$</prompt> <userinput>export ADMINPASS=secrete</userinput></screen></step>
<step><para>Run the following swift command with the correct Identity
Service URL:</para><screen><prompt>$</prompt> <userinput>swift -V 2.0 -A http://&lt;AUTH_HOSTNAME&gt;:5000/v2.0 -U demo:admin -K $ADMINPASS stat</userinput></screen>

2
doc/src/docbkx/openstack-install/start-storage-node-services.xml
View File

@ -5,7 +5,7 @@
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" >
<title>Start the Storage Nodes Services</title>
<para> Now that the ring files are on each storage node the
<para>Now that the ring files are on each storage node the
services can be started. On each storage node run the
following:<screen>
<prompt>#</prompt> <userinput>service swift-object start</userinput>

264
doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml
View File

@ -22,11 +22,11 @@
<tbody>
<tr>
<td>debug=False </td>
<td>debug=False</td>
<td>(BoolOpt) Prints debugging output.</td>
</tr>
<tr>
<td>verbose=False </td>
<td>verbose=False</td>
<td>(BoolOpt) Prints more verbose output.
</td>
</tr>
@ -55,35 +55,35 @@
</tr>
<tr>
<td>log_format=%(asctime)s %(levelname)8s
[%(name)s] %(message)s </td>
[%(name)s] %(message)s</td>
<td>(StrOpt) A logging.Formatter log message
format string that can use any of the
available logging.LogRecord attributes.
</td>
</tr>
<tr>
<td>log_date_format=%Y-%m-%d %H:%M:%S </td>
<td>log_date_format=%Y-%m-%d %H:%M:%S</td>
<td>(StrOpt) Format string for %(asctime)s in
log records.</td>
</tr>
<tr>
<td>log_file= </td>
<td>log_file=</td>
<td>(StrOpt) (Optional) Name of log file to
output to.  If not set, logging goes to
stdout.</td>
</tr>
<tr>
<td>log_dir= </td>
<td>log_dir=</td>
<td>(StrOpt) (Optional) The directory to keep
log files in (will be prepended to
--logfile).</td>
</tr>
<tr>
<td>use_syslog=False </td>
<td>use_syslog=False</td>
<td>(BoolOpt) Uses syslog for logging.</td>
</tr>
<tr>
<td>syslog_log_facility=LOG_USER </td>
<td>syslog_log_facility=LOG_USER</td>
<td>(StrOpt) The syslog facility to receive
log lines.</td>
</tr>
@ -125,17 +125,17 @@
<td>(StrOpt) Authentication protocol.</td>
</tr>
<tr>
<td>admin_tenant_name = </td>
<td>admin_tenant_name =</td>
<td>(StrOpt) The administrative tenant
name.</td>
</tr>
<tr>
<td>admin_user = </td>
<td>admin_user =</td>
<td>(StrOpt) The administrative user
name.</td>
</tr>
<tr>
<td>admin_password = </td>
<td>admin_password =</td>
<td>(StrOpt) The password for the
administrative user.</td>
</tr>
@ -158,26 +158,26 @@
</thead>
<tbody>
<tr>
<td>bind_host=0.0.0.0 </td>
<td>bind_host=0.0.0.0</td>
<td>(StrOpt) Server listening IP.</td>
</tr>
<tr>
<td>bind_port=9696 </td>
<td>bind_port=9696</td>
<td>(IntOpt) Server listening port.</td>
</tr>
<tr>
<td>api_paste_config=api-paste.ini </td>
<td>api_paste_config=api-paste.ini</td>
<td>(StrOpt) The paste configuration file,
which configures the WSGI application.
</td>
</tr>
<tr>
<td>api_extensions_path= </td>
<td>api_extensions_path=</td>
<td>(StrOpt) Enables custom addition to be
made to the above configuration.</td>
</tr>
<tr>
<td>policy_file=policy.json </td>
<td>policy_file=policy.json</td>
<td>(StrOpt) JSON file representing policies
to access and view data. The usage and
format is discussed in more detail in the
@ -185,18 +185,18 @@
</td>
</tr>
<tr>
<td>auth_strategy=keystone </td>
<td>auth_strategy=keystone</td>
<td>(StrOpt) The strategy used for
authentication. The supported values are
‘keystone’ and ‘noauth’.</td>
</tr>
<tr>
<td>core_plugin=neutron.plugins.sample.SamplePlugin.FakePlugin </td>
<td>core_plugin=neutron.plugins.sample.SamplePlugin.FakePlugin</td>
<td>(StrOpt) The plugin to be loaded by the
service.</td>
</tr>
<tr>
<td>pagination_max_limit=-1 </td>
<td>pagination_max_limit=-1</td>
<td>(StrOpt) The maximum number of items
returned in a single response. A value of
'infinite', or a negative integer means no
@ -218,7 +218,7 @@
</thead>
<tbody>
<tr>
<td>base_mac=fa:16:3e:00:00:00 </td>
<td>base_mac=fa:16:3e:00:00:00</td>
<td>(StrOpt) MAC addresses for a port are
generated. The first 3 octets will remain
unchanged. If the 4h octet is not 00, it
@ -226,18 +226,18 @@
randomly generated.</td>
</tr>
<tr>
<td>mac_generation_retries=16 </td>
<td>mac_generation_retries=16</td>
<td>(IntOpt) The number of times the plugin
attempts to generate a unique MAC address.
</td>
</tr>
<tr>
<td>allow_bulk=True </td>
<td>allow_bulk=True</td>
<td>(BoolOpt) Enables or disables bulk
create/update/delete operations.</td>
</tr>
<tr>
<td>allow_overlapping_ips=False </td>
<td>allow_overlapping_ips=False</td>
<td><para>(BoolOpt) Enables or disables whether overlapping IPs can be
created for subnets with different
tenants. L3 agent and dhcp agent must
@ -247,7 +247,7 @@
</td>
</tr>
<tr>
<td>allow_pagination=False </td>
<td>allow_pagination=False</td>
<td><para>(BoolOpt) Enables or disables
pagination. If plugin doesn't support
native pagination, it will enable
@ -266,7 +266,7 @@
</td>
</tr>
<tr>
<td>allow_sorting=False </td>
<td>allow_sorting=False</td>
<td><para>(BoolOpt) Enables or disables
sorting. If plugin doesn't support
native sorting, it will enable
@ -280,19 +280,19 @@
</td>
</tr>
<tr>
<td>force_gateway_on_subnet = False </td>
<td>force_gateway_on_subnet = False</td>
<td><para>(BoolOpt) Enables or disables
that a gateway must be configured on a subnet.</para>
</td>
</tr>
<tr>
<td>max_dns_nameservers=5 </td>
<td>max_dns_nameservers=5</td>
<td>(IntOpt) The maximum amount of DNS
nameservers that can be configured per
subnet.</td>
</tr>
<tr>
<td>max_subnet_host_routes=20 </td>
<td>max_subnet_host_routes=20</td>
<td>(IntOpt) The maximum amount of host routes
that can be configured per subnet.</td>
</tr>
@ -302,7 +302,7 @@
configuration files.</td>
</tr>
<tr>
<td>dhcp_lease_duration=120 </td>
<td>dhcp_lease_duration=120</td>
<td>(IntOpt) The default expiration time, in
seconds, for a DHCP address.</td>
</tr>
@ -323,38 +323,38 @@
</thead>
<tbody>
<tr>
<td>control_exchange=neutron </td>
<td>control_exchange=neutron</td>
<td>(StrOpt) AMQP exchange to connect to if
using RabbitMQ or QPID.</td>
</tr>
<tr>
<td>rpc_backend=neutron.openstack.common.rpc.impl_kombu </td>
<td>rpc_backend=neutron.openstack.common.rpc.impl_kombu</td>
<td>(StrOpt) The messaging module to use, defaults to kombu. For qpid, make
use of neutron.openstack.common.rpc.impl_qpid.</td>
</tr>
<tr>
<td>rpc_thread_pool_size=64 </td>
<td>rpc_thread_pool_size=64</td>
<td>(IntOpt) Size of RPC thread pool.</td>
</tr>
<tr>
<td>rpc_conn_pool_size=30 </td>
<td>rpc_conn_pool_size=30</td>
<td>(IntOpt) Size of RPC connection pool.
</td>
</tr>
<tr>
<td>rpc_response_timeout=60 </td>
<td>rpc_response_timeout=60</td>
<td>(IntOpt) Seconds to wait for a response
from call or multi call.</td>
</tr>
<tr>
<td>allowed_rpc_exception_modules='neutron.openstack.common.exception',
'nova.exception' </td>
'nova.exception'</td>
<td>(ListOpt) Modules of exceptions that are
permitted to be recreated upon receiving
exception data from an rpc call.</td>
</tr>
<tr>
<td>fake_rabbit=False </td>
<td>fake_rabbit=False</td>
<td>(BoolOpt) If passed, use a fake RabbitMQ
provider.</td>
</tr>
@ -374,57 +374,57 @@
</thead>
<tbody>
<tr>
<td>kombu_ssl_version= </td>
<td>kombu_ssl_version=</td>
<td>(StrOpt) SSL version to use (valid only if
SSL enabled).</td>
</tr>
<tr>
<td>kombu_ssl_keyfile= </td>
<td>kombu_ssl_keyfile=</td>
<td>(StrOpt) SSL key file (valid only if SSL
enabled).</td>
</tr>
<tr>
<td>kombu_ssl_certfile= </td>
<td>kombu_ssl_certfile=</td>
<td>(StrOpt) SSL cert file (valid only if SSL
enabled).</td>
</tr>
<tr>
<td>kombu_ssl_ca_certs= </td>
<td>kombu_ssl_ca_certs=</td>
<td>(StrOpt) SSL certification authority file
(valid only if SSL enabled).</td>
</tr>
<tr>
<td>rabbit_host=localhost </td>
<td>rabbit_host=localhost</td>
<td>(StrOpt) IP address of the RabbitMQ
installation.</td>
</tr>
<tr>
<td>rabbit_password=guest </td>
<td>rabbit_password=guest</td>
<td>Password of the RabbitMQ server.</td>
</tr>
<tr>
<td>rabbit_port=5672 </td>
<td>rabbit_port=5672</td>
<td>(IntOpt) Port where RabbitMQ server is
running/listening.</td>
</tr>
<tr>
<td>rabbit_userid=guest </td>
<td>rabbit_userid=guest</td>
<td>(StrOpt) User ID used for RabbitMQ
connections.</td>
</tr>
<tr>
<td>rabbit_virtual_host=/ </td>
<td>rabbit_virtual_host=/</td>
<td>(StrOpt) Location of a virtual RabbitMQ
installation.</td>
</tr>
<tr>
<td>rabbit_max_retries=0 </td>
<td>rabbit_max_retries=0</td>
<td>(IntOpt) Maximum retries with trying to
connect to RabbitMQ. The default of 0
implies an infinite retry count.</td>
</tr>
<tr>
<td>rabbit_retry_interval=1 </td>
<td>rabbit_retry_interval=1</td>
<td>(IntOpt) RabbitMQ connection retry
interval.</td>
</tr>
@ -444,71 +444,71 @@
</thead>
<tbody>
<tr>
<td>qpid_hostname=localhost </td>
<td>qpid_hostname=localhost</td>
<td>(StrOpt) Qpid broker hostname.</td>
</tr>
<tr>
<td>qpid_port=5672 </td>
<td>qpid_port=5672</td>
<td>(IntOpt) Qpid broker port.</td>
</tr>
<tr>
<td>qpid_username= </td>
<td>qpid_username=</td>
<td>(StrOpt) Username for qpid connection.
</td>
</tr>
<tr>
<td>qpid_password= </td>
<td>qpid_password=</td>
<td>(StrOpt) Password for qpid connection.
</td>
</tr>
<tr>
<td>qpid_sasl_mechanisms= </td>
<td>qpid_sasl_mechanisms=</td>
<td>(StrOpt) Space separated list of SASL
mechanisms to use for auth.</td>
</tr>
<tr>
<td>qpid_reconnect=True </td>
<td>qpid_reconnect=True</td>
<td>(BoolOpt) Automatically reconnect.</td>
</tr>
<tr>
<td>qpid_reconnect_timeout=0 </td>
<td>qpid_reconnect_timeout=0</td>
<td>(IntOpt) The number of seconds to wait
before deciding that a reconnect attempt
has failed.</td>
</tr>
<tr>
<td>qpid_reconnect_limit=0 </td>
<td>qpid_reconnect_limit=0</td>
<td>(IntOpt) The limit for the number of times
to reconnect before considering the
connection to be failed.</td>
</tr>
<tr>
<td>qpid_reconnect_interval_min=0 </td>
<td>qpid_reconnect_interval_min=0</td>
<td>(IntOpt) Minimum seconds between
reconnection attempts.</td>
</tr>
<tr>
<td>qpid_reconnect_interval_max=0 </td>
<td>qpid_reconnect_interval_max=0</td>
<td>(IntOpt) Maximum seconds between
reconnection attempts.</td>
</tr>
<tr>
<td>qpid_reconnect_interval=0 </td>
<td>qpid_reconnect_interval=0</td>
<td>(IntOpt) Equivalent to setting max and min
to the same value.</td>
</tr>
<tr>
<td>qpid_heartbeat=60 </td>
<td>qpid_heartbeat=60</td>
<td>(IntOpt) Seconds between connection
keepalive heartbeats.</td>
</tr>
<tr>
<td>qpid_protocol=tcp </td>
<td>qpid_protocol=tcp</td>
<td>(StrOpt) Transport to use, either 'tcp' or
'ssl.' </td>
</tr>
<tr>
<td>qpid_tcp_nodelay=True </td>
<td>qpid_tcp_nodelay=True</td>
<td>(BoolOpt) Disable Nagle algorithm.</td>
</tr>
</tbody>
@ -526,30 +526,30 @@
</thead>
<tbody>
<tr>
<td>notification_driver=neutron.openstack.common.notifier.list_notifier </td>
<td>notification_driver=neutron.openstack.common.notifier.list_notifier</td>
<td>(MultiStrOpt) Driver or drivers to handle
sending notifications. The default is set
as notifier as the DHCP agent makes use of
the notifications.</td>
</tr>
<tr>
<td>default_notification_level=INFO </td>
<td>default_notification_level=INFO</td>
<td>(StrOpt) Default notification level for
outgoing notifications.</td>
</tr>
<tr>
<td>default_publisher_id=$host </td>
<td>default_publisher_id=$host</td>
<td>(StrOpt) Default publisher_id for outgoing
notifications.</td>
</tr>
<tr>
<td>
list_notifier_drivers='neutron.openstack.common.notifier.no_op_notifier' </td>
list_notifier_drivers='neutron.openstack.common.notifier.no_op_notifier'</td>
<td>(MultiStrOpt) List of drivers to send
notifications.</td>
</tr>
<tr>
<td>notification_topics='notifications' </td>
<td>notification_topics='notifications'</td>
<td>(ListOpt) AMQP topic used for openstack
notifications.</td>
</tr>
@ -569,7 +569,7 @@
</thead>
<tbody>
<tr>
<td>quota_driver=neutron.quota.ConfDriver </td>
<td>quota_driver=neutron.quota.ConfDriver</td>
<td>(StrOpt) Default driver to use for quota checks. If the default driver
is used then the configuration values below are in effect. To limit
quotas per tenant then use:
@ -577,28 +577,28 @@
</td>
</tr>
<tr>
<td>quota_items=network,subnet,port </td>
<td>quota_items=network,subnet,port</td>
<td>(ListOpt) Resource names that are
supported by the Quotas feature.</td>
</tr>
<tr>
<td>default_quota=-1 </td>
<td>default_quota=-1</td>
<td>(IntOpt) Default number of resources
allowed per tenant, minus for unlimited.
</td>
</tr>
<tr>
<td>quota_network=10 </td>
<td>quota_network=10</td>
<td>(IntOpt) Number of networks allowed per
tenant, and minus means unlimited.</td>
</tr>
<tr>
<td>quota_subnet=10 </td>
<td>quota_subnet=10</td>
<td>(IntOpt) Number of subnets allowed per
tenant, and minus means unlimited.</td>
</tr>
<tr>
<td>quota_port=50 </td>
<td>quota_port=50</td>
<td>(IntOpt) Number of ports allowed per
tenant, and minus means unlimited.</td>
</tr>
@ -625,7 +625,7 @@
</thead>
<tbody>
<tr>
<td>sql_connection=sqlite:// </td>
<td>sql_connection=sqlite://</td>
<td><para>(StrOpt) The details of the database connection. For example
mysql://root:nova@127.0.0.1:3306/ovs_neutron. Replace 127.0.0.1
above with the IP address of the database used by the main OpenStack
@ -638,14 +638,14 @@
</td>
</tr>
<tr>
<td>sql_max_retries=10 </td>
<td>sql_max_retries=10</td>
<td>(IntOpt) The number of database
re-connection retry times. Used if
connectivity is lost with the database. -1
implies an infinite retry count.</td>
</tr>
<tr>
<td>reconnect_interval=2 </td>
<td>reconnect_interval=2</td>
<td>(IntOpt) The database reconnection
interval in seconds. Used if connectivity
is lost.</td>
@ -671,7 +671,7 @@
</thead>
<tbody>
<tr>
<td>network_vlan_ranges=default:2000:3999 </td>
<td>network_vlan_ranges=default:2000:3999</td>
<td>(ListOpt) Comma-separated list of 
&lt;physical_network&gt;:&lt;vlan_min&gt;:&lt;vlan_max&gt;
tuples enumerating ranges of VLAN IDs on
@ -679,14 +679,14 @@
for allocation.</td>
</tr>
<tr>
<td>tunnel_id_ranges= </td>
<td>tunnel_id_ranges=</td>
<td>(ListOpt) Comma-separated list of
&lt;tun_min&gt;:&lt;tun_max&gt; tuples
enumerating ranges of GRE tunnel IDs that
are available for allocation.</td>
</tr>
<tr>
<td>integration_bridge=br-int </td>
<td>integration_bridge=br-int</td>
<td>(StrOpt) The name of the OVS integration
bridge. There is one per hypervisor. The
integration bridge acts as a virtual
@ -697,14 +697,14 @@
good reason to.</td>
</tr>
<tr>
<td>tunnel_bridge=br-tun </td>
<td>tunnel_bridge=br-tun</td>
<td>(StrOpt) The name of the OVS tunnel bridge
used by the agent for GRE tunnels. Only
used if tunnel_id_ranges is not empty.
</td>
</tr>
<tr>
<td>bridge_mappings=default:br-eth1 </td>
<td>bridge_mappings=default:br-eth1</td>
<td>(ListOpt) Comma-separated list of
&lt;physical_network&gt;:&lt;bridge&gt;
tuples mapping physical network names to
@ -714,13 +714,13 @@
a port.</td>
</tr>
<tr>
<td>local_ip=10.0.0.3 </td>
<td>local_ip=10.0.0.3</td>
<td>(StrOpt) The local IP address of this
hypervisor. Used only when
tunnel_id_ranges are used.</td>
</tr>
<tr>
<td>enable_tunneling=False </td>
<td>enable_tunneling=False</td>
<td>(BoolOpt) A flag indicating if tunneling
is supported. Not all systems that support
Open vSwitch support its GRE tunneling
@ -746,7 +746,7 @@
</thead>
<tbody>
<tr>
<td>rpc=True </td>
<td>rpc=True</td>
<td>(BoolOpt) If <literal>True</literal>, the agent communicates with the
plugin through the OpenStack RPC, which is configured in
<filename>neutron.conf.</filename> If <literal>False</literal>, the
@ -755,12 +755,12 @@
access the database.</td>
</tr>
<tr>
<td>polling_interval=2 </td>
<td>polling_interval=2</td>
<td>(IntOpt) Agent's polling interval in
seconds.</td>
</tr>
<tr>
<td>root_helper=sudo </td>
<td>root_helper=sudo</td>
<td>(StrOpt) Limits the commands that can be
run. See the rootwrap section for more
details.</td>
@ -785,7 +785,7 @@
</thead>
<tbody>
<tr>
<td>sql_connection=sqlite:// </td>
<td>sql_connection=sqlite://</td>
<td><para>(StrOpt) The details of the database connection. For example
mysql://root:nova@127.0.0.1:3306/ovs_neutron. Replace 127.0.0.1
above with the IP address of the database used by the main
@ -799,14 +799,14 @@
</td>
</tr>
<tr>
<td>sql_max_retries=10 </td>
<td>sql_max_retries=10</td>
<td>(IntOpt) Database re-connection retry
times. Used if connectivity is lost
with the database. -1 implies an
infinite retry count.</td>
</tr>
<tr>
<td>reconnect_interval=2 </td>
<td>reconnect_interval=2</td>
<td>(IntOpt) Database reconnection
interval in seconds. Used if
connectivity is lost.</td>
@ -828,7 +828,7 @@
</thead>
<tbody>
<tr>
<td>network_vlan_ranges=default:1000:2999 </td>
<td>network_vlan_ranges=default:1000:2999</td>
<td>(ListOpt) Comma-separated list of
&lt;physical_network&gt;:&lt;vlan_min&gt;:&lt;vlan_max&gt;
tuples enumerating ranges of VLAN IDs
@ -852,7 +852,7 @@
</thead>
<tbody>
<tr>
<td>physical_interface_mappings=default:eth1 </td>
<td>physical_interface_mappings=default:eth1</td>
<td>(ListOpt) Comma-separated list of
&lt;physical_network&gt;:&lt;physical_interface&gt;
tuples mapping physical network names
@ -878,7 +878,7 @@
</thead>
<tbody>
<tr>
<td>rpc=True </td>
<td>rpc=True</td>
<td>(BoolOpt) If <literal>True</literal>, the agent communicates with
the plugin through the OpenStack RPC, which is configured in
<filename>neutron.conf</filename>. If <literal>False</literal>,
@ -887,12 +887,12 @@
settings on the agent so that it can access the database.</td>
</tr>
<tr>
<td>polling_interval=2 </td>
<td>polling_interval=2</td>
<td>(IntOpt) Agent's polling interval in
seconds.</td>
</tr>
<tr>
<td>root_helper=sudo </td>
<td>root_helper=sudo</td>
<td>(StrOpt) Limits the commands that can
be run. See the rootwrap section for
more details.</td>
@ -921,24 +921,24 @@
</thead>
<tbody>
<tr>
<td>root_helper=sudo </td>
<td>root_helper=sudo</td>
<td>(StrOpt) Limits the commands that can
be run. See the rootwrap section for
more details.</td>
</tr>
<tr>
<td>dhcp_driver=neutron.agent.linux.dhcp.Dnsmasq </td>
<td>dhcp_driver=neutron.agent.linux.dhcp.Dnsmasq</td>
<td>(StrOpt) The driver used to manage the
DHCP server.</td>
</tr>
<tr>
<td>
dhcp_lease_relay_socket=$state_path/dhcp/lease_relay </td>
dhcp_lease_relay_socket=$state_path/dhcp/lease_relay</td>
<td>(StrOpt) Location to DHCP lease relay
UNIX domain socket.</td>
</tr>
<tr>
<td>use_namespaces=True </td>
<td>use_namespaces=True</td>
<td><para>(BoolOpt) Allows overlapping
IP.</para>
@ -967,27 +967,27 @@
</thead>
<tbody>
<tr>
<td>dhcp_confs=$state_path/dhcp </td>
<td>dhcp_confs=$state_path/dhcp</td>
<td>(StrOpt) Location to store DHCP server
config files.</td>
</tr>
<tr>
<td>dhcp_lease_time=120 </td>
<td>dhcp_lease_time=120</td>
<td>(IntOpt) Lifetime of a DHCP lease in
seconds.</td>
</tr>
<tr>
<td>dhcp_domain=openstacklocal </td>
<td>dhcp_domain=openstacklocal</td>
<td>(StrOpt) Domain to use for building
the host names.</td>
</tr>
<tr>
<td>dnsmasq_config_file= </td>
<td>dnsmasq_config_file=</td>
<td>(StrOpt) Overrides the default dnsmasq
settings with this file.</td>
</tr>
<tr>
<td>dnsmasq_dns_server= </td>
<td>dnsmasq_dns_server=</td>
<td>(StrOpt) Specifies whether to use
another DNS server before any in
<filename>/etc/resolv.conf</filename>.
@ -1016,18 +1016,18 @@
</thead>
<tbody>
<tr>
<td>root_helper=sudo </td>
<td>root_helper=sudo</td>
<td>(StrOpt) Limits the commands that can
be run. See the rootwrap section for
more details.</td>
</tr>
<tr>
<td>external_network_bridge=br-ex </td>
<td>external_network_bridge=br-ex</td>
<td>(StrOpt) Name of bridge used for
external network traffic.</td>
</tr>
<tr>
<td>use_namespaces=True </td>
<td>use_namespaces=True</td>
<td><para>(BoolOpt) Allows overlapping IP.</para>
<para>If you run multiple agents
with different IP addresses on the
@ -1038,28 +1038,28 @@
</tr>
<tr>
<td>polling_interval=3 </td>
<td>polling_interval=3</td>
<td>(IntOpt) The time, in seconds, between
state poll requests.</td>
</tr>
<tr>
<td>metadata_port=9697 </td>
<td>metadata_port=9697</td>
<td>(IntOpt) TCP Port used by metadata namespace proxy.</td>
</tr>
<tr>
<td>router_id= </td>
<td>router_id=</td>
<td>(StrOpt) If namespaces is disabled,
the l3 agent can only configure a
router whose ID matches this
parameter.</td>
</tr>
<tr>
<td>handle_internal_only_routers=True </td>
<td>handle_internal_only_routers=True</td>
<td>(BoolOpt) Agent should implement
routers with no gateway.</td>
</tr>
<tr>
<td>gateway_external_network_id= </td>
<td>gateway_external_network_id=</td>
<td>(StrOpt) UUID of external network for
routers implemented by the agents.
</td>
@ -1076,47 +1076,47 @@
<thead>
<tr>
<th>Configuration option=Default value</th>
<th>(Type) Description </th>
<th>(Type) Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>nova_metadata_ip=127.0.0.1 </td>
<td>nova_metadata_ip=127.0.0.1</td>
<td>(StrOpt) The IP address of the Nova metadata service.</td>
</tr>
<tr>
<td>nova_metadata_port=8775 </td>
<td>nova_metadata_port=8775</td>
<td>(IntOpt) The TCP port of the Nova metadata service.</td>
</tr>
<tr>
<td>metadata_proxy_shared_secret= </td>
<td>metadata_proxy_shared_secret=</td>
<td>(StrOpt) When proxying metadata requests, Neutron signs the Instance-ID
header with a shared secret to prevent spoofing. You may select any
string for a secret, but it must match here and in the configuration
used by the Nova Metadata Server. NOTE: Nova uses a different key:
neutron_metadata_proxy_shared_secret </td>
neutron_metadata_proxy_shared_secret</td>
</tr>
<tr>
<td>admin_user= </td>
<td>admin_user=</td>
<td>(StrOpt) The administrative user name for OpenStack Networking, which is
defined in <link xlink:href="keystone.html">OpenStack Identity</link>
(keystone).</td>
</tr>
<tr>
<td>admin_password= </td>
<td>admin_password=</td>
<td>(StrOpt) The password for the administrative user.</td>
</tr>
<tr>
<td>admin_tenant_name= </td>
<td>admin_tenant_name=</td>
<td>(StrOpt) The administrative user's tenant name.</td>
</tr>
<tr>
<td>auth_url= </td>
<td>auth_url=</td>
<td>(StrOpt) The URL used to validate tokens. For example,
<code>`auth_protocol`://`auth_host`:`auth_port`/v2.0</code>.</td>
</tr>
<tr>
<td>auth_region= </td>
<td>auth_region=</td>
<td>(StrOpt) The authentication region.</td>
</tr>
</tbody>
@ -1137,7 +1137,7 @@
</thead>
<tbody>
<tr>
<td>interface_driver= </td>
<td>interface_driver=</td>
<td>(StrOpt) The driver used to manage the
virtual interface.</td>
</tr>
@ -1150,7 +1150,7 @@
switch and check port status.</td>
</tr>
<tr>
<td>admin_user= </td>
<td>admin_user=</td>
<td>(StrOpt) The administrative user name for
OpenStack Networking, which is defined in
<link xlink:href="keystone.html"
@ -1158,60 +1158,60 @@
Only relevant if using MetaPlugin.</td>
</tr>
<tr>
<td>admin_password= </td>
<td>admin_password=</td>
<td>(StrOpt) The password for the
administrative user. Only relevant if
using MetaPlugin.</td>
</tr>
<tr>
<td>admin_tenant_name= </td>
<td>admin_tenant_name=</td>
<td>(StrOpt) The administrative user's tenant
name. Only relevant if using
MetaPlugin.</td>
</tr>
<tr>
<td>auth_url= </td>
<td>auth_url=</td>
<td>(StrOpt) The URL used to validate tokens.
For example,
<code>`auth_protocol`://`auth_host`:`auth_port`/v2.0</code>.
Only relevant if using MetaPlugin.</td>
</tr>
<tr>
<td>auth_strategy=keystone </td>
<td>auth_strategy=keystone</td>
<td>(StrOpt) The strategy to use for
authentication. Supports noauth or
keystone. Only relevant if using
MetaPlugin.</td>
</tr>
<tr>
<td>auth_region= </td>
<td>auth_region=</td>
<td>(StrOpt) The authentication region. Only
relevant if using MetaPlugin.</td>
</tr>
<tr>
<td>ovs_integration_bridge=br-int </td>
<td>ovs_integration_bridge=br-int</td>
<td>(StrOpt) Name of Open vSwitch bridge to
use. Only relevant if using Open vSwitch.
</td>
</tr>
<tr>
<td>network_device_mtu= </td>
<td>network_device_mtu=</td>
<td>(StrOpt) MTU setting for device. Only
relevant if using Open vSwitch.</td>
</tr>
<!-- <tr>
<td>ryu_api_host=127.0.0.1:8080 </td>
<td>ryu_api_host=127.0.0.1:8080</td>
<td>(StrOpt) OpenFlow Ryu REST API host:port.
Only relevant if using Ryu.</td>
</tr>-->
<tr>
<td>meta_flavor_driver_mappings= </td>
<td>meta_flavor_driver_mappings=</td>
<td>(StrOpt). Mappings between flavors and
drivers. Only relevant if using
MetaPlugin.</td>
</tr>
<tr>
<td>resync_interval=30 </td>
<td>resync_interval=30</td>
<td>(IntOpt) If an exception occurs on the neutron-server service, the DHCP
agent ensures that it syncs with the <filename>neutron.conf</filename>
configuration. The validation about syncing occurs every

18
doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml
View File

@ -9,22 +9,22 @@
sorting</caption>
<thead>
<tr>
<th>Plugin </th>
<th>Support Native Pagination </th>
<th>Support Native Sorting </th>
<th>Plugin</th>
<th>Support Native Pagination</th>
<th>Support Native Sorting</th>
</tr>
</thead>
<tbody>
<tr>
<td>Open vSwitch </td>
<td>True </td>
<td>True </td>
<td>Open vSwitch</td>
<td>True</td>
<td>True</td>
</tr>
<tr>
<td>LinuxBridge </td>
<td>True </td>
<td>True </td>
<td>LinuxBridge</td>
<td>True</td>
<td>True</td>
</tr>
</tbody>
</table>

24
doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml
View File

@ -75,7 +75,7 @@ mysql&gt; grant all on &lt;database-name&gt;.* to '&lt;user-name&gt;'@'%';</comp
<td>$NEUTRON_CONF_DIR/plugins/openvswitch/ovs_neutron_plugin.ini</td>
</tr>
<tr>
<td>Agent </td>
<td>Agent</td>
<td>neutron-openvswitch-agent</td>
</tr>
<tr>
@ -95,7 +95,7 @@ mysql&gt; grant all on &lt;database-name&gt;.* to '&lt;user-name&gt;'@'%';</comp
<td>$NEUTRON_CONF_DIR/plugins/linuxbridge/linuxbridge_conf.ini</td>
</tr>
<tr>
<td>Agent </td>
<td>Agent</td>
<td>neutron-linuxbridge-agent</td>
</tr>
</tbody>
@ -120,8 +120,8 @@ mysql&gt; grant all on &lt;database-name&gt;.* to '&lt;user-name&gt;'@'%';</comp
<col width="50%"/>
<thead>
<tr>
<th>Parameter </th>
<th>Value </th>
<th>Parameter</th>
<th>Value</th>
</tr>
</thead>
<tbody>
@ -170,8 +170,8 @@ mysql&gt; grant all on &lt;database-name&gt;.* to '&lt;user-name&gt;'@'%';</comp
<col width="50%"/>
<thead>
<tr>
<th>Parameter </th>
<th>Value </th>
<th>Parameter</th>
<th>Value</th>
</tr>
</thead>
<tbody>
@ -180,23 +180,23 @@ mysql&gt; grant all on &lt;database-name&gt;.* to '&lt;user-name&gt;'@'%';</comp
<td/>
</tr>
<tr>
<td>interface_driver ($NEUTRON_CONF_DIR/l3_agent.ini) </td>
<td>neutron.agent.linux.interface.OVSInterfaceDriver </td>
<td>interface_driver ($NEUTRON_CONF_DIR/l3_agent.ini)</td>
<td>neutron.agent.linux.interface.OVSInterfaceDriver</td>
</tr>
<tr>
<td>external_network_bridge ($NEUTRON_CONF_DIR/l3_agent.ini) </td>
<td>br-ex </td>
<td>external_network_bridge ($NEUTRON_CONF_DIR/l3_agent.ini)</td>
<td>br-ex</td>
</tr>
<tr>
<td><emphasis role="bold">Linux Bridge</emphasis></td>
<td/>
</tr>
<tr>
<td>interface_driver ($NEUTRON_CONF_DIR/l3_agent.ini) </td>
<td>interface_driver ($NEUTRON_CONF_DIR/l3_agent.ini)</td>
<td>neutron.agent.linux.interface.BridgeInterfaceDriver</td>
</tr>
<tr>
<td>external_network_bridge ($NEUTRON_CONF_DIR/l3_agent.ini) </td>
<td>external_network_bridge ($NEUTRON_CONF_DIR/l3_agent.ini)</td>
<td>This field must be empty (or the bridge name for the external
network).</td>
</tr>

190
doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml
View File

@ -142,17 +142,17 @@
<col width="40%"/>
<thead>
<tr>
<th> Attribute name </th>
<th> Type </th>
<th> Default Value </th>
<th> Description </th>
<th>Attribute name</th>
<th>Type</th>
<th>Default Value</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>provider:network_type </td>
<td>String </td>
<td>N/A </td>
<td>provider:network_type</td>
<td>String</td>
<td>N/A</td>
<td>The physical mechanism by which the
virtual network is realized. Possible
values are "flat", "vlan", "local", and
@ -166,8 +166,8 @@
configuration.</td>
</tr>
<tr>
<td>provider:physical_network </td>
<td>String </td>
<td>provider:physical_network</td>
<td>String</td>
<td>If a physical network named "default" has
been configured, and if
provider:network_type is "flat" or "vlan",
@ -284,45 +284,45 @@
<col width="40%"/>
<thead>
<tr>
<th> Attribute name </th>
<th> Type </th>
<th> Default Value </th>
<th> Description </th>
<th>Attribute name</th>
<th>Type</th>
<th>Default Value</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>id </td>
<td>uuid-str </td>
<td>generated </td>
<td>id</td>
<td>uuid-str</td>
<td>generated</td>
<td>UUID for the router.</td>
</tr>
<tr>
<td>name </td>
<td>String </td>
<td>None </td>
<td>name</td>
<td>String</td>
<td>None</td>
<td>Human-readable name for the router. Might
not be unique.</td>
</tr>
<tr>
<td>admin_state_up </td>
<td>Bool </td>
<td>True </td>
<td>admin_state_up</td>
<td>Bool</td>
<td>True</td>
<td>The administrative state of router. If
false (down), the router does not forward
packets.</td>
</tr>
<tr>
<td>status </td>
<td>String </td>
<td>N/A </td>
<td>status</td>
<td>String</td>
<td>N/A</td>
<td><para>Indicates whether router is
currently operational.</para></td>
</tr>
<tr>
<td>tenant_id </td>
<td>uuid-str </td>
<td>N/A </td>
<td>tenant_id</td>
<td>uuid-str</td>
<td>N/A</td>
<td>Owner of the router. Only admin users can
specify a tenant_id other than its own.
</td>
@ -345,17 +345,17 @@
<col width="40%"/>
<thead>
<tr>
<th> Attribute name </th>
<th> Type </th>
<th> Default Value </th>
<th> Description </th>
<th>Attribute name</th>
<th>Type</th>
<th>Default Value</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>id </td>
<td>uuid-str </td>
<td>generated </td>
<td>id</td>
<td>uuid-str</td>
<td>generated</td>
<td>UUID for the floating IP.</td>
</tr>
<tr>
@ -375,8 +375,8 @@
should be allocated</para></td>
</tr>
<tr>
<td>router_id </td>
<td>uuid-str </td>
<td>router_id</td>
<td>uuid-str</td>
<td>N/A</td>
<td>Read-only value indicating the router that
connects the external network to the
@ -401,9 +401,9 @@
have more than one IP address).</td>
</tr>
<tr>
<td>tenant_id </td>
<td>uuid-str </td>
<td>N/A </td>
<td>tenant_id</td>
<td>uuid-str</td>
<td>N/A</td>
<td>Owner of the Floating IP. Only admin users
can specify a tenant_id other than its
own.</td>
@ -438,10 +438,10 @@ neutron router-interface-add router1 &lt;subnet2-uuid&gt;</computeroutput></scre
to the external network as well as support for
floating IPs allocated on that external networks (see
below).  Commonly an external network maps to a
network in the provider </para>
network in the provider</para>
<para>A router can also be connected to an “external
network”, allowing that router to act as a NAT gateway
for external connectivity.  </para>
for external connectivity.</para>
<screen><computeroutput>neutron router-gateway-set router1 &lt;ext-net-id&gt; </computeroutput></screen>
<para>Viewing routers:</para>
<para>List all routers:
@ -539,39 +539,39 @@ neutron floatingip-associate &lt;floatingip-id&gt; &lt;internal VM port-id&gt; <
<col width="40%"/>
<thead>
<tr>
<th> Attribute name </th>
<th> Type </th>
<th> Default Value </th>
<th> Description </th>
<th>Attribute name</th>
<th>Type</th>
<th>Default Value</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>id </td>
<td>uuid-str </td>
<td>generated </td>
<td>id</td>
<td>uuid-str</td>
<td>generated</td>
<td>UUID for the security group.</td>
</tr>
<tr>
<td>name </td>
<td>String </td>
<td>None </td>
<td>name</td>
<td>String</td>
<td>None</td>
<td>Human-readable name for the security
group. Might not be unique. Cannot be
named default as that is automatically
created for a tenant.</td>
</tr>
<tr>
<td>description </td>
<td>String </td>
<td>None </td>
<td>description</td>
<td>String</td>
<td>None</td>
<td>Human-readable description of a security
group.</td>
</tr>
<tr>
<td>tenant_id </td>
<td>uuid-str </td>
<td>N/A </td>
<td>tenant_id</td>
<td>uuid-str</td>
<td>N/A</td>
<td>Owner of the security group. Only admin
users can specify a tenant_id other than
their own.</td>
@ -586,17 +586,17 @@ neutron floatingip-associate &lt;floatingip-id&gt; &lt;internal VM port-id&gt; <
<col width="40%"/>
<thead>
<tr>
<th> Attribute name </th>
<th> Type </th>
<th> Default Value </th>
<th> Description </th>
<th>Attribute name</th>
<th>Type</th>
<th>Default Value</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>id </td>
<td>uuid-str </td>
<td>generated </td>
<td>id</td>
<td>uuid-str</td>
<td>generated</td>
<td>UUID for the security group rule.</td>
</tr>
<tr>
@ -615,7 +615,7 @@ neutron floatingip-associate &lt;floatingip-id&gt; &lt;internal VM port-id&gt; <
</tr>
<tr>
<td>protocol</td>
<td>String </td>
<td>String</td>
<td>None</td>
<td>IP Protocol (icmp, tcp, udp, etc).</td>
</tr>
@ -653,9 +653,9 @@ neutron floatingip-associate &lt;floatingip-id&gt; &lt;internal VM port-id&gt; <
rule.</td>
</tr>
<tr>
<td>tenant_id </td>
<td>uuid-str </td>
<td>N/A </td>
<td>tenant_id</td>
<td>uuid-str</td>
<td>N/A</td>
<td>Owner of the security group rule. Only
admin users can specify a tenant_id other
than its own.</td>
@ -768,22 +768,22 @@ neutron lb-vip-create --name myvip --protocol-port 80 --protocol HTTP --subnet-i
<col width="40%"/>
<thead>
<tr>
<th> Attribute name </th>
<th> Type </th>
<th> Default Value </th>
<th> Description </th>
<th>Attribute name</th>
<th>Type</th>
<th>Default Value</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>id </td>
<td>uuid-str </td>
<td>generated </td>
<td>id</td>
<td>uuid-str</td>
<td>generated</td>
<td>UUID for the QoS queue.</td>
</tr>
<tr>
<td>default </td>
<td>Boolean </td>
<td>default</td>
<td>Boolean</td>
<td>False by default</td>
<td>If True ports will be created with
this queue size unless the network
@ -791,42 +791,42 @@ neutron lb-vip-create --name myvip --protocol-port 80 --protocol HTTP --subnet-i
a queue at port creation time.</td>
</tr>
<tr>
<td>name </td>
<td>String </td>
<td>None </td>
<td>name</td>
<td>String</td>
<td>None</td>
<td>Name for QoS queue.</td>
</tr>
<tr>
<td>min </td>
<td>Integer </td>
<td>0 </td>
<td>min</td>
<td>Integer</td>
<td>0</td>
<td>Minimum Bandwidth Rate (kbps).
</td>
</tr>
<tr>
<td>max </td>
<td>Integer </td>
<td>N/A </td>
<td>max</td>
<td>Integer</td>
<td>N/A</td>
<td>Maximum Bandwidth Rate (kbps).
</td>
</tr>
<tr>
<td>qos_marking </td>
<td>qos_marking</td>
<td>String</td>
<td>untrusted by default </td>
<td>untrusted by default</td>
<td>Whether QoS marking should be
trusted or untrusted.</td>
</tr>
<tr>
<td>dscp </td>
<td>Integer </td>
<td>0 </td>
<td>dscp</td>
<td>Integer</td>
<td>0</td>
<td>DSCP Marking value.</td>
</tr>
<tr>
<td>tenant_id </td>
<td>uuid-str </td>
<td>N/A </td>
<td>tenant_id</td>
<td>uuid-str</td>
<td>N/A</td>
<td>The owner of the QoS queue.</td>
</tr>
</tbody>

11
doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml
View File

@ -420,12 +420,11 @@ catalog.$Region.network.internalURL = http://10.211.55.17:9696
</section>
</section>
<section xml:id="nova_with_neutron_example">
<title> Example nova.conf Values (for nova-compute and nova-api)</title>
<para>The following code provides example <filename>nova.conf</filename>
values, for a cloud controller node running OpenStack Compute and
OpenStack Networking with an IP address of 192.168.1.2
and vif-plugging using the LibvirtHybridOVSBridgeDriver.
</para>
<title>Example nova.conf (for <systemitem class="service">nova-compute</systemitem> and <systemitem class="service">nova-api</systemitem>)</title>
<para>Example values for the above settings, assuming a
cloud controller node running OpenStack Compute and
OpenStack Networking with an IP address of 192.168.1.2
and vif-plugging using the LibvirtHybridOVSBridgeDriver.</para>
<screen><computeroutput>network_api_class=nova.network.neutronv2.api.API
neutron_url=http://192.168.1.2:9696
neutron_auth_strategy=keystone

12
doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml
View File

@ -7,7 +7,7 @@
<para>Learn how to install and get the OpenStack Networking service
up and running.</para>
<section xml:id="install_prereqs">
<title> Initial Prerequisites </title>
<title>Initial Prerequisites</title>
<para>
<itemizedlist>
<listitem>
@ -38,7 +38,7 @@
<prompt>$</prompt><userinput>sudo apt-get update</userinput>
<prompt>$</prompt><userinput>sudo apt-get upgrade</userinput> </screen>
<section xml:id="install_neutron_server">
<title>Install neutron-server </title>
<title>Install neutron-server</title>
<para>The <systemitem class="service"
>neutron-server</systemitem> handles OpenStack Networking's
user requests and exposes the API. <procedure>
@ -84,7 +84,7 @@
</step>
</procedure></para>
<section xml:id="rpc_setup">
<title>RPC Setup </title>
<title>RPC Setup</title>
<para>Many OpenStack Networking plugins use RPC to enable
agents to communicate with the main <systemitem
class="service">neutron-server</systemitem> process. If
@ -757,7 +757,7 @@
>https://fedoraproject.org/wiki/OpenStack</link>
</para>
<section xml:id="fedora_rpc_setup">
<title xml:id="qpid_rpc_setup">RPC Setup </title>
<title xml:id="qpid_rpc_setup">RPC Setup</title>
<para>OpenStack Networking uses RPC to allow DHCP agents and any
plugin agents to communicate with the main <systemitem
class="service">neutron-server</systemitem> process. 
@ -794,7 +794,7 @@
</para>
</section>
<section xml:id="fedora_q_server">
<title>Install neutron-server and plugin </title>
<title>Install neutron-server and plugin</title>
<para>
<procedure>
<title>To install and configure the Neutron server and
@ -901,7 +901,7 @@
</para>
</section>
<section xml:id="fedora_q_l3">
<title>Install L3 Agent </title>
<title>Install L3 Agent</title>
<para>
<procedure>
<title>To install and configure the L3 agent</title>

4
doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml
View File

@ -29,11 +29,11 @@
<itemizedlist>
<listitem>
<para>Linux kernel 2.6.24 or newer (with CONFIG_NET_NS=y in kernel
configuration) and </para>
configuration) and</para>
</listitem>
<listitem>
<para>iproute2 utilities ('ip' command) version 3.1.0 (aka 20111117) or
newer </para>
newer</para>
</listitem>
</itemizedlist>
<para>To check whether your host supports namespaces try running the following as

16
doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml
View File

@ -212,13 +212,13 @@
<col/>
<thead>
<tr>
<th> </th>
<th> Libvirt (KVM/QEMU) </th>
<th> XenServer </th>
<th> VMware </th>
<th> Hyper-V </th>
<th> Bare-metal </th>
<th> PowerVM </th>
<th></th>
<th>Libvirt (KVM/QEMU)</th>
<th>XenServer</th>
<th>VMware</th>
<th>Hyper-V</th>
<th>Bare-metal</th>
<th>PowerVM</th>
</tr>
</thead>
<tbody>
@ -327,7 +327,7 @@
</section>
</section>
<section xml:id="Architecture">
<title>OpenStack Networking Architecture </title>
<title>OpenStack Networking Architecture</title>
<para>This section describes the high-level components of an
OpenStack Networking deployment. Before you deploy OpenStack Networking, it is useful to
understand the different components that make up the

200
doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml
View File

@ -58,59 +58,59 @@
<col width="40%"/>
<thead>
<tr>
<th> Attribute name </th>
<th> Type </th>
<th> Default Value </th>
<th> Description </th>
<th>Attribute name</th>
<th>Type</th>
<th>Default Value</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>id </td>
<td>uuid-str </td>
<td>generated </td>
<td>id</td>
<td>uuid-str</td>
<td>generated</td>
<td>UUID for the network.</td>
</tr>
<tr>
<td>name </td>
<td>String </td>
<td>None </td>
<td>name</td>
<td>String</td>
<td>None</td>
<td>Human-readable name for the network. Might
not be unique.</td>
</tr>
<tr>
<td>admin_state_up </td>
<td>Bool </td>
<td>True </td>
<td>admin_state_up</td>
<td>Bool</td>
<td>True</td>
<td>The administrative state of network. If
false (down), the network does not forward
packets.</td>
</tr>
<tr>
<td>status </td>
<td>String </td>
<td>N/A </td>
<td>status</td>
<td>String</td>
<td>N/A</td>
<td><para>Indicates whether network is
currently operational.</para></td>
</tr>
<tr>
<td>subnets </td>
<td>list(uuid-str) </td>
<td>Empty list </td>
<td>subnets</td>
<td>list(uuid-str)</td>
<td>Empty list</td>
<td>Subnets associated with this network.
</td>
</tr>
<tr>
<td>shared </td>
<td>Bool </td>
<td>False </td>
<td>shared</td>
<td>Bool</td>
<td>False</td>
<td>Specifies whether the network resource can
be accessed by any tenant or not.</td>
</tr>
<tr>
<td>tenant_id </td>
<td>uuid-str </td>
<td>N/A </td>
<td>tenant_id</td>
<td>uuid-str</td>
<td>N/A</td>
<td>Owner of network. Only admin users can
specify a tenant_id other than its own.
</td>
@ -125,91 +125,91 @@
<col width="40%"/>
<thead>
<tr>
<th>Attribute </th>
<th>Type </th>
<th>Default Value </th>
<th>Attribute</th>
<th>Type</th>
<th>Default Value</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>id </td>
<td>uuid-str </td>
<td>generated </td>
<td>UUID representing the subnet </td>
<td>id</td>
<td>uuid-str</td>
<td>generated</td>
<td>UUID representing the subnet</td>
</tr>
<tr>
<td>network_id </td>
<td>uuid-str </td>
<td>N/A </td>
<td>network_id</td>
<td>uuid-str</td>
<td>N/A</td>
<td>network this subnet is associated with.</td>
</tr>
<tr>
<td>name </td>
<td>String </td>
<td>None </td>
<td>name</td>
<td>String</td>
<td>None</td>
<td>Human-readable name for the subnet. Might
not be unique.</td>
</tr>
<tr>
<td>ip_version </td>
<td>int </td>
<td>4 </td>
<td>IP version </td>
<td>ip_version</td>
<td>int</td>
<td>4</td>
<td>IP version</td>
</tr>
<tr>
<td>cidr </td>
<td>string </td>
<td>N/A </td>
<td>cidr</td>
<td>string</td>
<td>N/A</td>
<td>cidr representing IP range for this
subnet, based on IP version </td>
subnet, based on IP version</td>
</tr>
<tr>
<td>gateway_ip </td>
<td>string </td>
<td>gateway_ip</td>
<td>string</td>
<td>first address in <emphasis role="italic"
>cidr</emphasis>
</td>
<td>default gateway used by devices in this
subnet </td>
subnet</td>
</tr>
<tr>
<td>dns_nameservers </td>
<td>list(str) </td>
<td>Empty list </td>
<td>dns_nameservers</td>
<td>list(str)</td>
<td>Empty list</td>
<td>DNS name servers used by hosts in this
subnet.</td>
</tr>
<tr>
<td>allocation_pools </td>
<td>list(dict) </td>
<td>allocation_pools</td>
<td>list(dict)</td>
<td>Every address in <emphasis role="italic"
>cidr</emphasis>, excluding <emphasis
role="italic">gateway_ip</emphasis> if
configured </td>
configured</td>
<td>Sub-ranges of cidr available for dynamic
allocation to ports [ { "start":
"10.0.0.2", "end": "10.0.0.254"} ] </td>
"10.0.0.2", "end": "10.0.0.254"} ]</td>
</tr>
<tr>
<td>host_routes </td>
<td>list(dict) </td>
<td>Empty List </td>
<td>host_routes</td>
<td>list(dict)</td>
<td>Empty List</td>
<td>Routes that should be used by devices with
IPs from this subnet (not including local
subnet route).</td>
</tr>
<tr>
<td>enable_dhcp </td>
<td>Bool </td>
<td>True </td>
<td>enable_dhcp</td>
<td>Bool</td>
<td>True</td>
<td>Specifies whether DHCP is enabled for
this subnet or not.</td>
</tr>
<tr>
<td>tenant_id </td>
<td>uuid-str </td>
<td>N/A </td>
<td>tenant_id</td>
<td>uuid-str</td>
<td>N/A</td>
<td>Owner of network. Only admin users can
specify a tenant_id other than its own.
</td>
@ -224,81 +224,81 @@
<col width="40%"/>
<thead>
<tr>
<th>Attribute </th>
<th>Type </th>
<th>Default Value </th>
<th>Attribute</th>
<th>Type</th>
<th>Default Value</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>id </td>
<td>uuid-str </td>
<td>generated </td>
<td>id</td>
<td>uuid-str</td>
<td>generated</td>
<td>UUID for the port.</td>
</tr>
<tr>
<td>network_id </td>
<td>uuid-str </td>
<td>N/A </td>
<td>network_id</td>
<td>uuid-str</td>
<td>N/A</td>
<td>Network that this port is associated with.
</td>
</tr>
<tr>
<td>name </td>
<td>String </td>
<td>None </td>
<td>name</td>
<td>String</td>
<td>None</td>
<td>Human-readable name for the port. Might
not be unique.</td>
</tr>
<tr>
<td>admin_state_up </td>
<td>bool </td>
<td>true </td>
<td>admin_state_up</td>
<td>bool</td>
<td>true</td>
<td>Administrative state of port. If false
(down), port does not forward packets.
</td>
</tr>
<tr>
<td>status </td>
<td>string </td>
<td>N/A </td>
<td>status</td>
<td>string</td>
<td>N/A</td>
<td><para>Indicates whether network is
currently operational.</para>
</td>
</tr>
<tr>
<td>mac_address </td>
<td>string </td>
<td>generated </td>
<td>mac_address</td>
<td>string</td>
<td>generated</td>
<td>Mac address to use on this port.</td>
</tr>
<tr>
<td>fixed_ips </td>
<td>list(dict) </td>
<td>automatically allocated from pool </td>
<td>fixed_ips</td>
<td>list(dict)</td>
<td>automatically allocated from pool</td>
<td>Specifies IP addresses for the port thus
associating the port itself with the
subnets where the IP addresses are picked
from </td>
from</td>
</tr>
<tr>
<td>device_id </td>
<td>str </td>
<td>None </td>
<td>device_id</td>
<td>str</td>
<td>None</td>
<td>identifies the device (e.g., virtual
server) using this port.</td>
</tr>
<tr>
<td>device_owner </td>
<td>str </td>
<td>None </td>
<td>device_owner</td>
<td>str</td>
<td>None</td>
<td>Identifies the entity (e.g.: dhcp agent) using this port.</td>
</tr>
<tr>
<td>tenant_id </td>
<td>uuid-str </td>
<td>N/A </td>
<td>tenant_id</td>
<td>uuid-str</td>
<td>N/A</td>
<td>Owner of network. Only admin users can
specify a tenant_id other than its own.
</td>
@ -383,7 +383,7 @@
<section xml:id="using_nova_with_neutron">
<title>Using OpenStack Compute with OpenStack Networking</title>
<section xml:id="basic_workflow_with_nova">
<title>Basic Workflow </title>
<title>Basic Workflow</title>
<para>Check available networks:</para>
<screen><prompt>$</prompt> <userinput>neutron net-list</userinput></screen>
<para>Boot the VM with a single NIC on the selected network (net1):</para>

2
doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml
View File

@ -1331,7 +1331,7 @@ can be overridden in any of the other sections.</para>
<td></td>
<td>Entry point for paste.deploy to use for auth, set to:
<code>egg:swauth#swauth</code> to use the swauth downloaded from
https://github.com/gholt/swauth </td>
https://github.com/gholt/swauth</td>
</tr>
<tr>
<td>log_name</td>

2
doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml
View File

@ -531,7 +531,7 @@ net.ipv4.netfilter.ip_conntrack_max = 262144
<para>Another helpful tuning parameter on slower systems
that helps to ensure enough time is allowed for
service restarts is the <literal>-k N</literal> (or
<literal>--kill-wait N </literal>) parameter of
<literal>--kill-wait N</literal>) parameter of
<command>swift-init</command>. This allows you to
change the default (15 second) time (N, in seconds)
that swift waits for processes to die and notably you

2
doc/src/docbkx/openstack-security/ch013_node-bootstrapping.xml
View File

@ -104,7 +104,7 @@
<para>At this point we know that the node has booted with the correct kernel and underlying components. There are many paths for hardening a given operating system deployment. The specifics on these steps are outside of the scope of this book.  We recommend following the guidance from a hardening guide specific to your operating system.  For example, the security technical implementation guides (STIG, http://iase.disa.mil/stigs/) and the NSA guides (http://www.nsa.gov/ia/mitigation_guidance/security_configuration_guides/) are useful starting places.</para>
<para>The nature of the nodes makes additional hardening possible. We recommend the following additional steps for production nodes:</para>
<itemizedlist><listitem>
<para>Use a read-only file system where possible.  Ensure that writeable file systems do not permit execution.  This can be handled through the mount options provided in <literal> /etc/fstab </literal>.</para>
<para>Use a read-only file system where possible. Ensure that writeable file systems do not permit execution.  This can be handled through the mount options provided in <literal>/etc/fstab</literal>.</para>
</listitem>
<listitem>
<para>Use a mandatory access control policy to contain the instances, the node services, and any other critical processes and data on the node.  See the discussions on sVirt / SELinux and AppArmor below.</para>

4
doc/src/docbkx/openstack-security/ch052_devices.xml
View File

@ -46,12 +46,12 @@ glance image-update \
    --property hw_cdrom_bus=ide \
    --property hw_vif_model=e1000 \
    f16-x86_64-openstack-sda</screen>
<para>A cloud architect should decide what devices to make available to cloud users. Anything that is not needed should be removed from QEMU. This step requires recompiling QEMU after modifying the options passed to the QEMU configure script. For a complete list of up-to-date options simply run <literal> ./configure --help </literal> from within the QEMU source directory. Decide what is needed for your deployment, and disable the remaining options.</para>
<para>A cloud architect should decide what devices to make available to cloud users. Anything that is not needed should be removed from QEMU. This step requires recompiling QEMU after modifying the options passed to the QEMU configure script. For a complete list of up-to-date options simply run <literal>./configure --help</literal> from within the QEMU source directory. Decide what is needed for your deployment, and disable the remaining options.</para>
</section>
<section xml:id="ch052_devices-idp494336">
<title>Compiler Hardening</title>
<para>The next step is to harden QEMU using compiler hardening options. Modern compilers provide a variety of compile time options to improve the security of the resulting binaries. These features, which we will describe in more detail below, include relocation read-only (RELRO), stack canaries, never execute (NX), position independent executable (PIE), and address space layout randomization (ASLR).</para>
<para>Many modern linux distributions already build QEMU with compiler hardening enabled, so you may want to verify your existing executable before proceeding with the information below. One tool that can assist you with this verification is called <literal> checksec.sh </literal> (http://www.trapkit.de/tools/checksec.html).</para>
<para>Many modern linux distributions already build QEMU with compiler hardening enabled, so you may want to verify your existing executable before proceeding with the information below. One tool that can assist you with this verification is called <literal>checksec.sh</literal> (http://www.trapkit.de/tools/checksec.html).</para>
<itemizedlist><listitem>
<para><emphasis>RELocation Read-Only (RELRO)</emphasis> : Hardens the data sections of an executable. Both full and partial RELRO modes are supported by gcc. For QEMU full RELRO is your best choice. This will make the global offset table read-only and place various internal data sections before the program data section in the resulting executable.</para>
</listitem>

16
doc/src/docbkx/openstack-training/bk002-ch003-operations-general.xml
View File

@ -28,7 +28,7 @@
<para>Add your GitHub username and password</para>
</step>
<step>
<para>Set your local </para>
<para>Set your local</para>
</step>
</procedure>
</step>
@ -175,7 +175,7 @@ $ git config --global user.email "your_email@youremail.com" </programlisting></p
<programlisting>$ git checkout -b bug/1188522 </programlisting></para>
</step>
<step>
<para>Verify that you have the branch open through SourceTree </para>
<para>Verify that you have the branch open through SourceTree</para>
</step>
<step>
<para>Correct the bug through Oxygen. Toggle back and forth through the different views at
@ -200,22 +200,22 @@ $ git config --global user.email "your_email@youremail.com" </programlisting></p
<para>Track the Gerrit review process at<link
xlink:href="https://review.openstack.org/#/c/33713"
>https://review.openstack.org/#/c/33713</link> Follow and respond inline to the Code
Review requests and comments </para>
Review requests and comments</para>
</step>
<step>
<para>Your change will be tested, track the Jenkins testing process at
https://jenkins.openstack.org </para>
https://jenkins.openstack.org</para>
</step>
<step>
<para>If your change is rejected.<procedure>
<step>
<para>Respond to the inline comments if any </para>
<para>Respond to the inline comments if any</para>
</step>
<step>
<para>Update the status to work in progress </para>
<para>Update the status to work in progress</para>
</step>
<step>
<para>Follow the recommended tweaks to the files </para>
<para>Follow the recommended tweaks to the files</para>
</step>
<step>
<para>Rerun <programlisting>$ mvn clean generate-sources</programlisting></para>
@ -230,7 +230,7 @@ $ git config --global user.email "your_email@youremail.com" </programlisting></p
<para>Final commit <programlisting>$ git review -v</programlisting></para>
</step>
<step>
<para>Update the Jenkins status to change completed </para>
<para>Update the Jenkins status to change completed</para>
</step>
</procedure></para>
</step>

76
doc/src/docbkx/openstack-training/bk002-ch008-operations-assessment.xml
View File

@ -23,146 +23,146 @@
<orderedlist>
<listitem>
<para>As a trainee I must configure a virtual environment to accomplish the
configuration tasks </para>
configuration tasks</para>
</listitem>
<listitem>
<para>As a trainee I must understand the basic overview of OpenStack core projects </para>
<para>As a trainee I must understand the basic overview of OpenStack core projects</para>
</listitem>
<listitem>
<para>As a trainee I must understand the architecture the RefStack architecture described
in the Basic Install Guide </para>
in the Basic Install Guide</para>
</listitem>
<listitem>
<para>As a trainee I must understand how to install Ubuntu 12.04 (or 13.04 in later
versions) </para>
versions)</para>
</listitem>
<listitem>
<para>As a trainee I must understand the role of the Controller Node in The RefStack
architecture described in the basic install guide </para>
architecture described in the basic install guide</para>
</listitem>
<listitem>
<para>As a trainee I must understand the role of MySql server in the Controller Node </para>
<para>As a trainee I must understand the role of MySql server in the Controller Node</para>
</listitem>
<listitem>
<para>As a trainee I must install MySql server in the Controller Node </para>
<para>As a trainee I must install MySql server in the Controller Node</para>
</listitem>
<listitem>
<para>As a trainee I must understand the role of RabbitMQ Messaging Service in the
Controller Node </para>
Controller Node</para>
</listitem>
<listitem>
<para>As a trainee I must install and configure RabbitMQ Messaging Service in the
Controller Node </para>
Controller Node</para>
</listitem>
<listitem>
<para>As a trainee I must understand the role of OpenStack Identity Service in the
Controller Node </para>
Controller Node</para>
</listitem>
<listitem>
<para>As a trainee I must Install and Configure OpenStack Identity Service in the
Controller Node </para>
Controller Node</para>
</listitem>
<listitem>
<para>As a trainee I must understand the role of OpenStack Image Service in the Controller
Node </para>
Node</para>
</listitem>
<listitem>
<para>As a trainee I must Install and configure OpenStack Identity Service in the
Controller Node </para>
Controller Node</para>
</listitem>
<listitem>
<para>As a trainee I must understand the role of OpenStack Compute (Cloud Controller
Services) in the Controller Node </para>
Services) in the Controller Node</para>
</listitem>
<listitem>
<para>As a trainee I must install and configure OpenStack Compute (Cloud Controller
Services) in the Controller Node </para>
Services) in the Controller Node</para>
</listitem>
<listitem>
<para>As a trainee I must understand the role of OpenStack Block Storage Service in the
Controller Node </para>
Controller Node</para>
</listitem>
<listitem>
<para>As a trainee I must install and configure OpenStack Block Storage Service in the
Controller Node </para>
Controller Node</para>
</listitem>
<listitem>
<para>As a trainee I must understand the role of OpenStack Network Service (cloud
controller) in the Controller Node </para>
controller) in the Controller Node</para>
</listitem>
<listitem>
<para>As a trainee I must install and configure OpenStack Network Service (cloud
controller) in the Controller Node </para>
controller) in the Controller Node</para>
</listitem>
<listitem>
<para>As trainee I must verify the proper configuration and operation of the Controller
node within the RefStack architecture described in the Basic Install Guide </para>
node within the RefStack architecture described in the Basic Install Guide</para>
</listitem>
<listitem>
<para>As a trainee I must understand the role of Network Node within the RefStack
architecture described in the Basic Install Guide </para>
architecture described in the Basic Install Guide</para>
</listitem>
<listitem>
<para>As a trainee I must understand the role of Open vSwitch in the Network Node </para>
<para>As a trainee I must understand the role of Open vSwitch in the Network Node</para>
</listitem>
<listitem>
<para>As a trainee I must install and configure Open vSwitch in the Network Node </para>
<para>As a trainee I must install and configure Open vSwitch in the Network Node</para>
</listitem>
<listitem>
<para>As a trainee I must understand the role of Neutron (formerly Quantum) in the Network
Node </para>
Node</para>
</listitem>
<listitem>
<para>As a trainee I must install and configure Neutron (formerly Quantum) in the Network
Node </para>
Node</para>
</listitem>
<listitem>
<para>As a trainee I must understand the how to create virtual networking in the Network
Node </para>
Node</para>
</listitem>
<listitem>
<para>As a trainee I must configure virtual networking in the Network Node </para>
<para>As a trainee I must configure virtual networking in the Network Node</para>
</listitem>
<listitem>
<para>As a trainee I must understand L3 Configuration in the Network Node </para>
<para>As a trainee I must understand L3 Configuration in the Network Node</para>
</listitem>
<listitem>
<para>As a trainee I must configure L3 Configuration in the Network Node </para>
<para>As a trainee I must configure L3 Configuration in the Network Node</para>
</listitem>
<listitem>
<para>As a trainee I must verify the proper configuration and operation of the Network
Node within the Reference Architecture described in the basic install guide </para>
Node within the Reference Architecture described in the basic install guide</para>
</listitem>
<listitem>
<para>As a trainee I must understand the role of Compute Node within the RefStack
architecture described in the Basic Install Guide </para>
architecture described in the Basic Install Guide</para>
</listitem>
<listitem>
<para>As a trainee I must understand Nova (compute node services) in the Compute Node </para>
<para>As a trainee I must understand Nova (compute node services) in the Compute Node</para>
</listitem>
<listitem>
<para>As a trainee I must install and configure Nova (compute node services) in the
Compute Node </para>
Compute Node</para>
</listitem>
<listitem>
<para>As a trainee I must understand OpenStack Networking using Open vSwitch in the
Compute Node </para>
Compute Node</para>
</listitem>
<listitem>
<para>As a trainee I must install and configure OpenStack Networking using Open vSwitch in
the Compute Node </para>
the Compute Node</para>
</listitem>
<listitem>
<para>As a trainee I must understand OpenStack Networking using Neutron (formerly Quantum)
in the Compute Node </para>
in the Compute Node</para>
</listitem>
<listitem>
<para>As a trainee I must install and configure OpenStack Networking using Open Neutron
(formerly Quantum) n the Compute Node </para>
(formerly Quantum) n the Compute Node</para>
</listitem>
<listitem>
<para>As a trainee I must understand instantiation of a Virtual Machine (Instance) using
OpenStack Dashboard (Horizon) </para>
OpenStack Dashboard (Horizon)</para>
</listitem>
<listitem>
<para>As a trainee I must instantiate of a Virtual Machine (Instance) using OpenStack

18
doc/src/docbkx/openstack-user/src/ch_cli.xml
View File

@ -11,23 +11,23 @@
</info>
<xi:include href="section_cli_overview.xml"/>
<xi:include href="section_cli_install.xml"/>
<xi:include href="section_cli_version.xml"/>
<xi:include href="section_cli_openrc.xml"/>
<xi:include href="../../common/section_glance_cli_manage_images.xml"/>
<xi:include href="section_cli_configure_instances.xml"/>
<xi:include href="../../common/section_nova_cli_boot.xml"/>
<xi:include href="section_cli_manage_instances.xml"/>
<xi:include href="../../common/section_neutron_cli_manage_networks.xml"/>
<xi:include href="section_cli_heat.xml"/>
<xi:include href="section_cli_manage_volumes.xml"/>

2
doc/src/docbkx/openstack-user/src/section_cli_install.xml
View File

@ -52,7 +52,7 @@
<tr>
<td valign="top">
<para><command>setuptools</command>
package </para>
package</para>
</td>
<td>
<para>Installed by default on Mac OS