CCR offers new cloud users with a 30 day complimentary "exploratory" account.  This is available for UB faculty, staff and students only.  


Interested people should create themselves a CCR account, if they don't already have one. Instructions can be found here


If you already have a CCR account, whomever is in charge of your group account should request an allocation for the Lake Effect compute resource in ColdFront.  In the justification field, request access to a 30 day exploratory account. 

Requesting a new allocation in ColdFront


If you are not part of a group project and not affiliated with a faculty member that has a CCR account, you will be permitted access to the cloud for the purposes of testing the CCR cloud service.  However, you will NOT be able to maintain access after the 30 day period without becoming a part of a faculty group AND purchasing additional cloud time.  Please submit a ticket to CCR Help requesting access to the exploratory account.

Cloud subscriptions and pricing


A few things to note about the exploratory accounts:
  • Users are part of a shared Openstack project.  Consider it a sandbox where others are playing also and only use it to test the services offered in CCR's cloud. Do NOT use this for production data or services.

  • Because there are others in the same project, you have to be aware of what is yours and what isn't.  When you see items that you may not have created such as security groups and existing instances, do NOT alter them. 

  • Because this is a shared project, you can delete existing instances and remove volumes of other users.  Please do not delete or modify anything that you have not created.  

  • We recommend when you create items in LakeEffect you label them so they're easy to decipher.  For example, using your last name in the name of the instance, security group, or volumes so that other users know they do not belong to them and so we know for when its time to clean out old stuff.  

  • CCR staff reserves the right to shut down or delete an instance or volume without notice as well as remove access from a user.  Again, this is not the place for production work.

  • All responsibilities for securing instances and proper use of the cloud service applies in this exploratory account, just as it does for any other account.  Please see these articles for more details:
    Use and Misuse of LakeEffect
    Updating and securing instances

We have some basic documentation that is specific to OpenStack.  If you're familiar with AWS EC2 most of the things you'll do in OpenStack will be very similar.  Check these out to get started:

Logging into Lake Effect - OpenStack Console
Launching Openstack Instances
Security Groups - controlling access to your Openstack instance
Setting up OpenStack CLI Tools
Is the research cloud backed up?