Info

PLEASE FOLLOW THESE INSTRUCTIONS

The content of this template is expected to be filled out for the M1 Release Planning Milestone.
Use the "Copy" command, available under the ..., top right of this page, to copy this template into your project wiki. Be sure to set the "Parent page" field correctly for your project wiki.
After you have successfully copied this template into your project wiki, you may delete this info box.

Overview

Project Name	Enter the name of the project
Target Release Name	Enter the name of the release you are targeting to deliver (e.g., Jerma)
Project Lifecycle State	TBD

Category	Description
Model	Existing: Cleanup and publish the existing (FP) one. We may have to publish in a more usable form (part of a framework, or Python program). Ongoing: Log Analysis (BERT).
Tools	Existing: Cleanup the AlgoSelector. Ongoing: Data Slection/Anonymization. Ongoing: Chaos* (stress-ng) – Used in the testbed (Intel Pod18, for ex.. but restricted to K8S cluster)
Framework (MaaS)	Upstream: Kubeflow/Acumos. Thoth: Kubeflow + Supervised Techniques + Integration with important Data-Pipelines/Sources
WhitePaper (Research effort)	AI/ML & Kubernetes (CN-NFV)

Scope

High level description of the goals for the project

Provide a list of features or use cases, documented as Epics or Stories in Jira. Use the Jira issue insertion feature for Confluence.

Indicate the work product (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) for this release.

Name	Description	Format (Container, Compressed File, etc.)

Insert diagram or link.

List any Anuket projects on which this release is dependent and describe the dependency.

List any external dependencies (OpenStack, ODL, etc.). Include specific versions, if relevant.

Describe how the project will be tested and verified.

List any risks and a plan to mitigate each risk.

Risk Description	Mitigation Plan