This space searches only documentation in the Atmosphere space. To search all CyVerse wiki content, use the box at the upper right.


For overview information, see Atmosphere on the CyVerse website.

Atmosphere User Manual
Icon

To keep your data safe, use a script to back up your data to the Data Store. For more information, see Backing Up and Restoring Your Data to the Data Store.

Important Notice about iPlant Cloud – Tucson
The iPlant Cloud – Tucson cloud provider is no longer available for new instance launches. If you did not back up your data on the iPlant – Tucson cloud, submit a request to support@cyverse.org for data migration to the new Marana cloud provider.
Skip to end of metadata
Go to start of metadata

There are different ways to stop and start instances, depending on your needs:

  • Shelve and unshelve an instance: A shelved instance allows you to shut down your instance without using allocated time, and then unshelve it to active status later. A shelved instance will consume the least amount of resources on a cloud provider and is preferred over suspending or stopping an instance.
  • Suspend and resume an instance: A suspended instance allows you to save your instance state, without using allocated time, and then restore it to active status later. Although allocation time is not used for the suspended instance, CPU and memory resources remain allocated for the instance and thus cannot be used for other instances.
  • Stop and start an instance: You can stop an active instance, but time allocation continues to be used while it is stopped. To avoid wasting your allocation, you may want to suspend the instance instead. To restart a stopped instance, you must have sufficient quota and the cloud provider must have enough room to support your instance's size.
  • Reboot an instance: Rebooting closes the instance and reopens it in the same state. While it is rebooting, the instance is inaccessible. You also can do a hard reboot on the instance to forcibly restart it.

When you know you no longer need an instance, you can delete it, or move it to a different project.

FactorShelvedSuspendedStopped
Continues to use allocation time  (tick)
Reserves CPU and memory resources (not available for other instances) (tick) 
IP address reassigned(tick)(tick)(tick)
Maximum instances allowedUnlimited4Unlimited

Shelving and unshelving instances (if supported by provider)

Shelving an instance is equivalent to shutting down your computer: all programs and documents are closed and the machine is powered off. You can unshelve the instance again later.

A shelved instance will not use time allocation. To restart the shelved instance, you must have sufficient quota to restart the instance, the provider must have enough room available to support your instance's size, and you will need to reopen the applications and documents. You also may delete an instance at any time.

Shelving an instance

  1. Click Projects on the menu bar, and then click to open the project with the instance to shelve.
  2. Click the instance name to open the instance.
  3. In the Actions list on the right, click Shelve.
  4. After reading the message, click Yes, shelve this instance. The status changes to Shelved. To verify, you may need to refresh the window.

Unshelving a shelved instance

  1. Click Projects on the menu bar, and then click the project with the instance to restart.
  2. Click the instance name to open the instance.
  3. In the Actions list on the right, click Unshelve.
  4. After reading the message, click Shelve Instance. The status changes to Active.
  5. Reopen the applications and documents.

Suspending and resuming instances

Suspending an instance allows you to freeze your instance in its same state without the need for requesting an image of your instance. Allocation time for suspended instances is not used; however, the CPU and memory resources are still allocated for the instance and cannot be used for other instances.

You can suspend up to four instances that were launched with the iPlant Cloud-Tucson provider. Note that if you run out of allocation resources, your instances will be suspended automatically and maintained in that state up to the limit for that provider, as outlined in Allocation Policies. You can resume your instances at the beginning of the month when your allocation is reset.

A resumed instance may be assigned a different IP address from the IP address it had before the instance was suspended. If the instance was launched using Web Shell or Remote Desktop (see Logging In to an Instance), the shell access also may be reconfigured and the Remote Desktop session will be relaunched.

Suspending an instance

  1. Click Projects on the menu bar and then click to open the project with the instance to suspend.
  2. Click the checkbox for the active instance to suspend.
  3. Click Suspend at the top right.
  4. Click yes to the prompt.
    The status changes to Active - suspending and finally to Suspended, and the IP address changes to 0.0.0.0 to indicate it is now unassigned. This process may take up to 30 minutes to complete so please be patient.
    You may resume (up to the limit specified in Allocation Policies) or delete the instance at any time.

Resuming a suspended instance

  1. Click Projects on the menu bar and then click to open the project with the instance to resume.
  2. Click the checkbox for the suspended instance to resume.
  3. Click Resume at the top right.
  4. Click yes to the prompt.
  5. In the Actions panel on the right, click Resume.
  6. After reading the message, click Yes, resume this instance. The instance status changes to Suspended - resuming and finally to Active.

Stopping and starting instances

Stopping an instance is equivalent to shutting down your computer: all programs and documents are closed and the machine is powered off. You can start the instance again later.

