2019-03-18: Development Meeting

Kacper, Craig, Tommy, Mike H, Ian, Adam, Tim, Mike L

Agenda

  • Updates
  • Discussion
    • What goes into a published Tale? (HTTP files problem)

Updates

  • Mike H:
    • Worked on Kubernetes drivers: https://github.com/whole-tale/wt-kubernetes
    • Followed what they did with NFS for WebDav
    • Mount times out
    • Chose CSI over Flexvolume
  • Craig:
    • DEPLOYED V0.6!
    • Created real Tales (Kyle’s B., Seni, …)
    • Issued PRs related to repo2docker
    • Looking into Tommy’s publish PRs
  • Kacper:
  • Tommy:
    • Minor changes to manifest (before kacper’s changes)
    • Removed file picker from UI
    • Refactored gwvolman to account for dashboard change
    • Currently:
      • Writing dev docs for publishing (girder_wholetale)
      • Rebase dashboard & clean up commits
      • Investigate LIGO HTTP missing from published Tale?
  • Mike L:
    • PR for build notifications via EventSource API
    • Separate PR for Rebuild/Restart buttons
      • Merge order TBD
    • PR Review
      • Publishing PR review in progress
      • Copy on Launch PR review pending
  • Adam/Ian:
    • Met with Craig and Kacper
    • Planning dev activity for Y4 and Y5
  • Tim:
    • Using Ansible (on localhost) to configure my working environment for one of my projects (https://github.com/tmcphillips/openrefine-provenance).
    • Bootstrap script retrieved via wget or curl installs minimal requirements for Ansible, installs Ansible via pip in a Python virtual environment, and clones Git repo with Ansible playbooks for further configuration.
    • Goal is to be able to reproduce my computing environment across multiple computers (including in WSL environment), VMs (via Vagrant on Windows, MacOS, and Linux), and Docker containers while doing the work in the first place.
    • Hope is that I will be able to share the computing environment in the same way via Binder and Whole Tale when the project is complete, and share with the resulting publication.