As of 2016-01-24, the CCVM project has been fully decommissioned.
This page is about using OpenStack as a Computer Club member. For instructions for usage as a CMU student, see Projects/ccvms. For information about Openstack maintenance and deployment, see Projects/ccvms/Openstack.
Contents
Introduction
OpenStack and CCVM offers Computer Club the opportunity to have a robust, stable, serious-business infastructure. We can greatly reduce the brittleness and complexity of our infastructure by moving services to OpenStack.
Unique advantages include:
- Live migration of VM between hosts
- Quick, scripted creation of VMs
- Web, command line, and application programming interfaces, all accessible securely and remotely
The ability to run distros and kernel versions other than Debian Wheezy, kernel 3.2 (because we aren't using Xen paravirtualization for OpenStack)
- And much more!
Other current advantages (that aren't really unique to OpenStack, but haven't been done elsewhere) include:
- Ability to conserve IPs by using a network routed only between our own VMs
- And much more!
Getting access
For now, you can either make an account on https://www.club.cc.cmu.edu/ccvms/signup.php, or manually make an account by following the instructions here.
Later on, we'll be able to directly use Computer Club accounts to access OpenStack, but that hasn't been set up yet. Contact sbaugh if you would like to help get that integration set up!
Creating a Clubified VM
At the most basic level this is extremely simple.
- Make an instance in the CClub project/tenant, using the "Clubified Debian 7" image and the appropriate sized flavor.
- Associate a floating IP with it.
- Done!
This new VM has AFS installed, will accept password-based logins from CClub accounts, and grants root access via sudo to CClub admins!
Adding additional features
DNS record
Follow Common Maintenance Tasks/Adding and removing DNS records.
Ticket-based login
First make a DNS record. Then run the following commands on the VM as root to create a Kerberos host principal and corresponding key.
1 kinit -S kadmin/admin $YOUR_CCLUB_USER/admin
2 kadmin ank --use-defaults -r host/$SHORTNAME.club.cc.cmu.edu
3 kadmin ext_keytab host/$SHORTNAME.club.cc.cmu.edu
This will allow ticket-based login, since you will then be able to get a ticket corresponding to that principal. See http://web.mit.edu/kerberos/dialogue.html.