Last modified: 2014-11-18 21:45:53 UTC
From email discussion with Brandon Black re bug 73357: Brandon said: > Greg said: >> Can we make sure that when we upgrade Varnish on prod we do so on Beta >> Cluster as well? Maybe even doing it first on Beta Cluster to test >> things :) But I'll leave specifics to you. > > Yes! :) Perhaps ideally, we should have puppet auto-upgrading to the latest > package revs in beta. The only reason we don't do that in prod is because > there are outage impacts from restarts, so the upgrade->restart cycle has to be > paced out manually after testing. But for now, I'll try to remember to include > beta.
Mukunda: Could you take a stab at this one with feedback from Brandon and Antoine?
CCing Brandon The straight forward way would be to have puppet auto-upgrade varnish on beta cluster. Maybe using hiera() to define ensure => latest only on labs. There is a couple oddities if I remember properly: * the package upgrade override some of our puppet provided files (init defaults, some config). So it needs to be restarted again once puppet reapplied the conf * if the new version of vagrant is not back compatible with our conf, we need the conf to be merged first. Take them with a grain of salt though. I would love release and ops team to write down the way Vagrant related changes are pushed to production. From there come up with a nicer strategy that might involve beta cluster and some integration tests as a stage before the change land to production.
