You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+30-11Lines changed: 30 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,16 +8,16 @@ everything is done using CloudFormation or resources within AWS.
8
8
9
9
### Installation
10
10
11
-
The current working version is cfncluster-0.0.11. The CLI is written in python and uses BOTO for AWS actions. You can install the CLI with the following command:
11
+
The current working version is cfncluster-0.0.12. The CLI is written in python and uses BOTO for AWS actions. You can install the CLI with the following command:
Once installed, you should update the Environment Variables to have the Python install directory and Python Scripts directory in the PATH, for example: C:\Python27;C:\Python27\Scripts
33
33
34
+
Now it should be possible to run the following within a command prompt window:
35
+
36
+
```
37
+
C:\> easy_install cfncluster
38
+
```
39
+
40
+
#### Upgrading
41
+
42
+
To upgrade an older version of cfncluster, you can use either of the following commands, depening on how it was originally installed:
43
+
44
+
```
45
+
$ sudo pip install --upgrade cfncluster
46
+
```
47
+
or
48
+
```
49
+
$ sudo easy_install -U cfncluster
50
+
```
51
+
52
+
** Remember when upgrading to check that the exiting config is compatible with the latest version installed.
53
+
34
54
### Configuration
35
55
36
56
Once installed you will need to setup some initial config. The easiest way to do this is below:
You should now edit the config and set some defaults before launching the cluster. First define a keypair that already exists in EC2.
68
+
You should now edit the config and set some defaults before launching the cluster. First define a keypair that already exists in EC2. If you do not already have a keypair, refer to the EC2 documentation on EC2 Key Pairs - http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html
49
69
50
70
```
51
71
[keypair mykey]
52
72
key_location = /path/to/key.pem
73
+
````
74
+
53
75
Then you should associate that keypair with the cluster template.
76
+
````
54
77
[cluster default]
55
78
# Name of an existing EC2 KeyPair to enable SSH access to the instances.
56
79
key_name = mykey
57
80
```
58
81
59
-
Finally, a base cluster launches into a VPC and uses an existing subnet which supports public IP's i.e. the route table for the subnet is 0.0.0.0/0 => igw-xxxxxx. The VPC must have "DNS Resolution = yes" and "DNS Hostnames = yes". It should also have DHCP options with the correct "domain-name" for the region, as defined in the docs: http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_DHCP_Options.html
82
+
Next, a simple cluster launches into a VPC and uses an existing subnet which supports public IP's i.e. the route table for the subnet is 0.0.0.0/0 => igw-xxxxxx. The VPC must have "DNS Resolution = yes" and "DNS Hostnames = yes". It should also have DHCP options with the correct "domain-name" for the region, as defined in the docs: http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_DHCP_Options.html
60
83
61
84
```
62
85
## VPC Settings
63
86
[vpc public]
64
87
# ID of the VPC you want to provision cluster into.
65
-
vpc_id = vpc-
88
+
vpc_id = CHANGE ME, for example vpc-a1b2c3d4
66
89
# ID of the Subnet you want to provision the Master server into
67
-
public_subnet = subnet-
68
-
# Availability zones of VPC resources
69
-
# This is a comma delimited list and must always contain three values
70
-
# Example: us-west-2a,NONE,NONE
71
-
availability_zones =
90
+
master_subnet_id = CHANGE ME, for exaple subnet-1ab2c3d4
72
91
```
73
92
74
93
Once all of those settings contain valid values, you can launch the cluster by repeating the command that was used at the start.
0 commit comments