Tracking Lakelse Development

Vineperf DPPD-Prox:

1. Baremetal: Rapid is used to 'test-management' only.req
2. Kubernetes: Rapid will be used AS-IS (assuming there will be changes in the rapid deployment).
   1. Rapid programs must be run inside the cluster, with the script  run_rapid
   2. Question: can we add a Nodeport service inside rapid_k8s-deployment.py or not?
3. --verbosity error/critical: clean output - only the results will be displayed. This will help in using Kubernetes Logs api.
4.  Artifacts as part of lakelse release. 
   1. dpdkfwd
   2. trex
   3. vineperf
   4. CNIs: userspace
   5. noisy-neighbor (shubhank)
   6. spirent stcc
   7. Questions: (a) What will be the docker registry (for artifact submission) - dockerhub (opnfv - https://hub.docker.com/u/opnfv or anuket, no charges), or private (LF pods, maintain our own registry), or every projects maintain their artifacts on their own  (b) How do we submit these artifacts - accounts will be shared with all PTLs, or there will be a separate build machine with account configured.  Currently using dockerhub - opnfv.  Migration is not a problem for ViNePerf - other projects need  migrations if a new (free) account or a private account is chosen.
5. Testing proposal for Student Volunteer: K8s Pod 2 Pod communication benchmarking. Kubernetes Pod-2-Pod Communication Benchmarking This is a test of the non-accelerated plug-ins.