Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/equinix/terraform-equinix-csr1000v
Terraform module for quick deployment of Cisco CSR1000V router on Equinix Platform
https://github.com/equinix/terraform-equinix-csr1000v
cisco csr1000v equinix equinix-platform nfv router sdn terraform terraform-module
Last synced: about 1 month ago
JSON representation
Terraform module for quick deployment of Cisco CSR1000V router on Equinix Platform
- Host: GitHub
- URL: https://github.com/equinix/terraform-equinix-csr1000v
- Owner: equinix
- License: mit
- Created: 2021-03-11T15:16:32.000Z (almost 4 years ago)
- Default Branch: main
- Last Pushed: 2023-12-15T02:23:39.000Z (about 1 year ago)
- Last Synced: 2024-05-09T14:25:09.899Z (8 months ago)
- Topics: cisco, csr1000v, equinix, equinix-platform, nfv, router, sdn, terraform, terraform-module
- Language: HCL
- Homepage:
- Size: 28.3 KB
- Stars: 5
- Watchers: 10
- Forks: 5
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Equinix Network Edge: Cisco CSR 1000V Router
A Terraform module to create Cisco CSR 1000V router network device
on the Equinix platform.
Supported device modes:
| Management Mode | License mode | Notes |
|-----------------|--------------|-------|
| Equinix managed | Subscription |-|
| Equinix managed | Bring your own license | `license_token` required|
| Self managed | Bring your own license |-|
## Requirements
| Name | Version |
|------|---------|
| terraform | >= 0.13.0 |
| equinix/equinix | >= 1.1.0 |
## Providers
| Name | Version |
|---------|----------|
| equinix/equinix | >= 1.1.0 |
## Assumptions
* if `account_number` is not provided, then `Active` account within given metro
will be used
* most recent, stable version of a device software for a given `software_package`
will be used
* secondary device name will be same as primary with `-secondary` suffix added
* secondary device notification list will be same as for primary
* secondary device `ssh-key` will be same as for primary (if provided)
## Example usage
```hcl
provider equinix {
client_id = var.equinix_client_id
client_secret = var.equinix_client_secret
}
module "csr1000v" {
source = "equinix/csr1000v/equinix"
metro_code = "SV"
platform = "medium"
software_package = "IPBASE"
software_version = "16.09.02"
throughput = 1
throughput_unit = "Gbps"
name = "tf-tst-csr1000v"
hostname = "pri"
term_length = 1
notifications = ["[email protected]"]
secondary = {
enabled = true
metro_code = "DC"
hostname = "sec"
}
}
```
## Inputs
| Name | Description | Type | Default | Required |
|------|-------------|------|---------|----------|
|metro_code|Two-letter device location's metro code|`string`|`""`|yes|
|account_number|Billing account number for a device. If not provided, active account for a device metro code will be used|`string`|`0`|no|
|platform|Device hardware platform flavor: `small`, `medium`, `large`|`string`|`""`|yes|
|software_package|Device software package: `APPX`, `AX`, `IPBASE`, `SEC`|`string`|`""`|yes|
|software_version|Device software Version: `16.09.02`, `16.09.03`, `16.09.05`, `16.12.03`|`string`|`""`|no|
|self_managed|Determines device management mode: self-managed or Equinix managed|`bool`|`false`|no|
|byol|Determines device licensing mode: bring your own license or subscription|`bool`|`false`|no|
|license_token|License token applicable for Equinix managed device in BYOL licensing mode|`string`|`""`|no|
|throughput|Device license throughput|`number`|`0`|yes|
|throughput_unit|License throughput unit (`Mbps` or `Gbps`)|`string`|`""`|yes|
|name|Device name|`string`|`""`|yes|
|hostname|Device hostname prefix|`string`|`""`|yes|
|term_length|Term length in months: `1`, `12`, `24`, `36`|`number`|`0`|yes|
|notifications|List of email addresses that will receive notifications about device|`list(string)`|n/a|yes|
|acl_template_id|Identifier of a network ACL template that will be applied on a device|`string`|`""`|no|
|additional_bandwidth|Amount of additional internet bandwidth for a device, in Mbps|`number`|`0`|no|
|interface_count|Device interface count: either `10` or `24`|`number`|`10`|no|
|ssh_key|Map of SSH public key attributes|`map`|N/A|no|
|secondary|Map of secondary device attributes in redundant setup|`map`|N/A|no|
SSH key map attributes:
| Name | Description | Type | Default | Required |
|------|-------------|------|---------|----------|
|username|Username associated with a given public key|`string`|`""`|yes|
|key_name|The name of the SSH public key|`string`|`""`|yes|
Secondary device map attributes:
| Name | Description | Type | Default | Required |
|------|-------------|------|---------|----------|
|enabled|Value that determines if secondary device shall be created|`bool`|`false`|no|
|license_token|License token applicable for Equinix managed device in BYOL licensing mode|`string`|`""`|no|
|metro_code|Two-letter secondary device location's metro code|`string`|`""`|yes|
|account_number|Billing account number for a device. If not provided, active account for a device metro code will be used|`string`|`0`|no|
|hostname|Device hostname prefix|`string`|`""`|yes|
|acl_template_id|Identifier of a network ACL template that will be applied on a secondary device|`string`|`""`|no|
|additional_bandwidth|Amount of additional internet bandwidth for a secondary device, in Mbps|`number`|`0`|no|
## Outputs
| Name | Description |
|------|-------------|
|id|Device identifier|
|status|Device provisioning status|
|license_status|Device license status|
|account_number|Device billing account number|
|cpu_count|Number of device CPU cores|
|memory|Amount of device memory|
|software_version|Device software version|
|region|Device region|
|ibx|Device IBX center code|
|ssh_ip_address|Device SSH interface IP address|
|ssh_ip_fqdn|Device SSH interface FQDN|
|interfaces|List of network interfaces present on a device|
|secondary|Secondary device outputs (same as for primary). Present when secondary device was enabled|