CORTX Provisioner offers a framework which accepts configurations (cluster.yaml and config.yaml) in the form of ConfigMap, translates into internal configuration (CORTX Conf Store) and then orchestrates across components mini provisioners to allow them to configure services. In Kubernetes environment, CORTX Provisioner framework runs on all the CORTX PODs (in a separate one time init container).
Data_node type values are prone to change with respect to multiple data pods, hence we need to remove the hard dependency from this constants and recognize data pods based on storage key.
Coding
Checklist for Author
[x] Coding conventions are followed and code is consistent
Testing
Checklist for Author
[x] Unit and System Tests are added
[ ] Test Cases cover Happy Path, Non-Happy Path and Scalability
[x] Testing was performed with RPM
Impact Analysis
Checklist for Author/Reviewer/GateKeeper
[ ] Interface change (if any) are documented
[ ] Side effects on other features (deployment/upgrade)
[ ] Dependencies on other component(s)
Review Checklist
Checklist for Author
[x] JIRA number/GitHub Issue added to PR
[x] PR is self reviewed
[x] Jira and state/status is updated and JIRA is updated with PR link
[x] Check if the description is clear and explained
Documentation
Checklist for Author
[ ] Changes done to WIKI / Confluence page / Quick Start Guide
Signed-off-by: Tanuja Shinde tanuja.shinde@seagate.com
Problem Statement
Design
Data_node type values are prone to change with respect to multiple data pods, hence we need to remove the hard dependency from this constants and recognize data pods based on storage key.
Coding
Checklist for Author
Testing
Checklist for Author
Impact Analysis
Checklist for Author/Reviewer/GateKeeper
Review Checklist
Checklist for Author
Documentation
Checklist for Author