Skip to content
This repository has been archived by the owner on Sep 18, 2020. It is now read-only.

reboot groups #17

Open
mischief opened this issue Oct 17, 2016 · 3 comments
Open

reboot groups #17

mischief opened this issue Oct 17, 2016 · 3 comments

Comments

@mischief
Copy link
Contributor

this issue is for discussion on implementing reboot groups, similar to what locksmith has today.

currently my idea is to create a kubernetes TPR that describes which nodes are in which groups, and how many nodes of that groupt to reboot at once.

@ghost
Copy link

ghost commented Jan 16, 2018

is it possible to simulate reboot groups by running several set of agents and operator each on different namespace? e.g. group1 will have agents and operator with namespace group1, group2 will have agents and operator with namespace group2

@sdemos
Copy link
Contributor

sdemos commented Jan 16, 2018

It seems like that would be possible, as long as you restrict the nodes that the agent can run on to only nodes in your "group", but I've never tried to do anything like that before. However, currently cluo only reboots one node at a time anyway, so the main reason that reboot groups exist in locksmith isn't actually relevant here unless we provide the ability to configure the number of machines rebooting at once.

@ghost
Copy link

ghost commented Jan 17, 2018

yes, the agent will be restricted into particular node using node selector, thus effectively it is possible two nodes on different group will reboot at the same time

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants