Edited note admonitions

Made all notes (except note referencing the draft version) into standard
paragraphs.

Change-Id: I4cf643ca043a626351b50d19c0ddada1afa83a6c
Closes-Bug: #1494558
This commit is contained in:
Deena 2015-09-11 17:17:24 +10:00
parent 417752ef96
commit 84a3af34d7
1 changed files with 15 additions and 23 deletions

View File

@ -10,32 +10,24 @@ Basic environment
version <http://docs.openstack.org>`__ of this guide instead.
This section explains how to configure each node in the
:ref:`overview-example-architectures`,
including the two-node architecture with legacy
networking :ref:`figure-legacy-network-hw`
and three-node architecture with OpenStack Networking
(neutron) :ref:`figure-neutron-network-hw`.
:ref:`overview-example-architectures`, including the two-node architecture
with legacy networking :ref:`figure-legacy-network-hw` and three-node
architecture with OpenStack Networking (neutron)
:ref:`figure-neutron-network-hw`.
.. note::
Although most environments include Identity, Image service, Compute, at least
one networking service, and the dashboard, the Object Storage service can
operate independently. If your use case only involves Object Storage, you can
skip to :ref:`swift` after configuring the appropriate nodes for it. However,
the dashboard requires at least the Image service and Compute.
Although most environments include Identity, Image service, Compute,
at least one networking service, and the dashboard, the Object
Storage service can operate independently. If your use case only
involves Object Storage, you can skip to :ref:`swift` after
configuring the appropriate nodes for it. However, the dashboard requires at
least the Image service and Compute.
You must use an account with administrative privileges to configure each node.
Either run the commands as the ``root`` user or configure the ``sudo``
utility.
.. note::
You must use an account with administrative privileges to configure
each node. Either run the commands as the ``root`` user or configure
the ``sudo`` utility.
.. note::
The :command:`systemctl enable` call on openSUSE outputs a warning message
when the service uses SysV Init scripts instead of native systemd
files. This warning can be ignored.
The :command:`systemctl enable` call on openSUSE outputs a warning message
when the service uses SysV Init scripts instead of native systemd files. This
warning can be ignored.
Before you begin