Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

« Previous Version 2 Next »

NoTest CaseProgressBlocking Issue
1.Collection package

90%


1a.Test collection package using Helm and ensure all pods and services come up fine100%
1b.Test collection package using Helm Template and Kubectl and ensure all pods and services come up fine100%
1c.Ensure Prometheus is up and running and the collectd endpoints are registered and metrics are scraped successfully.100%
1d.Ensure Prometheus is up and running and the cadvisor endpoints are registered and metrics are scraped successfully.100%
1e.Ensure Prometheus is up and running and the Node Exporter endpoints are registered and metrics are scraped successfully.100%
1f.Soft multi-tenancy support for collection package by bringing up 2 packages in 2 different namespace within the same cluster100%
1g.Ensure Prometheus end points visible in Grafana visualization package by enabling the Prometheus url and importing the dash board50%
1h.Test Day0 configuration100%
1i.Test Day2 configuration75%Prometheus remote_write Day-2 config not working as intended. Need to use a combination of kubectl apply and kubectl patch.
2.Data Lake50%
2a.Make sure M3DB charts are running successfully and the pods/services are up100%
2b.Make sure HDFS charts are running successfully and the pods/services are up100%
2c.Prometheus integration with M3DB remote_write. Ensure metrics can be queried from M3DB co-ordinator service

2d.


2e.


3.Messaging

4. Training

5.Model Repository

6. Inference

7.End to End Distributed Analytics stack composition

  • No labels