Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Browse files

Reorganize the cloudinit.d documentation into three main sections

  • Loading branch information...
commit 313ddc2b796001a16d9f984405b75bf1da3a4842 1 parent 2e2a90f
@priteau priteau authored
16 cloudinitd/index.rst
@@ -4,13 +4,15 @@ cloudinit.d
cloudinit.d is a tool designed for launching, controlling, and monitoring
complex environments in the cloud. Its most important feature is repeatable,
-one-click, deployment of sets of VMs configured with *launch plans*. These
+one-click, deployment of sets of VMs configured with launch plans. These
sets of VMs can be deployed over multiple clouds (Eucalyptus, Nimbus,
OpenStack, and Amazon EC2 are currently supported) as well as include
non-virtualized resources. Like the Unix init.d process, cloudinit.d can
manage dependencies between deployed VMs. It also provides mechanisms for
-testing, monitoring, and repairing a launch. For more information about
-cloudinit.d see the pages below and our `Teragrid 2011 paper
+testing, monitoring, and repairing a launch.
+For more information about cloudinit.d and example launchplans see the links
+below and our `Teragrid 2011 paper
For repeatable experiment management with cloudinit.d read the `report on
support for experimental computer science
@@ -19,14 +21,8 @@ support for experimental computer science
.. toctree::
:maxdepth: 1
- intro
- wordpress
- cloudfoundry
- service
- install
- deps
- monitor
+ tutorial
.. image:: images/cloudinitd_dia.png
8 cloudinitd/quickstart.rst
@@ -211,3 +211,11 @@ in our case ``54c03415`` and giving it as an option to the terminate directive::
deleting the db file /home/bresnaha/.cloudinitd/cloudinitd-54c03415.db
+Example launch plans
+.. toctree::
+ :maxdepth: 1
+ wordpress
+ cloudfoundry
20 cloudinitd/intro.rst → cloudinitd/tutorial.rst
@@ -1,11 +1,10 @@
+cloudinit.d tutorial
Solving the problems in computing often requires a set of services all
working together in concert. As distributed computing has evolved, the
management and coordination of these services has become a complicated
@@ -126,3 +125,14 @@ balancer. The plan is configured in such a way as to route the important
connection information from the mongo DB cluster, to each HTTP server.
And similarly the list of HTTP servers is sent to the load balancer once
boot level 2 completes.
+.. toctree::
+ :maxdepth: 1
+ service
+ install
+ deps
+ monitor
Please sign in to comment.
Something went wrong with that request. Please try again.