OpenPlans Operations

Various discussions and emails after this last deployment have made it obvious that I’m not the only person invested in the deployments.  As such, I want to be a bit more open with what my plans are so as not to step on the toes of other people who access and support our stack.

In the last deployment, I built a second site to increase my level of comfort with the deploy.  It gave me a larger safety net, and a way to deploy without needing as much knowledge of the existing site structure.  Going forward, while I want to be able to run parallel deploys, I’m not locked down to the way things are.  In fact, I already have to clean up the mess of one site connecting to the zeo from a different site.  I’d like to fix this by performing a micro-deploy on Thursday that just moves zeo out of the build so that we can build sites independantly, and as Rob pointed out, run zopes in parallel for higher availablity and load balancing.

 Since it’s so small, and we know have builds handling it, I’d also like to change the Maildrop config to run out of supervisor.  The upside is not worrying about touching the system for a build, and the downside is that we have to make sure to either migrate the spool, or (ideally) leave any existing maildrop running until it flushes its queue.