This section explores options for expanding the sample application.
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!
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!
Using Pacemaker to look at the API.
Note
This section is incomplete. Please help us finish it!
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.
We have not quite figured out how to stop using a database, but the general steps are:
Note
This section is incomplete. Please help us finish it!
Wow! If you have made it through this section, you know more than the authors of this guide know about working with OpenStack clouds.
Perhaps you can contribute?
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.