e3c4fc02c3
This moves the old chapter 8 "What's next" to become a partintro for the ops part. Change-Id: I362d559a0c343bb625deb5fad61e1f8807a1a785
56 lines
2.8 KiB
XML
56 lines
2.8 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE chapter [
|
|
<!-- Some useful entities borrowed from HTML -->
|
|
<!ENTITY ndash "–">
|
|
<!ENTITY mdash "—">
|
|
<!ENTITY hellip "…">
|
|
<!ENTITY plusmn "±">
|
|
|
|
|
|
]>
|
|
<part xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
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"/>
|
|
<xi:include href="ch_ops_maintenance.xml"/>
|
|
<xi:include href="ch_ops_network_troubleshooting.xml"/>
|
|
<xi:include href="ch_ops_log_monitor.xml"/>
|
|
<xi:include href="ch_ops_backup_recovery.xml"/>
|
|
<xi:include href="ch_ops_customize.xml"/>
|
|
<xi:include href="ch_ops_upstream.xml"/>
|
|
<xi:include href="ch_ops_advanced_configuration.xml"/>
|
|
|
|
</part>
|