asc.core.core role – Deploy the shared core infrastructure (network, DNS, Key Vault, storage and jumphost)
Note
This role is part of the asc.core collection (version 2.0.0).
It is not included in ansible-core.
To check whether it is installed, run ansible-galaxy collection list.
To install it use: git clone git@ssh.dev.azure.com:v3/cloudasc/iac-ansible-collections/core $HOME/.ansible/collections/ansible_collections/asc/core.
To use it in a playbook, specify: asc.core.core.
Entry point main – Deploy the shared core infrastructure (network, DNS, Key Vault, storage and jumphost)
New in asc.core 1.0.0
Synopsis
Provisions the foundation every ASC environment builds on - the resource group, virtual networks and subnets, the private DNS zone, an Azure Key Vault for secrets, the shared storage account, and the Linux jumphost that fronts SSH/WinRM access to every other host.
Runs in two phases controlled by the
common_terraform_*variables: first it renders the Terraform configuration from the role templates and can runplan/apply/destroy, then the configure pass provisions and hardens the jumphost over the generated inventory.This role must be deployed first; the
ap,dfirandxhackcollections peer their own networks onto the vnets it creates.
Parameters
Parameter |
Comments |
|---|---|
SSH public key to use for the admin user on all systems |
|
Name of the admin user on all systems Default: |
|
Environment the deployed resources will be tagged with (p: prod, d: dev, t: training, e: demo) Choices:
|
|
Azure location (region) to deploy the resources to Default: |
|
Refresh the dynamic inventory from the Terraform state after Choices:
|
|
Wether to run ‘terraform apply’ or not Choices:
|
|
If ‘true’, generates new terraform configuration files, otherwise will use the existing ones Choices:
|
|
Wether to run ‘terraform destroy’ or not Choices:
|
|
The directory where the terraform configuration files are located (relative to the deployment folder) Default: |
|
Wether to run ‘terraform plan’ or not. (implied if ‘common_terraform_apply’ or ‘common_terraform_destroy’ is ‘true’) Choices:
|
|
Virtual networks for the core services, keyed by vnet name. Each vnet takes Merged with the other modules’ vnets into |
|
Virtual network peerings for the core services, each a Merged with the other modules’ peerings into Default: |
|
Name of the first vnet. |
|
Name of the second vnet. |
|
Name of the environment to deploy |
|
Internal domain name to use for the deployed resources Default: |
|
Jumphost VM settings. |
|
Inventory host name of the jumphost, used for its Guacamole SSH connection. Falls back to |
|
Name of the jumphost VM. Default: |
|
Azure VM size of the jumphost. Default: |
|
Path to use for temporary files on Linux systems Default: |
|
Email address(es) of the person to contact in case of issues with the Azure resources |
|
Azure subscription ID to deploy the resources to |
|
Team code to tag Azure resources (cf. https://eysbp.visualstudio.com/ADV-ASC/_git/asc-cloud-wiki?path=%2FPlatform-Standards%2FNaming-Convention%2FTeams.md) |
|
Azure tenant ID to deploy the resources to Default: |
|
Dictionary of remote state configuration to use for the terraform deployment. If not specified, the remote state will be stored locally. |
|
Azure storage container name to use for the remote state |
|
If ‘true’, the remote state will be enabled Choices:
|
|
Key to use for the remote state Default: |
|
Azure resource group name to use for the remote state |
|
Azure storage account name to use for the remote state |
|
Azure subscription ID to use for the remote state Default: |
|
Azure tenant ID to use for the remote state Default: |
|
Timezone to use for the deployed resources Default: |
|
Path to use for temporary files on Windows systems Default: |
Authors
Ignace De Cock