From 8816354a58d2199de58fbafa959953e5de9871b7 Mon Sep 17 00:00:00 2001 From: Andreas Jaeger Date: Wed, 22 Apr 2015 20:50:54 +0200 Subject: [PATCH] FirstApp: Edits section9 Wrap overlong lines, follow markup conventions. Change-Id: I0e59d511cdfdcb039a45e295f78b5d4f211301d2 --- openstack-firstapp/doc/source/section9.rst | 77 +++++++++++++--------- 1 file changed, 45 insertions(+), 32 deletions(-) diff --git a/openstack-firstapp/doc/source/section9.rst b/openstack-firstapp/doc/source/section9.rst index d64d45ffb..50d40dcf6 100644 --- a/openstack-firstapp/doc/source/section9.rst +++ b/openstack-firstapp/doc/source/section9.rst @@ -1,60 +1,73 @@ -========================= -Section Nine: Going Crazy -========================= +=========== +Going crazy +=========== -In this section, we will look at further options for expanding the sample application. +This section explores options for expanding the sample application. Regions and geographic diversity --------------------------------- +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.. note:: For more information on multi-site clouds, check out the `Multi-Site chapter `_ of the Architecture Design Guide. +.. note:: For more information about multi-site clouds, see the + `Multi-Site chapter + `_ + in the Architecture Design Guide. -OpenStack supports the concepts of 'Regions' - ususally geographicaly separated installations that are -all connected to the one service catalogue. This section explains how to expand the Fractal app to -to use multiple regions for high availability. +OpenStack supports 'regions', which are geographically-separated installations +that are connected to a single service catalog. This section explains how to +expand the Fractal application to use multiple regions for high availability. .. note:: This section is incomplete. Please help us finish it! Multiple clouds ---------------- +~~~~~~~~~~~~~~~ -.. note:: For more information on hybrid-clouds, check out the `Hybrid Cloud chapter `_ of the Architecture Design Guide +.. note:: For more information about hybrid clouds, see the `Hybrid + Cloud chapter + `_ + in the Architecture Design Guide. -Sometimes, you want to use multiple clouds, such as a private cloud inside your organisation -and a public cloud. This section attempts to do exactly that. +You might want to use multiple clouds such as a private cloud inside your +organization and a public cloud. This section attempts to do exactly that. .. note:: This section is incomplete. Please help us finish it! -High Availability ------------------ +High availability +~~~~~~~~~~~~~~~~~ + Using Pacemaker to look at the API. .. note:: This section is incomplete. Please help us finish it! conf.d, etc.d -------------- +~~~~~~~~~~~~~ + Use conf.d and etc.d. -In earlier sections, the Fractal Application uses an install script, with parameters passed in from the metadata API, -in order to bootstrap the cluster. `Etcd `_ is a "a distributed, consistent key value store for shared configuration and service discovery" -that can be used for storing configuration. Updated versions of the Fractal worker -component could be writted to connect to Etcd, or use `Confd `_ which will -poll for changes from Etcd and write changes to a configuration file on the local filesystem, which the Fractal worker -could use for configuration. +In earlier sections, the Fractal application used an installation script into +which the metadata API passed parameters to bootstrap the cluster. `Etcd +`_ is "a distributed, consistent key-value +store for shared configuration and service discovery" that you can use to +store configurations. You can write updated versions of the Fractal worker +component to connect to Etcd or use `Confd +`_ to poll for changes from Etcd and +write changes to a configuration file on the local file system, which the +Fractal worker can use for configuration. -Using Swift instead of a database ---------------------------------- +Using Object Storage instead of a database +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -We haven't quite figured out how to do this yet, but the general steps involve changing the fractal upload -code to store metadata with the object in swift, then changing the API code such as "list fractals" to -query swift to retrieve the metadata. If you do this, you should be able to stop using a database. +We haven't quite figured out how to do this yet, but the general steps involve +changing the fractal upload code to store metadata with the object in swift, +then changing the API code such as "list fractals" to query swift to get the +metadata. If you do this, you should be able to stop using a database. .. note:: This section is incomplete. Please help us finish it! -Next Steps ----------- -Wow, if you've made it through this section, you know more about -working with OpenStack clouds than the authors of this guide. +Next steps +~~~~~~~~~~ -Perhaps you can `contribute `_? +Wow! If you've made it through this section, you know more than the authors of +this guide know about working with OpenStack clouds. +Perhaps you can `contribute +`_?