openstack/api-site
Code Issues Proposed changes
api-site/firstapp/source/section9.rst
Andreas Jaeger f58477ef61 FirstApp: Move source directory up, rename top-level dir 
For the RST guides, we do not need doc/source, since doc is always
empty. Use source directly.

This syncs the setup used here with openstack-manuals.

Rename top-level from openstack-firstapp to firstapp, there's no need
for the long name in this repo.

Change-Id: If4e11a4f90d580876865348e0d88b92cec4b6659
2015-05-01 17:22:46 +02:00

2.6 KiB
Raw Blame History

Going crazy

This section explores options for expanding the sample application.

Regions and geographic diversity

Note

For more information about multi-site clouds, see the Multi-Site chapter in the Architecture Design Guide.

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 about hybrid clouds, see the Hybrid Cloud chapter in the Architecture Design Guide.

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

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 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 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 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 than the authors of this guide know about working with OpenStack clouds.

Perhaps you can contribute?