Migrated from
f5alliances/f5_provisioner#8

reported by @codygreen

Please abstract the linux AMI information to a variable so customers that only have access to private market places, such as the F5 UDF environment, can still deploy the f5 provisioner.Another option would be to search for the latest version of the AMI versus requiring a hardcoded version.

migrated from f5alliances/f5_provisioner#13

reported by @codygreen

currently, TMOS 13.1.0.7 is deployed. We should target the latest version of the BIG-IP AMI.

@payalsin

Member
payalsin commented 24 days ago
I would want to leave it at one TMOS release since if we keep supporting the latest we will have to test everything that we are running on this environment using the latest release. Maybe first phase we go with 13.1.0.7 and then gradually start supporting more BIG-IP releases.

We can provide it to be a variable so that if customer/user wants to install another release they have a path forward

migrated from
f5alliances/f5_provisioner#7

reported by @codygreen:

Please abstract the F5 AMI information to a variable so customers that only have access to private market places, such as the F5 UDF environment, can still deploy the f5 provisioner.

Another option would be to search for the latest version of the AMI versus requiring a hardcoded version.

migrated from
f5alliances/f5_provisioner#20

reported by @boroboromy

At the step 6 of AWS setup, "Make sure you have subscribed to the right marketplace AMI (Amazon Machine Image)", the link Click Here direct to F5 BIG-IP Virtual Edition - GOOD (PAYG, 25Mbps)， while it is "name: "F5 Networks Prelicensed Hourly BIGIP-13.1.0.7-0.0.1 - Best 25MBPS *" " in /root/f5_provisioner/provisioner/roles/manage_ec2_instances/defaults. It misleads process

Migrated from f5alliances/f5_provisioner#10

reported by @codygreen

the default password in the f5_vars.yaml file is too basic and I doubt many users will change it which can result in a compromised environment.Have ansible create a random password or leverage SSH keys.

Migrated from
f5alliances/f5_provisioner#9

reported by @codygreen

I can only successfully deployment the provisioner via Python 2.7. When I attempt to do this with Python3 the following task always fails:
TASK [connectivity_test : Wait 400 seconds (using wait_for_connection)]

@danielcayer danielcayer mentioned this issue 24 days ago
provision_lab.yml fails on Mac OS #14