Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support availability zones in Failover #11

Open
JeffGiroux opened this issue Jul 11, 2022 · 2 comments
Open

Support availability zones in Failover #11

JeffGiroux opened this issue Jul 11, 2022 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@JeffGiroux
Copy link

Is your feature request related to a problem?

Yes, BIG-IPs are deployed to same availability zone and this reduces physical redundancy.

Describe the solution you'd like

User would like to deploy BIG-IP to two different availability zones. This will require an additional zone parameter where the 2nd BIG-IP will be deployed to the second zone.

Describe alternatives you've considered

Right now in current template form, user must edit the python script file to adjust for a second zone and/or modify the yaml file to pass an additional zone parameter into python file...both requiring edits.

Additional context

BIG-IP deployment should follow cloud best practices and CSP recommended guidance for SLAs and HA. This results in BIG-IP needing to be deployed to multiple AZs.

@shyawnkarim
Copy link

Thanks for requesting this enhancement. Its been added to our backlog and is now being tracked with internal ID, ESECLDTPLT-3138.

@shyawnkarim shyawnkarim added enhancement New feature or request labels Jul 13, 2022
@shyawnkarim shyawnkarim modified the milestone: backlog Jul 13, 2022
@JeffGiroux
Copy link
Author

Is this going to make the next release (zone selection per BIG-IP VM instance)? If not, what is estimated time? Tnhx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants