Terraform templates to create F5XC rSeries based CE (manual mode deployment).
Name | Version |
---|---|
terraform | >= 1.7.0 |
curl | >= 1.7 |
git | >= 8.0 |
jq | latest |
Name | Status |
---|---|
Linux | supported |
Mac OS (Sonoma) | supported |
Windows | unsupported |
- Git (https://git-scm.com/book/en/v2/Getting-Started-Installing-Git)
- Terraform (https://developer.hashicorp.com/terraform/install?product_intent=terraform)
- F5 XC Credentials (https://docs.cloud.f5.com/docs/how-to/user-mgmt/credentials)
- API Certificate
- SSH public key
- ssh-keygen -t rsa -b 4096 -C "[email protected]"
- F5 XC full tenant name
- Clone this repo with:
git clone --recurse-submodules https://github.com/f5devcentral/terraform-xc-rseries-ce
- Enter repository directory with:
cd terraform-xc-rseries-ce
- Follow usage description in topologies section
- Multiple examples in example directory are available. Change to example directory that is to be deployed
with
cd examples/<example_dir_name>
Description of available input variables. Used input variables will change per topology example:
Name | Description |
---|---|
SLO | Site local outside interface (external interface / egress interface) |
SLI | Site local inside interface (internal interface ( ingress interface) |
project_prefix | String added at the beginning of various rSeries / F5 XC object identifier. <project_prefix>_<object> |
project_suffix | String added at the end of various rSeries / F5 XC object identifier. <project_prefix>_<object>_<project_suffix> |
Example prefix + suffix for F5XC site name project_prefix_cluster_name_project_suffix |
|
f5xc_tenant | Full f5 xc tenant name e.g. playground-abcdefg |
f5xc_api_url | F5 XC API URL e.g. https://playground.console.ves.volterra.io/api |
f5xc_cluster_name | F5 XC cluster name e.g. "rseries-ce-test" |
f5xc_api_p12_file | Path to F5 XC exported API cert file |
Name | Description |
---|---|
Single Node Single NIC | Description |
Single Node Multi NIC | Description |
Three Node Cluster Single NIC | Description |
Three Node Cluster Multi NIC | Description |
Name | Description |
---|
Find CE cloud-config example for ClickOps deployment at Cloud-Config
For support, please open a GitHub issue. Note, the code in this repository is community supported and is not supported by F5 Networks. For a complete list of supported projects please reference SUPPORT.md.
Please refer to the F5 DevCentral Community Code of Conduct.
Copyright 2014-2020 F5 Networks Inc.
Before you start contributing to any project sponsored by F5 Networks, Inc. (F5) on GitHub, you will need to sign a Contributor License Agreement (CLA).
If you are signing as an individual, we recommend that you talk to your employer (if applicable) before signing the CLA since some employment agreements may have restrictions on your contributions to other projects. Otherwise, by submitting a CLA you represent that you are legally entitled to grant the licenses recited therein.
If your employer has rights to intellectual property that you create, such as your contributions, you represent that you have received permission to make contributions on behalf of that employer, that your employer has waived such rights for your contributions, or that your employer has executed a separate CLA with F5.
If you are signing on behalf of a company, you represent that you are legally entitled to grant the license recited therein. You represent further that each employee of the entity that submits contributions is authorized to submit such contributions on behalf of the entity pursuant to the CLA.