While working on today’s micro-deployment, I decided I need a few diagrams to make it clear to myself what was really going. Since I went to the effort of making them, I thought I’d share them here with everyone.
Below is the deploy structure we’ve been using for quite a while. There are some more pieces to the puzzle, but for the purpose of this deployment, they’re irrelevant. Notice that we have multiple complete setups, but they all exist within an analogous space. Only one set can be running at a time, and squid is always pointing to whichever stack is running.
The current live deployment is a little bit messy, since we have two side by side setups, but with both zope instances pointing to the same instance zeo. While providing the side by side deployment that I prefer, the intertangling is messy and just not sustainable.
This is the deplyment we’ll have after today. There will be a separate zeo instance that both zope instances will point to. Care has to be kept to give zeo access to any code that performs zeo write conflict resolution. Currently, the only Product we use that does is the QueueCatalog…
Yay. This also is a necessary prerequisite to running both stacks at once behind a load balancer, which we’ve been wanting for a while. RA is working on that.
Comment by admin on July 31, 2008 at 3:35 pm