Page History

2016-02-08

Discussion of workflow:

• A ticket is owned by Mike (implementation + documentation)
• Create sub-task for unit testing, assign to Craig
• Once testing complete, marked as resolved, pull request is issued
• Create sub-task for pull-request
• Once pull-request merged, close tickets.
  
  

Prioritization of high-level tasks (will add tickets to JIRA with more detail, then provide estimates)

1. Kubernetes cluster
   
   1. On Openstack

      1. Jira
         server OpenSource JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-98

         : Deployment of Kubernetes cluster on multiple VMs on OpenStack
         
         1. New Task: Testing (due 2/?)
         2. New Task: Update labs portal documentation (assigned to Mike, 2/?)
   2. Development stack– NDS Dev (David + Mike ~?) (single node)
      

      1. Jira
         server OpenSource JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-82

         : Allows anyone to bring up Kubernetes
         
         1. New tasks: Testing (due 2/9- Craig), documentation (done - Mike)
2. NDS Ops services (the thing that let's you deploy #3)

   1. Jira
      server OpenSource JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-92

      : Set of containers (logging, monitor, alert) = ELK
      1. New task: Testing (needs to be done as of 2/8), documentation (done)
   2. Ability to scale it up and down (David)
      1. New task: Allows anyone (NDS Labs user) to scale up their cluster if they need to – adding more OpenStack resources. (Not for NDS5)
3. Demo #1 (TERRA) 

   1. Jira
      server OpenSource JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-105

      : Elasticsearch + Jupyter + Terratoolsrv
   2. Scale (elasticity, sharding mongo, sharding rabbit) see how it fits
   3. Script/documentation of what the demo is (done by Kenton in diagrams, but we need to review)
4. Demo #2 (Dataverse)

   1. Jira
      server OpenSource JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-103

      : Adding DataVerse support
   2. Script/documentation of what the demo is (review Kenton's diagrams)
5. Backend APIs
   1. Administrative API (provision resources, new namespace)
   2. Project user API

   3. Jira
      server OpenSource JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-108

      : API/CLI prototype
6. Deployment GUIs

   1. Jira
      server OpenSource JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-93

      1 day prototype/proof of concept (Mike)
   2. Actual GUI (est TBD)
7. Do the TERRA demo validation (end-to-end walkthrough, Dev + OpenStack envs)
8. Do the DataVerse demo validation (end-to-end walkthrough)
9. Save it and make it a container, add it to the services (projects?)
10. Workshop preparation (presentations)

...

2016-01-21 

Notes from discussion about tasks for upcoming NDS5 workshop.

...