Forum Discussion
NimbostratusF5 for rolling deployments
Hi all!
I'd like to achieve rolling web deployments for servers behind a F5. However the F5 proxies multiple applications. So any misconfiguration/error while deploying one application shouldn't affect other applications. Is there a way to achieve this? I read about hardware/software partition with user accounts with limited administrative capability. Is this something that can help me? Considering I'm new to F5 would this be a complicated setup to achieve?
AMiles_377865Cirrocumulus
Hello Vignesh,
To clarify, you are attempting to set up rolling deployments on your back-end servers, and not your F5s, correct? I could be misunderstanding your question, but you shouldn't have to worry about partitions/administrative privileges; it should be a fairly normal configuration. The F5s will continue to proxy traffic to your different applications regardless of the status of an individual application.
Just be careful to put a very robust monitor on your applications, to ensure that the F5 does not send traffic to the server you are updating. The F5 should have the server you are updating marked as down, and the rest of the servers as up.
At a high-level, your rolling deployment upgrade plan should look like this:
- Disable/remove the server you are updating from any pools/VS. This will prevent traffic from being sent to it.
- Perform upgrade.
- Test server
- If working, list it as "up" so that traffic can be sent to it.
- Move on to the next server in your pool.
Best of Luck,
Austin