From 588d397e8f7807ae49fe6047feacdf46fc654580 Mon Sep 17 00:00:00 2001 From: Christian Berendt Date: Wed, 7 Aug 2013 08:58:27 +0200 Subject: [PATCH] cleaning up whitespaces 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 --- doc/src/docbkx/common/ch_getstart.xml | 2 +- doc/src/docbkx/common/ch_support-compute.xml | 16 +- doc/src/docbkx/common/ch_support.xml | 6 +- .../docbkx/common/glossary/glossary-terms.xml | 2 +- .../section_compute-configure-console.xml | 2 +- .../docbkx/common/section_fibrechannel.xml | 2 +- .../section_glance_cli_manage_images.xml | 2 +- .../common/section_keystone-concepts.xml | 4 +- .../section_keystone_certificates-for-pki.xml | 16 +- doc/src/docbkx/common/section_kvm.xml | 2 +- doc/src/docbkx/common/section_moosefs.xml | 2 +- .../common/section_storage-concepts.xml | 2 +- .../common/section_using-vnc-console.xml | 2 +- doc/src/docbkx/common/section_xen-install.xml | 2 +- .../common/tables/ldap-keystone-conf.xml | 6 +- .../openstack-admin-user/src/ch_cli.xml | 2 +- .../src/section_cli_manage_images.xml | 2 +- .../src/section_dashboard_prereqs.xml | 4 +- .../backup-block-storage-disks.xml | 6 +- .../drivers/hds-volume-driver.xml | 8 +- .../drivers/huawei-storage-driver.xml | 2 +- .../drivers/ibm-storwize-svc-driver.xml | 4 +- .../drivers/netapp-volume-driver.xml | 6 +- .../drivers/xen-sm-driver.xml | 2 +- .../openstack-compute-admin/adding-images.xml | 36 +-- .../ch_identity_mgmt.xml | 156 +++++------ .../openstack-compute-admin/ch_image_mgmt.xml | 4 +- .../ch_instance_mgmt.xml | 2 +- .../computeautomation.xml | 2 +- .../computenetworking.xml | 130 +++++---- .../computescheduler.xml | 22 +- .../computetutorials.xml | 2 +- .../moosefsbackend.xml | 2 +- .../openstack-config/ch_computeconfigure.xml | 4 +- .../openstack-config/ch_computescheduler.xml | 22 +- .../openstack-config/ch_identityconfigure.xml | 2 +- .../compute-configure-migrations.xml | 2 +- .../docbkx/openstack-image/ch_converting.xml | 2 +- .../openstack-image/ch_modifying_images.xml | 2 +- .../openstack-install/ap_installingfolsom.xml | 4 +- .../openstack-install/ch_installidentity.xml | 2 +- .../ch_installobjectstorage.xml | 2 +- .../openstack-install/ch_terminology.xml | 2 +- .../openstack-install/compute-db-sync.xml | 2 +- .../compute-sys-requirements.xml | 4 +- .../install-config-glance.xml | 2 +- .../object-storage-install-ubuntu.xml | 2 +- .../object-storage-verifying-install.xml | 2 +- .../start-storage-node-services.xml | 2 +- .../app_core.xml | 264 +++++++++--------- .../app_pagination_and_sorting_support.xml | 18 +- .../ch_adv_config.xml | 24 +- .../ch_adv_features.xml | 190 ++++++------- .../ch_config.xml | 11 +- .../ch_install.xml | 12 +- .../ch_limitations.xml | 4 +- .../ch_overview.xml | 16 +- .../ch_using.xml | 200 ++++++------- .../objectstorage-config-reference.xml | 2 +- .../objectstorageadmin.xml | 2 +- .../ch013_node-bootstrapping.xml | 2 +- .../openstack-security/ch052_devices.xml | 4 +- .../bk002-ch003-operations-general.xml | 16 +- .../bk002-ch008-operations-assessment.xml | 76 ++--- doc/src/docbkx/openstack-user/src/ch_cli.xml | 18 +- .../src/section_cli_install.xml | 2 +- 66 files changed, 689 insertions(+), 690 deletions(-) diff --git a/doc/src/docbkx/common/ch_getstart.xml b/doc/src/docbkx/common/ch_getstart.xml index ce4d548489..25589ac26e 100644 --- a/doc/src/docbkx/common/ch_getstart.xml +++ b/doc/src/docbkx/common/ch_getstart.xml @@ -461,7 +461,7 @@ installations that need to support euca2ools. The euca2ools tools talk to nova-objectore in “S3 language” and nova-objectstore translates S3 requests into glance - requests + requests. The euca2ools client is not an diff --git a/doc/src/docbkx/common/ch_support-compute.xml b/doc/src/docbkx/common/ch_support-compute.xml index 74a9a24b6c..c1f4a859cd 100644 --- a/doc/src/docbkx/common/ch_support-compute.xml +++ b/doc/src/docbkx/common/ch_support-compute.xml @@ -4,13 +4,15 @@ xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="troubleshooting-openstack-compute"> Troubleshooting OpenStack Compute 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. -
Log files for OpenStack ComputeLog 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 +
Log files for OpenStack ComputeLog 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. 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.
diff --git a/doc/src/docbkx/common/ch_support.xml b/doc/src/docbkx/common/ch_support.xml index 4f0323161a..a878040be3 100644 --- a/doc/src/docbkx/common/ch_support.xml +++ b/doc/src/docbkx/common/ch_support.xml @@ -40,7 +40,7 @@ additional mailing lists is available at http://wiki.openstack.org/MailingLists. - The OpenStack Wiki search + The OpenStack Wiki search The OpenStack wiki 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. - The Launchpad Bugs area + The Launchpad Bugs area 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 @@ - The OpenStack IRC channel + The OpenStack IRC channel 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 diff --git a/doc/src/docbkx/common/glossary/glossary-terms.xml b/doc/src/docbkx/common/glossary/glossary-terms.xml index 789035bebf..a691a6d9c4 100644 --- a/doc/src/docbkx/common/glossary/glossary-terms.xml +++ b/doc/src/docbkx/common/glossary/glossary-terms.xml @@ -8,7 +8,7 @@ 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 + the License at - SPICE support in OpenStack Compute shares a similar + 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 nova-spicehtml5proxy service using diff --git a/doc/src/docbkx/common/section_fibrechannel.xml b/doc/src/docbkx/common/section_fibrechannel.xml index fe8b86c4c2..1813dd3b97 100644 --- a/doc/src/docbkx/common/section_fibrechannel.xml +++ b/doc/src/docbkx/common/section_fibrechannel.xml @@ -20,7 +20,7 @@
- Requirements for KVM Hosts + Requirements for KVM Hosts The KVM host must have the following system packages installed: diff --git a/doc/src/docbkx/common/section_glance_cli_manage_images.xml b/doc/src/docbkx/common/section_glance_cli_manage_images.xml index 76b03e520c..b32a206408 100644 --- a/doc/src/docbkx/common/section_glance_cli_manage_images.xml +++ b/doc/src/docbkx/common/section_glance_cli_manage_images.xml @@ -20,7 +20,7 @@ >Virtual Machine Image Guide.
- Manage images with the glance client + Manage images with the glance client To list images diff --git a/doc/src/docbkx/common/section_keystone-concepts.xml b/doc/src/docbkx/common/section_keystone-concepts.xml index f60347adf4..b265808276 100644 --- a/doc/src/docbkx/common/section_keystone-concepts.xml +++ b/doc/src/docbkx/common/section_keystone-concepts.xml @@ -39,10 +39,10 @@ are: - Username and password + Username and password - Username and API key + Username and API key An authentication token provided by the diff --git a/doc/src/docbkx/common/section_keystone_certificates-for-pki.xml b/doc/src/docbkx/common/section_keystone_certificates-for-pki.xml index e5cced18ea..135af087c2 100644 --- a/doc/src/docbkx/common/section_keystone_certificates-for-pki.xml +++ b/doc/src/docbkx/common/section_keystone_certificates-for-pki.xml @@ -113,11 +113,11 @@ SrWY8lF3HrTcJT23sZIleg== all certificate and key files must be in - Privacy Enhanced Mail (PEM) format + Privacy Enhanced Mail (PEM) format private key files must not be protected by a - password + password When using signing certificate issued by an external @@ -135,10 +135,10 @@ SrWY8lF3HrTcJT23sZIleg== Convert certificate and private key to PEM if - needed + needed - Install External Signing Certificate + Install External Signing Certificate
@@ -191,21 +191,21 @@ openssl req -newkey rsa:1024 -keyout signing_key.pem -keyform PEM -out signing_c signing_cert.pem - (Keystone - token) signing certificate in PEM format + token) signing certificate in PEM format signing_key.pem - corresponding - (non-encrypted) private key in PEM format + (non-encrypted) private key in PEM format cacert.pem - trust CA - certificate chain in PEM format + certificate chain in PEM format Copy the above to your certificate directory. For - example: + example: mkdir -p /etc/keystone/ssl/certs cp signing_cert.pem /etc/keystone/ssl/certs/ diff --git a/doc/src/docbkx/common/section_kvm.xml b/doc/src/docbkx/common/section_kvm.xml index 43d677f5d1..0ebdebcd27 100644 --- a/doc/src/docbkx/common/section_kvm.xml +++ b/doc/src/docbkx/common/section_kvm.xml @@ -112,7 +112,7 @@ KVM acceleration can NOT be used
Enabling KVM - KVM requires the kvm and either kvm-intel or + KVM requires the kvm and either kvm-intel or kvm-amd modules to be loaded. This may have been configured automatically on your distribution when KVM is installed. You can check that they have been loaded using lsmod, as follows, diff --git a/doc/src/docbkx/common/section_moosefs.xml b/doc/src/docbkx/common/section_moosefs.xml index 1c8ff5c5e2..2523585d84 100644 --- a/doc/src/docbkx/common/section_moosefs.xml +++ b/doc/src/docbkx/common/section_moosefs.xml @@ -77,7 +77,7 @@
- Installing the MooseFS metadata and metalogger servers + Installing the MooseFS metadata and metalogger servers Both components could be run anywhere , as long as the MooseFS chunkservers can reach the MooseFS master server. In our deployment, both MooseFS master and slave run their services inside a virtual diff --git a/doc/src/docbkx/common/section_storage-concepts.xml b/doc/src/docbkx/common/section_storage-concepts.xml index 561376a364..ad55c7aaa1 100644 --- a/doc/src/docbkx/common/section_storage-concepts.xml +++ b/doc/src/docbkx/common/section_storage-concepts.xml @@ -13,7 +13,7 @@ - On-instance / ephemeral + On-instance / ephemeral Volumes block storage (Cinder) Object Storage (Swift) diff --git a/doc/src/docbkx/common/section_using-vnc-console.xml b/doc/src/docbkx/common/section_using-vnc-console.xml index 65ec7e5334..c588bb4d8f 100644 --- a/doc/src/docbkx/common/section_using-vnc-console.xml +++ b/doc/src/docbkx/common/section_using-vnc-console.xml @@ -6,7 +6,7 @@ Using VNC Console 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 . diff --git a/doc/src/docbkx/common/section_xen-install.xml b/doc/src/docbkx/common/section_xen-install.xml index 8cd28db0ff..ad0a927eaf 100644 --- a/doc/src/docbkx/common/section_xen-install.xml +++ b/doc/src/docbkx/common/section_xen-install.xml @@ -65,7 +65,7 @@ selected by choosing "XenDesktop Optimized" option. In case you are using an answer file, make sure you use srtype="ext" within the - installation tag of the answer + installation tag of the answer file.
diff --git a/doc/src/docbkx/common/tables/ldap-keystone-conf.xml b/doc/src/docbkx/common/tables/ldap-keystone-conf.xml index ff81815ddc..3867116f7a 100644 --- a/doc/src/docbkx/common/tables/ldap-keystone-conf.xml +++ b/doc/src/docbkx/common/tables/ldap-keystone-conf.xml @@ -18,16 +18,16 @@ - user = dc=Manager,dc=example,dc=com + user = dc=Manager,dc=example,dc=com (StrOpt) User for the LDAP server to use as default. - password = None + password = None (StrOpt) Password for LDAP server to connect to. - suffix = cn=example,cn=com + suffix = cn=example,cn=com (StrOpt) Default suffix for your LDAP server. use_dumb_member = False diff --git a/doc/src/docbkx/openstack-admin-user/src/ch_cli.xml b/doc/src/docbkx/openstack-admin-user/src/ch_cli.xml index cca85f693f..fd6675d653 100644 --- a/doc/src/docbkx/openstack-admin-user/src/ch_cli.xml +++ b/doc/src/docbkx/openstack-admin-user/src/ch_cli.xml @@ -9,7 +9,7 @@ OpenStack command-line clients - + diff --git a/doc/src/docbkx/openstack-admin-user/src/section_cli_manage_images.xml b/doc/src/docbkx/openstack-admin-user/src/section_cli_manage_images.xml index 668389a7f8..8505c75a51 100644 --- a/doc/src/docbkx/openstack-admin-user/src/section_cli_manage_images.xml +++ b/doc/src/docbkx/openstack-admin-user/src/section_cli_manage_images.xml @@ -20,7 +20,7 @@ >Virtual Machine Image Guide.
- Manage images with the glance client + Manage images with the glance client To list images diff --git a/doc/src/docbkx/openstack-admin-user/src/section_dashboard_prereqs.xml b/doc/src/docbkx/openstack-admin-user/src/section_dashboard_prereqs.xml index ae20d2f622..e9106b6ef4 100644 --- a/doc/src/docbkx/openstack-admin-user/src/section_dashboard_prereqs.xml +++ b/doc/src/docbkx/openstack-admin-user/src/section_dashboard_prereqs.xml @@ -1,9 +1,9 @@ - - + ]>
tar creates a - minimum-sized backup + minimum-sized backup sha1sum calculates the - backup checksum, to check its consistency + backup checksum, to check its consistency @@ -191,7 +191,7 @@ You didn't allocate enough - space for the snapshot + space for the snapshot diff --git a/doc/src/docbkx/openstack-block-storage-admin/drivers/hds-volume-driver.xml b/doc/src/docbkx/openstack-block-storage-admin/drivers/hds-volume-driver.xml index 0aa2a82fcd..42ca720a0c 100644 --- a/doc/src/docbkx/openstack-block-storage-admin/drivers/hds-volume-driver.xml +++ b/doc/src/docbkx/openstack-block-storage-admin/drivers/hds-volume-driver.xml @@ -52,7 +52,7 @@ HDS driver supports the concept of differentiated services, Not to be confused with - Cinder volume service where where volume type 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 @@ hds_cinder_config_file option is used to point to an unique configuration file for each block. Set volume_driver for each backend to - cinder.volume.drivers.hds.hds.HUSDriver + cinder.volume.drivers.hds.hds.HUSDriver enabled_backends=hus1,hus2 [hus1] @@ -222,7 +222,7 @@ - Type extra specs: volume_backend and volume type + Type extra specs: volume_backend and volume type If volume type are used, they should be configured in the configuration file as @@ -238,7 +238,7 @@ - Non differentiated deployment of HUS arrays + Non differentiated deployment of HUS arrays Multiple cinder instances, each controlling a separate HUS array and with no volume type being associated with any of diff --git a/doc/src/docbkx/openstack-block-storage-admin/drivers/huawei-storage-driver.xml b/doc/src/docbkx/openstack-block-storage-admin/drivers/huawei-storage-driver.xml index b172793cb9..4e5c1ca451 100644 --- a/doc/src/docbkx/openstack-block-storage-admin/drivers/huawei-storage-driver.xml +++ b/doc/src/docbkx/openstack-block-storage-admin/drivers/huawei-storage-driver.xml @@ -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"> - Huawei Storage Driver + Huawei Storage Driver Huawei storage drivers integrate OceanStor T series unified storage with OceanStor Dorado high-performance storage to provide block storage services for OpenStack. diff --git a/doc/src/docbkx/openstack-block-storage-admin/drivers/ibm-storwize-svc-driver.xml b/doc/src/docbkx/openstack-block-storage-admin/drivers/ibm-storwize-svc-driver.xml index 04ef106bff..9dd952b6cc 100644 --- a/doc/src/docbkx/openstack-block-storage-admin/drivers/ibm-storwize-svc-driver.xml +++ b/doc/src/docbkx/openstack-block-storage-admin/drivers/ibm-storwize-svc-driver.xml @@ -9,7 +9,7 @@ instances with access to IBM Storwize family or SVC storage systems.
- Configuring the Storwize Family and SVC System + Configuring the Storwize Family and SVC System Network Configuration @@ -191,7 +191,7 @@ ssh-keygen -t rsa
- Configuring the Storwize Family and SVC Driver + Configuring the Storwize Family and SVC Driver Enabling the Storwize family and SVC driver diff --git a/doc/src/docbkx/openstack-block-storage-admin/drivers/netapp-volume-driver.xml b/doc/src/docbkx/openstack-block-storage-admin/drivers/netapp-volume-driver.xml index 687c9e96ca..ecaf2785b1 100644 --- a/doc/src/docbkx/openstack-block-storage-admin/drivers/netapp-volume-driver.xml +++ b/doc/src/docbkx/openstack-block-storage-admin/drivers/netapp-volume-driver.xml @@ -174,7 +174,7 @@ driver on OpenStack. Configuration options for the clustered - Data ONTAP driver + Data ONTAP driver Set the volume driver to the clustered Data ONTAP driver by setting the volume_driver @@ -409,7 +409,7 @@
- NetApp iSCSI direct driver for clustered Data ONTAP + NetApp iSCSI direct driver for clustered Data ONTAP 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 @@
- NetApp NFS driver for clustered Data ONTAP + NetApp NFS driver for clustered Data ONTAP The NetApp NFS driver for clustered Data ONTAP is a driver interface from OpenStack to clustered Data ONTAP systems for provisioning and managing OpenStack diff --git a/doc/src/docbkx/openstack-block-storage-admin/drivers/xen-sm-driver.xml b/doc/src/docbkx/openstack-block-storage-admin/drivers/xen-sm-driver.xml index 6df4bfbf46..07008c6423 100644 --- a/doc/src/docbkx/openstack-block-storage-admin/drivers/xen-sm-driver.xml +++ b/doc/src/docbkx/openstack-block-storage-admin/drivers/xen-sm-driver.xml @@ -193,7 +193,7 @@ Note: SR type and config connection parameters are in keeping with the XenAPI Co - Creating and Accessing the volumes from VMs + Creating and Accessing the volumes from VMs 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 diff --git a/doc/src/docbkx/openstack-compute-admin/adding-images.xml b/doc/src/docbkx/openstack-compute-admin/adding-images.xml index 7bbea9d936..c9cca4226e 100644 --- a/doc/src/docbkx/openstack-compute-admin/adding-images.xml +++ b/doc/src/docbkx/openstack-compute-admin/adding-images.xml @@ -387,7 +387,7 @@ arch - This is: Arch Linux + This is: Arch Linux Do not use: archlinux, or org.archlinux @@ -398,7 +398,7 @@ centos This is: Community Enterprise - Operating System + Operating System Do not use: org.centos CentOS @@ -408,7 +408,7 @@ debian - This is: Debian + This is: Debian Do not use: Debian, or org.debian @@ -418,7 +418,7 @@ fedora - This is: Fedora + This is: Fedora Do not use: Fedora, org.fedora, or @@ -429,7 +429,7 @@ freebsd - This is: FreeBSD + This is: FreeBSD Do not use: org.freebsd, freeBSD, or @@ -440,7 +440,7 @@ gentoo - This is: Gentoo Linux + This is: Gentoo Linux Do not use: Gentoo, or org.gentoo @@ -450,7 +450,7 @@ mandrake - This is: Mandrakelinux (MandrakeSoft) + This is: Mandrakelinux (MandrakeSoft) Do not use: mandrakelinux, or MandrakeLinux @@ -460,7 +460,7 @@ mandriva - This is: Mandriva Linux + This is: Mandriva Linux Do not use: mandrivalinux @@ -469,7 +469,7 @@ mes - This is: Mandriva Enterprise Server + This is: Mandriva Enterprise Server Do not use: mandrivaent, or mandrivaES @@ -480,7 +480,7 @@ msdos This is: Microsoft Disc Operating - System + System Do not use: ms-dos @@ -488,7 +488,7 @@ netbsd - This is: NetBSD + This is: NetBSD Do not use: NetBSD, or org.netbsd @@ -498,7 +498,7 @@ netware - This is: Novell NetWare + This is: Novell NetWare Do not use: novell, or NetWare @@ -508,7 +508,7 @@ openbsd - This is: OpenBSD + This is: OpenBSD Do not use: OpenBSD, or org.openbsd @@ -527,7 +527,7 @@ opensuse - This is: openSUSE + This is: openSUSE Do not use: suse, SuSE, or org.opensuse @@ -537,7 +537,7 @@ rhel - This is: Red Hat Enterprise Linux + This is: Red Hat Enterprise Linux Do not use: redhat, RedHat, or @@ -549,7 +549,7 @@ sled This is: SUSE Linux Enterprise - Desktop + Desktop Do not use: com.suse @@ -558,7 +558,7 @@ ubuntu - This is: Ubuntu + This is: Ubuntu Do not use: Ubuntu, com.ubuntu, @@ -570,7 +570,7 @@ windows - This is: Microsoft Windows + This is: Microsoft Windows Do not use: com.microsoft.server, or windoze diff --git a/doc/src/docbkx/openstack-compute-admin/ch_identity_mgmt.xml b/doc/src/docbkx/openstack-compute-admin/ch_identity_mgmt.xml index 42404fac32..6df4bdc943 100644 --- a/doc/src/docbkx/openstack-compute-admin/ch_identity_mgmt.xml +++ b/doc/src/docbkx/openstack-compute-admin/ch_identity_mgmt.xml @@ -150,7 +150,7 @@ pipeline = [...] json_body stats_reporting ec2_extension [...] admin_service $ curl -H 'X-Auth-Token: ADMIN' -X DELETE http://localhost:35357/v2.0/OS-STATS/stats
- +
Running the Identity Service @@ -233,7 +233,7 @@ keystone-manage db_sync --password OS_PASSWORD. The administrator - password + password @@ -307,16 +307,16 @@ keystone --username=admin --password=secrete --tenant_name=admin tenant-create - it.
<literal>tenant-create</literal> - keyword arguments + keyword arguments - name + name - description (optional, defaults to None) + description (optional, defaults to None) - enabled (optional, defaults to True) + enabled (optional, defaults to True) The following command creates a tenant named @@ -325,39 +325,39 @@ keystone --username=admin --password=secrete --tenant_name=admin tenant-create -
<literal>tenant-delete</literal> - arguments + arguments - tenant_id + tenant_id - example: + example: keystone tenant-delete f2b7b39c860840dfa47d9ee4adffa0b3
<literal>tenant-enable</literal> - arguments + arguments - tenant_id + tenant_id - example: + example: keystone tenant-enable f2b7b39c860840dfa47d9ee4adffa0b3
<literal>tenant-disable</literal> - arguments + arguments - tenant_id + tenant_id - example: + example: keystone tenant-disable f2b7b39c860840dfa47d9ee4adffa0b3 @@ -367,25 +367,25 @@ keystone tenant-disable f2b7b39c860840dfa47d9ee4adffa0b3 Users
<literal>user-create</literal> - keyword arguments: + keyword arguments: - name + name - pass + pass - email + email - default_tenant (optional, defaults to None) + default_tenant (optional, defaults to None) - enabled (optional, defaults to True) + enabled (optional, defaults to True) - example: + example: keystone user-create --name=admin \ @@ -395,13 +395,13 @@ keystone user-create
<literal>user-delete</literal> - keyword arguments: + keyword arguments: - user + user - example: + example: keystone user-delete f2b7b39c860840dfa47d9ee4adffa0b3 @@ -409,74 +409,74 @@ keystone user-delete f2b7b39c860840dfa47d9ee4adffa0b3
<literal>user-list</literal> list users in the system, optionally by a specific tenant - (identified by tenant_id) - arguments + (identified by tenant_id) + arguments - tenant_id (optional, defaults to None) + tenant_id (optional, defaults to None) - example: + example: keystone user-list
<literal>user-update --email</literal> - arguments + arguments - user_id + user_id - email + email - example: + example: keystone user-update --email 03c84b51574841ba9a0d8db7882ac645 "someone@somewhere.com"
<literal>user-enable</literal> - arguments + arguments - user_id + user_id - example: + example: keystone user-enable 03c84b51574841ba9a0d8db7882ac645
<literal>user-disable</literal> - arguments + arguments - user_id + user_id - example: + example: keystone user-disable 03c84b51574841ba9a0d8db7882ac645
<literal>user-update --password</literal> - arguments + arguments - user_id + user_id - password + password - example: + example: keystone user-update --password 03c84b51574841ba9a0d8db7882ac645 foo @@ -486,65 +486,65 @@ keystone user-update --password 03c84b51574841ba9a0d8db7882ac645 foo Roles
<literal>role-create</literal> - arguments + arguments - name + name - example: + example: keystone role-create --name=demo
<literal>role-delete</literal> - arguments + arguments - role_id + role_id - example: + example: keystone role-delete 19d1d3344873464d819c45f521ff9890
<literal>role-list</literal> - example: + example: keystone role-list
<literal>role-get</literal> - arguments + arguments - role_id + role_id - example: + example: keystone role-get role=19d1d3344873464d819c45f521ff9890
<literal>add-user-role</literal> - arguments + arguments - role_id + role_id - user_id + user_id - tenant_id + tenant_id - example: + example: keystone add-user-role \ 3a751f78ef4c412b827540b829e2d7dd \ @@ -554,19 +554,19 @@ keystone add-user-role \
<literal>remove-user-role</literal> - arguments + arguments - role_id + role_id - user_id + user_id - tenant_id + tenant_id - example: + example: keystone remove-user-role \ 19d1d3344873464d819c45f521ff9890 \ @@ -579,19 +579,19 @@ keystone remove-user-role \ Services
<literal>service-create</literal> - keyword arguments + keyword arguments - name + name - type + type - description + description - example: + example: keystone service create \ --name=nova \ @@ -601,39 +601,39 @@ keystone service create \
<literal>service-list</literal> - arguments + arguments - service_id + service_id - example: + example: keystone service-list
<literal>service-get</literal> - arguments + arguments - service_id + service_id - example: + example: keystone service-get 08741d8ed88242ca88d1f61484a0fe3b
<literal>service-delete</literal> - arguments + arguments - service_id + service_id - example: + example: keystone service-delete 08741d8ed88242ca88d1f61484a0fe3b @@ -690,7 +690,7 @@ keystone service-delete 08741d8ed88242ca88d1f61484a0fe3b This is configured in keystone.conf file under the section [DEFAULT]. In the sample file provided with the keystone project, the line - defining this token is + defining this token is
[DEFAULT] admin_token = ADMIN diff --git a/doc/src/docbkx/openstack-compute-admin/ch_image_mgmt.xml b/doc/src/docbkx/openstack-compute-admin/ch_image_mgmt.xml index 9bed2fa568..84feefda25 100644 --- a/doc/src/docbkx/openstack-compute-admin/ch_image_mgmt.xml +++ b/doc/src/docbkx/openstack-compute-admin/ch_image_mgmt.xml @@ -265,7 +265,7 @@ within policy.json on the desired roles. By default, only the admin role has this setting enabled. You can view the list of valid compute hosts by using the nova - hypervisor-list command, for + hypervisor-list command, for example:$ nova hypervisor-list +----+---------------------+ | ID | Hypervisor hostname | @@ -291,7 +291,7 @@
- Replicating images across multiple data centers + Replicating images across multiple data centers The image service comes with a tool called glance-replicator that can be used to populate a new glance server using the images stored in diff --git a/doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml b/doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml index 55bf3ea87d..77c8cbb385 100644 --- a/doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml +++ b/doc/src/docbkx/openstack-compute-admin/ch_instance_mgmt.xml @@ -323,7 +323,7 @@ header: Date: Thu, 13 Sep 2012 20:27:36 GMT Flavors define a number of elements - ID: a unique numeric id + ID: a unique numeric id Name: a descriptive name. diff --git a/doc/src/docbkx/openstack-compute-admin/computeautomation.xml b/doc/src/docbkx/openstack-compute-admin/computeautomation.xml index 1556c91075..8bdb1000a0 100644 --- a/doc/src/docbkx/openstack-compute-admin/computeautomation.xml +++ b/doc/src/docbkx/openstack-compute-admin/computeautomation.xml @@ -269,7 +269,7 @@ format="SVG" scale="60"/> Notes - SSH login nova instance after test of nova + SSH login nova instance after test of nova An instance will be started during the test of nova. After the test, you can login the instance by executing the following commands. For openstack nova folsom, diff --git a/doc/src/docbkx/openstack-compute-admin/computenetworking.xml b/doc/src/docbkx/openstack-compute-admin/computenetworking.xml index 640e460abd..026a655657 100644 --- a/doc/src/docbkx/openstack-compute-admin/computenetworking.xml +++ b/doc/src/docbkx/openstack-compute-admin/computenetworking.xml @@ -607,7 +607,7 @@ iface br100 inet dhcp
Flat network, all-in-one server - installation + installation public_interface refers to the network interfce on the VM running the - OpenStack services. + OpenStack services. With VLAN networking and the XenAPI driver, the - following things happen when you start a VM: + following things happen when you start a VM: + - First the XenServer network is + First the XenServer network is attached to the appropriate physical interface (PIF) and VLAN unless the - network already exists. + network already exists. - When the VM is created, its VIF is - attached to the above network. + When the VM is created, its VIF is + attached to the above network. - The 'Openstack domU', i.e. where + 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 + are plugged. To help understand VLAN networking with the XenAPI further, here are some important things to - note: + note: + - A physical interface (PIF) + 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 + default the first tag is 100. - VIF for VM instances within this + 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. + until a VIF is plugged in it. - The 'Openstack domU', i.e. the VM + 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.Dom0IptablesFirewallDrivervlan_interface is eth0 it must be plugged in xenbr1, - eth1 --> xenbr1, etc. + eth1 --> xenbr1, etc. - Within the Openstack domU, 'ip + 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 + (nova IPAM or Melange). @@ -1277,7 +1279,7 @@ firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver + gateway. 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 + real bridges with ovs-vsctl. 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.Dom0IptablesFirewallDrivernova-compute controlled - instances. + instances.
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 - - Cloudpipe is a method for connecting end users to - their project instances in VLAN networking mode. - The support code for cloudpipe implements admin + Cloudpipe is a method for connecting end users to + their project instances in VLAN networking mode. + 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 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. - The cloudpipe image is basically just a Linux - + internet. + 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. + nova. 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 Installing the required packages - We start by installing the required + We start by installing the required packages on our instance: # apt-get update && apt-get upgrade && apt-get install openvpn bridge-utils unzip -y - Creating the server configuration + Creating the server configuration template - Create a configuration for Openvpn, and + Create a configuration for Openvpn, and save it under /etc/openvpn/server.conf - : + : port 1194 @@ -1463,7 +1462,7 @@ mute 20 Create the network scripts - The next step is to create both scripts + 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 Edit the network interface configuration file - Update the + Update the /etc/network/interfaces accordingly (We tear down the main interface and enable the bridged @@ -1526,7 +1525,7 @@ bridge_ports eth0 Edit the rc.local file - The next step consists in updating the + The next step consists in updating the /etc/rc.local file. We will ask our image to retrieve the payload, decrypt it, and use both key @@ -1586,11 +1585,11 @@ exit 0
Upload your instance to Glance - We will make use of the We will make use of the nova snapshot feature in order to create an image from our running instance. We start by retrieving the - instance ID: + instance ID: $ nova list @@ -1603,7 +1602,7 @@ exit 0 +--------------------------------------+------------+--------+---------------------+ - We create an image with, using the instance ID + We create an image with, using the instance ID : $ nova image-create 739079a-b-0f8e-404a-ae6e-a91f4fe99c94 @@ -1641,7 +1640,7 @@ cnt_vpn_clients=5
Power-up your instance - Use the nova + Use the nova cloudpipe 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. - The user data for cloudpipe isn't currently - + connecting to the vpn. + 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. @@ -1766,9 +1764,9 @@ ALLOW -1:-1 from 0.0.0.0/0
- Remote access to your cloudpipe instance from + <title>Remote access to your cloudpipe instance from an OpenVPN client - Now your cloudpipe instance is running, you can + 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 Generate your certificates - Start by generating a private key and a + Start by generating a private key and a certificate for your project: $ nova x509-create-cert @@ -1792,7 +1790,7 @@ ALLOW -1:-1 from 0.0.0.0/0 Create the openvpn configuration file - The following template, which can be + The following template, which can be found under nova/cloudpipe/client.ovpn.template contains the necessary instructions for @@ -1826,7 +1824,7 @@ ping-timer-rem persist-tun persist-key - Update the file accordingly. In order + 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 - Start your OpenVPN client - Depending on the client you are using, + Start your OpenVPN client + 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 instance using an interface - Download an OpenVPN client - In order to connect to the + Download an OpenVPN client + In order to connect to the project's network, you will need an OpenVPN client for your computer. Here are several clients - For Ubuntu: + For Ubuntu: OpenVPN @@ -1879,7 +1877,7 @@ persist-key >gopenvpn - For Mac OsX: + For Mac OsX: - For Windows: + For Windows: - Configure your client - In this example we will use + Configure your client + 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 - Certificate: The generated + Certificate: The generated certificate - Key: The private key + Key: The private key @@ -2002,7 +2000,7 @@ persist-key Troubleshoot your cloudpipe instance - A periodic task disassociates the fixed + A periodic task disassociates the fixed ip address for the cloudpipe instance. Into /var/log/nova/nova-network.log, @@ -2057,7 +2055,7 @@ persist-key Automate the cloudpipe image installation - You can automate the image creation by + You can automate the image creation by download that script and running it from inside the instance: - you can check if the forwarding is enabled by + you can check if the forwarding is enabled by running the following command: $ cat /proc/sys/net/ipv4/ip_forward 0 Or using sysctl$ sysctl net.ipv4.ip_forward @@ -2317,7 +2315,7 @@ auto_assign_floating_ip=True
Using the multinic feature - In order to use the multinic feature, first create + In order to use the multinic feature, first create two networks, and attach them to your project: $ nova network-create first-net --fixed-range-v4=20.20.0.0/24 --project-id=$your-project $ nova network-create second-net --fixed-range-v4=20.20.10.0/24 --project-id=$your-project @@ -2419,7 +2417,7 @@ iface eth1 inet dhcp 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 nova-api service + The nova-api service is needed so that it can act as a metadata server for the instances. To run in HA mode, each compute host must run the diff --git a/doc/src/docbkx/openstack-compute-admin/computescheduler.xml b/doc/src/docbkx/openstack-compute-admin/computescheduler.xml index f121d27688..a4fa869c0a 100644 --- a/doc/src/docbkx/openstack-compute-admin/computescheduler.xml +++ b/doc/src/docbkx/openstack-compute-admin/computescheduler.xml @@ -137,7 +137,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
- AggregateRamFilter + AggregateRamFilter Implements blueprint per-aggregate-resource-ratio. Supports per-aggregate @@ -153,7 +153,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
- AvailabilityZoneFilter + AvailabilityZoneFilter 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
- ComputeFilter + ComputeFilter - Passes all hosts that are operational and + Passes all hosts that are operational and enabled. In general, this filter should always be enabled. @@ -189,7 +189,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
- CoreFilter + CoreFilter 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). This filter can be configured to allow a fixed amount of vCPU overcommitment by using the - cpu_allocation_ratio + cpu_allocation_ratio Configuration option in nova.conf. The default setting is: @@ -251,7 +251,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter sufficient disk space available for root and ephemeral storage. This filter can be configured to allow a fixed amount of disk overcommitment by using the - disk_allocation_ratio + disk_allocation_ratio Configuration option in nova.conf. The default setting is: @@ -291,7 +291,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter these properties using glance image-update img-uuid --property architecture=arm --property hypervisor_type=qemu - The image properties that the filter checks for + The image properties that the filter checks for are: @@ -318,7 +318,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
- IsolatedHostsFilter + IsolatedHostsFilter 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 - The default is to spread instances across all hosts + The default is to spread instances across all hosts evenly. Set the ram_weight_multiplier option to a negative number if you prefer stacking instead - of spreading. + of spreading.
diff --git a/doc/src/docbkx/openstack-compute-admin/computetutorials.xml b/doc/src/docbkx/openstack-compute-admin/computetutorials.xml index 295c5f9885..2a1a60d56a 100644 --- a/doc/src/docbkx/openstack-compute-admin/computetutorials.xml +++ b/doc/src/docbkx/openstack-compute-admin/computetutorials.xml @@ -69,7 +69,7 @@ export NOVA_VERSION=1.1 II!
- Part II: Starting Virtual Machines + Part II: Starting Virtual Machines Understanding what you can do with cloud computing means you should have a grasp on the concept of virtualization. With virtualization, you can run diff --git a/doc/src/docbkx/openstack-compute-admin/moosefsbackend.xml b/doc/src/docbkx/openstack-compute-admin/moosefsbackend.xml index a8310a679f..7e5da89036 100644 --- a/doc/src/docbkx/openstack-compute-admin/moosefsbackend.xml +++ b/doc/src/docbkx/openstack-compute-admin/moosefsbackend.xml @@ -76,7 +76,7 @@
- Installing the MooseFS metadata and metalogger servers + Installing the MooseFS metadata and metalogger servers You can run these components anywhere as long as the MooseFS chunkservers can reach the MooseFS master server. In our deployment, both MooseFS master and slave run their services inside a virtual diff --git a/doc/src/docbkx/openstack-config/ch_computeconfigure.xml b/doc/src/docbkx/openstack-config/ch_computeconfigure.xml index b5ab9c743a..7e5c7671e4 100644 --- a/doc/src/docbkx/openstack-config/ch_computeconfigure.xml +++ b/doc/src/docbkx/openstack-config/ch_computeconfigure.xml @@ -451,7 +451,7 @@ $ sudo service nova-compute restart
Example <filename>nova.conf</filename> Configuration Files - The following sections describe many of the configuration + The following sections describe many of the configuration option settings that can go into the nova.conf files. Copies of each nova.conf file need to be copied to each @@ -586,7 +586,7 @@ xenapi_remap_vbd_dev=true Configuring the Compute API Configuring Compute API password handling - The OpenStack Compute API allows the user to specify an + 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 diff --git a/doc/src/docbkx/openstack-config/ch_computescheduler.xml b/doc/src/docbkx/openstack-config/ch_computescheduler.xml index 43cf17c32e..0e3dbcdcee 100644 --- a/doc/src/docbkx/openstack-config/ch_computescheduler.xml +++ b/doc/src/docbkx/openstack-config/ch_computescheduler.xml @@ -145,7 +145,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
- AvailabilityZoneFilter + AvailabilityZoneFilter Filters hosts by availability zone. This filter must be enabled for the scheduler to respect availability zones in requests. @@ -169,9 +169,9 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
- ComputeFilter + ComputeFilter - Passes all hosts that are operational and + Passes all hosts that are operational and enabled. In general, this filter should always be enabled. @@ -179,7 +179,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
- CoreFilter + CoreFilter 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). This filter can be configured to allow a fixed amount of vCPU overcommitment by using the - cpu_allocation_ratio + cpu_allocation_ratio Configuration option in nova.conf. The default setting is: @@ -237,18 +237,18 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
DiskFilter - Only schedule instances on hosts if there is + Only schedule instances on hosts if there is sufficient disk space available for root and ephemeral storage. This filter can be configured to allow a fixed amount of disk overcommitment by using the - disk_allocation_ratio + disk_allocation_ratio Configuration option in nova.conf. The default setting is: disk_allocation_ratio=1.0 - + 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
GroupAntiAffinityFilter - The GroupAntiAffinityFilter ensures that each + 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 group as the @@ -282,7 +282,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter these properties using glance image-update img-uuid --property architecture=arm --property hypervisor_type=qemu - The image properties that the filter checks for + The image properties that the filter checks for are: @@ -311,7 +311,7 @@ scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter
- IsolatedHostsFilter + IsolatedHostsFilter 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 diff --git a/doc/src/docbkx/openstack-config/ch_identityconfigure.xml b/doc/src/docbkx/openstack-config/ch_identityconfigure.xml index fed364a6b3..2485dd186a 100644 --- a/doc/src/docbkx/openstack-config/ch_identityconfigure.xml +++ b/doc/src/docbkx/openstack-config/ch_identityconfigure.xml @@ -25,5 +25,5 @@ - + diff --git a/doc/src/docbkx/openstack-config/compute-configure-migrations.xml b/doc/src/docbkx/openstack-config/compute-configure-migrations.xml index 78497865a2..83e16a8afe 100644 --- a/doc/src/docbkx/openstack-config/compute-configure-migrations.xml +++ b/doc/src/docbkx/openstack-config/compute-configure-migrations.xml @@ -158,7 +158,7 @@ $ /etc/init.d/idmapd restart - Set the 'execute/search' bit on your shared directory + Set the 'execute/search' bit on your shared directory. 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 diff --git a/doc/src/docbkx/openstack-image/ch_converting.xml b/doc/src/docbkx/openstack-image/ch_converting.xml index 3bbe287e56..fd7ced09c4 100644 --- a/doc/src/docbkx/openstack-image/ch_converting.xml +++ b/doc/src/docbkx/openstack-image/ch_converting.xml @@ -40,7 +40,7 @@ - This example will convert a raw image file named centos63.dsk to a qcow2 image file + This example will convert a raw image file named centos63.dsk to a qcow2 image file. $ qemu-img convert -f raw -O qcow2 centos64.dsk centos64.qcow2 diff --git a/doc/src/docbkx/openstack-image/ch_modifying_images.xml b/doc/src/docbkx/openstack-image/ch_modifying_images.xml index 95e21e316b..93b6fc7ea6 100644 --- a/doc/src/docbkx/openstack-image/ch_modifying_images.xml +++ b/doc/src/docbkx/openstack-image/ch_modifying_images.xml @@ -208,7 +208,7 @@ disk, carefully check that the resized disk boots and works correctly. Mounting a raw image (without LVM) If you have a raw virtual machine image that is not using LVM to manage its - partitions. First, use the losetup command to find an unused loop + partitions. First, use the losetup command to find an unused loop device. # losetup -f /dev/loop0 diff --git a/doc/src/docbkx/openstack-install/ap_installingfolsom.xml b/doc/src/docbkx/openstack-install/ap_installingfolsom.xml index 980a669890..be83e6bc75 100644 --- a/doc/src/docbkx/openstack-install/ap_installingfolsom.xml +++ b/doc/src/docbkx/openstack-install/ap_installingfolsom.xml @@ -351,7 +351,7 @@ flavor = keystone
- Installing and configuring Compute + Installing and configuring Compute Install the packages.$ 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 Update @@ -470,7 +470,7 @@ nova-cert ubuntu-precise nova enabled :-) 2012-09-1 LOGIN_REDIRECT_URL='/horizon' Restart the services.$ sudo service apache2 restart; sudo service memcached restart - Logging into the dashboard with browser + Logging into the dashboard with browser http://127.0.0.1/horizon
diff --git a/doc/src/docbkx/openstack-install/ch_installidentity.xml b/doc/src/docbkx/openstack-install/ch_installidentity.xml index 17c8a6fc85..a67e8e90d4 100644 --- a/doc/src/docbkx/openstack-install/ch_installidentity.xml +++ b/doc/src/docbkx/openstack-install/ch_installidentity.xml @@ -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"> - Installing OpenStack Identity Service + Installing OpenStack Identity Service The OpenStack Identity Service manages users, tenants (accounts or projects) and offers a common identity system for all the OpenStack components. diff --git a/doc/src/docbkx/openstack-install/ch_installobjectstorage.xml b/doc/src/docbkx/openstack-install/ch_installobjectstorage.xml index ccd89b250b..e0319e8750 100644 --- a/doc/src/docbkx/openstack-install/ch_installobjectstorage.xml +++ b/doc/src/docbkx/openstack-install/ch_installobjectstorage.xml @@ -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"> - Installing OpenStack Object Storage + Installing OpenStack Object Storage The OpenStack Object Storage services work together to provide object storage and retrieval through a REST API. diff --git a/doc/src/docbkx/openstack-install/ch_terminology.xml b/doc/src/docbkx/openstack-install/ch_terminology.xml index b815106f8c..c61dbc51d8 100644 --- a/doc/src/docbkx/openstack-install/ch_terminology.xml +++ b/doc/src/docbkx/openstack-install/ch_terminology.xml @@ -6,7 +6,7 @@ OpenStack Terminology
- Version Names and Release Notes + Version Names and Release Notes 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 diff --git a/doc/src/docbkx/openstack-install/compute-db-sync.xml b/doc/src/docbkx/openstack-install/compute-db-sync.xml index 3ae5437e28..46cf466da5 100644 --- a/doc/src/docbkx/openstack-install/compute-db-sync.xml +++ b/doc/src/docbkx/openstack-install/compute-db-sync.xml @@ -14,7 +14,7 @@ response means the command completed correctly and your nova database is now populated. Deprecation warnings - Note that if while running this command you see warnings such as SADeprecationWarning: The 'listeners' argument to Pool (and create_engine()) is deprecated. Use event.listen()., these will be fixed in future version of the libraries and can be safely ignored. + Note that if while running this command you see warnings such as SADeprecationWarning: The 'listeners' argument to Pool (and create_engine()) is deprecated. Use event.listen()., these will be fixed in future version of the libraries and can be safely ignored. Restart all services in total, just to cover the entire spectrum. On the controller node run: diff --git a/doc/src/docbkx/openstack-install/compute-sys-requirements.xml b/doc/src/docbkx/openstack-install/compute-sys-requirements.xml index 2399a5d974..590660f2fd 100644 --- a/doc/src/docbkx/openstack-install/compute-sys-requirements.xml +++ b/doc/src/docbkx/openstack-install/compute-sys-requirements.xml @@ -30,10 +30,10 @@ services) Processor: 64-bit x86 - Memory: 12 GB RAM + Memory: 12 GB RAM Disk space: 30 GB (SATA, SAS or SSD) Volume storage: two disks with 2 TB (SATA) for volumes attached to the - compute nodes + compute nodes Network: one 1 Gbps Network Interface Card (NIC) diff --git a/doc/src/docbkx/openstack-install/install-config-glance.xml b/doc/src/docbkx/openstack-install/install-config-glance.xml index cb5416d282..933be758e6 100644 --- a/doc/src/docbkx/openstack-install/install-config-glance.xml +++ b/doc/src/docbkx/openstack-install/install-config-glance.xml @@ -45,7 +45,7 @@ determines which row in the user table it uses when authenticating connections. - Enter quit at the + Enter quit at the mysql> prompt to exit MySQL. mysql> quit diff --git a/doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml b/doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml index 458e2d63cd..149d21ab57 100644 --- a/doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml +++ b/doc/src/docbkx/openstack-install/object-storage-install-ubuntu.xml @@ -41,7 +41,7 @@
- General Installation Steps + General Installation Steps Install the baseline operating system, such as diff --git a/doc/src/docbkx/openstack-install/object-storage-verifying-install.xml b/doc/src/docbkx/openstack-install/object-storage-verifying-install.xml index b2fea7aba6..7015ae6f9c 100644 --- a/doc/src/docbkx/openstack-install/object-storage-verifying-install.xml +++ b/doc/src/docbkx/openstack-install/object-storage-verifying-install.xml @@ -28,7 +28,7 @@ - Export the ADMINPASS environment variable: + Export the ADMINPASS environment variable: $ export ADMINPASS=secrete Run the following swift command with the correct Identity Service URL:$ swift -V 2.0 -A http://<AUTH_HOSTNAME>:5000/v2.0 -U demo:admin -K $ADMINPASS stat diff --git a/doc/src/docbkx/openstack-install/start-storage-node-services.xml b/doc/src/docbkx/openstack-install/start-storage-node-services.xml index b16a5b8b63..9ac19eeb0e 100644 --- a/doc/src/docbkx/openstack-install/start-storage-node-services.xml +++ b/doc/src/docbkx/openstack-install/start-storage-node-services.xml @@ -5,7 +5,7 @@ xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" > Start the Storage Nodes Services - Now that the ring files are on each storage node the + Now that the ring files are on each storage node the services can be started. On each storage node run the following: # service swift-object start diff --git a/doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml b/doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml index 13c2fcbf85..62f9d66a44 100644 --- a/doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml +++ b/doc/src/docbkx/openstack-network-connectivity-admin/app_core.xml @@ -22,11 +22,11 @@ - debug=False + debug=False (BoolOpt) Prints debugging output. - verbose=False + verbose=False (BoolOpt) Prints more verbose output. @@ -55,35 +55,35 @@ log_format=%(asctime)s %(levelname)8s - [%(name)s] %(message)s + [%(name)s] %(message)s (StrOpt) A logging.Formatter log message format string that can use any of the available logging.LogRecord attributes. - log_date_format=%Y-%m-%d %H:%M:%S + log_date_format=%Y-%m-%d %H:%M:%S (StrOpt) Format string for %(asctime)s in log records. - log_file= + log_file= (StrOpt) (Optional) Name of log file to output to.  If not set, logging goes to stdout. - log_dir= + log_dir= (StrOpt) (Optional) The directory to keep log files in (will be prepended to --logfile). - use_syslog=False + use_syslog=False (BoolOpt) Uses syslog for logging. - syslog_log_facility=LOG_USER + syslog_log_facility=LOG_USER (StrOpt) The syslog facility to receive log lines. @@ -125,17 +125,17 @@ (StrOpt) Authentication protocol. - admin_tenant_name = + admin_tenant_name = (StrOpt) The administrative tenant name. - admin_user = + admin_user = (StrOpt) The administrative user name. - admin_password = + admin_password = (StrOpt) The password for the administrative user. @@ -158,26 +158,26 @@ - bind_host=0.0.0.0 + bind_host=0.0.0.0 (StrOpt) Server listening IP. - bind_port=9696 + bind_port=9696 (IntOpt) Server listening port. - api_paste_config=api-paste.ini + api_paste_config=api-paste.ini (StrOpt) The paste configuration file, which configures the WSGI application. - api_extensions_path= + api_extensions_path= (StrOpt) Enables custom addition to be made to the above configuration. - policy_file=policy.json + policy_file=policy.json (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 @@ - auth_strategy=keystone + auth_strategy=keystone (StrOpt) The strategy used for authentication. The supported values are ‘keystone’ and ‘noauth’. - core_plugin=neutron.plugins.sample.SamplePlugin.FakePlugin + core_plugin=neutron.plugins.sample.SamplePlugin.FakePlugin (StrOpt) The plugin to be loaded by the service. - pagination_max_limit=-1 + pagination_max_limit=-1 (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 @@ - base_mac=fa:16:3e:00:00:00 + base_mac=fa:16:3e:00:00:00 (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. - mac_generation_retries=16 + mac_generation_retries=16 (IntOpt) The number of times the plugin attempts to generate a unique MAC address. - allow_bulk=True + allow_bulk=True (BoolOpt) Enables or disables bulk create/update/delete operations. - allow_overlapping_ips=False + allow_overlapping_ips=False (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 @@ - allow_pagination=False + allow_pagination=False (BoolOpt) Enables or disables pagination. If plugin doesn't support native pagination, it will enable @@ -266,7 +266,7 @@ - allow_sorting=False + allow_sorting=False (BoolOpt) Enables or disables sorting. If plugin doesn't support native sorting, it will enable @@ -280,19 +280,19 @@ - force_gateway_on_subnet = False + force_gateway_on_subnet = False (BoolOpt) Enables or disables that a gateway must be configured on a subnet. - max_dns_nameservers=5 + max_dns_nameservers=5 (IntOpt) The maximum amount of DNS nameservers that can be configured per subnet. - max_subnet_host_routes=20 + max_subnet_host_routes=20 (IntOpt) The maximum amount of host routes that can be configured per subnet. @@ -302,7 +302,7 @@ configuration files. - dhcp_lease_duration=120 + dhcp_lease_duration=120 (IntOpt) The default expiration time, in seconds, for a DHCP address. @@ -323,38 +323,38 @@ - control_exchange=neutron + control_exchange=neutron (StrOpt) AMQP exchange to connect to if using RabbitMQ or QPID. - rpc_backend=neutron.openstack.common.rpc.impl_kombu + rpc_backend=neutron.openstack.common.rpc.impl_kombu (StrOpt) The messaging module to use, defaults to kombu. For qpid, make use of neutron.openstack.common.rpc.impl_qpid. - rpc_thread_pool_size=64 + rpc_thread_pool_size=64 (IntOpt) Size of RPC thread pool. - rpc_conn_pool_size=30 + rpc_conn_pool_size=30 (IntOpt) Size of RPC connection pool. - rpc_response_timeout=60 + rpc_response_timeout=60 (IntOpt) Seconds to wait for a response from call or multi call. allowed_rpc_exception_modules='neutron.openstack.common.exception', - 'nova.exception' + 'nova.exception' (ListOpt) Modules of exceptions that are permitted to be recreated upon receiving exception data from an rpc call. - fake_rabbit=False + fake_rabbit=False (BoolOpt) If passed, use a fake RabbitMQ provider. @@ -374,57 +374,57 @@ - kombu_ssl_version= + kombu_ssl_version= (StrOpt) SSL version to use (valid only if SSL enabled). - kombu_ssl_keyfile= + kombu_ssl_keyfile= (StrOpt) SSL key file (valid only if SSL enabled). - kombu_ssl_certfile= + kombu_ssl_certfile= (StrOpt) SSL cert file (valid only if SSL enabled). - kombu_ssl_ca_certs= + kombu_ssl_ca_certs= (StrOpt) SSL certification authority file (valid only if SSL enabled). - rabbit_host=localhost + rabbit_host=localhost (StrOpt) IP address of the RabbitMQ installation. - rabbit_password=guest + rabbit_password=guest Password of the RabbitMQ server. - rabbit_port=5672 + rabbit_port=5672 (IntOpt) Port where RabbitMQ server is running/listening. - rabbit_userid=guest + rabbit_userid=guest (StrOpt) User ID used for RabbitMQ connections. - rabbit_virtual_host=/ + rabbit_virtual_host=/ (StrOpt) Location of a virtual RabbitMQ installation. - rabbit_max_retries=0 + rabbit_max_retries=0 (IntOpt) Maximum retries with trying to connect to RabbitMQ. The default of 0 implies an infinite retry count. - rabbit_retry_interval=1 + rabbit_retry_interval=1 (IntOpt) RabbitMQ connection retry interval. @@ -444,71 +444,71 @@ - qpid_hostname=localhost + qpid_hostname=localhost (StrOpt) Qpid broker hostname. - qpid_port=5672 + qpid_port=5672 (IntOpt) Qpid broker port. - qpid_username= + qpid_username= (StrOpt) Username for qpid connection. - qpid_password= + qpid_password= (StrOpt) Password for qpid connection. - qpid_sasl_mechanisms= + qpid_sasl_mechanisms= (StrOpt) Space separated list of SASL mechanisms to use for auth. - qpid_reconnect=True + qpid_reconnect=True (BoolOpt) Automatically reconnect. - qpid_reconnect_timeout=0 + qpid_reconnect_timeout=0 (IntOpt) The number of seconds to wait before deciding that a reconnect attempt has failed. - qpid_reconnect_limit=0 + qpid_reconnect_limit=0 (IntOpt) The limit for the number of times to reconnect before considering the connection to be failed. - qpid_reconnect_interval_min=0 + qpid_reconnect_interval_min=0 (IntOpt) Minimum seconds between reconnection attempts. - qpid_reconnect_interval_max=0 + qpid_reconnect_interval_max=0 (IntOpt) Maximum seconds between reconnection attempts. - qpid_reconnect_interval=0 + qpid_reconnect_interval=0 (IntOpt) Equivalent to setting max and min to the same value. - qpid_heartbeat=60 + qpid_heartbeat=60 (IntOpt) Seconds between connection keepalive heartbeats. - qpid_protocol=tcp + qpid_protocol=tcp (StrOpt) Transport to use, either 'tcp' or 'ssl.' - qpid_tcp_nodelay=True + qpid_tcp_nodelay=True (BoolOpt) Disable Nagle algorithm. @@ -526,30 +526,30 @@ - notification_driver=neutron.openstack.common.notifier.list_notifier + notification_driver=neutron.openstack.common.notifier.list_notifier (MultiStrOpt) Driver or drivers to handle sending notifications. The default is set as notifier as the DHCP agent makes use of the notifications. - default_notification_level=INFO + default_notification_level=INFO (StrOpt) Default notification level for outgoing notifications. - default_publisher_id=$host + default_publisher_id=$host (StrOpt) Default publisher_id for outgoing notifications. - list_notifier_drivers='neutron.openstack.common.notifier.no_op_notifier' + list_notifier_drivers='neutron.openstack.common.notifier.no_op_notifier' (MultiStrOpt) List of drivers to send notifications. - notification_topics='notifications' + notification_topics='notifications' (ListOpt) AMQP topic used for openstack notifications. @@ -569,7 +569,7 @@ - quota_driver=neutron.quota.ConfDriver + quota_driver=neutron.quota.ConfDriver (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 @@ - quota_items=network,subnet,port + quota_items=network,subnet,port (ListOpt) Resource names that are supported by the Quotas feature. - default_quota=-1 + default_quota=-1 (IntOpt) Default number of resources allowed per tenant, minus for unlimited. - quota_network=10 + quota_network=10 (IntOpt) Number of networks allowed per tenant, and minus means unlimited. - quota_subnet=10 + quota_subnet=10 (IntOpt) Number of subnets allowed per tenant, and minus means unlimited. - quota_port=50 + quota_port=50 (IntOpt) Number of ports allowed per tenant, and minus means unlimited. @@ -625,7 +625,7 @@ - sql_connection=sqlite:// + sql_connection=sqlite:// (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 @@ - sql_max_retries=10 + sql_max_retries=10 (IntOpt) The number of database re-connection retry times. Used if connectivity is lost with the database. -1 implies an infinite retry count. - reconnect_interval=2 + reconnect_interval=2 (IntOpt) The database reconnection interval in seconds. Used if connectivity is lost. @@ -671,7 +671,7 @@ - network_vlan_ranges=default:2000:3999 + network_vlan_ranges=default:2000:3999 (ListOpt) Comma-separated list of  <physical_network>:<vlan_min>:<vlan_max> tuples enumerating ranges of VLAN IDs on @@ -679,14 +679,14 @@ for allocation. - tunnel_id_ranges= + tunnel_id_ranges= (ListOpt) Comma-separated list of <tun_min>:<tun_max> tuples enumerating ranges of GRE tunnel IDs that are available for allocation. - integration_bridge=br-int + integration_bridge=br-int (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. - tunnel_bridge=br-tun + tunnel_bridge=br-tun (StrOpt) The name of the OVS tunnel bridge used by the agent for GRE tunnels. Only used if tunnel_id_ranges is not empty. - bridge_mappings=default:br-eth1 + bridge_mappings=default:br-eth1 (ListOpt) Comma-separated list of <physical_network>:<bridge> tuples mapping physical network names to @@ -714,13 +714,13 @@ a port. - local_ip=10.0.0.3 + local_ip=10.0.0.3 (StrOpt) The local IP address of this hypervisor. Used only when tunnel_id_ranges are used. - enable_tunneling=False + enable_tunneling=False (BoolOpt) A flag indicating if tunneling is supported. Not all systems that support Open vSwitch support its GRE tunneling @@ -746,7 +746,7 @@ - rpc=True + rpc=True (BoolOpt) If True, the agent communicates with the plugin through the OpenStack RPC, which is configured in neutron.conf. If False, the @@ -755,12 +755,12 @@ access the database. - polling_interval=2 + polling_interval=2 (IntOpt) Agent's polling interval in seconds. - root_helper=sudo + root_helper=sudo (StrOpt) Limits the commands that can be run. See the rootwrap section for more details. @@ -785,7 +785,7 @@ - sql_connection=sqlite:// + sql_connection=sqlite:// (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 @@ - sql_max_retries=10 + sql_max_retries=10 (IntOpt) Database re-connection retry times. Used if connectivity is lost with the database. -1 implies an infinite retry count. - reconnect_interval=2 + reconnect_interval=2 (IntOpt) Database reconnection interval in seconds. Used if connectivity is lost. @@ -828,7 +828,7 @@ - network_vlan_ranges=default:1000:2999 + network_vlan_ranges=default:1000:2999 (ListOpt) Comma-separated list of <physical_network>:<vlan_min>:<vlan_max> tuples enumerating ranges of VLAN IDs @@ -852,7 +852,7 @@ - physical_interface_mappings=default:eth1 + physical_interface_mappings=default:eth1 (ListOpt) Comma-separated list of <physical_network>:<physical_interface> tuples mapping physical network names @@ -878,7 +878,7 @@ - rpc=True + rpc=True (BoolOpt) If True, the agent communicates with the plugin through the OpenStack RPC, which is configured in neutron.conf. If False, @@ -887,12 +887,12 @@ settings on the agent so that it can access the database. - polling_interval=2 + polling_interval=2 (IntOpt) Agent's polling interval in seconds. - root_helper=sudo + root_helper=sudo (StrOpt) Limits the commands that can be run. See the rootwrap section for more details. @@ -921,24 +921,24 @@ - root_helper=sudo + root_helper=sudo (StrOpt) Limits the commands that can be run. See the rootwrap section for more details. - dhcp_driver=neutron.agent.linux.dhcp.Dnsmasq + dhcp_driver=neutron.agent.linux.dhcp.Dnsmasq (StrOpt) The driver used to manage the DHCP server. - dhcp_lease_relay_socket=$state_path/dhcp/lease_relay + dhcp_lease_relay_socket=$state_path/dhcp/lease_relay (StrOpt) Location to DHCP lease relay UNIX domain socket. - use_namespaces=True + use_namespaces=True (BoolOpt) Allows overlapping IP. @@ -967,27 +967,27 @@ - dhcp_confs=$state_path/dhcp + dhcp_confs=$state_path/dhcp (StrOpt) Location to store DHCP server config files. - dhcp_lease_time=120 + dhcp_lease_time=120 (IntOpt) Lifetime of a DHCP lease in seconds. - dhcp_domain=openstacklocal + dhcp_domain=openstacklocal (StrOpt) Domain to use for building the host names. - dnsmasq_config_file= + dnsmasq_config_file= (StrOpt) Overrides the default dnsmasq settings with this file. - dnsmasq_dns_server= + dnsmasq_dns_server= (StrOpt) Specifies whether to use another DNS server before any in /etc/resolv.conf. @@ -1016,18 +1016,18 @@ - root_helper=sudo + root_helper=sudo (StrOpt) Limits the commands that can be run. See the rootwrap section for more details. - external_network_bridge=br-ex + external_network_bridge=br-ex (StrOpt) Name of bridge used for external network traffic. - use_namespaces=True + use_namespaces=True (BoolOpt) Allows overlapping IP. If you run multiple agents with different IP addresses on the @@ -1038,28 +1038,28 @@ - polling_interval=3 + polling_interval=3 (IntOpt) The time, in seconds, between state poll requests. - metadata_port=9697 + metadata_port=9697 (IntOpt) TCP Port used by metadata namespace proxy. - router_id= + router_id= (StrOpt) If namespaces is disabled, the l3 agent can only configure a router whose ID matches this parameter. - handle_internal_only_routers=True + handle_internal_only_routers=True (BoolOpt) Agent should implement routers with no gateway. - gateway_external_network_id= + gateway_external_network_id= (StrOpt) UUID of external network for routers implemented by the agents. @@ -1076,47 +1076,47 @@ Configuration option=Default value - (Type) Description + (Type) Description - nova_metadata_ip=127.0.0.1 + nova_metadata_ip=127.0.0.1 (StrOpt) The IP address of the Nova metadata service. - nova_metadata_port=8775 + nova_metadata_port=8775 (IntOpt) The TCP port of the Nova metadata service. - metadata_proxy_shared_secret= + metadata_proxy_shared_secret= (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 + neutron_metadata_proxy_shared_secret - admin_user= + admin_user= (StrOpt) The administrative user name for OpenStack Networking, which is defined in OpenStack Identity (keystone). - admin_password= + admin_password= (StrOpt) The password for the administrative user. - admin_tenant_name= + admin_tenant_name= (StrOpt) The administrative user's tenant name. - auth_url= + auth_url= (StrOpt) The URL used to validate tokens. For example, `auth_protocol`://`auth_host`:`auth_port`/v2.0. - auth_region= + auth_region= (StrOpt) The authentication region. @@ -1137,7 +1137,7 @@ - interface_driver= + interface_driver= (StrOpt) The driver used to manage the virtual interface. @@ -1150,7 +1150,7 @@ switch and check port status. - admin_user= + admin_user= (StrOpt) The administrative user name for OpenStack Networking, which is defined in - admin_password= + admin_password= (StrOpt) The password for the administrative user. Only relevant if using MetaPlugin. - admin_tenant_name= + admin_tenant_name= (StrOpt) The administrative user's tenant name. Only relevant if using MetaPlugin. - auth_url= + auth_url= (StrOpt) The URL used to validate tokens. For example, `auth_protocol`://`auth_host`:`auth_port`/v2.0. Only relevant if using MetaPlugin. - auth_strategy=keystone + auth_strategy=keystone (StrOpt) The strategy to use for authentication. Supports noauth or keystone. Only relevant if using MetaPlugin. - auth_region= + auth_region= (StrOpt) The authentication region. Only relevant if using MetaPlugin. - ovs_integration_bridge=br-int + ovs_integration_bridge=br-int (StrOpt) Name of Open vSwitch bridge to use. Only relevant if using Open vSwitch. - network_device_mtu= + network_device_mtu= (StrOpt) MTU setting for device. Only relevant if using Open vSwitch. - meta_flavor_driver_mappings= + meta_flavor_driver_mappings= (StrOpt). Mappings between flavors and drivers. Only relevant if using MetaPlugin. - resync_interval=30 + resync_interval=30 (IntOpt) If an exception occurs on the neutron-server service, the DHCP agent ensures that it syncs with the neutron.conf configuration. The validation about syncing occurs every diff --git a/doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml b/doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml index 6b99f21788..45e5c629ba 100644 --- a/doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml +++ b/doc/src/docbkx/openstack-network-connectivity-admin/app_pagination_and_sorting_support.xml @@ -9,22 +9,22 @@ sorting - Plugin - Support Native Pagination - Support Native Sorting + Plugin + Support Native Pagination + Support Native Sorting - Open vSwitch - True - True + Open vSwitch + True + True - LinuxBridge - True - True + LinuxBridge + True + True diff --git a/doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml b/doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml index 7b4c8f482c..58cb9b8293 100644 --- a/doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml +++ b/doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_config.xml @@ -75,7 +75,7 @@ mysql> grant all on <database-name>.* to '<user-name>'@'%';$NEUTRON_CONF_DIR/plugins/openvswitch/ovs_neutron_plugin.ini - Agent + Agent neutron-openvswitch-agent @@ -95,7 +95,7 @@ mysql> grant all on <database-name>.* to '<user-name>'@'%';$NEUTRON_CONF_DIR/plugins/linuxbridge/linuxbridge_conf.ini - Agent + Agent neutron-linuxbridge-agent @@ -120,8 +120,8 @@ mysql> grant all on <database-name>.* to '<user-name>'@'%'; - Parameter - Value + Parameter + Value @@ -170,8 +170,8 @@ mysql> grant all on <database-name>.* to '<user-name>'@'%'; - Parameter - Value + Parameter + Value @@ -180,23 +180,23 @@ mysql> grant all on <database-name>.* to '<user-name>'@'%'; - interface_driver ($NEUTRON_CONF_DIR/l3_agent.ini) - neutron.agent.linux.interface.OVSInterfaceDriver + interface_driver ($NEUTRON_CONF_DIR/l3_agent.ini) + neutron.agent.linux.interface.OVSInterfaceDriver - external_network_bridge ($NEUTRON_CONF_DIR/l3_agent.ini) - br-ex + external_network_bridge ($NEUTRON_CONF_DIR/l3_agent.ini) + br-ex Linux Bridge - interface_driver ($NEUTRON_CONF_DIR/l3_agent.ini) + interface_driver ($NEUTRON_CONF_DIR/l3_agent.ini) neutron.agent.linux.interface.BridgeInterfaceDriver - external_network_bridge ($NEUTRON_CONF_DIR/l3_agent.ini) + external_network_bridge ($NEUTRON_CONF_DIR/l3_agent.ini) This field must be empty (or the bridge name for the external network). diff --git a/doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml b/doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml index cc85c9716f..0a81b025c7 100644 --- a/doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml +++ b/doc/src/docbkx/openstack-network-connectivity-admin/ch_adv_features.xml @@ -142,17 +142,17 @@ - Attribute name - Type - Default Value - Description + Attribute name + Type + Default Value + Description - provider:network_type - String - N/A + provider:network_type + String + N/A The physical mechanism by which the virtual network is realized. Possible values are "flat", "vlan", "local", and @@ -166,8 +166,8 @@ configuration. - provider:physical_network - String + provider:physical_network + String If a physical network named "default" has been configured, and if provider:network_type is "flat" or "vlan", @@ -284,45 +284,45 @@ - Attribute name - Type - Default Value - Description + Attribute name + Type + Default Value + Description - id - uuid-str - generated + id + uuid-str + generated UUID for the router. - name - String - None + name + String + None Human-readable name for the router. Might not be unique. - admin_state_up - Bool - True + admin_state_up + Bool + True The administrative state of router. If false (down), the router does not forward packets. - status - String - N/A + status + String + N/A Indicates whether router is currently operational. - tenant_id - uuid-str - N/A + tenant_id + uuid-str + N/A Owner of the router. Only admin users can specify a tenant_id other than its own. @@ -345,17 +345,17 @@ - Attribute name - Type - Default Value - Description + Attribute name + Type + Default Value + Description - id - uuid-str - generated + id + uuid-str + generated UUID for the floating IP. @@ -375,8 +375,8 @@ should be allocated - router_id - uuid-str + router_id + uuid-str N/A Read-only value indicating the router that connects the external network to the @@ -401,9 +401,9 @@ have more than one IP address). - tenant_id - uuid-str - N/A + tenant_id + uuid-str + N/A Owner of the Floating IP. Only admin users can specify a tenant_id other than its own. @@ -438,10 +438,10 @@ neutron router-interface-add router1 <subnet2-uuid> + network in the provider A router can also be connected to an “external network”, allowing that router to act as a NAT gateway - for external connectivity.  + for external connectivity. neutron router-gateway-set router1 <ext-net-id> Viewing routers: List all routers: @@ -539,39 +539,39 @@ neutron floatingip-associate <floatingip-id> <internal VM port-id> < - Attribute name - Type - Default Value - Description + Attribute name + Type + Default Value + Description - id - uuid-str - generated + id + uuid-str + generated UUID for the security group. - name - String - None + name + String + None Human-readable name for the security group. Might not be unique. Cannot be named default as that is automatically created for a tenant. - description - String - None + description + String + None Human-readable description of a security group. - tenant_id - uuid-str - N/A + tenant_id + uuid-str + N/A Owner of the security group. Only admin users can specify a tenant_id other than their own. @@ -586,17 +586,17 @@ neutron floatingip-associate <floatingip-id> <internal VM port-id> < - Attribute name - Type - Default Value - Description + Attribute name + Type + Default Value + Description - id - uuid-str - generated + id + uuid-str + generated UUID for the security group rule. @@ -615,7 +615,7 @@ neutron floatingip-associate <floatingip-id> <internal VM port-id> < protocol - String + String None IP Protocol (icmp, tcp, udp, etc). @@ -653,9 +653,9 @@ neutron floatingip-associate <floatingip-id> <internal VM port-id> < rule. - tenant_id - uuid-str - N/A + tenant_id + uuid-str + N/A Owner of the security group rule. Only admin users can specify a tenant_id other than its own. @@ -768,22 +768,22 @@ neutron lb-vip-create --name myvip --protocol-port 80 --protocol HTTP --subnet-i - Attribute name - Type - Default Value - Description + Attribute name + Type + Default Value + Description - id - uuid-str - generated + id + uuid-str + generated UUID for the QoS queue. - default - Boolean + default + Boolean False by default 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. - name - String - None + name + String + None Name for QoS queue. - min - Integer - 0 + min + Integer + 0 Minimum Bandwidth Rate (kbps). - max - Integer - N/A + max + Integer + N/A Maximum Bandwidth Rate (kbps). - qos_marking + qos_marking String - untrusted by default + untrusted by default Whether QoS marking should be trusted or untrusted. - dscp - Integer - 0 + dscp + Integer + 0 DSCP Marking value. - tenant_id - uuid-str - N/A + tenant_id + uuid-str + N/A The owner of the QoS queue. diff --git a/doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml b/doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml index b5c3dbaea9..8ae8a58590 100644 --- a/doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml +++ b/doc/src/docbkx/openstack-network-connectivity-admin/ch_config.xml @@ -420,12 +420,11 @@ catalog.$Region.network.internalURL = http://10.211.55.17:9696
- Example nova.conf Values (for nova-compute and nova-api) - The following code provides example nova.conf - 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. - + Example nova.conf (for <systemitem class="service">nova-compute</systemitem> and <systemitem class="service">nova-api</systemitem>) + 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. network_api_class=nova.network.neutronv2.api.API neutron_url=http://192.168.1.2:9696 neutron_auth_strategy=keystone diff --git a/doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml b/doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml index bab586299e..c10b1c85dc 100644 --- a/doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml +++ b/doc/src/docbkx/openstack-network-connectivity-admin/ch_install.xml @@ -7,7 +7,7 @@ Learn how to install and get the OpenStack Networking service up and running.
- Initial Prerequisites + Initial Prerequisites @@ -38,7 +38,7 @@ $sudo apt-get update $sudo apt-get upgrade
- Install neutron-server + Install neutron-server The neutron-server handles OpenStack Networking's user requests and exposes the API. @@ -84,7 +84,7 @@
- RPC Setup + RPC Setup Many OpenStack Networking plugins use RPC to enable agents to communicate with the main neutron-server process. If @@ -757,7 +757,7 @@ >https://fedoraproject.org/wiki/OpenStack
- RPC Setup + RPC Setup OpenStack Networking uses RPC to allow DHCP agents and any plugin agents to communicate with the main neutron-server process.  @@ -794,7 +794,7 @@
- Install neutron-server and plugin + Install neutron-server and plugin To install and configure the Neutron server and @@ -901,7 +901,7 @@ </para> </section> <section xml:id="fedora_q_l3"> - <title>Install L3 Agent + Install L3 Agent To install and configure the L3 agent diff --git a/doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml b/doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml index 5f04e557c9..a685e8f7dc 100644 --- a/doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml +++ b/doc/src/docbkx/openstack-network-connectivity-admin/ch_limitations.xml @@ -29,11 +29,11 @@ Linux kernel 2.6.24 or newer (with CONFIG_NET_NS=y in kernel - configuration) and + configuration) and iproute2 utilities ('ip' command) version 3.1.0 (aka 20111117) or - newer + newer To check whether your host supports namespaces try running the following as diff --git a/doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml b/doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml index 5ed538a3b1..edb7399d88 100644 --- a/doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml +++ b/doc/src/docbkx/openstack-network-connectivity-admin/ch_overview.xml @@ -212,13 +212,13 @@ - - Libvirt (KVM/QEMU) - XenServer - VMware - Hyper-V - Bare-metal - PowerVM + + Libvirt (KVM/QEMU) + XenServer + VMware + Hyper-V + Bare-metal + PowerVM @@ -327,7 +327,7 @@
- OpenStack Networking Architecture + OpenStack Networking Architecture 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 diff --git a/doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml b/doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml index c8ddebb174..b0e3bba6d2 100644 --- a/doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml +++ b/doc/src/docbkx/openstack-network-connectivity-admin/ch_using.xml @@ -58,59 +58,59 @@ - Attribute name - Type - Default Value - Description + Attribute name + Type + Default Value + Description - id - uuid-str - generated + id + uuid-str + generated UUID for the network. - name - String - None + name + String + None Human-readable name for the network. Might not be unique. - admin_state_up - Bool - True + admin_state_up + Bool + True The administrative state of network. If false (down), the network does not forward packets. - status - String - N/A + status + String + N/A Indicates whether network is currently operational. - subnets - list(uuid-str) - Empty list + subnets + list(uuid-str) + Empty list Subnets associated with this network. - shared - Bool - False + shared + Bool + False Specifies whether the network resource can be accessed by any tenant or not. - tenant_id - uuid-str - N/A + tenant_id + uuid-str + N/A Owner of network. Only admin users can specify a tenant_id other than its own. @@ -125,91 +125,91 @@ - Attribute - Type - Default Value + Attribute + Type + Default Value Description - id - uuid-str - generated - UUID representing the subnet + id + uuid-str + generated + UUID representing the subnet - network_id - uuid-str - N/A + network_id + uuid-str + N/A network this subnet is associated with. - name - String - None + name + String + None Human-readable name for the subnet. Might not be unique. - ip_version - int - 4 - IP version + ip_version + int + 4 + IP version - cidr - string - N/A + cidr + string + N/A cidr representing IP range for this - subnet, based on IP version + subnet, based on IP version - gateway_ip - string + gateway_ip + string first address in cidr default gateway used by devices in this - subnet + subnet - dns_nameservers - list(str) - Empty list + dns_nameservers + list(str) + Empty list DNS name servers used by hosts in this subnet. - allocation_pools - list(dict) + allocation_pools + list(dict) Every address in cidr, excluding gateway_ip if - configured + configured Sub-ranges of cidr available for dynamic allocation to ports [ { "start": - "10.0.0.2", "end": "10.0.0.254"} ] + "10.0.0.2", "end": "10.0.0.254"} ] - host_routes - list(dict) - Empty List + host_routes + list(dict) + Empty List Routes that should be used by devices with IPs from this subnet (not including local subnet route). - enable_dhcp - Bool - True + enable_dhcp + Bool + True Specifies whether DHCP is enabled for this subnet or not. - tenant_id - uuid-str - N/A + tenant_id + uuid-str + N/A Owner of network. Only admin users can specify a tenant_id other than its own. @@ -224,81 +224,81 @@ - Attribute - Type - Default Value + Attribute + Type + Default Value Description - id - uuid-str - generated + id + uuid-str + generated UUID for the port. - network_id - uuid-str - N/A + network_id + uuid-str + N/A Network that this port is associated with. - name - String - None + name + String + None Human-readable name for the port. Might not be unique. - admin_state_up - bool - true + admin_state_up + bool + true Administrative state of port. If false (down), port does not forward packets. - status - string - N/A + status + string + N/A Indicates whether network is currently operational. - mac_address - string - generated + mac_address + string + generated Mac address to use on this port. - fixed_ips - list(dict) - automatically allocated from pool + fixed_ips + list(dict) + automatically allocated from pool Specifies IP addresses for the port thus associating the port itself with the subnets where the IP addresses are picked - from + from - device_id - str - None + device_id + str + None identifies the device (e.g., virtual server) using this port. - device_owner - str - None + device_owner + str + None Identifies the entity (e.g.: dhcp agent) using this port. - tenant_id - uuid-str - N/A + tenant_id + uuid-str + N/A Owner of network. Only admin users can specify a tenant_id other than its own. @@ -383,7 +383,7 @@
Using OpenStack Compute with OpenStack Networking
- Basic Workflow + Basic Workflow Check available networks: $ neutron net-list Boot the VM with a single NIC on the selected network (net1): diff --git a/doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml b/doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml index 68fa2bb117..daf05912f2 100644 --- a/doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml +++ b/doc/src/docbkx/openstack-object-storage-admin/objectstorage-config-reference.xml @@ -1331,7 +1331,7 @@ can be overridden in any of the other sections. Entry point for paste.deploy to use for auth, set to: egg:swauth#swauth to use the swauth downloaded from - https://github.com/gholt/swauth + https://github.com/gholt/swauth log_name diff --git a/doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml b/doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml index e169a53f99..b8ffc2c9e7 100644 --- a/doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml +++ b/doc/src/docbkx/openstack-object-storage-admin/objectstorageadmin.xml @@ -531,7 +531,7 @@ net.ipv4.netfilter.ip_conntrack_max = 262144 Another helpful tuning parameter on slower systems that helps to ensure enough time is allowed for service restarts is the -k N (or - --kill-wait N ) parameter of + --kill-wait N) parameter of swift-init. This allows you to change the default (15 second) time (N, in seconds) that swift waits for processes to die and notably you diff --git a/doc/src/docbkx/openstack-security/ch013_node-bootstrapping.xml b/doc/src/docbkx/openstack-security/ch013_node-bootstrapping.xml index df52aa9c52..c3d6d17c10 100644 --- a/doc/src/docbkx/openstack-security/ch013_node-bootstrapping.xml +++ b/doc/src/docbkx/openstack-security/ch013_node-bootstrapping.xml @@ -104,7 +104,7 @@ 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. The nature of the nodes makes additional hardening possible. We recommend the following additional steps for production nodes: - 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 /etc/fstab . + 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 /etc/fstab. 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. diff --git a/doc/src/docbkx/openstack-security/ch052_devices.xml b/doc/src/docbkx/openstack-security/ch052_devices.xml index eb4832106f..9882270d1d 100644 --- a/doc/src/docbkx/openstack-security/ch052_devices.xml +++ b/doc/src/docbkx/openstack-security/ch052_devices.xml @@ -46,12 +46,12 @@ glance image-update \     --property hw_cdrom_bus=ide \     --property hw_vif_model=e1000 \     f16-x86_64-openstack-sda - 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 ./configure --help from within the QEMU source directory. Decide what is needed for your deployment, and disable the remaining options. + 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 ./configure --help from within the QEMU source directory. Decide what is needed for your deployment, and disable the remaining options.
Compiler Hardening 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). - 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 checksec.sh (http://www.trapkit.de/tools/checksec.html). + 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 checksec.sh (http://www.trapkit.de/tools/checksec.html). RELocation Read-Only (RELRO) : 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. diff --git a/doc/src/docbkx/openstack-training/bk002-ch003-operations-general.xml b/doc/src/docbkx/openstack-training/bk002-ch003-operations-general.xml index bc33a0878f..4e079ce428 100644 --- a/doc/src/docbkx/openstack-training/bk002-ch003-operations-general.xml +++ b/doc/src/docbkx/openstack-training/bk002-ch003-operations-general.xml @@ -28,7 +28,7 @@ Add your GitHub username and password - Set your local + Set your local @@ -175,7 +175,7 @@ $ git config --global user.email "your_email@youremail.com"

$ git checkout -b bug/1188522 - Verify that you have the branch open through SourceTree + Verify that you have the branch open through SourceTree 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"

Track the Gerrit review process athttps://review.openstack.org/#/c/33713 Follow and respond inline to the Code - Review requests and comments + Review requests and comments Your change will be tested, track the Jenkins testing process at - https://jenkins.openstack.org + https://jenkins.openstack.org If your change is rejected. - Respond to the inline comments if any + Respond to the inline comments if any - Update the status to work in progress + Update the status to work in progress - Follow the recommended tweaks to the files + Follow the recommended tweaks to the files Rerun $ mvn clean generate-sources @@ -230,7 +230,7 @@ $ git config --global user.email "your_email@youremail.com"

Final commit $ git review -v - Update the Jenkins status to change completed + Update the Jenkins status to change completed diff --git a/doc/src/docbkx/openstack-training/bk002-ch008-operations-assessment.xml b/doc/src/docbkx/openstack-training/bk002-ch008-operations-assessment.xml index 2670ccbdff..2633e73788 100644 --- a/doc/src/docbkx/openstack-training/bk002-ch008-operations-assessment.xml +++ b/doc/src/docbkx/openstack-training/bk002-ch008-operations-assessment.xml @@ -23,146 +23,146 @@ As a trainee I must configure a virtual environment to accomplish the - configuration tasks + configuration tasks - As a trainee I must understand the basic overview of OpenStack core projects + As a trainee I must understand the basic overview of OpenStack core projects As a trainee I must understand the architecture the RefStack architecture described - in the Basic Install Guide + in the Basic Install Guide As a trainee I must understand how to install Ubuntu 12.04 (or 13.04 in later - versions) + versions) As a trainee I must understand the role of the Controller Node in The RefStack - architecture described in the basic install guide + architecture described in the basic install guide - As a trainee I must understand the role of MySql server in the Controller Node + As a trainee I must understand the role of MySql server in the Controller Node - As a trainee I must install MySql server in the Controller Node + As a trainee I must install MySql server in the Controller Node As a trainee I must understand the role of RabbitMQ Messaging Service in the - Controller Node + Controller Node As a trainee I must install and configure RabbitMQ Messaging Service in the - Controller Node + Controller Node As a trainee I must understand the role of OpenStack Identity Service in the - Controller Node + Controller Node As a trainee I must Install and Configure OpenStack Identity Service in the - Controller Node + Controller Node As a trainee I must understand the role of OpenStack Image Service in the Controller - Node + Node As a trainee I must Install and configure OpenStack Identity Service in the - Controller Node + Controller Node As a trainee I must understand the role of OpenStack Compute (Cloud Controller - Services) in the Controller Node + Services) in the Controller Node As a trainee I must install and configure OpenStack Compute (Cloud Controller - Services) in the Controller Node + Services) in the Controller Node As a trainee I must understand the role of OpenStack Block Storage Service in the - Controller Node + Controller Node As a trainee I must install and configure OpenStack Block Storage Service in the - Controller Node + Controller Node As a trainee I must understand the role of OpenStack Network Service (cloud - controller) in the Controller Node + controller) in the Controller Node As a trainee I must install and configure OpenStack Network Service (cloud - controller) in the Controller Node + controller) in the Controller Node As trainee I must verify the proper configuration and operation of the Controller - node within the RefStack architecture described in the Basic Install Guide + node within the RefStack architecture described in the Basic Install Guide As a trainee I must understand the role of Network Node within the RefStack - architecture described in the Basic Install Guide + architecture described in the Basic Install Guide - As a trainee I must understand the role of Open vSwitch in the Network Node + As a trainee I must understand the role of Open vSwitch in the Network Node - As a trainee I must install and configure Open vSwitch in the Network Node + As a trainee I must install and configure Open vSwitch in the Network Node As a trainee I must understand the role of Neutron (formerly Quantum) in the Network - Node + Node As a trainee I must install and configure Neutron (formerly Quantum) in the Network - Node + Node As a trainee I must understand the how to create virtual networking in the Network - Node + Node - As a trainee I must configure virtual networking in the Network Node + As a trainee I must configure virtual networking in the Network Node - As a trainee I must understand L3 Configuration in the Network Node + As a trainee I must understand L3 Configuration in the Network Node - As a trainee I must configure L3 Configuration in the Network Node + As a trainee I must configure L3 Configuration in the Network Node 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 + Node within the Reference Architecture described in the basic install guide As a trainee I must understand the role of Compute Node within the RefStack - architecture described in the Basic Install Guide + architecture described in the Basic Install Guide - As a trainee I must understand Nova (compute node services) in the Compute Node + As a trainee I must understand Nova (compute node services) in the Compute Node As a trainee I must install and configure Nova (compute node services) in the - Compute Node + Compute Node As a trainee I must understand OpenStack Networking using Open vSwitch in the - Compute Node + Compute Node As a trainee I must install and configure OpenStack Networking using Open vSwitch in - the Compute Node + the Compute Node As a trainee I must understand OpenStack Networking using Neutron (formerly Quantum) - in the Compute Node + in the Compute Node As a trainee I must install and configure OpenStack Networking using Open Neutron - (formerly Quantum) n the Compute Node + (formerly Quantum) n the Compute Node As a trainee I must understand instantiation of a Virtual Machine (Instance) using - OpenStack Dashboard (Horizon) + OpenStack Dashboard (Horizon) As a trainee I must instantiate of a Virtual Machine (Instance) using OpenStack diff --git a/doc/src/docbkx/openstack-user/src/ch_cli.xml b/doc/src/docbkx/openstack-user/src/ch_cli.xml index 87bab6d3f0..801934ac79 100644 --- a/doc/src/docbkx/openstack-user/src/ch_cli.xml +++ b/doc/src/docbkx/openstack-user/src/ch_cli.xml @@ -11,23 +11,23 @@ - + - + - + - + - + - + - + - + - + diff --git a/doc/src/docbkx/openstack-user/src/section_cli_install.xml b/doc/src/docbkx/openstack-user/src/section_cli_install.xml index 9b347657a7..85640ae834 100644 --- a/doc/src/docbkx/openstack-user/src/section_cli_install.xml +++ b/doc/src/docbkx/openstack-user/src/section_cli_install.xml @@ -52,7 +52,7 @@ setuptools - package + package Installed by default on Mac OS