[admin-cloud-guide] links update for Mitaka
Updates links to the versioned guides for mitaka (to Install guides and Config Reference) Change-Id: I2132ef1ecafd1f364dc9eb9a2d6420c95d22fadf
This commit is contained in:
parent
3c52d715d6
commit
2ddc924be8
|
@ -26,7 +26,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
|
||||
<http://docs.openstack.org/liberty/config-reference/content/>`__ for more
|
||||
<http://docs.openstack.org/mitaka/config-reference/>`__ for more
|
||||
details.
|
||||
|
||||
#. If the volume is attached to a VM instance, the Block Storage creates a
|
||||
|
|
|
@ -102,7 +102,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
|
||||
Configuration Reference <http://docs.openstack.org/liberty/config-reference/content/ch_configuring-openstack-block-storage.html>`_.
|
||||
Configuration Reference <http://docs.openstack.org/mitaka/config-reference/block-storage.html>`_.
|
||||
|
||||
#. To update Block Storage service quotas for an existing project (tenant)
|
||||
|
||||
|
|
|
@ -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/liberty/config-reference/content/ch_configuring-openstack-image-service.html>`__
|
||||
<http://docs.openstack.org/mitaka/config-reference/image-service.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/liberty/config-reference/content/section_glance-api.conf.html>`__.
|
||||
<http://docs.openstack.org/mitaka/config-reference/image-service/sample-configuration-files.html#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
|
||||
<http://docs.openstack.org/liberty/config-reference/content/section_glance-api.conf.html>`__.
|
||||
<http://docs.openstack.org/mitaka/config-reference/image-service/sample-configuration-files.html#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 <http://docs.openstack.org/liberty/config-reference/content/>`__.
|
||||
Reference <http://docs.openstack.org/mitaka/config-reference/>`__.
|
||||
|
||||
Instance building blocks
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
@ -414,7 +414,7 @@ Control where instances run
|
|||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
The `OpenStack Configuration
|
||||
Reference <http://docs.openstack.org/liberty/config-reference/content/>`__
|
||||
Reference <http://docs.openstack.org/mitaka/config-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
|
||||
|
|
|
@ -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/liberty/config-reference/content/list-of-compute-config-options.html>`_.
|
||||
<http://docs.openstack.org/mitaka/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/liberty/config-reference/content/>`__.
|
||||
the `OpenStack Configuration Reference <http://docs.openstack.org/mitaka/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/liberty/config-reference/content/>`__,
|
||||
Reference <http://docs.openstack.org/mitaka/config-reference/>`__,
|
||||
and `the dnsmasq
|
||||
documentation <http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq.conf.example>`__.
|
||||
|
||||
|
|
|
@ -79,10 +79,6 @@ node for the ZooKeeper driver:
|
|||
[zookeeper]
|
||||
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 <http://docs.openstack.org/liberty/config-reference/
|
||||
content/list-of-compute-config-options.html#config_table_nova_zookeeper>`_.
|
||||
|
||||
.. _memcache-servicegroup-driver:
|
||||
|
||||
Memcache ServiceGroup driver
|
||||
|
|
|
@ -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/liberty/config-reference/content/section_compute-hypervisors.html>`__
|
||||
`Hypervisors <http://docs.openstack.org/mitaka/config-reference/compute/hypervisors.html>`__
|
||||
section in the OpenStack Configuration Reference.
|
||||
|
||||
Tenants, users, and roles
|
||||
|
@ -139,7 +139,7 @@ ephemeral volume is defined by the flavor of an instance.
|
|||
|
||||
In addition to the ephemeral root volume, all default types of flavors,
|
||||
except ``m1.tiny``, which is the smallest one, provide an additional
|
||||
ephemeral block device sized between 20 and 160 GB (a configurable value
|
||||
ephemeral block device sized between 20 and 160 GB (a configurable value
|
||||
to suit an environment). It is represented as a raw block device with no
|
||||
partition table or file system. A cloud-aware operating system can
|
||||
discover, format, and mount such a storage device. OpenStack Compute
|
||||
|
@ -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
|
||||
<http://docs.openstack.org/liberty/config-reference/content/>`__.
|
||||
<http://docs.openstack.org/mitaka/config-reference/>`__.
|
||||
|
||||
.. note::
|
||||
|
||||
|
@ -194,10 +194,7 @@ EC2 compatibility API
|
|||
~~~~~~~~~~~~~~~~~~~~~
|
||||
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 <http://docs.openstack.org/liberty/config-reference/content/
|
||||
configuring-ec2-api.html>`__.
|
||||
to work with OpenStack.
|
||||
|
||||
.. warning::
|
||||
|
||||
|
|
|
@ -25,7 +25,7 @@ security advisory below for more information.
|
|||
not covered by this document. For those, please refer to their respective
|
||||
implementations:
|
||||
|
||||
* `CORS in Object Storage <http://docs.openstack.org/liberty/config-reference/content/object-storage-cores.html>`_
|
||||
* `CORS in Object Storage <http://docs.openstack.org/mitaka/config-reference/object-storage/cors.html>`_
|
||||
* `CORS in dashboard <http://docs.openstack.org/security-guide/dashboard/cross-origin-resource-sharing-cors.html>`_
|
||||
|
||||
|
||||
|
|
|
@ -11,7 +11,7 @@ multiple aggregates.
|
|||
|
||||
The scheduler uses this information to make scheduling decisions.
|
||||
For information, see
|
||||
`Scheduling <http://docs.openstack.org/liberty/config-reference/content/section_compute-scheduler.html>`__.
|
||||
`Scheduling <http://docs.openstack.org/mitaka/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/liberty/config-reference/content/ch_configuring-trove.html>`_
|
||||
<http://docs.openstack.org/mitaka/config-reference/database-service.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/liberty/config-reference/content>`_ for details on common
|
||||
openstack.org/mitaka/config-reference/>`_ for details on common
|
||||
models of deploying Networking L3 routers.
|
||||
|
||||
The L3 router provides basic NAT capabilities on gateway ports that
|
||||
|
|
|
@ -122,8 +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/liberty/config-reference/content/networking
|
||||
-options-dhcp.html>`__
|
||||
options <http://docs.openstack.org/mitaka/config-reference/networking/networking_options_reference.html#dhcp-agent>`__
|
||||
listed in the OpenStack Configuration Reference.
|
||||
|
||||
DHCP agent setup: OVS plug-in
|
||||
|
@ -423,8 +422,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/liberty/config-reference/content/
|
||||
hyper-v-virtualization-platform.html>`__.
|
||||
`instructions <http://docs.openstack.org/mitaka/config-reference/compute/hypervisor-hyper-v.html>`__.
|
||||
|
||||
**To install the OpenStack Networking Hyper-V agent and configure the node**
|
||||
|
||||
|
@ -450,8 +448,7 @@ hyper-v-virtualization-platform.html>`__.
|
|||
|
||||
#. 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/liberty/config-reference/content/
|
||||
networking-plugin-hyperv_agent.html>`__. Here is a sample config file:
|
||||
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:
|
||||
|
||||
.. code-block:: ini
|
||||
|
||||
|
|
|
@ -3,8 +3,7 @@ Plug-in configurations
|
|||
======================
|
||||
|
||||
For configurations options, see `Networking configuration
|
||||
options <http://docs.openstack.org/liberty/config-reference
|
||||
/content/section_networking-options-reference.html>`__
|
||||
options <http://docs.openstack.org/mitaka/config-reference/networking/networking_options_reference.html>`__
|
||||
in Configuration Reference. These sections explain how to configure
|
||||
specific plug-ins.
|
||||
|
||||
|
@ -32,8 +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/liberty/install-guide-ubuntu
|
||||
/neutron-controller-install.html>`__
|
||||
Services <http://docs.openstack.org/mitaka/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.)
|
||||
|
@ -80,8 +78,7 @@ Configure Brocade plug-in
|
|||
ostype = NOS
|
||||
|
||||
For database configuration, see `Install Networking
|
||||
Services <http://docs.openstack.org/liberty/install-guide-ubuntu/
|
||||
neutron-controller-install.html>`__
|
||||
Services <http://docs.openstack.org/mitaka/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.)
|
||||
|
@ -177,8 +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/liberty/install-guide-ubuntu/
|
||||
neutron-controller-install.html>`__
|
||||
Services <http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-controller-install.html>`__
|
||||
in the Installation Guide.
|
||||
|
||||
#. Restart ``neutron-server`` to apply settings:
|
||||
|
@ -241,8 +237,7 @@ Configure PLUMgrid plug-in
|
|||
password = "PLUMgrid-director-admin-password"
|
||||
|
||||
For database configuration, see `Install Networking
|
||||
Services <http://docs.openstack.org/liberty/install-guide-ubuntu/
|
||||
neutron-controller-install.html>`__
|
||||
Services <http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-controller-install.html>`__
|
||||
in the Installation Guide.
|
||||
|
||||
#. Restart the ``neutron-server`` service to apply the settings:
|
||||
|
|
|
@ -7,6 +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/liberty/config-reference/content/ch_configuring-object-storage.html>`__
|
||||
See the `OpenStack Configuration Reference <http://docs.openstack.org/mitaka/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/liberty/config-reference/content/proxy-server-configuration.html>`_.
|
||||
<http://docs.openstack.org/mitaka/config-reference/object-storage/configure.html#proxy-server-configuration>`_.
|
||||
|
||||
Rings
|
||||
-----
|
||||
|
|
|
@ -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/liberty/config-reference/content/ch_configuring-openstack-telemetry.html>`_.
|
||||
`OpenStack Configuration Reference <http://docs.openstack.org/mitaka/config-reference/telemetry.html>`_.
|
||||
|
||||
Using alarms
|
||||
~~~~~~~~~~~~
|
||||
|
|
|
@ -75,7 +75,7 @@ each OpenStack service that are transformed to samples by Telemetry.
|
|||
| | image.upload | found in `Configure the Image |
|
||||
| | | service for Telemetry section |
|
||||
| | image.delete | <http://docs.openstack.org |
|
||||
| | | /liberty/install-guide-ubuntu |
|
||||
| | | /mitaka/install-guide-ubuntu |
|
||||
| | image.send | /ceilometer-glance.html>`__ |
|
||||
| | | section in the OpenStack |
|
||||
| | | Installation Guide |
|
||||
|
@ -132,7 +132,7 @@ each OpenStack service that are transformed to samples by Telemetry.
|
|||
| | volume.create.\* | be found in the `Add the |
|
||||
| | | Block Storage service agent |
|
||||
| | volume.delete.\* | for Telemetry section <http: |
|
||||
| | | //docs.openstack.org/liberty/ |
|
||||
| | | //docs.openstack.org/mitaka/ |
|
||||
| | volume.update.\* | install-guide-ubuntu/ |
|
||||
| | | /ceilometer-cinder.html>`__ |
|
||||
| | volume.resize.\* | section in the |
|
||||
|
@ -172,7 +172,7 @@ administrators and users. Configuring ``nova_notifications`` in the
|
|||
rapidly. For more information on configuring notifications for the
|
||||
compute service, see
|
||||
`Telemetry services <http://docs.openstack.org/
|
||||
liberty/install-guide-ubuntu/ceilometer-nova.html>`__ in the
|
||||
mitaka/install-guide-ubuntu/ceilometer-nova.html>`__ in the
|
||||
OpenStack Installation Guide.
|
||||
|
||||
.. note::
|
||||
|
@ -193,7 +193,7 @@ 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/liberty/install-guide-ubuntu/ceilometer-swift.html>`__
|
||||
<http://docs.openstack.org/mitaka/install-guide-ubuntu/ceilometer-swift.html>`__
|
||||
section in the OpenStack Installation Guide.
|
||||
|
||||
Telemetry middleware
|
||||
|
@ -291,7 +291,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/liberty/install-guide-ubuntu/ceilometer.html>`__
|
||||
<http://docs.openstack.org/mitaka/install-guide-ubuntu/ceilometer.html>`__
|
||||
section in the OpenStack Installation Guide.
|
||||
|
||||
The central agent does not need direct database connection. The samples
|
||||
|
@ -316,7 +316,7 @@ information.
|
|||
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/liberty/install-guide-ubuntu/ceilometer-nova.html>`__
|
||||
<http://docs.openstack.org/mitaka/install-guide-ubuntu/ceilometer-nova.html>`__
|
||||
section in the OpenStack Installation Guide.
|
||||
|
||||
Just like the central agent, this component also does not need a direct
|
||||
|
@ -399,7 +399,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/liberty/config-reference/content/ch_configuring-openstack-telemetry.html>`__
|
||||
<http://docs.openstack.org/mitaka/config-reference/telemetry/telemetry_service_config_opts.html>`__
|
||||
in the OpenStack Configuration Reference.
|
||||
|
||||
Notification agent HA deployment
|
||||
|
@ -413,7 +413,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/liberty/config-reference/content/ch_configuring-openstack-telemetry.html>`__ in the OpenStack Configuration Reference.
|
||||
`Notification section <http://docs.openstack.org/mitaka/config-reference/telemetry/telemetry_service_config_opts.html>`__ in the OpenStack Configuration Reference.
|
||||
|
||||
.. note::
|
||||
|
||||
|
@ -451,7 +451,7 @@ 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/liberty/config-reference/content/ch_configuring-openstack-telemetry.html>`__
|
||||
<http://docs.openstack.org/mitaka/config-reference/telemetry/telemetry_service_config_opts.html>`__
|
||||
in the OpenStack Configuration Reference.
|
||||
|
||||
.. warning::
|
||||
|
@ -466,7 +466,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/liberty/config-reference/content/ch_configuring-openstack-telemetry.html>`__
|
||||
<http://docs.openstack.org/mitaka/config-reference/telemetry/telemetry_service_config_opts.html>`__
|
||||
in the ``ceilometer.conf`` configuration file.
|
||||
|
||||
|
||||
|
@ -583,7 +583,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/liberty/config-reference/content/ch_configuring-openstack-telemetry.html>`__
|
||||
<http://docs.openstack.org/mitaka/config-reference/telemetry/telemetry_service_config_opts.html>`__
|
||||
section in the OpenStack Configuration Reference respectively. Multiple
|
||||
pipelines can be defined in one pipeline configuration file.
|
||||
|
||||
|
@ -1085,7 +1085,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/liberty/config-reference/content/ch_configuring-openstack-telemetry.html>`__
|
||||
<http://docs.openstack.org/mitaka/config-reference/telemetry/telemetry_service_config_opts.html>`__
|
||||
of the ``ceilometer.conf`` configuration file.
|
||||
|
||||
Database dispatcher
|
||||
|
@ -1138,7 +1138,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/liberty/config-reference/content/ch_configuring-openstack-telemetry.html>`__
|
||||
section <http://docs.openstack.org/mitaka/config-reference/telemetry/telemetry_service_config_opts.html>`__
|
||||
in the OpenStack Configuration Reference.
|
||||
|
||||
File dispatcher
|
||||
|
@ -1147,7 +1147,7 @@ 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/liberty/config-reference/content/ch_configuring-openstack-telemetry.html>`__
|
||||
<http://docs.openstack.org/mitaka/config-reference/telemetry/telemetry_service_config_opts.html>`__
|
||||
in the OpenStack Configuration Reference.
|
||||
|
||||
Gnocchi dispatcher
|
||||
|
@ -1160,5 +1160,5 @@ configuration file.
|
|||
|
||||
For the list of options that you need to set, see the
|
||||
`dispatcher_gnocchi section
|
||||
<http://docs.openstack.org/liberty/config-reference/content/ch_configuring-openstack-telemetry.html>`__
|
||||
<http://docs.openstack.org/mitaka/config-reference/telemetry/telemetry_service_config_opts.html>`__
|
||||
in the OpenStack Configuration Reference.
|
||||
|
|
|
@ -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/liberty/install-guide-ubuntu/ceilometer.html>`__
|
||||
chapter <http://docs.openstack.org/mitaka/install-guide-ubuntu/ceilometer.html>`__
|
||||
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/liberty/config-reference/content/ch_configuring-openstack-telemetry.html>`__.
|
||||
<http://docs.openstack.org/mitaka/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/liberty/install-guide-ubuntu/ceilometer.html>`__
|
||||
<http://docs.openstack.org/mitaka/install-guide-ubuntu/ceilometer.html>`__
|
||||
in the OpenStack Installation Guide. Also check the `Telemetry manual
|
||||
installation <http://docs.openstack.org/developer/ceilometer/install/manual.html>`__
|
||||
description.
|
||||
|
@ -424,7 +424,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/liberty/config-reference/content/list-of-compute-config-options.html>`__
|
||||
<http://docs.openstack.org/mitaka/config-reference/compute/config-options.html>`__
|
||||
of the OpenStack Configuration Reference.
|
||||
|
||||
The following host machine related meters are collected for OpenStack
|
||||
|
|
|
@ -156,8 +156,8 @@ Users, roles, and tenants
|
|||
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/liberty/config-reference/content/ch_configuring-openstack-telemetry.html>`__
|
||||
in the *OpenStack Configuration Reference*.
|
||||
section <http://docs.openstack.org/mitaka/config-reference/telemetry.html>`__
|
||||
in the OpenStack Configuration Reference.
|
||||
|
||||
The system uses two roles:``admin`` and ``non-admin``. The authorization
|
||||
happens before processing each API request. The amount of returned data
|
||||
|
|
|
@ -11,8 +11,8 @@ 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/liberty/config-reference/content/ch_configuring-openstack-telemetry.html>`__
|
||||
in the *OpenStack Configuration Reference*.
|
||||
section <http://docs.openstack.org/mitaka/config-reference/telemetry.html>`__
|
||||
in the OpenStack Configuration Reference.
|
||||
|
||||
By default ``stderr`` is used as standard output for the log messages.
|
||||
It can be changed to either a log file or syslog. The ``debug`` and
|
||||
|
|
|
@ -14,7 +14,6 @@ Solution
|
|||
On the KVM host, run :command:`cat /proc/cpuinfo`. Make sure the ``vmx`` or
|
||||
``svm`` flags are set.
|
||||
|
||||
Follow the instructions in the `enabling KVM
|
||||
section <http://docs.openstack.org/liberty/config-reference/content/kvm.html#section_kvm_enable>`__
|
||||
of the Configuration Reference to enable hardware virtualization support
|
||||
in your BIOS.
|
||||
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
|
||||
virtualization support in your BIOS.
|
||||
|
|
Loading…
Reference in New Issue