Underline should match the title length in docs
According to the openstack contributer guide, the underlines in an rst file should be of the same length as that of the heading text to follow rst formatting conventions. http://docs.openstack.org/contributor-guide/rst-conv/titles.html Change-Id: I186abdfd87bc1e26fb822412b7335b1c42c25b25 Signed-off-by: Asha Saravanamohan <assarava@cisco.com>
This commit is contained in:
parent
0f9534bc23
commit
a109c7473f
@ -30,7 +30,7 @@ Basics
|
||||
.. _here: https://wiki.openstack.org/wiki/GitCommitMessages
|
||||
|
||||
Development Environment
|
||||
========================
|
||||
=======================
|
||||
|
||||
#. Please follow our `quickstart`_ to deploy your environment and test your
|
||||
changes.
|
||||
|
@ -35,7 +35,7 @@ Note: This step is necessary until the default Kibana dashboard is implemented
|
||||
in Kolla.
|
||||
|
||||
Search logs - Discover tab
|
||||
===========================
|
||||
==========================
|
||||
|
||||
Logs search is available under Discover tab. In the menu on the left side,
|
||||
one can choose any field that will be included in a new search. To do this,
|
||||
@ -85,7 +85,7 @@ If a Dashboard has already been saved, it can be opened by choosing *open
|
||||
dashboard* option in the menu on the right.
|
||||
|
||||
Exporting and importing created items - Settings tab
|
||||
=====================================================
|
||||
====================================================
|
||||
|
||||
Once visualizations, searches or dashboards are created, they can be exported
|
||||
to a json format by choosing Settings tab and then Objects tab. Each of the
|
||||
|
@ -321,7 +321,7 @@ For more information refer to
|
||||
`_bug 1562334 <https://bugs.launchpad.net/kolla/+bug/1562334>`__.
|
||||
|
||||
Building Container Images
|
||||
==========================
|
||||
=========================
|
||||
|
||||
The Kolla community builds and pushes tested images for each tagged release of
|
||||
Kolla, but if running from master, it is recommended to build images locally.
|
||||
@ -441,7 +441,7 @@ the local registry is operating on IP address 192.168.1.100 and the port 4000.
|
||||
|
||||
For *all-in-one* deploys, the following commands can be run. These will
|
||||
setup all of the containers on the localhost. These commands will be
|
||||
wrapped in the kolla-script in the future.
|
||||
wrapped in the kolla-script in the future.
|
||||
|
||||
.. note:: even for all-in-one installs it is possible to use the docker
|
||||
registry for deployment, although not strictly required.
|
||||
@ -512,7 +512,7 @@ available by entering IP address or hostname from ``kolla_external_fqdn``, or
|
||||
default to ``kolla_internal_vip_address``.
|
||||
|
||||
Useful tools
|
||||
-------------
|
||||
------------
|
||||
After successful deployment of OpenStack, run the following command can create
|
||||
an openrc file ``/etc/kolla/admin-openrc.sh`` on the deploy node. Or view
|
||||
``tools/openrc-example`` for an example of an openrc that may be used with the
|
||||
|
Loading…
Reference in New Issue
Block a user