Last modified 7 years ago Last modified on 06/11/13 15:08:55

DevOps Weekly Meeting | May 28, 2013

Time & Location: 11am-2:00pm in LHL164


mhanby, tanthony, jpr

2013-05-28 Agenda

  • Agenda bash
  • OpenStackPlusCeph context switch
    • review steps to launch vms on openstack
    • review features of ceph block devices
    • identify next steps for configuration and connectivity
    • Todo
      • document vm create steps
      • test openstack client commands
      • add ubuntu 12.04 to the glance repo
      • Performance numbers on containers
      • Setup nas-01 to serve up jpr and mhanby home off Ceph


We spent most of the meeting stepping through the create and launch steps of vms in the openstack fabric with two new vms instantiated by mhanby and jpr during the meeting. Along the way we identified necessary configuration changes with the environment to explore and improve the developer experience, namely unfettered access to the fabric through the firewall and availability of client side openstack and ceph tools to configure the fabric.


Accessing the openstack fabric is described on the OpenStackPlusCeph page and currently relies on a cluster desktop to get around the firewall limitations.

The steps for creating a vm are fairly intuitive once they have been stepped through. The first time creating a vm takes a few extra steps to define the security and access rules, specifically the firewall access to allow ssh logins and the public key to use for ssh need to be selected at instance startup. The ssh key (newly created or an imported public key for an existing entry) is added to the VM's default user account during instantiation. A public IP address also needs to be assign to access the vm from the rcs-srv-02 gateway but that can happen after the instance is running. (Note: need to check if it's possible to change the firewall config of a running instance.)

With these parameters defined, starting a VM is a simple matter of going to an image of interest and selecting the launch icon. A dialog comes up where you name the instance and select the firewall and key parameters for access. Launching the VM gets it created. You can then associate a public IP address with it and access it from the rcs-srv-02 gateway.

The ceph docs on creating block devices also need to be explored further. The feature of layering is likely to be a very valuable asset. We just reviewed the docs and didn't step through any actual creation.

A long list of todo's was sketched out which need to be converted to tickets in dev. The most important is getting access to the internet from the VMs so that we can install additional packages.