Last modified 7 years ago Last modified on 06/26/13 15:17:25

DevOps Weekly Meeting | June 25, 2013

Time & Location: 10am-1:00pm in LHL164


mhanby, tanthony, jpr, pavgi, bade

2013-06-25 Agenda


  • matlab
    • java updates still a pain the new release breaks matlab again
  • sge
    • the SGE temp changes have been good for jobs using local scratch
  • OpenStackPlusCeph
    • folks starting to consider developing storage solutions using this fabric
    • have updated dso on openstack and awaiting followup
    • we need more engagement on api of openstack and ceph. next up will be chef/crowbar. talked about storage billing and 100G intrements. each person needs to be a tenant.
    • todo: we need access to the admin node interface via the controller
    • todo: we need to engage with dell on crowbar limitation on storage use, don't know if we get improvements from storage.
  • clcgenomics trial
    • pavgi playing with workbench and has connected to gs with plugin. sees some options for mem profile. may need a debug job.
    • will keep plugging on with clc and determine point where public demo can go forward.
  • galaxy update
    • pavgi still documenting migration steps
    • discuss opening galaxy wiki to public at next galaxy dev
    • tool migration wrapper is not a problem.
    • discuss how to merge module dev efforts with the from the tool shed. some sort of dynamic name resolution needed where can be sourced automatically by modules
    • good model for how we are buidling a separate environment for dev and how we can float that across a number of different instances. much cleaner. also using a virtual compute node for the galaxy host would help keep system config in sync
  • interns
    • wifi: request the students should have access to find a job for a semester
  • dspace report
    • overview of archival, experience with pilot, (labor intensive and implementation support), now there is netplus, future of storage looks bright
  • config management: saltstack and ansiblework.
    • might use these more for our cloud front end and still use chef for back end.
    • both use python2 and not python3