Merge "Updating and adding links to Cloud Admin .rst files"
This commit is contained in:
commit
67d65b0321
@ -2,10 +2,6 @@
|
||||
Images and instances
|
||||
====================
|
||||
|
||||
.. TODO (bmoss)
|
||||
|
||||
instance-scheduling-constraints.rst
|
||||
|
||||
|
||||
Disk images provide templates for virtual machine file systems. The
|
||||
Image service controls storage and management of images.
|
||||
|
@ -635,7 +635,7 @@ Managing the cloud with euca2ools
|
||||
|
||||
The ``euca2ools`` command-line tool provides a command line interface to
|
||||
EC2 API calls. For more information about ``euca2ools``, see
|
||||
`http://open.eucalyptus.com/wiki/Euca2oolsGuide\_v1.3 <http://open.eucalyptus.com/wiki/Euca2oolsGuide_v1.3>`__.
|
||||
`https://www.eucalyptus.com/docs/eucalyptus/4.1.2/index.html <https://www.eucalyptus.com/docs/eucalyptus/4.1.2/index.html>`__.
|
||||
|
||||
.. TODOcommon/cli_nova_usage_statistics.rst
|
||||
|
||||
|
@ -20,9 +20,7 @@ assignments in LDAP.
|
||||
|
||||
For OpenStack Identity assignments to access LDAP servers, you must
|
||||
define the destination LDAP server in the :file:`keystone.conf` file.
|
||||
For more information, see ?.
|
||||
|
||||
.. TODO (DC) Add link to keystone_integrate_identity_with_ldap.rst
|
||||
For more information, see :ref:`integrate-identity-with-ldap`.
|
||||
|
||||
**Integrating assignment back ends with LDAP**
|
||||
|
||||
|
@ -9,9 +9,7 @@ administrators to use users and groups in LDAP.
|
||||
|
||||
For OpenStack Identity service to access LDAP servers, you must
|
||||
define the destination LDAP server in the ``keystone.conf`` file.
|
||||
For more information, see Integrate Identity with LDAP.
|
||||
|
||||
.. TODO (DC) Add link to keystone_integrate_identity_with_ldap.rst
|
||||
For more information, see :ref:`integrate-identity-with-ldap`.
|
||||
|
||||
**Integrating an Identity back end with LDAP**
|
||||
|
||||
|
@ -171,7 +171,5 @@ before processing each API request. The amount of returned data depends on the
|
||||
role the requestor owns.
|
||||
|
||||
The creation of alarm definitions also highly depends on the role of the
|
||||
user, who initiated the action. Further details about alarm handling can
|
||||
be found in this guide.
|
||||
|
||||
.. TODO: (karenb) Add reference to telemetry-alarms.
|
||||
user, who initiated the action. Further details about :ref:`telemetry-alarms`
|
||||
handling can be found in this guide.
|
||||
|
Loading…
x
Reference in New Issue
Block a user