[Swift-commit] r7740 - SwiftApps/cloud

[ketan at ci.uchicago.edu]

Author: ketan
Date: 2014-03-19 14:34:38 -0500 (Wed, 19 Mar 2014)
New Revision: 7740

Modified:
   SwiftApps/cloud/README
Log:
Notes and Warnings


Modified: SwiftApps/cloud/README
===================================================================
--- SwiftApps/cloud/README	2014-03-19 19:16:49 UTC (rev 7739)
+++ SwiftApps/cloud/README	2014-03-19 19:34:38 UTC (rev 7740)
@@ -38,8 +38,12 @@
 
 To install Swift, follow the instructions found
 http://swift-lang.org/downloads/index.php[here]. We use the Swift version 0.94
-from the SVN repository. Note that Swift installation is required only on the
-submit host and not on the cloud instances. To checkout the Swift-cloud
+from the SVN repository. 
+
+NOTE: Swift installation is required only on the
+submit host and not on the cloud instances.
+
+To checkout the Swift-cloud
 provision package from SVN repository use the following command: 
 
 ----
@@ -194,10 +198,12 @@
 ./addnodes -n 6
 ----
 
-Note that the above command will trigger a create instance command on your EC2
-account and can take upto 2 minutes before the newly created instances can
-actually join the existing Swift execution. Typically, you will see output as follows:
+NOTE: The above command will trigger a "create-instance" command on your EC2
+account and can take upto a minute before the newly created instances can
+actually join the existing Swift execution. 
 
+Typically, you will see output as follows:
+
 ----
 Configuration: coaster-service.conf
 6
@@ -225,8 +231,8 @@
 ./addnodes -p 0.08 -n 2
 ----
 
-Note that there is no guarantee of the resources being available at this price.
-In case the resources are not available, the request will be silently ignored.
+NOTE: There is no guarantee of the resources being available at this price. In
+case the resources are not available, the request will be silently ignored.
 
 Remove EC2 compute instances
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -275,6 +281,10 @@
 
 Shut down
 ----------
+
+WARNING: At this point make sure all your EC2 instances are terminated in order
+to avoid undue metering on those resources.
+
 Use the stop-coaster-service command to terminate the coaster service and remote worker agents:
 
 ----