f5devcentral / fas-provisioner

F5 SANDBOX PROVISIONER

IMPORTANT NOTE: This GitHub repository is no longer being maintained or updated. The content is available as-is, and while it's still accessible, it may contain outdated or obsolete information.

Overview

The F5 Sandbox Provisioner is a part of the Solution Sandbox. This is a scenario based demo environment to help users learn about how F5 delivers Application Services to improve security and performance

Goal

With F5 Sandbox Provisioner, users are provided with an F5 + Ansible sandbox environment fully configured in the cloud. The Sandbox Provisioner deploys the infrastructure for the Solution Sandbox in AWS. This consists of:

• A F5 BIG-IP Virtual Edition instance
• Two webservers
• An Ansible node

The Solution Sandbox can be used:

• to build demos and proof of concepts
• to find automation solutions for common customer use-cases
• as a self learning tool to get familiar with Ansible Automation for F5

How to use?

Follow F5 Ansible AWS Provisioner for detailed steps to spin up and tear down the sandbox infrastructure using the Sandbox Provisioner

Support

This project is a community effort to promote Network and Security automation. For any feature requests or issues, feel free to open an issue and we will do our best to address it

fas-provisioner's Issues

Python3 Support

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

Password Should Be Randomly Generated

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.

Linux AMI harcoded

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.

F5 AMI hardcoded

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.

AMI which need be subscribed is wrong

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

Default to latest BIG-IP release

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