1 active_ebs_cluster = """EBS Cluster '%(cluster_name)s' already exists.
2
3 Either choose a different tag name, or stop the EBS cluster using:
4
5 $ starcluster stop %(cluster_name)s
6
7 This command will put all nodes into a 'stopped' state and preserve their \
8 local disks. The cluster can later be resumed by passing the -x option to \
9 the start command. Another option is to terminate the existing EBS Cluster \
10 using:
11
12 $ starcluster terminate %(cluster_name)s
13
14 NOTE: Terminating an EBS cluster will destroy the local disks (volumes) \
15 backing the nodes.
16 """
17
18 stopped_ebs_cluster = """Stopped EBS Cluster '%(cluster_name)s' already exists.
19
20 Either choose a different tag name, or start the stopped EBS cluster using:
21
22 $ starcluster start -x %(cluster_name)s
23
24 Another option is to terminate the existing EBS Cluster using:
25
26 $ starcluster terminate %(cluster_name)s
27
28 NOTE: Terminating an EBS cluster will destroy the local disks (volumes) \
29 backing the nodes.
30 """
31
32 cluster_exists = """Cluster with tag name %(cluster_name)s already exists.
33
34 If the cluster is a 'stopped' EBS cluster that you wish to 'start' or if you \
35 have yet to configure the existing cluster nodes, pass the -x option to the \
36 start command:
37
38 $ starcluster start -x %(cluster_name)s
39
40 If you wish to reconfigure the existing instances use the 'restart' command:
41
42 $ starcluster restart %(cluster_name)s
43
44 This will reboot all of the instances and configure the cluster starting from \
45 scratch.
46
47 Otherwise either choose a different tag name, or terminate the existing \
48 cluster using:
49
50 $ starcluster terminate %(cluster_name)s
51
52 """
53
54 cluster_started_msg = """
55 The cluster is now ready to use. To login to the master node as \
56 root, run:
57
58 $ starcluster sshmaster %(tag)s
59
60 When you are finished using the cluster and wish to terminate it and stop \
61 paying for service:
62
63 $ starcluster terminate %(tag)s
64
65 NOTE: Terminating an EBS cluster will destroy all EBS volumes backing the \
66 nodes.
67
68 Alternatively, if the cluster uses EBS instances, you can use the 'stop' \
69 command to put all nodes into a 'stopped' state:
70
71 $ starcluster stop %(tag)s
72
73 NOTE: Any data stored in ephemeral storage (usually /mnt) will be lost!
74
75 This will shutdown all nodes in the cluster and put them in a 'stopped' state \
76 that preserves the EBS volumes backing the nodes. A 'stopped' cluster may \
77 then be restarted at a later time, without losing data on the local disks, by \
78 passing the -x option to the 'start' command:
79
80 $ starcluster start -x %(tag)s
81
82 This will start all 'stopped' EBS instances and reconfigure the cluster.
83
84 """
85
86 spotmsg = """SPOT INSTANCES ARE NOT GUARANTEED TO COME UP
87
88 Spot instances can take a long time to come up and may not come up at all \
89 depending on the current AWS load and your max spot bid price.
90
91 StarCluster will wait indefinitely until all instances (%(size)s) come up. \
92 If this takes too long, you can cancel the start command using CTRL-C. \
93 You can then resume the start command later on using the --no-create (-x) \
94 option:
95
96 $ starcluster start -x %(tag)s
97
98 This will use the existing spot instances launched previously and continue \
99 starting the cluster. If you don't wish to wait on the cluster any longer \
100 after pressing CTRL-C simply terminate the cluster using the 'terminate' \
101 command.\
102 """
103
104 version_mismatch = """\
105 The cluster '%(cluster)s' was created with a newer version of StarCluster \
106 (%(new_version)s). You're currently using version %(old_version)s.
107
108 This may or may not be a problem depending on what's changed between these \
109 versions, however, it's highly recommended that you use version \
110 %(new_version)s when using the '%(cluster)s' cluster.\
111 """
112