f5_rs_aws_app - Creates an application in an auto-scale group¶
New in version 2.4.
Options¶
| parameter | required | default | choices | comments |
|---|---|---|---|---|
| aws_region |
no | us-west-2 |
|
aws region in which the vpc will be created |
| deploymentName |
yes | unique name for deployment, must be firstname-first letter of last name and a 3 digit number - example yossir100 | ||
| applicationSubnets |
yes | none |
|
expecting two subnets in the format of {subnet1, subnet2} |
| service_name |
yes | app1 |
|
service name for identification |
Examples¶
Deploy:
ansible-playbook –vault-password-file ~/.vault_pass.txt playbooks/aws_app_deploy.yaml -e “aws_region=”$(etcdctl get f5-rs-aws-net/yossir100/aws_region)” applicationSubnets=”$(etcdctl get f5-rs-aws-net/yossir100/applicationSubnets)” deploymentName=yossir100 service_name=App1 vpc=”$(etcdctl get f5-rs-aws-net/yossir100/vpc)”“
Destroy:
ansible-playbook –vault-password-file ~/.vault_pass.txt playbooks/aws_app_deploy.yaml -e “aws_region=”$(etcdctl get f5-rs-aws-net/yossir100/aws_region)” applicationSubnets=”$(etcdctl get f5-rs-aws-net/yossir100/applicationSubnets)” deploymentName=yossir100 service_name=App1 vpc=”$(etcdctl get f5-rs-aws-net/yossir100/vpc)” rs_state=absent”
Return Values¶
Return values are stored in the following etcd path:
f5_rs_aws_app/<deploymentName>/
| name | description | sample |
|---|---|---|
| appAutoscaleGroupName | auto scale group name of the app in EC2 | "yossir-demo1-App1-application-appAutoscaleGroup-SXQKA5PH9TI" |
| appInternalDnsName | internal DNS name of the ELB fronting the app | internal-demo1-App1-AppElb-1123840165.us-west-2.elb.amazonaws.comb |
| appInternalElasticLoadBalancer | Id of ELB for App Pool | demo1-App1-AppElb |
Notes¶
Note
- For more information on using Ansible to manage F5 Networks devices see https://www.ansible.com/integrations/networks/f5.
Status¶
This module is flagged as preview which means that it is not guaranteed to have a backwards compatible interface.
Support¶
This module is community maintained without core committer oversight.
For more information on what this means please read Get help
For help developing modules, should you be so inclined, please read Getting Involved, Writing a Module and Guidelines.