Seagate / cortx-prvsnr

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).
https://github.com/Seagate/cortx
GNU Affero General Public License v3.0
17 stars 40 forks source link

[WIP] CORTX-30726: Generate Machine-id for all Nodes from FQDN/any string coming from solution(cluster.yaml) #6357

Closed tanujashinde0405 closed 2 years ago

tanujashinde0405 commented 2 years ago

Problem Statement

Objectives

Anything that provisioner does must be transparent to the component, i.e. components should not have to change anything. ID treatment must be same for all Pods / containers. No special treatment for Server or Data Pods. Minimise the amount of business logic around machine-id in k8s code. How this can be done.

Provisioner will generate /etc/cortx/machine-id CORTX image will have link from /etc/machine-id -> /etc/cortx/machine-id

Design

Coding

Checklist for Author

Testing

Checklist for Author

Impact Analysis

Checklist for Author/Reviewer/GateKeeper

Review Checklist

Checklist for Author

Documentation

Checklist for Author

kailashyadav11 commented 2 years ago

Please run the unit tests related to the change and add new testcases if needed.

tanujashinde0405 commented 2 years ago

Please run the unit tests related to the change and add new test cases if needed.

Ran the tests, and everything is working, no new test cases are required. Samples files under the test folder were outdated, I have updated them as well as updated readme.md.