Using the Jetstream API

To request OpenStack API access, email with the subject "Requesting Jetstream API access for the <XYZ PROJECT>".  In your email, answer as many of the questions listed below as possible.

  • Briefly describe what you want to do and how you’re going to do it.
  • What will runtime operations look like?
  • Does this application exist already or is this primarily a development effort? If yes, what parts exist and where can they be referenced?
  • What API are you planning on using, Openstack, RADOS, Atmosphere, EC2, S3, something else?
  • Are any of these gateways? Might it spawn a gateway in the future?
  • What resources could you conceive this project consuming once in production? Please include sustained as well as peak resource demands.
  • Do you anticipate bursting into/out of Jetstream?
  • Jetstream contains more than one OpenStack cloud.  Were you aware of this and do you think your implementation will be able to leverage multiple clouds initially? Eventually?
  • Are there long term storage needs, for example for reference data, that need to be accessible from the running instances? If so, how much storage is needed?

  • Are there run-time scratch/transient/workbench storage needs?
  • What is/are the XSEDE project name(s)?
  • Who is working on this project and what are their roles?
  • Is there a group account that development will occur under?
  • Is there one primary developer that will be using this account; or, will a group of individuals be developing code within this account?

Important info about the Jetstream API

Jetstream's OpenStack API is open to advanced users. Jetstream API users should understand the following:

  1. You will be expected to have familiarity with being a unix system administrator. These are advanced areas of operation and require a more advanced skill set than using Jetstream via Atmosphere.
  2. Jetstream Support may not be able to help with issues beyond VM functionality and other OpenStack issues. Software and services such as databases, local or remote applications, or other server-based components are up to the user/developer to install, deploy, and maintain. 
  3. The current API environment is always under development. The base services are available and many features are added and upgraded as Jetstream matures.
  4. Jetstream staff and systems administrators will prioritize and address issues as they arise.
  5. Access may be revoked or restricted to insure the effective and efficient delivery of production services.
  6. This is an OpenStack API not an Atmosphere API. When you open up Atmosphere your OpenStack VMs will not be displayed and vice versa. We discourage manually deploying Atmosphere images in API and vice-versa as there are many configurational differences that can lead to deployment problems.

  7. PIs and developers must be aware of, and conform to, any and all policies required for users of the systems owned and/or operated by the service providers, Indiana University (IU) and Texas Advanced Computing Center (TACC).

Navigation Tree: