openstack/operations-guide
Code Issues Proposed changes

Add part intro for ops

Browse Source 
This moves the old chapter 8 "What's next" to become a partintro
for the ops part.

Change-Id: I362d559a0c343bb625deb5fad61e1f8807a1a785
This commit is contained in:
Tom Fifield 2014-01-23 15:03:31 -05:00
parent aab12198af
commit e3c4fc02c3
3 changed files with 29 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
doc/openstack-ops/ch_arch_example.xml
View File

@ -340,32 +340,5 @@
(see <xref linkend="maintenance"/>).</para>
</listitem>
</itemizedlist>
<note><title>What's Next?</title>
<para>Congratulations! By now, you should have a solid design for
your cloud. We now recommend that you turn to the <link
xlink:title="OpenStack Install and Deploy Manual - Ubuntu"
xlink:href="http://docs.openstack.org/havana/install-guide/install/apt/"
>OpenStack Install and Deploy Manual - Ubuntu</link>
(http://docs.openstack.org/havana/install-guide/install/apt/),
which contains a step-by-step guide on how to manually install
the OpenStack packages and dependencies on your cloud.</para>
<para>While it is important for an operator to be familiar with
the steps involved in deploying OpenStack, we also strongly
encourage you to evaluate configuration management tools such
as <glossterm>Puppet</glossterm> or
<glossterm>Chef</glossterm> that can help automate this
deployment process.</para>
<para>In the remainder of the guide, we assume that you have
successfully deployed an OpenStack cloud and are able to
perform basic operations such as adding images, booting
instances, and attaching volumes.</para>
<para>As your focus turns to stable operations, we recommend you
do an initial skim of the remainder of the book to get a sense
of the content. Some of this content is useful to read in
advance, so that you can put best practices into effect to
simplify your life in the long run. Other content is more
useful as a reference that you might refer when an unexpected
event occurs, such a power failure or troubleshooting a
particular problem.</para></note>
</section>
</chapter>

3
doc/openstack-ops/ch_ops_lay_of_land.xml
View File

@ -12,8 +12,7 @@
xml:id="lay_of_the_land">
<?dbhtml stop-chunking?>
<title>Lay of the Land</title>
<para>From this point forward in the guide, we assume that you
have an OpenStack cloud up and running. This section helps you
<para>This section helps you
set up your working environment and use it to take a look
around your cloud.</para>
<section xml:id="cli_tools">

28
doc/openstack-ops/part_operations.xml
View File

@ -13,6 +13,34 @@
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
xml:id="operations">
<title>Operations</title>
<partintro xml:id="ops-partintro">
<para>Congratulations! By now, you should have a solid design for
your cloud. We now recommend that you turn to the <link
xlink:title="OpenStack Install and Deploy Manual - Ubuntu"
xlink:href="http://docs.openstack.org/havana/install-guide/install/apt/"
>OpenStack Install and Deploy Manual - Ubuntu</link>
(http://docs.openstack.org/havana/install-guide/install/apt/),
which contains a step-by-step guide on how to manually install
the OpenStack packages and dependencies on your cloud.</para>
<para>While it is important for an operator to be familiar with
the steps involved in deploying OpenStack, we also strongly
encourage you to evaluate configuration management tools such
as <glossterm>Puppet</glossterm> or
<glossterm>Chef</glossterm> that can help automate this
deployment process.</para>
<para>In the remainder of the guide, we assume that you have
successfully deployed an OpenStack cloud and are able to
perform basic operations such as adding images, booting
instances, and attaching volumes.</para>
<para>As your focus turns to stable operations, we recommend you
do an initial skim of the remainder of the book to get a sense
of the content. Some of this content is useful to read in
advance, so that you can put best practices into effect to
simplify your life in the long run. Other content is more
useful as a reference that you might refer when an unexpected
event occurs, such a power failure or troubleshooting a
particular problem.</para>
</partintro>
<xi:include href="ch_ops_lay_of_land.xml"/>
<xi:include href="ch_ops_projects_users.xml"/>
<xi:include href="ch_ops_user_facing.xml"/>