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