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

document f5_cloud_failover_vips attribute for AWS #20

Closed
tewfikm opened this issue May 18, 2020 · 4 comments
Closed

document f5_cloud_failover_vips attribute for AWS #20

tewfikm opened this issue May 18, 2020 · 4 comments
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@tewfikm
Copy link

tewfikm commented May 18, 2020

Hi,
Clouddoc states that for AWS :

For Across Network Topology¶
If provisioning Across Network Topology, you will need to:

Create two sets of tags for Elastic IP addresses:

a special key called f5_cloud_failover_vips that contains a comma-separated list of addresses mapping to a private IP address on each instance in the cluster that the Elastic IP is associated with. For example: 10.0.0.10,10.0.0.11

ASK:

Could you please update API Docs with this parameter ?

Provide sample example for 2x EIP and 4 privates IPs ?

Thanks

@shyawnkarim
Copy link

I've created a document enhancement for this, internal ID AUTOSDK-320.

@shyawnkarim shyawnkarim added the documentation Improvements or additions to documentation label May 18, 2020
@shyawnkarim shyawnkarim added this to the backlog milestone May 29, 2020
@tewfikm
Copy link
Author

tewfikm commented Jun 11, 2020

Hi @shyawnkarim
Do you have an ETA please ?
Customer is chasing.
Many thanks

@nmenant
Copy link
Contributor

nmenant commented Sep 21, 2020

This is done:
image

@f5-chidambaram please close

@shyawnkarim
Copy link

This addition to our documentation was included with Release 1.5.

@shyawnkarim shyawnkarim reopened this Jan 29, 2021
@shyawnkarim shyawnkarim modified the milestones: backlog, Release 1.5 Jan 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

4 participants