orchestrator icon indicating copy to clipboard operation
orchestrator copied to clipboard

[Feature Request] Add API endpoint to submit pools per instance

Open tamimkh opened this issue 5 years ago • 2 comments

Currently, in order to add "pools" to orchestrator you need to provide a definitive list of instances that belong to a single pool. This API doesn't work well with management systems that are organized based on instances since it may be difficult to find a definitive list of instances for a given pool. Nonetheless, it does seem like the data model for pools is separated out by instances so it should be possible to just add a new API endpoint to accept the data per instance and have all the other pool related features work without any modifications.

Furthermore, "tags", which are instance based, don't seem to fit our use case very well since we are interested in UI features provided by pools. In particular, we want to have some way to tell which instance is in which pool and also have an overview page where all the pools are listed along with their instances for a specific cluster. For tags, these UI features don't currently exist and also would likely be difficult to implement since tags currently have no relationship with clusters.

As a result, I would like to propose the creation of a submit-instance-pools API endpoint and CLI option that will allow for the submission of all the pools associated with a single instance.

tamimkh avatar Feb 11 '20 19:02 tamimkh

@tamimkh thank you -- this makes perfect sense. If you're able to provide a PR, I'm grateful ❤️

shlomi-noach avatar Feb 12 '20 04:02 shlomi-noach

What is the function of pool? No such instructions were found in official documents I was researching orchestrator recently, and saw some parameters and commands about pool, but I really don't understand what pool is used, what problem is it used to solve?

Fanduzi avatar Jun 24 '22 09:06 Fanduzi