NOTE:  Before you can launch and login to instances, you must have setup a key pair.  Instructions for creating a key pair and managing openstack credentials can be found here



There are two ways to launch an instance - either from the Instances menu or from the Images menu.  


From the Instances menu, click on the "Launch Instance" button.  Enter an Instance Name and change the count, if desired.  The count is the number of instances you want to start up.  Most of the time, this should be left at 1.  Then click Next:


NOTE: Your project has a quota set for the total number of instances you're permitted to run.  The chart on the right shows the current usage.  If you've hit your limit, please contact ccr-help@buffalo.edu to request assistance.




Source:

On the Source tab, there are many things you need to consider when deciding how you want your instance created.  

Select Boot Source:  Options are Image, Instance Snapshot, Volume, Volume Snapshot

Create a new volume:  Yes/No (default is Yes which is what we recommend)

Volume Size: Minimum is 11GB (each project has a storage quota.  If you need more, cloud storage can be purchased for a nominal fee)

Delete Volume on Instance Delete:  Default is No (we recommend selecting Yes unless you want to use this volume attached to other instances)

Device name:  Default is vda (linux volume name)


Depending on what boot source you've selected, you will see different options available to select for the creation of your instance.  In this example, there are four images available to select for the operating system.  Click on the up arrow next to the one you want to use, then click the Next button.




Flavor:

This section displays all of the available options for sizing your instance.  You must use the up arrow next to the instance "flavor" you decide you want to run.  This list shows each flavor, the number of virtual CPUs (VCPUS), RAM (memory), total disk size, and total size of root disk.  If you click the arrow to the left of the flavor name, you will be shown how starting up an instance of that size will impact your group's (project) quota.





Networks:

At this time, there is only one network available to LakeEffect users.  This will automatically be added to the "allocated" section of your instance detail, as shown below.



Network Ports:

At this time there are no virtual switch ports configured in CCR's LakeEffect cloud so this step can be skipped.  We are currently testing this functionality of Openstack.  Please contact CCR help if this is something you'd be interested in utilizing.




Security Groups:


Security groups are an important concept to understand in Openstack.  Security groups define a set of IP filter rules that determine how network traffic flows to and from an instance like a firewall.  The default rule in LakeEffect only allows outbound traffic - no inbound traffic is permitted.  If the default security group is associated with an instance you will have no way to connect to it after it launches.  You will need to assign a security group to the instance that allows access via SSH.  Please see the article about security groups for more details on configuring them.






Key Pair:


A key pair allows you to SSH into your instance.  You may select an existing key pair, import a key pair you've already created (see how-to article on creating key pairs), or generate a new key pair from this tab





Configuration:


This tab allows you to script certain configuration details when an instance is launched.  Please click the question mark icon on this tab for more details.  This is for advanced users only.


Some users may want to partition the root disk of an instance in a specific way.  To do this, change the Automatic to Manual under Disk Partition and you will be prompted to setup the partitions when the instance is launched.





The remaining three tabs (server groups, scheduler hints, and metadata) on the launch instance GUI are not necessary.  You can now click the "Launch Instance" button to begin the process of spinning up the virtual machine.  You will then be presented with information about your virtual machine: