From 884caa4a89c14028dcee01a44646c24f4d2dcf64 Mon Sep 17 00:00:00 2001 From: Tom Fifield Date: Mon, 12 Oct 2015 17:18:03 +0800 Subject: [PATCH] Liberty Release note/link updates for all guides Patch updates text areas and links to reflect the Liberty release across all guides except the install guide. Certain old notes relating to unsupported releases were also removed. Change-Id: I65f6e3747266db5b56e766d389376fb928d881c8 --- .../source/blockstorage_volume_migration.rst | 2 +- .../source/compute-configuring-migrations.rst | 2 +- .../source/compute-images-instances.rst | 10 +++++----- .../source/compute-live-migration-usage.rst | 2 +- .../source/compute-manage-logs.rst | 6 +++--- .../source/compute-networking-nova.rst | 2 +- .../source/compute-service-groups.rst | 2 +- doc/admin-guide-cloud/source/compute_arch.rst | 6 +++--- .../source/cross_project_cors.rst | 2 +- .../source/networking_config-agents.rst | 6 +++--- .../source/networking_introduction.rst | 6 ------ .../source/objectstorage-admin.rst | 2 +- .../source/orchestration-auth-model.rst | 3 --- doc/admin-guide-cloud/source/telemetry-alarms.rst | 2 +- .../source/telemetry-data-collection.rst | 6 ------ .../source/ts_no_emulator_x86_64.rst | 2 +- doc/common-rst/app_support.rst | 10 +++++----- doc/common/app_support.xml | 12 ++++++------ doc/config-reference/ch_objectstorageconfigure.xml | 14 +++++++------- .../section_compute-sample-configuration-files.xml | 6 +++--- .../section_keystone-sample-conf-files.xml | 8 ++++---- ...on_image-service-sample-configuration-files.xml | 14 +++++++------- .../networking/section_networking-plugins.xml | 1 + ...ction_networking-sample-configuration-files.xml | 14 +++++++------- ...ection_telemetry-sample-configuration-files.xml | 6 +++--- doc/contributor-guide/source/content-specs.rst | 8 ++++---- doc/contributor-guide/source/docs_builds.rst | 12 ++++++------ doc/networking-guide/source/adv_config_ipv6.rst | 6 +++--- doc/networking-guide/source/config.rst | 2 +- .../source/intro_basic_networking.rst | 4 ++-- doc/networking-guide/source/scenario_dvr_ovs.rst | 4 ++-- doc/networking-guide/source/scenario_l3ha_lb.rst | 4 ++-- doc/networking-guide/source/scenario_l3ha_ovs.rst | 4 ++-- doc/user-guide-admin/source/cli_cinder_quotas.rst | 2 +- .../source/dashboard_manage_host_aggregates.rst | 2 +- .../source/cli_change_the_size_of_your_server.rst | 2 +- doc/user-guide/source/cli_config_drive.rst | 2 +- doc/user-guide/source/cli_reboot_an_instance.rst | 2 +- .../source/cli_stop_and_start_an_instance.rst | 2 +- doc/user-guide/source/cli_swift_static_website.rst | 4 ++-- 40 files changed, 96 insertions(+), 110 deletions(-) diff --git a/doc/admin-guide-cloud/source/blockstorage_volume_migration.rst b/doc/admin-guide-cloud/source/blockstorage_volume_migration.rst index 996cb74e01..62fea08b2c 100644 --- a/doc/admin-guide-cloud/source/blockstorage_volume_migration.rst +++ b/doc/admin-guide-cloud/source/blockstorage_volume_migration.rst @@ -29,7 +29,7 @@ These workflows are possible for a migration: While most back-ends support this function, not all do. See the driver documentation in the `OpenStack Configuration Reference - `__ for more + `__ for more details. #. If the volume is attached to a VM instance, the Block Storage creates a diff --git a/doc/admin-guide-cloud/source/compute-configuring-migrations.rst b/doc/admin-guide-cloud/source/compute-configuring-migrations.rst index 02db0cd8b0..c02e5d9389 100644 --- a/doc/admin-guide-cloud/source/compute-configuring-migrations.rst +++ b/doc/admin-guide-cloud/source/compute-configuring-migrations.rst @@ -272,7 +272,7 @@ Example Compute installation environment #. You can now configure other options for live migration. In most cases, you will not need to configure any options. For advanced configuration options, see the `OpenStack Configuration Reference Guide `_. .. _true-live-migration-kvm-libvirt: diff --git a/doc/admin-guide-cloud/source/compute-images-instances.rst b/doc/admin-guide-cloud/source/compute-images-instances.rst index 63b13d9527..1c0b2236c4 100644 --- a/doc/admin-guide-cloud/source/compute-images-instances.rst +++ b/doc/admin-guide-cloud/source/compute-images-instances.rst @@ -29,7 +29,7 @@ flavors that you can edit or add to. - For more information about image configuration options, see the `Image - services `__ + services `__ section of the OpenStack Configuration Reference. - For more information about flavors, see :ref:`compute-flavors` or @@ -286,7 +286,7 @@ these steps: `glance-api` service does not start. To view a sample configuration file, see - `glance-api.conf `__. + `glance-api.conf `__. #. Optionally, in the :file:`glance-api.conf` file, specify whether roles or policies are used in the property protections configuration file:: @@ -296,7 +296,7 @@ these steps: The default is ``roles``. To view a sample configuration file, see - `glance-api.conf `__. + `glance-api.conf `__. Image download: how it works ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -330,7 +330,7 @@ Compute nodes also implement caching of images, meaning that if an image has been used before it won't necessarily be downloaded every time. Information on the configuration options for caching on compute nodes can be found in the `Configuration -Reference `__. +Reference `__. Instance building blocks ~~~~~~~~~~~~~~~~~~~~~~~~ @@ -426,7 +426,7 @@ Guide `__. Control where instances run ~~~~~~~~~~~~~~~~~~~~~~~~~~~ The `OpenStack Configuration -Reference `__ +Reference `__ provides detailed information on controlling where your instances run, including ensuring a set of instances run on different compute nodes for service resiliency or on the same node for high performance diff --git a/doc/admin-guide-cloud/source/compute-live-migration-usage.rst b/doc/admin-guide-cloud/source/compute-live-migration-usage.rst index 33f0d532ac..55c2ee6069 100644 --- a/doc/admin-guide-cloud/source/compute-live-migration-usage.rst +++ b/doc/admin-guide-cloud/source/compute-live-migration-usage.rst @@ -16,7 +16,7 @@ Before starting a migration, review the Configure migrations section. Although the :command:`nova` command is called :command:`live-migration`, under the default Compute configuration options, the instances are suspended before migration. For more information, see - `Configure migrations `_. + `Configure migrations `_. in the OpenStack Configuration Reference. **Migrating instances** diff --git a/doc/admin-guide-cloud/source/compute-manage-logs.rst b/doc/admin-guide-cloud/source/compute-manage-logs.rst index 03d368af23..6bb99c8e63 100644 --- a/doc/admin-guide-cloud/source/compute-manage-logs.rst +++ b/doc/admin-guide-cloud/source/compute-manage-logs.rst @@ -39,7 +39,7 @@ For more about the logging configuration syntax, including the on logging configuration files. For an example :file:`logging.conf` file with various defined handlers, see -the `OpenStack Configuration Reference `__. +the `OpenStack Configuration Reference `__. Syslog ~~~~~~ @@ -130,8 +130,8 @@ The serial console provides a way to examine kernel output and other system messages during troubleshooting if the instance lacks network connectivity. -OpenStack Icehouse and earlier supports read-only access using the -serial console using the ``os-GetSerialOutput`` server action. Most +Read-only access from server serial console is possible +using the ``os-GetSerialOutput`` server action. Most cloud images enable this feature by default. For more information, see :ref:`compute-common-errors-and-fixes`. diff --git a/doc/admin-guide-cloud/source/compute-networking-nova.rst b/doc/admin-guide-cloud/source/compute-networking-nova.rst index f298301157..34b0f0456d 100644 --- a/doc/admin-guide-cloud/source/compute-networking-nova.rst +++ b/doc/admin-guide-cloud/source/compute-networking-nova.rst @@ -195,7 +195,7 @@ configuration file. Specify the configuration file using the For more information about creating a dnsmasq configuration file, see the `OpenStack Configuration -Reference `__, +Reference `__, and `the dnsmasq documentation `__. diff --git a/doc/admin-guide-cloud/source/compute-service-groups.rst b/doc/admin-guide-cloud/source/compute-service-groups.rst index dec0af7de6..0b7a1db8b8 100644 --- a/doc/admin-guide-cloud/source/compute-service-groups.rst +++ b/doc/admin-guide-cloud/source/compute-service-groups.rst @@ -80,7 +80,7 @@ node for the ZooKeeper driver: address="192.168.2.1:2181,192.168.2.2:2181,192.168.2.3:2181" For Compute Service groups customization options, see the `OpenStack -Configuration Reference Guide `_. .. _memcache-servicegroup-driver: diff --git a/doc/admin-guide-cloud/source/compute_arch.rst b/doc/admin-guide-cloud/source/compute_arch.rst index f3b7fdbce0..bdf02b8152 100644 --- a/doc/admin-guide-cloud/source/compute_arch.rst +++ b/doc/admin-guide-cloud/source/compute_arch.rst @@ -72,7 +72,7 @@ availability zones. Compute supports the following hypervisors: - `Xen `__ For more information about hypervisors, see the -`Hypervisors `__ +`Hypervisors `__ section in the OpenStack Configuration Reference. Tenants, users, and roles @@ -179,7 +179,7 @@ case, the root file system can be on the persistent volume, and its state is maintained, even if the instance is shut down. For more information about this type of configuration, see the `OpenStack Configuration Reference -`__. +`__. .. note:: @@ -196,7 +196,7 @@ In addition to the native compute API, OpenStack provides an EC2-compatible API. This API allows EC2 legacy workflows built for EC2 to work with OpenStack. For more information and configuration options about this compatibility API, see the `OpenStack Configuration -Reference `__. +Reference `__. Numerous third-party tools and language-specific SDKs can be used to interact with OpenStack clouds, using both native and compatibility diff --git a/doc/admin-guide-cloud/source/cross_project_cors.rst b/doc/admin-guide-cloud/source/cross_project_cors.rst index 44dd679d5e..d560baf74c 100644 --- a/doc/admin-guide-cloud/source/cross_project_cors.rst +++ b/doc/admin-guide-cloud/source/cross_project_cors.rst @@ -24,7 +24,7 @@ security advisory below for more information. not covered by this document. For those, please refer to their respective implementations: - * `CORS in Object Storage `_ + * `CORS in Object Storage `_ * `CORS in dashboard `_ diff --git a/doc/admin-guide-cloud/source/networking_config-agents.rst b/doc/admin-guide-cloud/source/networking_config-agents.rst index e378017209..9d4e3d1a0e 100644 --- a/doc/admin-guide-cloud/source/networking_config-agents.rst +++ b/doc/admin-guide-cloud/source/networking_config-agents.rst @@ -122,7 +122,7 @@ service, or no longer needed. This feature applies to all plug-ins that support DHCP scaling. For more information, see the `DHCP agent configuration -options `__ listed in the OpenStack Configuration Reference. @@ -420,7 +420,7 @@ Configure Hyper-V L2 agent Before you install the OpenStack Networking Hyper-V L2 agent on a Hyper-V compute node, ensure the compute node has been configured correctly using these -`instructions `__. **To install the OpenStack Networking Hyper-V agent and configure the node** @@ -447,7 +447,7 @@ hyper-v-virtualization-platform.html>`__. #. Create the :file:`C:\etc\neutron-hyperv-agent.conf` file and add the proper configuration options and the `Hyper-V related - options `__. Here is a sample config file: .. code-block:: ini diff --git a/doc/admin-guide-cloud/source/networking_introduction.rst b/doc/admin-guide-cloud/source/networking_introduction.rst index 35b53138cb..5f427bbb06 100644 --- a/doc/admin-guide-cloud/source/networking_introduction.rst +++ b/doc/admin-guide-cloud/source/networking_introduction.rst @@ -297,12 +297,6 @@ an IP address between two instances to enable fast data plane failover. $ neutron port-update PORT_UUID --allowed-address-pairs type=dict list=true mac_address=MAC_ADDRESS,ip_address=IP_CIDR -.. Note:: - - In releases earlier than Juno, OpenStack Networking prevents setting - an allowed address pair on a port that matches the MAC address and - one of the fixed IP addresses of the port. - .. |FWaaS architecture| image:: ../../common/figures/fwaas.png diff --git a/doc/admin-guide-cloud/source/objectstorage-admin.rst b/doc/admin-guide-cloud/source/objectstorage-admin.rst index 4969ee8562..34a6636a29 100644 --- a/doc/admin-guide-cloud/source/objectstorage-admin.rst +++ b/doc/admin-guide-cloud/source/objectstorage-admin.rst @@ -8,5 +8,5 @@ information is maintained in developer documentation at `docs.openstack.org/developer/swift/ `__. See the `OpenStack Configuration -Reference `__ +Reference `__ for a list of configuration options for Object Storage. diff --git a/doc/admin-guide-cloud/source/orchestration-auth-model.rst b/doc/admin-guide-cloud/source/orchestration-auth-model.rst index 1ada24f5d7..958a530011 100644 --- a/doc/admin-guide-cloud/source/orchestration-auth-model.rst +++ b/doc/admin-guide-cloud/source/orchestration-auth-model.rst @@ -53,9 +53,6 @@ The following steps are executed for password authorization: Keystone trusts authorization ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -OpenStack Identity trusts is a new authorization method available -since the Icehouse release. - A trust is an OpenStack Identity extension that provides a method to enable delegation, and optionally impersonation via OpenStack Identity. The key terminology is *trustor* (the user delegating) and diff --git a/doc/admin-guide-cloud/source/telemetry-alarms.rst b/doc/admin-guide-cloud/source/telemetry-alarms.rst index 9d4f485e26..e22e719183 100644 --- a/doc/admin-guide-cloud/source/telemetry-alarms.rst +++ b/doc/admin-guide-cloud/source/telemetry-alarms.rst @@ -116,7 +116,7 @@ information about this approach, see the section called To use this workload partitioning solution set the ``evaluation_service`` option to ``default``. For more information, see the alarm section in the -`OpenStack Configuration Reference `_. +`OpenStack Configuration Reference `_. Using alarms ~~~~~~~~~~~~ diff --git a/doc/admin-guide-cloud/source/telemetry-data-collection.rst b/doc/admin-guide-cloud/source/telemetry-data-collection.rst index e3df41e701..bed4379b8c 100644 --- a/doc/admin-guide-cloud/source/telemetry-data-collection.rst +++ b/doc/admin-guide-cloud/source/telemetry-data-collection.rst @@ -1013,12 +1013,6 @@ supported to start multiple worker threads per collector process. The `__ of the :file:`ceilometer.conf` configuration file. -.. note:: - - Prior to the Juno release, it is not recommended to use multiple - workers per collector process when using PostgreSQL as the database - back end. - Database dispatcher ------------------- When the database dispatcher is configured as data store, you have the diff --git a/doc/admin-guide-cloud/source/ts_no_emulator_x86_64.rst b/doc/admin-guide-cloud/source/ts_no_emulator_x86_64.rst index 9e9d776710..a3c75e08b2 100644 --- a/doc/admin-guide-cloud/source/ts_no_emulator_x86_64.rst +++ b/doc/admin-guide-cloud/source/ts_no_emulator_x86_64.rst @@ -15,6 +15,6 @@ On the KVM host, run ``cat /proc/cpuinfo``. Make sure the ``vmx`` or ``svm`` flags are set. Follow the instructions in the `enabling KVM -section `__ +section `__ of the Configuration Reference to enable hardware virtualization support in your BIOS. diff --git a/doc/common-rst/app_support.rst b/doc/common-rst/app_support.rst index f946271bcf..a43ab637c6 100644 --- a/doc/common-rst/app_support.rst +++ b/doc/common-rst/app_support.rst @@ -26,14 +26,14 @@ associated components: - `Installation Guide for openSUSE 13.2 and SUSE Linux Enterprise Server 12 - `__ + `__ - `Installation Guide for Red Hat Enterprise Linux 7, CentOS 7, and Fedora - 21 `__ + 21 `__ - `Installation Guide for Ubuntu - 14.04 `__ + 14.04 `__ The following books explain how to configure and run an OpenStack cloud: @@ -44,7 +44,7 @@ The following books explain how to configure and run an OpenStack cloud: Guide `__ - `Configuration - Reference `__ + Reference `__ - `Operations Guide `__ @@ -141,7 +141,7 @@ Some tips: - Be sure to include the software and package versions that you are using, especially if you are using a development branch, such as, - ``"Juno release" vs git commit bc79c3ecc55929bac585d04a03475b72e06a3208``. + ``"Kilo release" vs git commit bc79c3ecc55929bac585d04a03475b72e06a3208``. - Any deployment-specific information is helpful, such as whether you are using Ubuntu 14.04 or are performing a multi-node installation. diff --git a/doc/common/app_support.xml b/doc/common/app_support.xml index 6d50ff2e0c..f38d843e98 100644 --- a/doc/common/app_support.xml +++ b/doc/common/app_support.xml @@ -30,7 +30,7 @@ + xlink:href="http://docs.openstack.org/liberty/install-guide-obs/"> Installation Guide for openSUSE 13.2 and SUSE Linux Enterprise Server 12 @@ -38,16 +38,16 @@ + xlink:href="http://docs.openstack.org/liberty/install-guide-rdo/"> Installation Guide for Red Hat Enterprise Linux 7, CentOS 7, and - Fedora 21 + Fedora 22 + xlink:href="http://docs.openstack.org/liberty/install-guide-ubuntu/"> Installation Guide for Ubuntu 14.04 (LTS) @@ -71,7 +71,7 @@ Configuration Reference @@ -226,7 +226,7 @@ Be sure to include the software and package versions that you are using, especially if you are using a development branch, such as, - "Juno release" vs git commit + "Liberty release" vs git commit bc79c3ecc55929bac585d04a03475b72e06a3208. diff --git a/doc/config-reference/ch_objectstorageconfigure.xml b/doc/config-reference/ch_objectstorageconfigure.xml index e12d96fc8c..e62fe1f938 100644 --- a/doc/config-reference/ch_objectstorageconfigure.xml +++ b/doc/config-reference/ch_objectstorageconfigure.xml @@ -40,7 +40,7 @@ href="../common/tables/swift-object-server-filter-xprofile.xml"/>
Sample object server configuration file - +
@@ -65,7 +65,7 @@ href="../common/tables/swift-object-expirer-pipeline-main.xml"/>
Sample object expirer configuration file - +
@@ -97,7 +97,7 @@ href="../common/tables/swift-container-server-filter-xprofile.xml"/>
Sample container server configuration file - +
@@ -115,7 +115,7 @@ href="../common/tables/swift-container-sync-realms-realm2.xml"/>
Sample container sync realms configuration file - +
@@ -140,7 +140,7 @@ href="../common/tables/swift-container-reconciler-pipeline-main.xml"/>
Sample container sync reconciler configuration file - +
@@ -170,7 +170,7 @@ href="../common/tables/swift-account-server-filter-xprofile.xml"/>
Sample account server configuration file - +
@@ -213,7 +213,7 @@ href="../common/tables/swift-proxy-server-filter-xprofile.xml"/>
Sample proxy server configuration file - +
diff --git a/doc/config-reference/compute/section_compute-sample-configuration-files.xml b/doc/config-reference/compute/section_compute-sample-configuration-files.xml index 339a14af4e..7860f72a50 100644 --- a/doc/config-reference/compute/section_compute-sample-configuration-files.xml +++ b/doc/config-reference/compute/section_compute-sample-configuration-files.xml @@ -10,14 +10,14 @@ The Compute service stores its API configuration settings in the api-paste.ini file. - +
policy.json The policy.json file defines additional access controls that apply to the Compute service. - +
@@ -30,7 +30,7 @@ option in the section of the nova.conf configuration file. - +
diff --git a/doc/config-reference/identity/section_keystone-sample-conf-files.xml b/doc/config-reference/identity/section_keystone-sample-conf-files.xml index b481315b4e..86502a36d9 100644 --- a/doc/config-reference/identity/section_keystone-sample-conf-files.xml +++ b/doc/config-reference/identity/section_keystone-sample-conf-files.xml @@ -11,7 +11,7 @@ keystone.conf Use the keystone.conf file to configure most Identity service options: - +
@@ -19,7 +19,7 @@ Use the keystone-paste.ini file to configure the Web Service Gateway Interface (WSGI) middleware pipeline for the Identity service. - +
@@ -31,7 +31,7 @@ For details, see the (Python logging module documentation). - +
@@ -39,6 +39,6 @@ Use the policy.json file to define additional access controls that apply to the Identity service. - +
diff --git a/doc/config-reference/image-service/section_image-service-sample-configuration-files.xml b/doc/config-reference/image-service/section_image-service-sample-configuration-files.xml index 76e933de9f..ad2c8b8a0c 100644 --- a/doc/config-reference/image-service/section_image-service-sample-configuration-files.xml +++ b/doc/config-reference/image-service/section_image-service-sample-configuration-files.xml @@ -12,7 +12,7 @@ The configuration file for the Image service API is found in the glance-api.conf file. This file must be modified after installation. - +
glance-registry.conf @@ -20,14 +20,14 @@ stores the metadata about images, is found in the glance-registry.conf file. This file must be modified after installation. - +
glance-api-paste.ini Configuration for the Image service's API middleware pipeline is found in the glance-api-paste.ini file. You should not need to modify this file. - +
glance-manage.conf @@ -38,24 +38,24 @@ glance-registry.conf and glance-api.conf. Similarly, options in glance-api.conf will override options set in glance-registry.conf. - +
glance-registry-paste.ini The Image service's middleware pipeline for its registry is found in the glance-registry-paste.ini file. - +
glance-scrubber.conf glance-scrubber is a utility for the Image service that cleans up images that have been deleted; its configuration is stored in the glance-scrubber.conf file. - +
policy.json The /etc/glance/policy.json file defines additional access controls that apply to the Image service. - +
diff --git a/doc/config-reference/networking/section_networking-plugins.xml b/doc/config-reference/networking/section_networking-plugins.xml index 92b177c154..09c77be61d 100644 --- a/doc/config-reference/networking/section_networking-plugins.xml +++ b/doc/config-reference/networking/section_networking-plugins.xml @@ -15,6 +15,7 @@ L2-in-L3 tunneling or OpenFlow. These sections detail the configuration options for the various plug-ins. + The following plugins have been removed in Kilo: diff --git a/doc/config-reference/networking/section_networking-sample-configuration-files.xml b/doc/config-reference/networking/section_networking-sample-configuration-files.xml index bd757147c7..cfb4440b49 100644 --- a/doc/config-reference/networking/section_networking-sample-configuration-files.xml +++ b/doc/config-reference/networking/section_networking-sample-configuration-files.xml @@ -10,14 +10,14 @@ Use the neutron.conf file to configure the majority of the OpenStack Networking options. - +
api-paste.ini Use the api-paste.ini to configure the OpenStack Networking API. - +
@@ -25,7 +25,7 @@ Use the policy.json file to define additional access controls that apply to the OpenStack Networking service. - +
@@ -34,7 +34,7 @@ rootwrap script when the OpenStack Networking service must escalate its privileges to those of the root user. - +
@@ -45,19 +45,19 @@
dhcp_agent.ini - +
l3_agent.ini - +
metadata_agent.ini - +
diff --git a/doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml b/doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml index 5176777cff..a77805b259 100644 --- a/doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml +++ b/doc/config-reference/telemetry/section_telemetry-sample-configuration-files.xml @@ -24,7 +24,7 @@ This file provides a standard set of events and corresponding traits that may be of interest. This file can be modified to add and drop traits that operators may find useful. - +
pipeline.yaml @@ -34,7 +34,7 @@ file. This file can be modified to adjust polling intervals and the samples generated by the Telemetry module - +
event_pipeline.yaml @@ -49,7 +49,7 @@ policy.json The policy.json file defines additional access controls that apply to the Telemetry service. - +
diff --git a/doc/contributor-guide/source/content-specs.rst b/doc/contributor-guide/source/content-specs.rst index 6b910ed9da..c39a4e4b56 100644 --- a/doc/contributor-guide/source/content-specs.rst +++ b/doc/contributor-guide/source/content-specs.rst @@ -151,11 +151,11 @@ This guide has a review in place to get a license indicator in output: .. Links -.. _`Installation Guide for openSUSE and SUSE Linux Enterprise Server`: http://docs.openstack.org/kilo/install-guide/install/zypper/content/ -.. _`Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora`: http://docs.openstack.org/kilo/install-guide/install/yum/content/ -.. _`Installation Guide for Ubuntu 12.04 and 14.04 (LTS) Server`: http://docs.openstack.org/kilo/install-guide/install/apt/content/ +.. _`Installation Guide for openSUSE and SUSE Linux Enterprise Server`: http://docs.openstack.org/liberty/install-guide-obs/ +.. _`Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora`: http://docs.openstack.org/liberty/install-guide-rdo/ +.. _`Installation Guide for Ubuntu 12.04 and 14.04 (LTS) Server`: http://docs.openstack.org/liberty/install-guide-ubuntu/ -.. _`OpenStack Configuration Reference`: http://docs.openstack.org/kilo/config-reference/content/ +.. _`OpenStack Configuration Reference`: http://docs.openstack.org/liberty/config-reference/content/ .. _`release information`: https://wiki.openstack.org/wiki/Releases diff --git a/doc/contributor-guide/source/docs_builds.rst b/doc/contributor-guide/source/docs_builds.rst index b218d85d0c..0abba281d7 100644 --- a/doc/contributor-guide/source/docs_builds.rst +++ b/doc/contributor-guide/source/docs_builds.rst @@ -46,15 +46,15 @@ like the example above of stable/kilo. * - Installation Guide for openSUSE and SUSE Linux Enterprise Server - http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide - - http://docs.openstack.org/kilo/install-guide/install/zypper/content + - http://docs.openstack.org/liberty/install-guide-obs * - Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora - http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide - - http://docs.openstack.org/kilo/install-guide/install/yum/content + - http://docs.openstack.org/kilo/install-guide-rdo * - Installation Guide for Ubuntu 14.04 (LTS) - http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide - - http://docs.openstack.org/kilo/install-guide/install/apt/content + - http://docs.openstack.org/kilo/install-guide-ubuntu Guides for deployers and administrators --------------------------------------- @@ -72,7 +72,7 @@ Guides for deployers and administrators * - Configuration Reference - http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/config-reference - - http://docs.openstack.org/kilo/config-reference/content + - http://docs.openstack.org/liberty/config-reference/content * - Cloud Administrator Guide - http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/admin-guide-cloud @@ -201,8 +201,8 @@ file contain the Jenkins build jobs that build to the docs.openstack.org and developer.openstack.org sites, copying built files via FTP. The release specific books are build for the currently supported branches -(juno, kilo), development happens on the master branch. The continuously -released books are only build on the master branch. +(juno, kilo, liberty), development happens on the master branch. The +continuously released books are only build on the master branch. Maven plug-in ~~~~~~~~~~~~~ diff --git a/doc/networking-guide/source/adv_config_ipv6.rst b/doc/networking-guide/source/adv_config_ipv6.rst index 1b781dae14..668b1ba051 100644 --- a/doc/networking-guide/source/adv_config_ipv6.rst +++ b/doc/networking-guide/source/adv_config_ipv6.rst @@ -12,7 +12,7 @@ The basics ~~~~~~~~~~ OpenStack Networking has supported IPv6 tenant subnets in certain -configurations since Juno, but the Kilo release adds a number of new +configurations since Juno, but later releases added a number of new features, functionality and bug fixes to make it more robust. The focus of this page will be: @@ -457,8 +457,8 @@ external (to the OpenStack Networking service) DHCPv6 server to manage your tenant network prefixes. .. note:: - Prefix delegation will be in the upcoming Liberty release, it is - not available in the current OpenStack Kilo release. HA and DVR routers + Prefix delegation became available in the Liberty release, it is + not available in the Kilo release. HA and DVR routers are not currently supported by this feature. Configuring OpenStack Networking for prefix delegation diff --git a/doc/networking-guide/source/config.rst b/doc/networking-guide/source/config.rst index 2899ee12df..fd6be8644c 100644 --- a/doc/networking-guide/source/config.rst +++ b/doc/networking-guide/source/config.rst @@ -4,7 +4,7 @@ Configuration This content currently under development. For general configuration, see the `Configuration Reference -`_. +`_. .. toctree:: :maxdepth: 2 diff --git a/doc/networking-guide/source/intro_basic_networking.rst b/doc/networking-guide/source/intro_basic_networking.rst index 3c42927a72..64349cc8af 100644 --- a/doc/networking-guide/source/intro_basic_networking.rst +++ b/doc/networking-guide/source/intro_basic_networking.rst @@ -397,8 +397,8 @@ services. See `Appendix B. Firewalls and default ports`_ of the various services involved in an OpenStack deployment. .. _registry of port numbers: http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml -.. _Appendix B. Firewalls and default ports: http://docs.openstack.org/kilo/config-reference/content/firewalls-default-ports.html -.. _OpenStack Configuration Reference: http://docs.openstack.org/kilo/config-reference/content/index.html +.. _Appendix B. Firewalls and default ports: http://docs.openstack.org/liberty/config-reference/content/firewalls-default-ports.html +.. _OpenStack Configuration Reference: http://docs.openstack.org/liberty/config-reference/content/index.html The most common application programming interface (API) for writing TCP-based diff --git a/doc/networking-guide/source/scenario_dvr_ovs.rst b/doc/networking-guide/source/scenario_dvr_ovs.rst index 72d2b55e81..d871cf9314 100644 --- a/doc/networking-guide/source/scenario_dvr_ovs.rst +++ b/doc/networking-guide/source/scenario_dvr_ovs.rst @@ -21,8 +21,8 @@ routing and SNAT services between project and external networks. .. note:: In the Juno (initial) release, DVR supports VXLAN and GRE project networks. - In the Kilo release, DVR adds support for VLAN project networks. All - releases support flat and VLAN external networks. + In the Kilo release, support was added for DVR with VLAN project networks. + All releases support flat and VLAN external networks. Prerequisites ~~~~~~~~~~~~~ diff --git a/doc/networking-guide/source/scenario_l3ha_lb.rst b/doc/networking-guide/source/scenario_l3ha_lb.rst index 7644f281f2..0ca50e66b4 100644 --- a/doc/networking-guide/source/scenario_l3ha_lb.rst +++ b/doc/networking-guide/source/scenario_l3ha_lb.rst @@ -19,7 +19,7 @@ constraints and to improve scaling. Also, this implementation does not address situations where one or more layer-3 agents fail and the underlying virtual networks continue to operate normally. Consider deploying :doc:`scenario_dvr_ovs` to increase performance in addition to redundancy. As -of the Kilo release, you cannot combine the DVR and L3HA mechanisms. +of the Liberty release, you cannot combine the DVR and L3HA mechanisms. .. note:: The failover process only retains the state of network connections for @@ -30,7 +30,7 @@ project (tenant) network. However, this configuration also supports VLAN external and project networks. .. note:: - In the Juno (initial) and Kilo releases, L3HA with Linux bridge supports + In the releases prior to Liberty, L3HA with Linux bridge supports VLAN and VXLAN project networks. However, due to a bug, VXLAN project networks must use multicast instead of the layer-2 population mechanism. diff --git a/doc/networking-guide/source/scenario_l3ha_ovs.rst b/doc/networking-guide/source/scenario_l3ha_ovs.rst index bde6a26041..7dfebc4419 100644 --- a/doc/networking-guide/source/scenario_l3ha_ovs.rst +++ b/doc/networking-guide/source/scenario_l3ha_ovs.rst @@ -19,7 +19,7 @@ constraints and to improve scaling. Also, this implementation does not address situations where one or more layer-3 agents fail and the underlying virtual networks continue to operate normally. Consider deploying :doc:`scenario_dvr_ovs` to increase performance in addition to redundancy. As -of the Kilo release, you cannot combine the DVR and L3HA mechanisms. +of the Liberty release, you cannot combine the DVR and L3HA mechanisms. .. note:: The failover process only retains the state of network connections for @@ -30,7 +30,7 @@ project (tenant) network. However, this configuration also supports VLAN external networks, VLAN project networks, and GRE project networks. .. note:: - Due to a bug in the Juno (initial) and Kilo releases, VXLAN and GRE project + Due to a bug in releases prior to Liberty, VXLAN and GRE project networks must use multicast instead of the layer-2 population mechanism. .. todo: diff --git a/doc/user-guide-admin/source/cli_cinder_quotas.rst b/doc/user-guide-admin/source/cli_cinder_quotas.rst index 59693a93ca..b1c609a8b4 100644 --- a/doc/user-guide-admin/source/cli_cinder_quotas.rst +++ b/doc/user-guide-admin/source/cli_cinder_quotas.rst @@ -78,7 +78,7 @@ service quotas. update the property in the :guilabel:`cinder.quota` section of the :file:`/etc/cinder/cinder.conf` file. For more information, see the `Block Storage - Configuration Reference `_. + Configuration Reference `_. #. To update Block Storage service quotas, place the tenant ID in a variable:: diff --git a/doc/user-guide-admin/source/dashboard_manage_host_aggregates.rst b/doc/user-guide-admin/source/dashboard_manage_host_aggregates.rst index 8938d7d9dd..06dc16491c 100644 --- a/doc/user-guide-admin/source/dashboard_manage_host_aggregates.rst +++ b/doc/user-guide-admin/source/dashboard_manage_host_aggregates.rst @@ -11,7 +11,7 @@ multiple aggregates. The scheduler uses this information to make scheduling decisions. For information, see -`Scheduling `__. +`Scheduling `__. To create a host aggregate ~~~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/doc/user-guide/source/cli_change_the_size_of_your_server.rst b/doc/user-guide/source/cli_change_the_size_of_your_server.rst index e8b9b40bf6..67d6f1ad28 100644 --- a/doc/user-guide/source/cli_change_the_size_of_your_server.rst +++ b/doc/user-guide/source/cli_change_the_size_of_your_server.rst @@ -74,7 +74,7 @@ Change the size of a server by changing its flavor. period (in seconds) a guest operation system is allowed to complete the shutdown. The default timeout is 60 seconds. See `Description of Compute configuration options - `_ + `_ for details. The timeout value can be overridden on a per image basis diff --git a/doc/user-guide/source/cli_config_drive.rst b/doc/user-guide/source/cli_config_drive.rst index 124ea6bea7..29cb4b6bfe 100644 --- a/doc/user-guide/source/cli_config_drive.rst +++ b/doc/user-guide/source/cli_config_drive.rst @@ -276,7 +276,7 @@ If you choose VFAT, the configuration drive is 64 MB. .. note:: - In current version (Kilo) of OpenStack Compute, live migration with + In current version (Liberty) of OpenStack Compute, live migration with ``config_drive`` on local disk is forbidden due to the bug in libvirt of copying a read-only disk. However, if we use VFAT as the format of ``config_drive``, the function of live migration works well. diff --git a/doc/user-guide/source/cli_reboot_an_instance.rst b/doc/user-guide/source/cli_reboot_an_instance.rst index 640e751b3c..84f4e6c257 100644 --- a/doc/user-guide/source/cli_reboot_an_instance.rst +++ b/doc/user-guide/source/cli_reboot_an_instance.rst @@ -48,7 +48,7 @@ command:: a guest operation system is allowed to complete the shutdown. The default timeout is 60 seconds. See `Description of Compute configuration options - `_ + `_ for details. The timeout value can be overridden on a per image basis diff --git a/doc/user-guide/source/cli_stop_and_start_an_instance.rst b/doc/user-guide/source/cli_stop_and_start_an_instance.rst index 6ba693f928..e45a00c165 100644 --- a/doc/user-guide/source/cli_stop_and_start_an_instance.rst +++ b/doc/user-guide/source/cli_stop_and_start_an_instance.rst @@ -60,7 +60,7 @@ You can run the following shelving tasks: period (in seconds) a guest operation system is allowed to complete the shutdown. The default timeout is 60 seconds. See `Description of Compute configuration options - `_ + `_ for details. The timeout value can be overridden on a per image basis diff --git a/doc/user-guide/source/cli_swift_static_website.rst b/doc/user-guide/source/cli_swift_static_website.rst index 17ab293ab2..631d78133e 100644 --- a/doc/user-guide/source/cli_swift_static_website.rst +++ b/doc/user-guide/source/cli_swift_static_website.rst @@ -20,9 +20,9 @@ The Static Web filter must be added to the pipeline in your middleware. You must also add a Static Web middleware configuration section. -See the Cloud Administrator Guide for an example of the `static web configuration syntax `_. +See the Cloud Administrator Guide for an example of the `static web configuration syntax `_. -See the Cloud Administrator Guide for a complete example of the `/etc/swift/proxy-server.conf file `_ (including static web). +See the Cloud Administrator Guide for a complete example of the `/etc/swift/proxy-server.conf file `_ (including static web). Your publicly readable containers are checked for two headers, ``X-Container-Meta-Web-Index`` and ``X-Container-Meta-Web-Error``. The