A stopped instance continues to use time allocation. To restart the stopped instance, you must have sufficient quota to restart the instance, the provider must have enough room available to support your instance's size, and you will need to reopen the applications and documents. To preserve resources and time allocation, you may want to suspend the instance instead. You also may delete an instance at any time.

Icon

A stopped instance continues to use time allocation. You may want to suspend the instance instead.

Stopping an instance

  1. Click Projects on the menu bar, and then click to open the project with the instance to stop.
  2. Click the instance name to open the instance.
  3. In the Actions list on the right, click Stop.
  4. After reading the message, click Yes, stop this instance. The status changes to Shutoff. To verify, you may need to refresh the window.

Starting a stopped instance

  1. Click Projects on the menu bar, and then click the project with the instance to restart.
  2. Click the instance name to open the instance.
  3. In the Actions list on the right, click Start.
  4. After reading the message, click Start Instance. The status changes to Active.
  5. Reopen the applications and documents.

Rebooting instances

Rebooting an instance closes the active instance and reopens it in the same state. While it is rebooting, the instance is inaccessible. You also can do a hard reboot on the instance to forcibly restart it.

  1. Click Projects at the top, and then click the name of the active instance to reboot.
  2. In the Actions panel on the right, click Reboot.
  3. Click Reboot to start the process for rebooting your instance.
  4. If the reboot does not proceed successfully, click Hard Reboot to forcibly restart the instance. It may take a few minutes for the reboot to complete. Be patient and refresh the page periodically.

Deleting instances from a project

When you know you no longer need an instance, you can delete an instance from a project that is active, suspended, or stopped and not attached to a volume. To preserve your data you must first detach any volumes that are attached to the instance before deleting the instance. If there is any possibility you might need it again in the future, you can request an image of your instance before you delete it.

CyVerse Support also may delete an instance that has been suspended for an extended period of time.

  1. Detach any volumes that are attached to the instance, if you have not already done so.
  2. Click Projects on the menu bar and then click the project with the active, suspended, or stopped instance to delete.
  3. Click the instance checkbox for the instance or instances to delete.
  4. Click .
  5. After reading the message, click Yes, delete the resources. The instance is deleted from your Instances list and your resource usage is updated.

Moving instances to a different project

  1. Detach any volumes that are attached to the instance, if you have not already done so.
  2. Click Projects on the menu bar and then click to open the project with the instance to move.
  3. Click the instance checkbox for the instance or instances to move.
  4. Click .
  5. Select the project to which you want to move the instance.

Need help?

Click  at the bottom right of the screen to chat with an Atmosphere support team member during business hours. You also can go to Ask CyVerse for Atmosphere, or click Feedback & Support at the bottom of the screen.

Helpful Links

This page contains:

Related pages:

Definitions

Shelving an instance

  • Equivalent to shutting down your computer: all programs and documents are closed and the machine is powered off.
  • Allocation time will NOT be used.
  • To restart a stopped instance, you must have sufficient quota to restart the instance, and the provider must have enough room available to support your instance's size.
  • To begin using the instance again, use Unshelve.

Suspending an instance

  • Freezes instance in same state without the need for requesting an image of your instance.
  • Allocation time is suspended, but the CPU and memory resources are still allocated for the instance and cannot be used for other instances.
  • IP address is reassigned.
  • Maximum: four suspended instances that were launched with the iPlant Cloud-Tucson provider.
  • If you run out of allocation resources, your instances will be suspended automatically and maintained in that state up to the limit for that provider, as outlined in Allocation Policies on the CyVerse website. You can resume the instances at the beginning of the month when your allocation is reset.
  • To begin using the instance again, use Resume.

Stopping an instance

  • Equivalent to shutting down your computer: all programs and documents are closed and the machine is powered off.
  • Allocation time continues to be used. To preserve resources and time allocation, you may want to suspend the instance instead.
  • To restart a stopped instance, you must have sufficient quota to restart the instance, and the provider must have enough room available to support your instance's size.
  • To begin using the instance again, use Start.

Unshelving a shelved instance

  • Must have sufficient quota.
  • Provider used to launch the instance must have enough room available to support your instance's size.
  • Must reopen the applications and documents in the instance.

Resuming a suspended instance

  • May be assigned a different IP address from the IP address it had before the instance was suspended.
  • If the instance was launched using Web Shell or Remote Desktop, the shell access also may be reconfigured and the Remote Desktop session will be relaunched.

Starting a stopped instance

  • Must have sufficient quota.
  • Provider used to launch the instance must have enough room available to support your instance's size.
  • Must reopen the applications and documents in the instance.