Last modified 6 years ago Last modified on 07/30/13 14:38:20

DevOps Weekly Meeting | July 30, 2013

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


tanthony, jpr, pavgi, mhanby, bade

2013-07-30 Agenda


  • Crashplan updates
    • Netplus for public clouds only
    • Explore private cloud with Code42 directly
  • NGS/Galaxy/CLC
    • Cloud
      • MiSeq & HiSeq upload to cloud with apps, 1st TB free
      • Lots of sites integrating local tools with Galaxy as way to expose them
    • Galaxy
      • Most of the admin is done by part time admins in NGS domain, matches with our goals to in-source management of UAB Galaxy to the teams using galaxy
      • Added galaxy to the SGE NGS node slots
    • CLC
      • CLC fixed some ulimit issues with Java file opens
  • OpenStackPlusCeph
    • Fix rcs-srv-02 NAT rules
    • ai: need to create a uab public to floating-public translation table
    • ai: need to embed table in DNS
    • ai: need an ubuntu desktop image in glance. may require contortion of launching vm with iso or getting iso in glance and then installing into a volume and then launch a subsequent instance from that volume
    • ai: jpr: apply changes to ceph read caching, requires nova-compute restart. pending understanding crowbar and chef
    • 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.
  • dspace report.
    • ai: jpr: need to complete draft


Worked through expanding understanding resource definitions in SGE and allow Galaxy to use NGS nodes set aside for CLC pilot since those nodes aren't in use by CLC at this time. Gets us to allowing SMP NGS codes more efficient queue wait times.

Had some fun looking at the Leap motion device Bade brought and then explored some related tech that promises new interactivity with technology.

Continued analysis of characteristics of data stored on Lustre. We are looking a the size of the tree structure and developing efficient search algorithms across is so we can more accurately track growth and identify how the storage is used.