Automatically populate ClusterODM according to deployed NodeODMs

[nghi01]

What is the problem?

Currently, ClusterODM does not get populated automatically with deployed nodes.

What should be the expected behavior?

Make it so that when we finish deploying NodeODMs, when we launch ClusterODM, ClusterODM gets automatically populated with the relevant nodes where NodeODMs are running.

How can we reproduce this? (What steps did you do to trigger the problem? If applicable, please include multiple screenshots of the problem! Be detailed)

It's an enhancement/improvement plan.

[nghi01]

Suggested idea for solution:

• Spin up NodeODM instances as we are already doing
• Query the queue for which nodes got chosen
• Use the results of that query to populate the nodes.json file
• Launch ClusterODM which will automatically be populated with the relevant nodes where NodeODM is running.

[pierotofy]

Hey @nghi01 👋 we'd welcome a PR that improves automatic population of nodes.

Would you be interested in contributing one?

[nghi01]

Yes, I'll be working on it.