Refactor codes to support Mutli-Podmanager fully
Since our multi pod manager backend service seems ready as well as some of our controller api and logics still work for a locked pod manager based on the config file . So it's time to make a little refactor to support mlti-podmanager fully.
This BP would remove the podm cofiguration options in the config file.
And this change would cover the whole original composion logic and redfish.py api level as well as we would bring up the relations between the needed components and pod manager.
Then we would provide some new features or functions like :
"podmanager scheduler",
"safe-deletion logics on podm",
"podmanager connection/client" (refactor valence.
"podmanager connection pool"
more details please see the spec doc ：
https:/
Blueprint information
- Status:
- Not started
- Approver:
- Nate Potter
- Priority:
- Undefined
- Drafter:
- hubian
- Direction:
- Approved
- Assignee:
- hubian
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
What is meant by "Pod Manager Client"? Is that separate from the regular valence client? I'd also add ability to select pod manager at composition time and storing pod information in resources like nodes and systems database entries to work items. Thanks!
----Reply:
For the Pod manager client:
Pod manager client is just a code level feature. This just want to refactor valence.
Others of your comment are ok to me ~
