[Python-checkins] devguide: Add some information on setting up an EC2 latent slave.

zach.ware python-checkins at python.org
Fri Oct 16 15:18:14 EDT 2015


https://hg.python.org/devguide/rev/9168d237b0e7
changeset:   771:9168d237b0e7
user:        Zachary Ware <zachary.ware at gmail.com>
date:        Fri Oct 16 14:17:46 2015 -0500
summary:
  Add some information on setting up an EC2 latent slave.

files:
  buildslave.rst |  34 ++++++++++++++++++++++++++++++++++
  1 files changed, 34 insertions(+), 0 deletions(-)


diff --git a/buildslave.rst b/buildslave.rst
--- a/buildslave.rst
+++ b/buildslave.rst
@@ -53,6 +53,9 @@
 Setting up the buildslave
 -------------------------
 
+Conventional always-on machines
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
 You need a recent version of the `buildbot <http://buildbot.net/>`_ software,
 and you will probably want a separate 'buildbot' user to run the buildbot
 software.  You may also want to set the buildbot up using a virtual
@@ -189,6 +192,37 @@
 idea.
 
 
+Latent slaves
+^^^^^^^^^^^^^
+
+We also support running `latent buildslaves
+<http://docs.buildbot.net/current/manual/cfg-buildslaves.html#latent-buildslaves>`_
+on the AWS EC2 service.  To set up such a slave:
+
+    * Start an instance of your chosen base AMI and set it up as a
+      conventional slave.
+    * After the instance is fully set up as a conventional slave (including
+      slave name and password, and admin and host information), create an AMI
+      from the instance and stop the instance.
+    * Contact the buildmaster administrator who gave you your slave
+      name and password and give them the following information:
+
+      * Instance size (such as ``m4.large``)
+      * Full region specification (such as ``us-west-2``)
+      * AMI ID (such as ``ami-1234beef``)
+      * An Access Key ID and Access Key.  It is recommended to set up
+        a separate IAM user full access to EC2 and provide the access key
+        information for that user rather than for your main account.
+
+The buildmaster cannot guarantee that it will always shut down your
+instance(s), so it is recommended to periodically check and make sure
+there are no "zombie" instances running on your account, created by the
+buildbot master.  Also, if you notice that your slave seems to have been
+down for an unexpectedly long time, please ping the `python-buildbots
+<https://mail.python.org/mailman/listinfo/python-buildbots>`_ list to
+request that the master be restarted.
+
+
 Buildslave operation
 --------------------
 

-- 
Repository URL: https://hg.python.org/devguide


More information about the Python-checkins mailing list