DATACMNS-394 grid discovery spi #54
Closed
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
NOTE: PR to get visibility for this code and it needs a shared home outside of SHDP/XD.
Adding functionality on an interface level to do discovery of a grid,
handle node grouping and manage grouping.
framework interfaces and custom implementors to work around issues more easily.
ManagedContainerGridGroups. These should be flexible enough to be used
internally(grid will discover itself) or externally(data is fed in the
system externally). Should also work in cases where grid nodes will
discover itself without any central server(i.e. hazelcast), or having a central
point of origin for discovery(Hadoop Yarn/Appmaster).
not having a need to fix identifier as String or Object.
create a totally extended discovery spi while other users are still able to
understand what happens on a low level interfaces(what i.e.
ContainerGrid, ContainerNode is giving out.