diff --git a/README.rst b/README.rst
index bedb9eda484e4539c5d6730211b7573fcb24acb3..198973af6c12dbca6c4c43634002c1d88c85d646 100644
--- a/README.rst
+++ b/README.rst
@@ -40,6 +40,46 @@ variable to what you've assigned to the cluster. The jobs will
 automatically start as soon as the configuration is saved.
 
 
+Full cluster install procedure
+++++++++++++++++++++++++++++++
+
+This assumes that you have an existing domain name (here
+*example.com*) that you control, and that you will run the cluster
+under a sub-domain (*radio.example.com*). Follow these steps to
+bootstrap a new streaming cluster:
+
+#. Make sure that, on each of your servers, the output of ``hostname
+   -f`` is the fully-qualified hostname of the machine, and that it
+   resolves to its public IP (possibly using ``/etc/hosts``).
+
+#. On every server, run the above-mentioned steps to set up the APT
+   repository and install (do not configure) the ``etcd`` and
+   ``radioai`` packages.
+
+#. Pick one of your servers and add a delegation for
+   *radio.example.com* to it. For instance, with ``bind``::
+
+     radio  IN   NS  3600  machine1.example.com.
+
+#. On *machine1*, edit ``/etc/default/etcd`` and set
+   ``BOOTSTRAP=1``. Once you save the file, the ``etcd`` daemon will
+   start with an empty database.
+
+#. On *machine1*, edit ``/etc/default/radioai`` and set
+   ``DOMAIN=radio.example.com``. This will start the ``radiod`` and
+   ``redirectord`` daemons, and you will be able to serve DNS records
+   for the *radio.example.com* zone. Check with::
+
+     $ ping -c1 radio.example.com
+
+   This should send a ping to *machine1*.
+
+#. Set up all other machines, setting
+   ``ETCD_SERVER=etcd.radio.example.com`` in ``/etc/default/etcd`` and
+   ``DOMAIN=radio.example.com`` in ``/etc/default/radioai``.
+
+
+
 Securing etcd
 +++++++++++++