Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sequential reboot #35

Closed
swiftgist opened this issue Oct 27, 2016 · 1 comment
Closed

sequential reboot #35

swiftgist opened this issue Oct 27, 2016 · 1 comment

Comments

@swiftgist
Copy link
Contributor

In stage/prep/minion/default.sls, there is a restart call to ceph.updates.restart.

Since this is a minion file targeted from orchestration, these will run in parallel. Now, the reboot only happens when there's a kernel update. During a fresh installation, a parallel update/reboot is desirable.

Once a cluster is running, a sequential reboot is necessary. The preference is to keep all other steps running in parallel and only run the reboots sequentially when something like roles are defined.

My first guess would be create a salt-runner that returns each minion name in the proper order according to role or return '*' and hope that will work as a target. The "proper" order should reflect the same order as the restart orchestration (i.e. ceph/restart/default.sls)

@jschmid1
Copy link
Contributor

jschmid1 commented Nov 2, 2016

this is addressed by pullrequest #43

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

No branches or pull requests

2 participants