You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Notes from discussion about tasks for upcoming NDS5 workshop.

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

  1. Kubernetes cluster
    1. on Openstack (99%) (David ~4hrs)
    2. Development stack (NDS-82, 80%) – NDS Dev (David + Mike ~?)
      1. devstack up
  2. NDS Ops services (the thing that let's you deploy #3)
    1. Set of containers (logging, monitor, alert) = ELK? (David + Craig)
    2. Ability to scale it up and down (David)
  3. Demo #1 (TERRA)
    1. Write the pod specifications 
      1. identify which ones
    2. Put those all together + glue
      1. More containerizing for Clowder
      2. Scale (elasticity, sharding mongo, sharding rabbit) see how it fits
  4. Deployment GUI
    1. 1 day prototype/proof of concept (Mike)
    2. Actual GUI (est TBD)
  5. Do the TERRA demo validation (end-to-end walkthrough, Dev + OpenStack envs)
  6. Save it and make it a container, add it to the services (projects?)
  7. Demo #2 (MDF)
    1. MDF
      1. Workout with Globus
    2. Metasearch
      1. Flesh this out (Craig)
      2. Write the pod specifications
      3. Put those all together + glue
  8. Workshop preparation (presentations)

 

There was a discussion of different services. 

Question was asked whether the services list contains high-level component (e.g., clowder) or everything (e.g., clowder, rabbit, mongo, elastic). Answer: All.

Discussion of Kubernetes -- two steps: 1 deploy, 2 scale/replication, 

Things to discuss later/

  • Implementation that spans Nebula and Amazon? Once you get to #4 – all you need is the account. Idea: Terra is running on Nebula, migrates to Google Cloud?
  • Is storage more important?

 

  • No labels