Factor out EC2 parameters used to create master node, document them in-place.

Split EC2 params to sandbox-create.conf, add in-place docs there, to not
crowd README. Still, tweak README for better readability.

1 files changed, 31 insertions, 0 deletions

diff --git a/control/sandbox-create.conf b/control/sandbox-create.conf
new file mode 100644
index 0000000..a6f89ee
--- /dev/null
+++ b/control/sandbox-create.conf
@@ -0,0 +1,31 @@
+# API name of EC2 instance type to use for master node
+# See http://aws.amazon.com/ec2/instance-types/
+# Default: m1.small, enough to run 5-6 build slaves concurrently
+INSTANCE_TYPE="m1.small"
+
+# Amazon Image (AMI) id to use for master node, should match instance type above
+# See http://uec-images.ubuntu.com/
+# Default: ami-e2af508b, Ubuntu 11.04 (Natty) 32bit, instance store at us-east-1 region
+AMI=ami-e2af508b
+
+# EC2 Security groups to run master node with
+# Default: git-mirror, jenkins-master which corresponds to servers running on the node
+# git-mirror should allow connections TCP connections on ports:
+#   * 22 from outside (for# install and maintenance)
+#   * 8080 from machines of your account/default group (for mirror requests from slave, 
+#     jenkins slave implicitly have default group (Jenkins limitation)).
+# jenkins-master should allow TCP connections on ports:
+#   * 22 from outside (for install/maintenance)
+#   * 443 from outside (for web frontend).
+#
+# You can configure these groups by:
+#  1. Asking your EC2 admin (recommended)
+#  2. Via Amazon Web Console or other similar web frontend
+#  3. Via command line:
+#       ec2-add-group git-mirror -d "Cloud Buildd git mirror"
+#       ec2-add-group jenkins-master -d "Cloud Buildd Jenkins master"
+#       ec2-authorize git-mirror -p 22
+#       ec2-authorize git-mirror -p 8080 -u <Your EC2 numeric account id> -o default
+#       ec2-authorize jenkins-master -p 22
+#       ec2-authorize jenkins-mirror -p 443
+SECURITY_GROUPS="-g git-mirror -g jenkins-master"