@Dongdong-Zheng said in Declaim node from waroom via command line:
If I can put a weight to the above two scenarios, I would estimate a 80% UseCase A and 20% UseCase B.
Sorry that I may sound fussy with my ‘greedy’ requirements. Unfortunately managing cloud server pool is no fun job and we have to deal with various issues on a daily basis.
First of all, thank you again, and note that your feedback is very valuable to us.
Your requirements are not
greedy, indeed cloud infrastructures are much more dynamic and thus require more effort. However, we are determined to find a good solution.
My early thoughts are:
- for UseCaseA:
sudo netdata-unclaimed.sh would do the trick.
- for UseCaseB: A garbage collection setting that could be set either on space or at a room level. Nodes that are unreachable for a prolonged period, are automatically removed, with no action on your end.
- Alternative for UseCaseB: A way to access a subset cloud API using a token. So you can do actions like node addition or removal programmatically. This would be useful if you already have a way of a programmatic way of detecting non-responsive servers.
@Dongdong-Zheng I would like to ask, what do you think about 2, 3 in terms of effort and satisfaction from your end?
@Manos-Saratsis any thoughts on 2.
I am going to think and discuss with the team about it. So I may reply with extra feedback later.