[admin-guide] Update links to newton
Change-Id: Id40467c27f18622f1c0849cefaacf7829dc8f13f
This commit is contained in:
chenxing
Olena Logvinova
parent
ffec085a7b
commit
d10f645e00
|
|
@ -49,7 +49,7 @@ To enable the Networking service ML2 driver, edit the
|
|||
param_3 = ...
|
||||
|
||||
For more details, see
|
||||
`Networking service mechanism drivers <http://docs.openstack.org/mitaka/networking-guide/config-ml2-plug-in.html#mechanism-drivers>`__.
|
||||
`Networking service mechanism drivers <http://docs.openstack.org/newton/networking-guide/config-ml2.html#mechanism-drivers>`__.
|
||||
|
||||
Configure Bare Metal service
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
|
|
|||
|
|
@ -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 <http://docs.openstack.org/mitaka/config-reference/block-storage/volume-drivers.html>`__
|
||||
documentation <http://docs.openstack.org/newton/config-reference/block-storage/volume-drivers.html>`__
|
||||
in the OpenStack Configuration Reference for more details.
|
||||
|
||||
#. If the volume is attached to a VM instance, the Block Storage creates a
|
||||
|
|
|
|||
|
|
@ -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
|
||||
<http://docs.openstack.org/mitaka/config-reference/block-storage.html>`_
|
||||
<http://docs.openstack.org/newton/config-reference/block-storage.html>`_
|
||||
in OpenStack Configuration Reference.
|
||||
|
||||
#. To update Block Storage service quotas for an existing project
|
||||
|
|
|
|||
|
|
@ -72,7 +72,7 @@ availability zones. Compute supports the following hypervisors:
|
|||
- `Xen <http://www.xen.org/support/documentation.html>`__
|
||||
|
||||
For more information about hypervisors, see the
|
||||
`Hypervisors <http://docs.openstack.org/mitaka/config-reference/compute/hypervisors.html>`__
|
||||
`Hypervisors <http://docs.openstack.org/newton/config-reference/compute/hypervisors.html>`__
|
||||
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 <http://docs.openstack.org/mitaka/config-reference/block-storage/block-storage-overview.html>`_
|
||||
Block Storage service <http://docs.openstack.org/newton/config-reference/block-storage/block-storage-overview.html>`_
|
||||
in the OpenStack Configuration Reference.
|
||||
|
||||
.. note::
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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 <http://docs.openstack.org/mitaka/config-reference/compute/config-options.html>`_).
|
||||
configuration options <http://docs.openstack.org/newton/config-reference/compute/config-options.html>`_).
|
||||
- COUNT: (integer) The amount of PCI devices of type ALIAS to be assigned
|
||||
to a guest.
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ flavors that you can edit or add to.
|
|||
|
||||
- For more information about image configuration options, see the
|
||||
`Image services
|
||||
<http://docs.openstack.org/mitaka/config-reference/image-service.html>`__
|
||||
<http://docs.openstack.org/newton/config-reference/image.html>`__
|
||||
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
|
||||
<http://docs.openstack.org/mitaka/config-reference/image-service/sample-configuration-files.html#glance-api-conf>`__.
|
||||
<http://docs.openstack.org/newton/config-reference/image/glance-api.conf.html>`__.
|
||||
|
||||
#. 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
|
||||
<http://docs.openstack.org/mitaka/config-reference/image-service/sample-configuration-files.html#glance-api-conf>`__.
|
||||
<http://docs.openstack.org/newton/config-reference/image/glance-api.conf.html>`__.
|
||||
|
||||
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 <http://docs.openstack.org/mitaka/config-reference/>`__.
|
||||
Reference <http://docs.openstack.org/newton/config-reference/>`__.
|
||||
|
||||
Instance building blocks
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
|
@ -414,7 +414,7 @@ Control where instances run
|
|||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
The `Scheduling section
|
||||
<http://docs.openstack.org/mitaka/config-reference/compute/scheduler.html>`__
|
||||
<http://docs.openstack.org/newton/config-reference/compute/scheduler.html>`__
|
||||
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
|
||||
|
|
|
|||
|
|
@ -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
|
||||
<http://docs.openstack.org/mitaka/config-reference/compute/config-options.html>`_.
|
||||
<http://docs.openstack.org/newton/config-reference/compute/config-options.html>`_.
|
||||
in the OpenStack Configuration Reference.
|
||||
|
||||
**Migrating instances**
|
||||
|
|
|
|||
|
|
@ -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 <http://docs.openstack.org/mitaka/config-reference/>`__.
|
||||
the `OpenStack Configuration Reference <http://docs.openstack.org/newton/config-reference/>`__.
|
||||
|
||||
Syslog
|
||||
~~~~~~
|
||||
|
|
|
|||
|
|
@ -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 <http://docs.openstack.org/mitaka/config-reference/>`__,
|
||||
Reference <http://docs.openstack.org/newton/config-reference/>`__,
|
||||
and `the dnsmasq
|
||||
documentation <http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq.conf.example>`__.
|
||||
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ multiple aggregates.
|
|||
|
||||
The scheduler uses this information to make scheduling decisions.
|
||||
For information, see
|
||||
`Scheduling <http://docs.openstack.org/mitaka/config-reference/compute/scheduler.html>`__.
|
||||
`Scheduling <http://docs.openstack.org/newton/config-reference/compute/scheduler.html>`__.
|
||||
|
||||
To create a host aggregate
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
|
|
|||
|
|
@ -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
|
||||
<http://docs.openstack.org/mitaka/config-reference/database-service.html>`_
|
||||
<http://docs.openstack.org/newton/config-reference/database.html>`_
|
||||
chapter in the *Configuration Reference*.
|
||||
|
||||
Create a data store
|
||||
|
|
|
|||
|
|
@ -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 <http://docs.
|
||||
openstack.org/mitaka/config-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
|
||||
|
|
|
|||
|
|
@ -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 <http://docs.openstack.org/mitaka/config-reference/networking/networking_options_reference.html#dhcp-agent>`__
|
||||
options <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#dhcp-agent>`__
|
||||
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 <http://docs.openstack.org/mitaka/config-reference/compute/hypervisor-hyper-v.html>`__.
|
||||
`instructions <http://docs.openstack.org/newton/config-reference/compute/hypervisor-hyper-v.html>`__.
|
||||
|
||||
**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 <http://docs.openstack.org/mitaka/config-reference/networking/networking_options_reference.html#cloudbase-hyper-v-agent-configuration-options>`__. Here is a sample config file:
|
||||
options <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html#cloudbase-hyper-v-agent-configuration-options>`__. Here is a sample config file:
|
||||
|
||||
.. code-block:: ini
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ Plug-in configurations
|
|||
======================
|
||||
|
||||
For configurations options, see `Networking configuration
|
||||
options <http://docs.openstack.org/mitaka/config-reference/networking/networking_options_reference.html>`__
|
||||
options <http://docs.openstack.org/newton/config-reference/networking/networking_options_reference.html>`__
|
||||
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 <http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-controller-install.html>`__
|
||||
Services <http://docs.openstack.org/newton/install-guide-ubuntu/neutron-controller-install.html>`__
|
||||
in the Installation Guide in the `OpenStack Documentation
|
||||
index <http://docs.openstack.org>`__. (The link defaults to the Ubuntu
|
||||
version.)
|
||||
|
|
@ -78,7 +78,7 @@ Configure Brocade plug-in
|
|||
ostype = NOS
|
||||
|
||||
For database configuration, see `Install Networking
|
||||
Services <http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-controller-install.html>`__
|
||||
Services <http://docs.openstack.org/newton/install-guide-ubuntu/neutron-controller-install.html>`__
|
||||
in any of the Installation Guides in the `OpenStack Documentation
|
||||
index <http://docs.openstack.org>`__. (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 <http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-controller-install.html>`__
|
||||
Services <http://docs.openstack.org/newton/install-guide-ubuntu/neutron-controller-install.html>`__
|
||||
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 <http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-controller-install.html>`__
|
||||
Services <http://docs.openstack.org/newton/install-guide-ubuntu/neutron-controller-install.html>`__
|
||||
in the Installation Guide.
|
||||
|
||||
#. Restart the ``neutron-server`` service to apply the settings:
|
||||
|
|
|
|||
|
|
@ -3,4 +3,4 @@ Scalable and highly available DHCP agents
|
|||
=========================================
|
||||
|
||||
This section is fully described in the `Networking Guide
|
||||
<http://docs.openstack.org/mitaka/networking-guide/misc-add-ha-for-dhcp.html>`_.
|
||||
<http://docs.openstack.org/newton/networking-guide/config-dhcp-ha.html>`_.
|
||||
|
|
|
|||
|
|
@ -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/ <http://docs.openstack.org/developer/swift/>`__.
|
||||
|
||||
See the `OpenStack Configuration Reference <http://docs.openstack.org/mitaka/config-reference/object-storage.html>`__
|
||||
See the `OpenStack Configuration Reference <http://docs.openstack.org/newton/config-reference/object-storage.html>`__
|
||||
for a list of configuration options for Object Storage.
|
||||
|
|
|
|||
|
|
@ -49,7 +49,7 @@ take over.
|
|||
|
||||
For more information concerning proxy server configuration, see
|
||||
`Configuration Reference
|
||||
<http://docs.openstack.org/mitaka/config-reference/object-storage/configure.html#proxy-server-configuration>`_.
|
||||
<http://docs.openstack.org/newton/config-reference/object-storage/proxy-server.html>`_.
|
||||
|
||||
Rings
|
||||
-----
|
||||
|
|
|
|||
|
|
@ -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 <http://docs.openstack.org/mitaka/config-reference/shared-file-systems/drivers/zfs-on-linux-driver.html>`_
|
||||
See `Configuring the ZFSonLinux driver <http://docs.openstack.org/newton/config-reference/shared-file-systems/drivers/zfs-on-linux-driver.html>`_
|
||||
for information on how to set up the ZFSonLinux driver.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -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 <http://docs.openstack.org/mitaka/config-reference/telemetry.html>`_.
|
||||
`OpenStack Configuration Reference <http://docs.openstack.org/newton/config-reference/telemetry.html>`_.
|
||||
|
||||
Using alarms
|
||||
~~~~~~~~~~~~
|
||||
|
|
|
|||
|
|
@ -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 <http://docs.openstack.org/mitaka/install-guide-ubuntu/ceilometer-glance.html>`__
|
||||
`Configure the Image service for Telemetry <http://docs.openstack.org/project-install-guide/telemetry/newton>`__
|
||||
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 <http://docs.openstack.org/mitaka/install-guide-ubuntu//ceilometer-cinder.html>`__
|
||||
section in the OpenStack Installation Guide.
|
||||
`Add the Block Storage service agent for Telemetry section <http://docs.openstack.org/project-install-guide/telemetry/newton/configure_services/cinder/install-cinder-ubuntu.html>`__
|
||||
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 <http://docs.openstack.org/
|
||||
mitaka/install-guide-ubuntu/ceilometer-nova.html>`__ in the
|
||||
`Telemetry services <http://docs.openstack.org/project-install-guide/
|
||||
telemetry/newton/configure_services/nova/install-nova-ubuntu.html>`__ 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
|
||||
<http://docs.openstack.org/mitaka/install-guide-ubuntu/ceilometer-nova.html>`__
|
||||
<http://docs.openstack.org/project-install-guide/
|
||||
telemetry/newton/configure_services/nova/install-nova-ubuntu.html>`__
|
||||
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
|
||||
<http://docs.openstack.org/mitaka/install-guide-ubuntu/ceilometer-swift.html>`__
|
||||
<http://docs.openstack.org/project-install-guide/
|
||||
telemetry/newton/configure_services/swift/install-swift-ubuntu.html>`__
|
||||
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
|
||||
<http://docs.openstack.org/mitaka/install-guide-ubuntu/ceilometer.html>`__
|
||||
<http://docs.openstack.org/project-install-guide/telemetry/newton/install-base-ubuntu.html>`__
|
||||
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
|
||||
<http://docs.openstack.org/mitaka/config-reference/telemetry/telemetry_service_config_opts.html>`__
|
||||
<http://docs.openstack.org/newton/config-reference/telemetry/telemetry-config-options.html>`__
|
||||
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 <http://docs.openstack.org/mitaka/config-reference/telemetry/telemetry_service_config_opts.html>`__ in the OpenStack Configuration Reference.
|
||||
`Notification section <http://docs.openstack.org/newton/config-reference/telemetry/telemetry-config-options.html>`__ 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
|
||||
<http://docs.openstack.org/mitaka/config-reference/telemetry/telemetry_service_config_opts.html>`__
|
||||
``partitioning_group_prefix`` option in the `polling section
|
||||
<http://docs.openstack.org/newton/config-reference/telemetry/telemetry-config-options.html>`__
|
||||
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
|
||||
<http://docs.openstack.org/mitaka/config-reference/telemetry/telemetry_service_config_opts.html>`__
|
||||
<http://docs.openstack.org/newton/config-reference/telemetry/telemetry-config-options.html>`__
|
||||
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
|
||||
<http://docs.openstack.org/mitaka/config-reference/telemetry/telemetry_service_config_opts.html>`__
|
||||
<http://docs.openstack.org/newton/config-reference/telemetry/telemetry-config-options.html>`__
|
||||
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 <http://docs.openstack.org/mitaka/config-reference/telemetry/telemetry_service_config_opts.html>`__
|
||||
section <http://docs.openstack.org/newton/config-reference/telemetry/telemetry-config-options.html>`__
|
||||
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
|
||||
<http://docs.openstack.org/mitaka/config-reference/telemetry/telemetry_service_config_opts.html>`__
|
||||
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
|
||||
<http://docs.openstack.org/mitaka/config-reference/telemetry/telemetry_service_config_opts.html>`__
|
||||
<http://docs.openstack.org/newton/config-reference/telemetry/telemetry-config-options.html>`__
|
||||
in the OpenStack Configuration Reference.
|
||||
|
|
|
|||
|
|
@ -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
|
||||
<http://docs.openstack.org/mitaka/config-reference/telemetry/telemetry_service_config_opts.html>`__
|
||||
<http://docs.openstack.org/newton/config-reference/telemetry/telemetry-config-options.html>`__
|
||||
section in the OpenStack Configuration Reference respectively. Multiple
|
||||
pipelines can be defined in one pipeline configuration file.
|
||||
|
||||
|
|
|
|||
|
|
@ -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 <http://docs.openstack.org/mitaka/install-guide-ubuntu/ceilometer.html>`__
|
||||
chapter <http://docs.openstack.org/project-install-guide/telemetry/newton/>`__
|
||||
in the OpenStack Installation Guide.
|
||||
|
||||
.. note::
|
||||
|
|
|
|||
|
|
@ -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
|
||||
<http://docs.openstack.org/mitaka/config-reference/telemetry.html>`__.
|
||||
<http://docs.openstack.org/newton/config-reference/telemetry.html>`__.
|
||||
|
||||
.. note::
|
||||
|
||||
|
|
|
|||
|
|
@ -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
|
||||
<http://docs.openstack.org/mitaka/install-guide-ubuntu/ceilometer.html>`__
|
||||
<http://docs.openstack.org/project-install-guide/telemetry/newton/>`__
|
||||
in the OpenStack Installation Guide. Also check the `Telemetry manual
|
||||
installation <http://docs.openstack.org/developer/ceilometer/install/manual.html>`__
|
||||
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
|
||||
<http://docs.openstack.org/mitaka/config-reference/compute/config-options.html>`__
|
||||
<http://docs.openstack.org/newton/config-reference/compute/config-options.html>`__
|
||||
of the OpenStack Configuration Reference.
|
||||
|
||||
The following host machine related meters are collected for OpenStack
|
||||
|
|
|
|||
|
|
@ -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 <http://docs.openstack.org/mitaka/config-reference/telemetry.html>`__
|
||||
section <http://docs.openstack.org/newton/config-reference/telemetry.html>`__
|
||||
in the OpenStack Configuration Reference.
|
||||
|
||||
The system uses two roles:``admin`` and ``non-admin``. The authorization
|
||||
|
|
|
|||
|
|
@ -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 <http://docs.openstack.org/mitaka/config-reference/telemetry.html>`__
|
||||
section <http://docs.openstack.org/newton/config-reference/telemetry.html>`__
|
||||
in the OpenStack Configuration Reference.
|
||||
|
||||
By default ``stderr`` is used as standard output for the log messages.
|
||||
|
|
|
|||
|
|
@ -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
|
||||
<http://docs.openstack.org/mitaka/config-reference/compute/hypervisor-kvm.html#enable-kvm>`__ section in the OpenStack Configuration Reference to enable hardware
|
||||
<http://docs.openstack.org/newton/config-reference/compute/hypervisor-kvm.html#enable-kvm>`__ section in the OpenStack Configuration Reference to enable hardware
|
||||
virtualization support in your BIOS.
|
||||
|
|
|
|||
Loading…
Reference in New Issue