Skip to content

Commit 4cfa6b2

Browse files
committed
Corrected inaccuracy related to stopped instances.
1 parent d42490c commit 4cfa6b2

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/user/_sources/cloud.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ An Amazon Marketplace AMI for C-PAC has been released, making it easier for rese
1414

1515
* Terminated Instance - An instance is considered terminated when its resources have been completely freed up for use by others in the Amazon cloud. Any data on a terminated instance that is not relocated to persistent storage such as EBS (see below) will be completely discarded. Instance termination is the virtual equivalent of throwing out a physical server. When you have terminated an instance, you are no longer paying for it. If your data and results are in persistent storage, you should terminate any instances you are using when you are done. Note that by default, instances do not have persistent storage attached to them- you will need to configure persistent storage when you set up the instance.
1616

17-
* Stopped Instance - An instance is considered stopped when it is not active, but its resources are still available for future use whenever you choose to reactivate it. Stopping an instance is the virtual equivalent of turning a computer off or putting it in hibernate mode. When you stop an instance, you continue to pay for it, since it is only paused. You should stop an instance when the analyses you are working on are not fully done and you would like to preserve the current state of a running instance.
17+
* Stopped Instance - An instance is considered stopped when it is not active, but its resources are still available for future use whenever you choose to reactivate it. Stopping an instance is the virtual equivalent of turning a computer off or putting it in hibernate mode. When you stop an instance, you continue to pay for the storage associated with it (i.e., the main and other volumes attached to it), but not for the instance itself. You should stop an instance when the analyses you are working on are not fully done and you would like to preserve the current state of a running instance.
1818

1919
* Simple Storage Service (S3) - A form of storage offered by Amazon. S3 is not intended for use with instances since it lacks a filesystem, but it can be used to archive large datasets. It is less costly than EBS.
2020

docs/user/cloud.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ <h2>Introduction<a class="headerlink" href="#introduction" title="Permalink to t
6060
<li>Instance - A single running virtual machine whose initial state is based on the AMI that it is launched from. Instances can be classified as spot instances or on-demand instances. On-demand instances are reliably created the moment they are requested for a fixed rate. Spot instances are created based on whether or not a bid that you set is accepted by Amazon. They can be significantly cheaper than on-demand instances, but are only created when Amazon accepts your bid.</li>
6161
<li>Instance Type - The hardware specification for a given instance. A list of the instance types made available by Amazon may be found <a class="reference external" href="http://aws.amazon.com/ec2/instance-types">here</a>.</li>
6262
<li>Terminated Instance - An instance is considered terminated when its resources have been completely freed up for use by others in the Amazon cloud. Any data on a terminated instance that is not relocated to persistent storage such as EBS (see below) will be completely discarded. Instance termination is the virtual equivalent of throwing out a physical server. When you have terminated an instance, you are no longer paying for it. If your data and results are in persistent storage, you should terminate any instances you are using when you are done. Note that by default, instances do not have persistent storage attached to them- you will need to configure persistent storage when you set up the instance.</li>
63-
<li>Stopped Instance - An instance is considered stopped when it is not active, but its resources are still available for future use whenever you choose to reactivate it. Stopping an instance is the virtual equivalent of turning a computer off or putting it in hibernate mode. When you stop an instance, you continue to pay for it, since it is only paused. You should stop an instance when the analyses you are working on are not fully done and you would like to preserve the current state of a running instance.</li>
63+
<li>Stopped Instance - An instance is considered stopped when it is not active, but its resources are still available for future use whenever you choose to reactivate it. Stopping an instance is the virtual equivalent of turning a computer off or putting it in hibernate mode. When you stop an instance, you continue to pay for the storage associated with it (i.e., the main and other volumes attached to it), but not for the instance itself. You should stop an instance when the analyses you are working on are not fully done and you would like to preserve the current state of a running instance.</li>
6464
<li>Simple Storage Service (S3) - A form of storage offered by Amazon. S3 is not intended for use with instances since it lacks a filesystem, but it can be used to archive large datasets. It is less costly than EBS.</li>
6565
<li>Elastic Block Storage (EBS) - A form of persistent storage offered by Amazon for use with instances. When you have terminated an instance, items stored in an EBS volume can be accessed by any future instances that you start up.</li>
6666
<li>Head Node - The primary node of an HPC cluster, which all other nodes are connected to. The head node will run a job scheduler (such as Sun Grid Engine) to allocate jobs to the other nodes. Jobs may also be run on the head node.</li>

0 commit comments

Comments
 (0)