Atmosphere Release Notes -- Gunnr-Beta (February 4, 2014)

Owned by ES
Last updated: Mar 04, 2014 by corderov (Unlicensed)Version comment
2 min read

Atmosphere Release Notes – Gunnr-Beta (February 4, 2014)

This release marks the integration of Atmosphere with OpenStack Havana.

Known Issues

This section will be updated as known issues are found.

New Features

  • Performance improvements: Instance launches are substantially faster on OpenStack. Some instances will fully launch as quickly as 5 minutes.
  • Instance actions: Suspend, resume, stop, start, and resize instances are fully supported with OpenStack.
  • Time-based allocations: The new cloud also introduces a new type of time-based allocation called Atmosphere Units (AU). One AU is equal to one CPU-hour or running a one vCPU instance for one hour. A user running a 16-core instance for 1 hour will use 16 AUs. All users will begin with 168 AUs, enough time to continuously run a 1-vCPU instance for 1 week. Users who exceed their allocation will have their instances suspended until their allocation is refreshed. Additional allocation can be obtained using the Request more resources form within Atmosphere. This new allocation model should help with better fair share of resources.
  • Volume backup/restore script: iPlant created an interactive script to back up and restore data on a volume or another directory on an instance. The file is called iplant_backup and is located in /usr/local/bin/.

Atmosphere Policy Changes

iPlant Service Level Agreement (SLA) was modified to explicitly describe Atmosphere's Active Use policies:

Resources for Active Use

iPlant provides resources to the community for active use. Because infrastructure resources are finite, iPlant may operationally reclaim idle or unused resources for the overall benefit of the user community. The following resources are formally reclaimed on a defined schedule:

  • Idle instances within Atmosphere: An instance that has not performed significant computations measured by load average or has not had interactive sessions (via SSH or VNC) for more than three (3) calendar days may be suspended, preserving the state of the instance. Users can resume a suspended instance at a later time, depending on available resources.
  • Inactive volumes within Atmosphere: Volumes provide a persistent storage within the cloud that can be attached to active instances. Volumes that have not been used for more than three (3) months will be considered inactive, after which the data will be copied to the user's Data Store home directory (under /iplant/home/username/atmo/volume-name) and the volume will be deleted. Users can request a new volume and copy their data back to the new volume. iPlant Staff will be available to assist with restoring data to the new volume, if necessary.
Unable to render {include} The included page could not be found.