Commit 17c56a7d by Daniel Noland Describe basics of OpenStack.

Terms of use, simple rules, and some simple tips.
1 parent 830b0190
# CSEL OpenStack
CSEL OpenStack
The [CSEL]( [OpenStack](
cluster is an IaaS (cloud) platform hosted here in the [CS Department](
## Storage
OpenStack is a service provided by CSOps to the students and faculty of CU. This service allows you to install and configure a virtual machine which will run on our servers.
OpenStack calls a block device a *volume*. You can create volumes with a name,
size, and type. The primary volume type on this cluster is currently **ceph**.
Contact to apply for OpenStack access. Keep in mind, this is one of many services we offer, and it may not be the right fit for you. If you just want a simple website this is massive overkill.
**ceph** - The default. This uses a [CEPH]( storage cluster.
It is reliable (your data can survive 2 disk failures) and has
Generally, this service is reserved for large school projects, faculty, and school clubs with needs more sophisticated than a simple web site.
## Flavors
The rules
When you boot an instance, you select a *flavor* with the CPU, RAM, and other
properties appropriate to your use.
The rules are simple (and obvious):
**a.*** - These flavors are the default. They use reliable storage by default
and are run on our more stable hardware.
1. Your actions are logged! Don't attempt to mess anyone else's systems! You will be banned for this.
2. No running any illegal activities or services or anything which violate CU school policy. Again with the banning thing (not to mention whatever other penalties you may suffer).
3. Use the minimal amount of resources you can get away with. These are shared resources, and they are paid for by student fees. Don't waste your own money!
4. Keep your system secure! If we detect that you are operating a compromised system, we will shut it down without hesitation. If you don't know how to keep a server up to date and reasonably secure, this is not going to work.
**io.*** - These flavors are designed to support fast disk IO. They use
local SSD storage passed directly to the VM. The downside of these
flavors is that they will experience power outages when the Engineering
Center as a whole does. The are also a little less flexible
administratively, as their disks take longer to migrate.
1. Use an available image for your install. You are welcome to upload other operating system images, but they are not tested. If you go off the reservation, we may not be able to help you.
2. Use ssh keys! This is a huge help to keeping your system secure and easily accessible.
3. Think twice before you click on anything in the OpenStack web interface. We can't help you very much if you destroy your own virtual machine (but you can always start over)!
4. Ask for help when you need it (
Styling with Markdown is supported
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!