Merge pull request #202 from aaronlevy/qsname

Specify cluster identifier in quickstart guides

Author: aaronlevy

hack/quickstart/quickstart-aws.md

@@ -1,27 +1,35 @@
 ## AWS Quickstart
 
+### Choose a cluster prefix
+
+This can be changed to identify separate clusters.
+
+```
+export CLUSTER_PREFIX=quickstart
+```
+
 ### Configure Security Groups
 
 Make note of the `GroupId` output of this command, as it will be referenced later in this guide as `<K8S_SG_ID>`.
 
 ```
-$ aws ec2 create-security-group --region us-west-2 --group-name k8s-sg --description "Security group for k8s cluster"
+$ aws ec2 create-security-group --region us-west-2 --group-name ${CLUSTER_PREFIX}-sg --description "Security group for ${CLUSTER_PREFIX} cluster"
 GroupID: "sg-abcdefg"
 ```
 
 Next, create the security group rules.
 
 ```
-$ aws ec2 authorize-security-group-ingress --region us-west-2 --group-name k8s-sg --protocol tcp --port 22 --cidr 0.0.0.0/0
-$ aws ec2 authorize-security-group-ingress --region us-west-2 --group-name k8s-sg --protocol tcp --port 443 --cidr 0.0.0.0/0
-$ aws ec2 authorize-security-group-ingress --region us-west-2 --group-name k8s-sg --protocol tcp --port 0-65535 --source-group k8s-sg
+$ aws ec2 authorize-security-group-ingress --region us-west-2 --group-name ${CLUSTER_PREFIX}-sg --protocol tcp --port 22 --cidr 0.0.0.0/0
+$ aws ec2 authorize-security-group-ingress --region us-west-2 --group-name ${CLUSTER_PREFIX}-sg --protocol tcp --port 443 --cidr 0.0.0.0/0
+$ aws ec2 authorize-security-group-ingress --region us-west-2 --group-name ${CLUSTER_PREFIX}-sg --protocol tcp --port 0-65535 --source-group k8s-sg
 ```
 
 ### Create a key-pair
 
 ```
-$ aws ec2 create-key-pair --key-name k8s-key --query 'KeyMaterial' --output text > k8s-key.pem
-$ chmod 400 k8s-key.pem
+$ aws ec2 create-key-pair --key-name ${CLUSTER_PREFIX}-key --query 'KeyMaterial' --output text > ${CLUSTER_PREFIX}-key.pem
+$ chmod 400 ${CLUSTER_PREFIX}-key.pem
 ```
 
 ### Launch Nodes
@@ -31,7 +39,7 @@ To find the latest CoreOS alpha/beta/stable images, please see the [CoreOS AWS D
 In the command below, replace `<K8S_SG_ID>` with the security-group-id noted earlier.
 
 ```
-$ aws ec2 run-instances --region us-west-2 --image-id ami-184a8f78 --security-group-ids <K8S_SG_ID> --count 1 --instance-type m3.medium --key-name k8s-key --query 'Instances[0].InstanceId'
+$ aws ec2 run-instances --region us-west-2 --image-id ami-184a8f78 --security-group-ids <K8S_SG_ID> --count 1 --instance-type m3.medium --key-name ${CLUSTER_PREFIX}-key --query 'Instances[0].InstanceId'
 "i-abcdefgh"
 ```
 

hack/quickstart/quickstart-gce.md

@@ -1,22 +1,30 @@
 ## GCE Quickstart
 
+### Choose a cluster prefix
+
+This can be changed to identify separate clusters.
+
+```
+export CLUSTER_PREFIX=quickstart
+```
+
 ### Launch Nodes
 
 To find the latest CoreOS alpha/beta/stable images, please see the [CoreOS GCE Documentation](https://coreos.com/os/docs/latest/booting-on-google-compute-engine.html). Then replace the `--image` flag in the command below.
 
 Launch nodes:
 
 ```
-$ gcloud compute instances create k8s-core1 \
+$ gcloud compute instances create ${CLUSTER_PREFIX}-core1 \
   --image https://www.googleapis.com/compute/v1/projects/coreos-cloud/global/images/coreos-stable-1068-9-0-v20160809 \
   --zone us-central1-a --machine-type n1-standard-1
 ```
 
 Tag the first node as an apiserver node, and allow traffic to 443 on that node.
 
 ```
-$ gcloud compute instances add-tags k8s-core1 --tags apiserver
-$ gcloud compute firewall-rules create api-443 --target-tags=apiserver --allow tcp:443
+$ gcloud compute instances add-tags ${CLUSTER_PREFIX}-core1 --tags ${CLUSTER_PREFIX}-apiserver
+$ gcloud compute firewall-rules create ${CLUSTER_PREFIX}-443 --target-tags= ${CLUSTER_PREFIX}-apiserver --allow tcp:443
 ```
 
 ### Bootstrap Master
@@ -35,13 +43,13 @@ $ kubectl --kubeconfig=cluster/auth/kubeconfig get nodes
 
 ### Add Workers
 
-Run the `Launch Nodes` step for each additional node you wish to add (changing the name from `k8s-core1`)
+Run the `Launch Nodes` step for each additional node you wish to add (changing the name from ` ${CLUSTER_PREFIX}-core1`)
 
 Get the EXTERNAL_IP from each node you wish to add:
 
 ```
-$ gcloud compute instances list k8s-core2
-$ gcloud compute instances list k8s-core3
+$ gcloud compute instances list ${CLUSTER_PREFIX}-core2
+$ gcloud compute instances list ${CLUSTER_PREFIX}-core3
 ```
 
 Initialize each worker node by replacing `<node-ip>` with the EXTERNAL_IP from the commands above.