daos
daos copied to clipboard
DAOS-15215 control: Update internals for multiprovider
Backporting control plane related internal changes from the feature/multiprovider branch. These changes affect internals only, and not user interfaces.
- Updated protobuf structures to recognize secondary providers in a backward-compatible way.
- Updated libdaos network config logic to pass values from env variables to the agent, to allow better decision making when choosing a network interface.
- Add support for multiple providers to control plane internal structures, including config file structures. They are intended to be invisible to users until we enable the feature throughout the stack.
Features: control Required-githooks: true
Before requesting gatekeeper:
- [ ] Two review approvals and any prior change requests have been resolved.
- [ ] Testing is complete and all tests passed or there is a reason documented in the PR why it should be force landed and forced-landing tag is set.
- [x]
Features:
(orTest-tag*
) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR. - [x] Commit messages follows the guidelines outlined here.
- [x] Any tests skipped by the ticket being addressed have been run and passed in the PR.
Gatekeeper:
- [ ] You are the appropriate gatekeeper to be landing the patch.
- [ ] The PR has 2 reviews by people familiar with the code, including appropriate owners.
- [ ] Githooks were used. If not, request that user install them and check copyright dates.
- [ ] Checkpatch issues are resolved. Pay particular attention to ones that will show up on future PRs.
- [ ] All builds have passed. Check non-required builds for any new compiler warnings.
- [ ] Sufficient testing is done. Check feature pragmas and test tags and that tests skipped for the ticket are run and now pass with the changes.
- [ ] If applicable, the PR has addressed any potential version compatibility issues.
- [ ] Check the target branch. If it is master branch, should the PR go to a feature branch? If it is a release branch, does it have merge approval in the JIRA ticket.
- [ ] Extra checks if forced landing is requested
- [ ] Review comments are sufficiently resolved, particularly by prior reviewers that requested changes.
- [ ] No new NLT or valgrind warnings. Check the classic view.
- [ ] Quick-build or Quick-functional is not used.
- [ ] Fix the commit message upon landing. Check the standard here. Edit it to create a single commit. If necessary, ask submitter for a new summary.
Bug-tracker data: Ticket title is 'Backport internal control plane changes from feature/multiprovider' Status is 'In Progress' https://daosio.atlassian.net/browse/DAOS-15215
Bug-tracker data: Ticket title is 'Backport internal control plane changes from feature/multiprovider' Status is 'In Progress' https://daosio.atlassian.net/browse/DAOS-15215
Bug-tracker data: Ticket title is 'Backport internal control plane changes from feature/multiprovider' Status is 'In Progress' https://daosio.atlassian.net/browse/DAOS-15215
Bug-tracker data: Ticket title is 'Backport internal control plane changes from feature/multiprovider' Status is 'In Progress' https://daosio.atlassian.net/browse/DAOS-15215
Bug-tracker data: Ticket title is 'Backport internal control plane changes from feature/multiprovider' Status is 'In Progress' https://daosio.atlassian.net/browse/DAOS-15215
Ticket title is 'Backport internal control plane changes from feature/multiprovider' Status is 'In Review' https://daosio.atlassian.net/browse/DAOS-15215
Test stage Functional on EL 8.8 completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-13841/3/execution/node/1173/log
@daos-stack/daos-gatekeeper Please use the PR description as the commit message on this one.