CORTX-32740: HA - Consul Support for GCONF

[Madhura-08]

• Change the mechanism to fetch consul and kafka endpoints in order to adhere to consul based Gconf and it should also be backward compatible supporting yaml based Gconf.
• Remove storage keyword from the keys which is used to fetch cvg, data and metadata disks
• Add more logging

Signed-off-by: Madhura Mande madhura.mande@seagate.com

Problem Statement

https://jts.seagate.com/browse/CORTX-32740. As yaml based Gconf is changed to consul based Gconf, HA is failing to fetch consul and kafka endpoints. So, now HA need changed to support for consul based Gconf for HA mini provisioning to work.

Design

In order to get consul and kafka endpoints correctly, first number of endpoints can be fetched. Then after iterating, matching protocol scheme(like http, tcp) can be found in order to get correct endpoint

Coding

• [ ] Coding conventions are followed and code is consistent

Testing

• [x] Unit and System Tests are added
• [ ] Test Cases cover Happy Path, Non-Happy Path and Scalability
• [x] Testing was performed with RPM Test details: https://jts.seagate.com/secure/attachment/527134/CORTX-32740_Test_Results.txt https://jts.seagate.com/secure/attachment/527288/CORTX-32740_Yaml_Test_Results.txt

Review Checklist

• [x] PR is self reviewed
• [x] JIRA number/GitHub Issue added to PR
• [x] Jira and state/status is updated and JIRA is updated with PR link
• [ ] Check if the description is clear and explained
• [x] If yes for above point, is a notification sent to all other cortx components? [Y/N] N/A
• [x] Side effects on other features (deployment/upgrade)? [Y/N] N
• [x] Dependencies on other component(s)? [Y/N] N
• If yes for above point, post link to the corresponding PR.

Review Checklist

Documentation

Checklist for Author

• [ ] Changes done to WIKI / Confluence page / Quick Start Guide