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

Workflow for upgrading Salt #165

Closed
aneeshusa opened this issue Nov 21, 2015 · 3 comments
Closed

Workflow for upgrading Salt #165

aneeshusa opened this issue Nov 21, 2015 · 3 comments

Comments

@aneeshusa
Copy link
Member

@aneeshusa aneeshusa commented Nov 21, 2015

Homebrew has packaged Salt 2015.8.1 so I'll put in a PR to update the pinned salt version soon. However, upgrading Salt requires some extra care for two reasons:

  1. It's best to restart the service when the package is updated to keep the installed and running versions in sync, but restarting a master or minion service will interrupt an ongoing highstate.
  2. Masters need to be updated before minions, but salt '*' state.highstate cannot enforce ordering - Salt's orchestration can help with this.

I want to make sure there is a concrete plan for this and future Salt version upgrades to prevent breakage. Do you currently have a workflow for updating Salt? If not, I think manual updates are fine for now since there are so few machines: first on the salt master, then on the minions. I'll look into adding some automation to this.

@aneeshusa
Copy link
Member Author

@aneeshusa aneeshusa commented Nov 24, 2015

Blocked on saltstack/salt#29098.

@edunham
Copy link
Contributor

@edunham edunham commented Apr 4, 2016

@aneeshusa for the "document the workflow" part of this issue, I've moved the Salt docs into their own wiki page at https://github.com/servo/servo/wiki/SaltStack-Administration.

It looks like the Salt issue that this was previously blocked on is now resolved.

@aneeshusa
Copy link
Member Author

@aneeshusa aneeshusa commented Apr 7, 2016

Great, closing since we've agreed on manual updates for now.

@aneeshusa aneeshusa closed this Apr 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.