From d10f645e00434de6d2e8b459161fe223f1bf2c2b Mon Sep 17 00:00:00 2001 From: chenxing Date: Thu, 29 Sep 2016 08:11:01 +0000 Subject: [PATCH] [admin-guide] Update links to newton Change-Id: Id40467c27f18622f1c0849cefaacf7829dc8f13f --- .../source/baremetal-multitenancy.rst | 2 +- .../source/blockstorage-volume-migration.rst | 2 +- doc/admin-guide/source/cli-cinder-quotas.rst | 2 +- doc/admin-guide/source/compute-arch.rst | 4 +- .../source/compute-cpu-topologies.rst | 2 +- doc/admin-guide/source/compute-flavors.rst | 2 +- .../source/compute-images-instances.rst | 10 ++-- .../source/compute-live-migration-usage.rst | 2 +- .../source/compute-manage-logs.rst | 2 +- .../source/compute-networking-nova.rst | 2 +- .../source/compute-pci-passthrough.rst | 8 ++-- .../dashboard-manage-host-aggregates.rst | 2 +- doc/admin-guide/source/database.rst | 2 +- .../source/networking-adv-features.rst | 2 +- .../source/networking-config-agents.rst | 6 +-- .../source/networking-config-plugins.rst | 10 ++-- .../source/networking-multi-dhcp-agents.rst | 2 +- .../source/objectstorage-admin.rst | 2 +- .../source/objectstorage-components.rst | 2 +- .../shared-file-systems-share-replication.rst | 2 +- doc/admin-guide/source/telemetry-alarms.rst | 2 +- .../source/telemetry-data-collection.rst | 47 +++++++------------ .../source/telemetry-data-pipelines.rst | 2 +- .../source/telemetry-data-retrieval.rst | 2 +- doc/admin-guide/source/telemetry-events.rst | 2 +- .../source/telemetry-measurements.rst | 4 +- .../source/telemetry-system-architecture.rst | 2 +- .../telemetry-troubleshooting-guide.rst | 2 +- .../source/ts-no-emulator-x86-64.rst | 2 +- 29 files changed, 61 insertions(+), 72 deletions(-) diff --git a/doc/admin-guide/source/baremetal-multitenancy.rst b/doc/admin-guide/source/baremetal-multitenancy.rst index 61f7ad07a2..0eea6c44c9 100644 --- a/doc/admin-guide/source/baremetal-multitenancy.rst +++ b/doc/admin-guide/source/baremetal-multitenancy.rst @@ -49,7 +49,7 @@ To enable the Networking service ML2 driver, edit the param_3 = ... For more details, see -`Networking service mechanism drivers `__. +`Networking service mechanism drivers `__. Configure Bare Metal service ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/doc/admin-guide/source/blockstorage-volume-migration.rst b/doc/admin-guide/source/blockstorage-volume-migration.rst index e1537f8965..083a980318 100644 --- a/doc/admin-guide/source/blockstorage-volume-migration.rst +++ b/doc/admin-guide/source/blockstorage-volume-migration.rst @@ -25,7 +25,7 @@ These workflows are possible for a migration: .. note:: While most back ends support this function, not all do. See the `driver - documentation `__ + documentation `__ in the OpenStack Configuration Reference for more details. #. If the volume is attached to a VM instance, the Block Storage creates a diff --git a/doc/admin-guide/source/cli-cinder-quotas.rst b/doc/admin-guide/source/cli-cinder-quotas.rst index 87cec3344e..01c234c4a6 100644 --- a/doc/admin-guide/source/cli-cinder-quotas.rst +++ b/doc/admin-guide/source/cli-cinder-quotas.rst @@ -96,7 +96,7 @@ service quotas. update the property in the :guilabel:`cinder.quota` section of the ``/etc/cinder/cinder.conf`` file. For more information, see the `Block Storage service - `_ + `_ in OpenStack Configuration Reference. #. To update Block Storage service quotas for an existing project diff --git a/doc/admin-guide/source/compute-arch.rst b/doc/admin-guide/source/compute-arch.rst index 8535674300..5ed03801e6 100644 --- a/doc/admin-guide/source/compute-arch.rst +++ b/doc/admin-guide/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. Projects, users, and roles @@ -178,7 +178,7 @@ to keep ephemeral storage, depending on the flavor selected. In this 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 `Introduction to the -Block Storage service `_ +Block Storage service `_ in the OpenStack Configuration Reference. .. note:: diff --git a/doc/admin-guide/source/compute-cpu-topologies.rst b/doc/admin-guide/source/compute-cpu-topologies.rst index dc1d1f1356..4f947a99a5 100644 --- a/doc/admin-guide/source/compute-cpu-topologies.rst +++ b/doc/admin-guide/source/compute-cpu-topologies.rst @@ -306,7 +306,7 @@ For more information about image metadata, refer to the `Image metadata`_ guide. .. Links -.. _`Scheduling`: http://docs.openstack.org/mitaka/config-reference/compute/scheduler.html +.. _`Scheduling`: http://docs.openstack.org/newton/config-reference/compute/scheduler.html .. _`Flavors`: http://docs.openstack.org/admin-guide/compute-flavors.html .. _`Image metadata`: http://docs.openstack.org/image-guide/image-metadata.html .. _`discussion`: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090367.html diff --git a/doc/admin-guide/source/compute-flavors.rst b/doc/admin-guide/source/compute-flavors.rst index 0c2a5db749..b7599b2cef 100644 --- a/doc/admin-guide/source/compute-flavors.rst +++ b/doc/admin-guide/source/compute-flavors.rst @@ -522,6 +522,6 @@ PCI passthrough - ALIAS: (string) The alias which correspond to a particular PCI device class as configured in the nova configuration file (see `nova.conf - configuration options `_). + configuration options `_). - COUNT: (integer) The amount of PCI devices of type ALIAS to be assigned to a guest. diff --git a/doc/admin-guide/source/compute-images-instances.rst b/doc/admin-guide/source/compute-images-instances.rst index fc607e080c..eacd65c138 100644 --- a/doc/admin-guide/source/compute-images-instances.rst +++ b/doc/admin-guide/source/compute-images-instances.rst @@ -31,7 +31,7 @@ flavors that you can edit or add to. - For more information about image configuration options, see the `Image services - `__ + `__ section of the OpenStack Configuration Reference. - For more information about flavors, see :ref:`compute-flavors`. @@ -268,7 +268,7 @@ can also be used to set policies for Image service actions. To view a sample configuration file, see `glance-api.conf - `__. + `__. #. Optionally, in the ``glance-api.conf`` file, specify whether roles or policies are used in the property protections configuration file @@ -281,7 +281,7 @@ can also be used to set policies for Image service actions. To view a sample configuration file, see `glance-api.conf - `__. + `__. Image download: how it works ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -317,7 +317,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 ~~~~~~~~~~~~~~~~~~~~~~~~ @@ -414,7 +414,7 @@ Control where instances run ~~~~~~~~~~~~~~~~~~~~~~~~~~~ The `Scheduling section -`__ +`__ of OpenStack Configuration Reference provides detailed information on controlling where your instances run, including ensuring a set of instances run on different compute nodes for diff --git a/doc/admin-guide/source/compute-live-migration-usage.rst b/doc/admin-guide/source/compute-live-migration-usage.rst index d0f590655d..6c6a098d03 100644 --- a/doc/admin-guide/source/compute-live-migration-usage.rst +++ b/doc/admin-guide/source/compute-live-migration-usage.rst @@ -16,7 +16,7 @@ Before starting a migration, review the Configure migrations section. under the default Compute configuration options, the instances are suspended before migration. For more information, see `Configure migrations - `_. + `_. in the OpenStack Configuration Reference. **Migrating instances** diff --git a/doc/admin-guide/source/compute-manage-logs.rst b/doc/admin-guide/source/compute-manage-logs.rst index 03929e5c2e..55edb8b4b9 100644 --- a/doc/admin-guide/source/compute-manage-logs.rst +++ b/doc/admin-guide/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 of the ``logging.conf`` file with various defined handlers, see -the `OpenStack Configuration Reference `__. +the `OpenStack Configuration Reference `__. Syslog ~~~~~~ diff --git a/doc/admin-guide/source/compute-networking-nova.rst b/doc/admin-guide/source/compute-networking-nova.rst index a2bca41d0e..17ce87c10c 100644 --- a/doc/admin-guide/source/compute-networking-nova.rst +++ b/doc/admin-guide/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/source/compute-pci-passthrough.rst b/doc/admin-guide/source/compute-pci-passthrough.rst index 2ce4a72273..a7ecf5bf0c 100644 --- a/doc/admin-guide/source/compute-pci-passthrough.rst +++ b/doc/admin-guide/source/compute-pci-passthrough.rst @@ -140,8 +140,8 @@ the ``pci_alias`` from the flavor. # openstack server create --flavor m1.large --image cirros-0.3.4-x86_64-uec --wait test-pci .. Links -.. _`Create Virtual Functions`: http://docs.openstack.org/mitaka/networking-guide/adv-config-sriov.html#create-virtual-functions-compute -.. _`Configure nova-scheduler`: http://docs.openstack.org/mitaka/networking-guide/adv-config-sriov.html#configure-nova-scheduler-controller -.. _`nova.conf configuration options`: http://docs.openstack.org/mitaka/config-reference/compute/config-options.html +.. _`Create Virtual Functions`: http://docs.openstack.org/newton/networking-guide/config-sriov.html#create-virtual-functions-compute +.. _`Configure nova-scheduler`: http://docs.openstack.org/newton/networking-guide/config-sriov.html#configure-nova-scheduler-controller +.. _`nova.conf configuration options`: http://docs.openstack.org/newton/config-reference/compute/config-options.html .. _`flavor`: http://docs.openstack.org/admin-guide/compute-flavors.html -.. _`Networking Guide`: http://docs.openstack.org/mitaka/networking-guide/adv-config-sriov.html +.. _`Networking Guide`: http://docs.openstack.org/newton/networking-guide/config-sriov.html diff --git a/doc/admin-guide/source/dashboard-manage-host-aggregates.rst b/doc/admin-guide/source/dashboard-manage-host-aggregates.rst index adc5a4464c..7384179d3f 100644 --- a/doc/admin-guide/source/dashboard-manage-host-aggregates.rst +++ b/doc/admin-guide/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/admin-guide/source/database.rst b/doc/admin-guide/source/database.rst index 4df8042b86..a603eb29a1 100644 --- a/doc/admin-guide/source/database.rst +++ b/doc/admin-guide/source/database.rst @@ -23,7 +23,7 @@ configuration, patching, backups, restores, and monitoring. You can modify various cluster characteristics by editing the ``/etc/trove/trove.conf`` file. A comprehensive list of the Database service configuration options is described in the `Database service -`_ +`_ chapter in the *Configuration Reference*. Create a data store diff --git a/doc/admin-guide/source/networking-adv-features.rst b/doc/admin-guide/source/networking-adv-features.rst index 2365f71738..e0813024f8 100644 --- a/doc/admin-guide/source/networking-adv-features.rst +++ b/doc/admin-guide/source/networking-adv-features.rst @@ -180,7 +180,7 @@ routers can connect multiple L2 Networking networks and can also provide a gateway that connects one or more private L2 networks to a shared external network. For example, a public network for access to the Internet. See the `OpenStack Configuration Reference `_ for details on common +openstack.org/newton/config-reference/>`_ for details on common models of deploying Networking L3 routers. The L3 router provides basic NAT capabilities on gateway ports that diff --git a/doc/admin-guide/source/networking-config-agents.rst b/doc/admin-guide/source/networking-config-agents.rst index ce33939207..43434ac736 100644 --- a/doc/admin-guide/source/networking-config-agents.rst +++ b/doc/admin-guide/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 `__ +options `__ listed in the OpenStack Configuration Reference. DHCP agent setup: OVS plug-in @@ -404,7 +404,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 `__. +`instructions `__. **To install the OpenStack Networking Hyper-V agent and configure the node** @@ -430,7 +430,7 @@ correctly using these #. Create the ``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: + options `__. Here is a sample config file: .. code-block:: ini diff --git a/doc/admin-guide/source/networking-config-plugins.rst b/doc/admin-guide/source/networking-config-plugins.rst index 36985618c7..eec3ae9e41 100644 --- a/doc/admin-guide/source/networking-config-plugins.rst +++ b/doc/admin-guide/source/networking-config-plugins.rst @@ -3,7 +3,7 @@ Plug-in configurations ====================== For configurations options, see `Networking configuration -options `__ +options `__ in Configuration Reference. These sections explain how to configure specific plug-ins. @@ -31,7 +31,7 @@ Configure Big Switch (Floodlight REST Proxy) plug-in server = CONTROLLER_IP:PORT For database configuration, see `Install Networking - Services `__ + Services `__ in the Installation Guide in the `OpenStack Documentation index `__. (The link defaults to the Ubuntu version.) @@ -78,7 +78,7 @@ Configure Brocade plug-in ostype = NOS For database configuration, see `Install Networking - Services `__ + Services `__ in any of the Installation Guides in the `OpenStack Documentation index `__. (The link defaults to the Ubuntu version.) @@ -174,7 +174,7 @@ formerly known as Nicira NVP. NEUTRON_PLUGIN_CONFIG = /etc/neutron/plugins/vmware/nsx.ini For database configuration, see `Install Networking - Services `__ + Services `__ in the Installation Guide. #. Restart ``neutron-server`` to apply settings: @@ -237,7 +237,7 @@ Configure PLUMgrid plug-in password = "PLUMgrid-director-admin-password" For database configuration, see `Install Networking - Services `__ + Services `__ in the Installation Guide. #. Restart the ``neutron-server`` service to apply the settings: diff --git a/doc/admin-guide/source/networking-multi-dhcp-agents.rst b/doc/admin-guide/source/networking-multi-dhcp-agents.rst index 9cb00fd802..537e8878a6 100644 --- a/doc/admin-guide/source/networking-multi-dhcp-agents.rst +++ b/doc/admin-guide/source/networking-multi-dhcp-agents.rst @@ -3,4 +3,4 @@ Scalable and highly available DHCP agents ========================================= This section is fully described in the `Networking Guide -`_. +`_. diff --git a/doc/admin-guide/source/objectstorage-admin.rst b/doc/admin-guide/source/objectstorage-admin.rst index 2657101bce..b7390b47ca 100644 --- a/doc/admin-guide/source/objectstorage-admin.rst +++ b/doc/admin-guide/source/objectstorage-admin.rst @@ -7,5 +7,5 @@ administer your storage solution. The majority of the administration information is maintained in developer documentation at `docs.openstack.org/developer/swift/ `__. -See the `OpenStack Configuration Reference `__ +See the `OpenStack Configuration Reference `__ for a list of configuration options for Object Storage. diff --git a/doc/admin-guide/source/objectstorage-components.rst b/doc/admin-guide/source/objectstorage-components.rst index d39ea3313a..ef56638a44 100644 --- a/doc/admin-guide/source/objectstorage-components.rst +++ b/doc/admin-guide/source/objectstorage-components.rst @@ -49,7 +49,7 @@ take over. For more information concerning proxy server configuration, see `Configuration Reference -`_. +`_. Rings ----- diff --git a/doc/admin-guide/source/shared-file-systems-share-replication.rst b/doc/admin-guide/source/shared-file-systems-share-replication.rst index 8704a91b37..2ad47a629b 100644 --- a/doc/admin-guide/source/shared-file-systems-share-replication.rst +++ b/doc/admin-guide/source/shared-file-systems-share-replication.rst @@ -134,7 +134,7 @@ separate networks. The service network is reachable from the host where the ``manila-share`` service is running. The share export IP is from a network that allows user access. -See `Configuring the ZFSonLinux driver `_ +See `Configuring the ZFSonLinux driver `_ for information on how to set up the ZFSonLinux driver. diff --git a/doc/admin-guide/source/telemetry-alarms.rst b/doc/admin-guide/source/telemetry-alarms.rst index 782154ccf9..ed478c2cc4 100644 --- a/doc/admin-guide/source/telemetry-alarms.rst +++ b/doc/admin-guide/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/source/telemetry-data-collection.rst b/doc/admin-guide/source/telemetry-data-collection.rst index 238e0a840d..646449e2fe 100644 --- a/doc/admin-guide/source/telemetry-data-collection.rst +++ b/doc/admin-guide/source/telemetry-data-collection.rst @@ -88,7 +88,7 @@ types by each OpenStack service that Telemetry transforms into samples. image.send - The required configuration for Image service can be * - service found in - `Configure the Image service for Telemetry section `__ + `Configure the Image service for Telemetry `__ section in the OpenStack Installation Guide * - OpenStack Networking - floatingip.create.end @@ -171,8 +171,8 @@ types by each OpenStack service that Telemetry transforms into samples. volume.backup.restore.\ \* - The required configuration for Block Storage service can be found in the - `Add the Block Storage service agent for Telemetry section `__ - section in the OpenStack Installation Guide. + `Add the Block Storage service agent for Telemetry section `__ + in the OpenStack Installation Guide. .. note:: @@ -186,8 +186,8 @@ administrators and users. Configuring ``nova_notifications`` in the ``nova.conf`` file allows administrators to respond to events rapidly. For more information on configuring notifications for the compute service, see -`Telemetry services `__ in the +`Telemetry services `__ in the OpenStack Installation Guide. .. note:: @@ -209,7 +209,8 @@ information locally. A Compute agent instance has to be installed on each and every compute node, installation instructions can be found in the `Install the Compute agent for Telemetry -`__ +`__ section in the OpenStack Installation Guide. Just like the central agent, this component also does not need a direct @@ -241,7 +242,8 @@ meters are listed in :ref:`telemetry-object-storage-meter`, marked with The instructions on how to install this middleware can be found in `Configure the Object Storage service for Telemetry -`__ +`__ section in the OpenStack Installation Guide. Telemetry middleware @@ -339,7 +341,7 @@ The following services can be polled with this agent: framework To install and configure this service use the `Add the Telemetry service -`__ +`__ section in the OpenStack Installation Guide. The central agent does not need direct database connection. The samples @@ -414,7 +416,7 @@ Telemetry services. For information about the required configuration options that have to be set in the ``ceilometer.conf`` configuration file for both the central and Compute agents, see the `Coordination section -`__ +`__ in the OpenStack Configuration Reference. Notification agent HA deployment @@ -428,7 +430,7 @@ in a larger amount of load. To enable workload partitioning by notification agent, the ``backend_url`` option must be set in the ``ceilometer.conf`` configuration file. Additionally, ``workload_partitioning`` should be enabled in the -`Notification section `__ in the OpenStack Configuration Reference. +`Notification section `__ in the OpenStack Configuration Reference. .. note:: @@ -465,8 +467,8 @@ For backward compatibility and supporting existing deployments, the central agent configuration also supports using different configuration files for groups of service instances of this type that are running in parallel. For enabling this configuration set a value for the -``partitioning_group_prefix`` option in the `Central section -`__ +``partitioning_group_prefix`` option in the `polling section +`__ in the OpenStack Configuration Reference. .. warning:: @@ -481,7 +483,7 @@ in the OpenStack Configuration Reference. To enable the Compute agent to run multiple instances simultaneously with workload partitioning, the ``workload_partitioning`` option has to be set to ``True`` under the `Compute section -`__ +`__ in the ``ceilometer.conf`` configuration file. @@ -723,7 +725,7 @@ Multiple ``ceilometer-collector`` processes can be run at a time. It is also supported to start multiple worker threads per collector process. The ``collector_workers`` configuration option has to be modified in the `Collector section -`__ +`__ of the ``ceilometer.conf`` configuration file. Database dispatcher @@ -780,7 +782,7 @@ target. The samples are sent without any modification. To set this option as the collector's target, the ``dispatcher`` has to be changed to ``http`` in the ``ceilometer.conf`` configuration file. For the list of options that you need to set, see the see the `dispatcher_http -section `__ +section `__ in the OpenStack Configuration Reference. File dispatcher @@ -789,18 +791,5 @@ File dispatcher You can store samples in a file by setting the ``dispatcher`` option in the ``ceilometer.conf`` file. For the list of configuration options, see the `dispatcher_file section -`__ -in the OpenStack Configuration Reference. - -Gnocchi dispatcher ------------------- - -The Telemetry service supports sending the metering data to Gnocchi back end -through the gnocchi dispatcher. To set this option as the target, change the -``dispatcher`` to ``gnocchi`` in the ``ceilometer.conf`` -configuration file. - -For the list of options that you need to set, see the -`dispatcher_gnocchi section -`__ +`__ in the OpenStack Configuration Reference. diff --git a/doc/admin-guide/source/telemetry-data-pipelines.rst b/doc/admin-guide/source/telemetry-data-pipelines.rst index 32a5ee631b..ed774ab992 100644 --- a/doc/admin-guide/source/telemetry-data-pipelines.rst +++ b/doc/admin-guide/source/telemetry-data-pipelines.rst @@ -51,7 +51,7 @@ the ``ceilometer.conf`` file. The meter pipeline and event pipeline configuration files can be set by the ``pipeline_cfg_file`` and ``event_pipeline_cfg_file`` options listed in the `Description of configuration options for api table -`__ +`__ section in the OpenStack Configuration Reference respectively. Multiple pipelines can be defined in one pipeline configuration file. diff --git a/doc/admin-guide/source/telemetry-data-retrieval.rst b/doc/admin-guide/source/telemetry-data-retrieval.rst index 02b244e5d2..2e3dedaf9d 100644 --- a/doc/admin-guide/source/telemetry-data-retrieval.rst +++ b/doc/admin-guide/source/telemetry-data-retrieval.rst @@ -189,7 +189,7 @@ the requested operations. To be able to use the :command:`ceilometer` command, the python-ceilometerclient package needs to be installed and configured properly. For details about the installation process, see the `Telemetry -chapter `__ +chapter `__ in the OpenStack Installation Guide. .. note:: diff --git a/doc/admin-guide/source/telemetry-events.rst b/doc/admin-guide/source/telemetry-events.rst index 008916861b..17db976e0c 100644 --- a/doc/admin-guide/source/telemetry-events.rst +++ b/doc/admin-guide/source/telemetry-events.rst @@ -18,7 +18,7 @@ Event configuration To enable the creation and storage of events in the Telemetry service ``store_events`` option needs to be set to ``True``. For further configuration options, see the event section in the `OpenStack Configuration Reference -`__. +`__. .. note:: diff --git a/doc/admin-guide/source/telemetry-measurements.rst b/doc/admin-guide/source/telemetry-measurements.rst index 859d7c1e66..ee0d4709b4 100644 --- a/doc/admin-guide/source/telemetry-measurements.rst +++ b/doc/admin-guide/source/telemetry-measurements.rst @@ -20,7 +20,7 @@ below. You may need to configure Telemetry or other OpenStack services in order to be able to collect all the samples you need. For further information about configuration requirements see the `Telemetry chapter - `__ + `__ in the OpenStack Installation Guide. Also check the `Telemetry manual installation `__ description. @@ -450,7 +450,7 @@ the compute host machines. In order to use that you need to set the ``compute_monitors`` option to ``ComputeDriverCPUMonitor`` in the ``nova.conf`` configuration file. For further information see the Compute configuration section in the `Compute chapter -`__ +`__ of the OpenStack Configuration Reference. The following host machine related meters are collected for OpenStack diff --git a/doc/admin-guide/source/telemetry-system-architecture.rst b/doc/admin-guide/source/telemetry-system-architecture.rst index aa40344e84..fed63fa67f 100644 --- a/doc/admin-guide/source/telemetry-system-architecture.rst +++ b/doc/admin-guide/source/telemetry-system-architecture.rst @@ -156,7 +156,7 @@ Users, roles, and projects This service of OpenStack uses OpenStack Identity for authenticating and authorizing users. The required configuration options are listed in the `Telemetry -section `__ +section `__ in the OpenStack Configuration Reference. The system uses two roles:``admin`` and ``non-admin``. The authorization diff --git a/doc/admin-guide/source/telemetry-troubleshooting-guide.rst b/doc/admin-guide/source/telemetry-troubleshooting-guide.rst index 83751d135d..66111221d4 100644 --- a/doc/admin-guide/source/telemetry-troubleshooting-guide.rst +++ b/doc/admin-guide/source/telemetry-troubleshooting-guide.rst @@ -11,7 +11,7 @@ logging, the format of the log entries and the log levels. The log settings can be changed in ``ceilometer.conf``. The list of configuration options are listed in the logging configuration options table in the `Telemetry -section `__ +section `__ in the OpenStack Configuration Reference. By default ``stderr`` is used as standard output for the log messages. diff --git a/doc/admin-guide/source/ts-no-emulator-x86-64.rst b/doc/admin-guide/source/ts-no-emulator-x86-64.rst index 6bb3eae0ef..22cca43284 100644 --- a/doc/admin-guide/source/ts-no-emulator-x86-64.rst +++ b/doc/admin-guide/source/ts-no-emulator-x86-64.rst @@ -15,5 +15,5 @@ On the KVM host, run :command:`cat /proc/cpuinfo`. Make sure the ``vmx`` or ``svm`` flags are set. Follow the instructions in the `Enable KVM -`__ section in the OpenStack Configuration Reference to enable hardware +`__ section in the OpenStack Configuration Reference to enable hardware virtualization support in your BIOS.