Deployment tooling/Cabal/2016-09-26

Last Week

• Released: scap 3.3.0-1 -- changelog: https://github.com/wikimedia/scap/blob/master/debian/changelog#L1-L20
•  Done Allow per-environment config-override
•  Done Local config deploys should use the target's current version
  •  Done TODO: Break out proposed solution to separate task
  •  Done TODO: Store DEPLOY_HEAD on target
• N Not done Scap config management: Jinja2 fills templates with Pythonic values

Next release/blocking

• Scap config management: Jinja2 fills templates with Pythonic values
• Scap3 submodule space issues (all users, no workaround, enhancement)
• Scap SWAT automate patch merging & testing during a swat deployment

Soon™/Wishlist

• Scap3 config references to deployed directory (all users, no workaround, incorrect/non-obvious functionality)
• Announce all deploys via IRC
• Automate beta scap3/keyholder setup
  • Easy, but dumb to do manually
  • Tricky to automate

New tasks

• Make symlink swaps optional
  • Unneeded for some?
  • Complicated for others

• scap deploy-local should make fewer assumptions
  • Want to do for next release
  • Potential blocked on puppet changes

• remove hard-coded upstart commands
  • Should be an easy one

As Always

• Phase 2
• Phase 1
• Workboard https://phabricator.wikimedia.org/tag/scap3/
• Etherpad backed up to https://www.mediawiki.org/wiki/Deployment_tooling/Cabal
• Future document https://www.mediawiki.org/wiki/Deployment_tooling/Future
• Spreadsheet: https://docs.google.com/spreadsheets/d/1MlEsFxrLvdZdV_G82WEAIvBXr7ArO7nCEKaFClHhJEw/edit#gid=0