diff --git a/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2aws/README.md b/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2aws/README.md index 74be7d71c..b77ea1bb2 100644 --- a/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2aws/README.md +++ b/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2aws/README.md @@ -5,26 +5,23 @@ This example shows how create connection from Fabric Cloud Router to AWS, on ECX ## Adjust variables At minimum, you must set below variables in `terraform.tfvars` file: -* `equinix_client_id` - Equinix client ID (consumer key), obtained after - registering app in the developer platform -* `equinix_client_secret` - Equinix client secret ID (consumer secret), - obtained same way as above - -`fcr_uuid` - UUID of ECX Fabric Cloud Router on a-side -`zside_port_name` - Name of ECX Fabric z-side port , i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-000 -`connection_name` - the name of the connection -`connection_type` - connection type, please refer schema -`notifications_type` - notification type -`notifications_emails` - List of emails -`bandwidth` - bandwidth in MBs -`redundancy` - Port redundancy -`aside_ap_type` - Fabric Cloud Router type -`zside_ap_type` - Z side access point type -`zside_ap_authentication_key` - AWS authorization key, account number like 357848912121 -`zside_ap_profile_type` - Service profile type -`fabric_sp_name` - Service profile name, fetched based on Service Profile get call using Service Profile search schema -`zside_location` - Seller location -`seller_region` - Seller region code +- `equinix_client_id` - Equinix client ID (consumer key), obtained after registering app in the developer platform +- `equinix_client_secret` - Equinix client secret ID (consumer secret), obtained same way as above +- `fcr_uuid` - UUID of ECX Fabric Cloud Router on a-side +- `zside_port_name` - Name of ECX Fabric z-side port , i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-000 +- `connection_name` - the name of the connection +- `connection_type` - connection type, please refer schema +- `notifications_type` - notification type +- `notifications_emails` - List of emails +- `bandwidth` - bandwidth in MBs +- `redundancy` - Port redundancy +- `aside_ap_type` - Fabric Cloud Router type +- `zside_ap_type` - Z side access point type +- `zside_ap_authentication_key` - AWS authorization key, account number like 357848912121 +- `zside_ap_profile_type` - Service profile type +- `fabric_sp_name` - Service profile name, fetched based on Service Profile get call using Service Profile search schema +- `zside_location` - Seller location +- `seller_region` - Seller region code ## AWS login @@ -32,17 +29,17 @@ Log in to AWS portal use account that has permission to create necessary resourc ## Initialize - First step is to initialize the terraform directory/resource we are going to work on. - In the given example, the folder to perform CRUD operations on a fcr2port connection can be found at examples/fcr2port/. + In the given example, the folder to perform CRUD operations on a fcr2aws connection can be found at examples/fabric/v4/cloudRouterConnectivity/cloudRouter2aws/. -- Change directory into - `CD fcr2aws/` +- Change directory into - `examples/fabric/v4/cloudRouterConnectivity/cloudRouter2aws/` - Initialize Terraform plugins - `terraform init` -## Fabric Cloud Router to port connection : Create, Read, Update and Delete(CRUD) operations +## Fabric Cloud Router to AWS connection : Create, Read, Update and Delete(CRUD) operations Note: `–auto-approve` command does not prompt the user for validating the applying config. Remove it to get a prompt to confirm the operation. -| Operation | Command | Description | -|:----------|:---------------------------------:|-----------------------------------------------------------------------:| -| CREATE | `terraform apply –auto-approve` | Creates a fcr2port connection resource | -| READ | `terraform show` | Reads/Shows the current state of the fcr2port connection resource | -| UPDATE | `terraform apply -refresh` | Updates the fcr2port with values provided in the terraform.tfvars file | -| DELETE | `terraform destroy –auto-approve` | Deletes the created fcr2port connection resource | \ No newline at end of file +| Operation | Command | Description | +|:----------|:---------------------------------:|----------------------------------------------------------------------:| +| CREATE | `terraform apply –auto-approve` | Creates a fcr2aws connection resource | +| READ | `terraform show` | Reads/Shows the current state of the fcr2aws connection resource | +| UPDATE | `terraform apply -refresh` | Updates the fcr2aws with values provided in the terraform.tfvars file | +| DELETE | `terraform destroy –auto-approve` | Deletes the created fcr2aws connection resource | \ No newline at end of file diff --git a/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2azure/single-connection/README.md b/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2azure/single-connection/README.md index de7cc7d10..953d02866 100644 --- a/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2azure/single-connection/README.md +++ b/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2azure/single-connection/README.md @@ -5,25 +5,22 @@ This example shows how create single connection from Fabric Cloud Router to Azur ## Adjust variables At minimum, you must set below variables in `terraform.tfvars` file: -* `equinix_client_id` - Equinix client ID (consumer key), obtained after - registering app in the developer platform -* `equinix_client_secret` - Equinix client secret ID (consumer secret), - obtained same way as above - -`fcr_uuid` - UUID of ECX Fabric Cloud Router on a-side -`connection_name` - the name of the connection -`connection_type` - connection type, please refer schema -`notifications_type` - notification type -`notifications_emails` - List of emails -`bandwidth` - bandwidth in MBs -`redundancy` - Port redundancy -`aside_ap_type` - Fabric Cloud Router type -`zside_ap_type` - Z side access point type -`zside_ap_authentication_key` - Azure authorization key, service key generated from Azure Portal -`zside_ap_profile_type` - Service profile type -`fabric_sp_name` - Service profile name, fetched based on Service Profile get call using Service Profile search schema -`zside_location` - Seller location -`seller_region` - Seller region code +- `equinix_client_id` - Equinix client ID (consumer key), obtained after registering app in the developer platform +- `equinix_client_secret` - Equinix client secret ID (consumer secret), obtained same way as above +- `fcr_uuid` - UUID of ECX Fabric Cloud Router on a-sideshow +- `connection_name` - the name of the connection +- `connection_type` - connection type, please refer schema +- `notifications_type` - notification type +- `notifications_emails` - List of emails +- `bandwidth` - bandwidth in MBs +- `redundancy` - Port redundancy +- `aside_ap_type` - Fabric Cloud Router type +- `zside_ap_type` - Z side access point type +- `zside_ap_authentication_key` - Azure authorization key, service key generated from Azure Portal +- `zside_ap_profile_type` - Service profile type +- `fabric_sp_name` - Service profile name, fetched based on Service Profile get call using Service Profile search schema +- `zside_location` - Seller location +- `seller_region` - Seller region code ## Azure login @@ -31,12 +28,12 @@ Log in to Azure portal use account that has permission to create necessary resou ## Initialize - First step is to initialize the terraform directory/resource we are going to work on. - In the given example, the folder to perform CRUD operations on a fcr2port connection can be found at examples/fcr2port/. + In the given example, the folder to perform CRUD operations on a fcr2azure connection can be found at examples/fabric/v4/cloudRouterConnectivity/cloudRouter2azure/single-connection/. -- Change directory into - `CD cloudRouter2azure/single-connection` +- Change directory into - `CD examples/fabric/v4/cloudRouterConnectivity/cloudRouter2azure/single-connection/` - Initialize Terraform plugins - `terraform init` -## Fabric Cloud Router to port connection : Create, Read, Update and Delete(CRUD) operations +## Fabric Cloud Router to Azure single connection : Create, Read, Update and Delete(CRUD) operations Note: `–auto-approve` command does not prompt the user for validating the applying config. Remove it to get a prompt to confirm the operation. | Operation | Command | Description | diff --git a/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2azure/two-connections/README.md b/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2azure/two-connections/README.md index 423b27d38..bed6254a7 100644 --- a/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2azure/two-connections/README.md +++ b/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2azure/two-connections/README.md @@ -5,28 +5,25 @@ This example shows how create two redundant connections from Fabric Cloud Router ## Adjust variables At minimum, you must set below variables in `terraform.tfvars` file: -* `equinix_client_id` - Equinix client ID (consumer key), obtained after - registering app in the developer platform -* `equinix_client_secret` - Equinix client secret ID (consumer secret), - obtained same way as above - -`pri_connection_name` - the name of the primary connection -`sec_connection_name` - the name of the secondary connection -`connection_type` - connection type, please refer schema -`notifications_type` - notification type -`notifications_emails` - List of emails -`bandwidth` - bandwidth in MBs -`aside_ap_type` - Fabric Cloud Router type -`peering_type` - Peering type for the ECX Fabric Cloud Router on the a-side; typically PRIVATE +- `equinix_client_id` - Equinix client ID (consumer key), obtained after registering app in the developer platform +- `equinix_client_secret` - Equinix client secret ID (consumer secret), obtained same way as above +- `pri_connection_name` - the name of the primary connection +- `sec_connection_name` - the name of the secondary connection +- `connection_type` - connection type, please refer schema +- `notifications_type` - notification type +- `notifications_emails` - List of emails +- `bandwidth` - bandwidth in MBs +- `aside_ap_type` - Fabric Cloud Router type +- `peering_type` - Peering type for the ECX Fabric Cloud Router on the a-side; typically PRIVATE **Note: You can use one Cloud Router for both connections if you would like** -`cloud_router_primary_uuid` - UUID of ECX Fabric Cloud Router on a-side -`cloud_router_secondary_uuid` - UUID of ECX Fabric Cloud Router on a-side for secondary connection -`zside_ap_type` - Z side access point type -`zside_ap_authentication_key` - Azure authorization key, service key generated from Azure Portal -`zside_ap_profile_type` - Service profile type -`zside_ap_profile_uuid` - Service profile UUID -`zside_location` - Seller location -`fabric_sp_name` - Service profile name, fetched based on Service Profile get call using Service Profile search schema +- `cloud_router_primary_uuid` - UUID of ECX Fabric Cloud Router on a-side +- `cloud_router_secondary_uuid` - UUID of ECX Fabric Cloud Router on a-side for secondary connection +- `zside_ap_type` - Z side access point type +- `zside_ap_authentication_key` - Azure authorization key, service key generated from Azure Portal +- `zside_ap_profile_type` - Service profile type +- `zside_ap_profile_uuid` - Service profile UUID +- `zside_location` - Seller location +- `fabric_sp_name` - Service profile name, fetched based on Service Profile get call using Service Profile search schema ## Azure login @@ -34,12 +31,12 @@ Log in to Azure portal use account that has permission to create necessary resou ## Initialize - First step is to initialize the terraform directory/resource we are going to work on. - In the given example, the folder to perform CRUD operations on a fcr2port connection can be found at examples/fcr2port/. + In the given example, the folder to perform CRUD operations on a fcr2azure connection can be found at examples/fabric/v4/cloudRouterConnectivity/cloudRouter2azure/two-connections/. -- Change directory into - `CD cloudRouter2azure/two-connections` +- Change directory into - `CD examples/fabric/v4/cloudRouterConnectivity/cloudRouter2azure/two-connections/` - Initialize Terraform plugins - `terraform init` -## Fabric Cloud Router to port connection : Create, Read, Update and Delete(CRUD) operations +## Fabric Cloud Router to Azure Two connections : Create, Read, Update and Delete(CRUD) operations Note: `–auto-approve` command does not prompt the user for validating the applying config. Remove it to get a prompt to confirm the operation. | Operation | Command | Description | diff --git a/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2gcp/README.md b/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2gcp/README.md index adff88859..cbe182fdd 100644 --- a/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2gcp/README.md +++ b/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2gcp/README.md @@ -5,39 +5,36 @@ This example shows how create connection from Fabric Cloud Router to google, on ## Adjust variables At minimum, you must set below variables in `terraform.tfvars` file: -* `equinix_client_id` - Equinix client ID (consumer key), obtained after - registering app in the developer platform -* `equinix_client_secret` - Equinix client secret ID (consumer secret), - obtained same way as above - -`fcr_uuid` - UUID of ECX Fabric Cloud Router on a-side -`zside_port_name` - Name of ECX Fabric z-side port , i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-000 -`connection_name` - the name of the connection -`connection_type` - connection type, please refer schema -`notifications_type` - notification type -`notifications_emails` - List of emails -`bandwidth` - bandwidth in MBs -`redundancy` - Port redundancy -`aside_ap_type` - Fabric Cloud Router type -`zside_ap_type` - Z side access point type -`zside_ap_authentication_key` - Google authorization key following a pattern, like **9da09fe8-a33b-4457-ab7d-d91f83152276/us-west1/1** -`zside_ap_profile_type` - Service profile type -`zside_location` - Seller location -`seller_region` - Seller region code +- `equinix_client_id` - Equinix client ID (consumer key), obtained after registering app in the developer platform +- `equinix_client_secret` - Equinix client secret ID (consumer secret), obtained same way as above +- `fcr_uuid` - UUID of ECX Fabric Cloud Router on a-side +- `zside_port_name` - Name of ECX Fabric z-side port , i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-000 +- `connection_name` - the name of the connection +- `connection_type` - connection type, please refer schema +- `notifications_type` - notification type +- `notifications_emails` - List of emails +- `bandwidth` - bandwidth in MBs +- `redundancy` - Port redundancy +- `aside_ap_type` - Fabric Cloud Router type +- `zside_ap_type` - Z side access point type +- `zside_ap_authentication_key` - Google authorization key following a pattern, like **9da09fe8-a33b-4457-ab7d-d91f83152276/us-west1/1** +- `zside_ap_profile_type` - Service profile type +- `zside_location` - Seller location +- `seller_region` - Seller region code ## Initialize - First step is to initialize the terraform directory/resource we are going to work on. - In the given example, the folder to perform CRUD operations on a fcr2port connection can be found at examples/fcr2port/. + In the given example, the folder to perform CRUD operations on a fcr2gcp connection can be found at examples/fabric/v4/cloudRouterConnectivity/cloudRouter2gcp/. -- Change directory into - `CD fcr2gcp/` +- Change directory into - `CD examples/fabric/v4/cloudRouterConnectivity/cloudRouter2gcp/` - Initialize Terraform plugins - `terraform init` -## Fabric Cloud Router to port connection : Create, Read, Update and Delete(CRUD) operations +## Fabric Cloud Router to GCP connection : Create, Read, Update and Delete(CRUD) operations Note: `–auto-approve` command does not prompt the user for validating the applying config. Remove it to get a prompt to confirm the operation. -| Operation | Command | Description | -|:----------|:---------------------------------:|-----------------------------------------------------------------------:| -| CREATE | `terraform apply –auto-approve` | Creates a fcr2port connection resource | -| READ | `terraform show` | Reads/Shows the current state of the fcr2port connection resource | -| UPDATE | `terraform apply -refresh` | Updates the fcr2port with values provided in the terraform.tfvars file | -| DELETE | `terraform destroy –auto-approve` | Deletes the created fcr2port connection resource | \ No newline at end of file +| Operation | Command | Description | +|:----------|:---------------------------------:|----------------------------------------------------------------------:| +| CREATE | `terraform apply –auto-approve` | Creates a fcr2gcp connection resource | +| READ | `terraform show` | Reads/Shows the current state of the fcr2gcp connection resource | +| UPDATE | `terraform apply -refresh` | Updates the fcr2gcp with values provided in the terraform.tfvars file | +| DELETE | `terraform destroy –auto-approve` | Deletes the created fcr2gcp connection resource | \ No newline at end of file diff --git a/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2oracle/README.md b/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2oracle/README.md index aea16cdf9..694260c02 100644 --- a/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2oracle/README.md +++ b/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2oracle/README.md @@ -5,25 +5,22 @@ This example shows how create single connection from Fabric Cloud Router to Orac ## Adjust variables At minimum, you must set below variables in `terraform.tfvars` file: -* `equinix_client_id` - Equinix client ID (consumer key), obtained after - registering app in the developer platform -* `equinix_client_secret` - Equinix client secret ID (consumer secret), - obtained same way as above - -`fcr_uuid` - UUID of ECX Fabric Cloud Router on a-sideshow -`connection_name` - the name of the connection -`connection_type` - connection type, please refer schema -`notifications_type` - notification type -`notifications_emails` - List of emails -`bandwidth` - bandwidth in MBs -`redundancy` - Port redundancy -`aside_ap_type` - Fabric Cloud Router type -`zside_ap_type` - Z side access point type -`zside_ap_authentication_key` - Oracle authorization key following a pattern, like **ocid1.virtualcircuit.oc1.phx.aaaaaaaa62hgxtczqwpaour5gnaq4qn2wupjwpqtsknr2mvxblrcdtusda1a** -`zside_ap_profile_type` - Service profile type -`fabric_sp_name` - Service profile name, fetched based on Service Profile get call using Service Profile search schema -`zside_location` - Seller location -`seller_region` - Seller region code +- `equinix_client_id` - Equinix client ID (consumer key), obtained after registering app in the developer platform +- `equinix_client_secret` - Equinix client secret ID (consumer secret), obtained same way as above +- `fcr_uuid` - UUID of ECX Fabric Cloud Router on a-sideshow +- `connection_name` - the name of the connection +- `connection_type` - connection type, please refer schema +- `notifications_type` - notification type +- `notifications_emails` - List of emails +- `bandwidth` - bandwidth in MBs +- `redundancy` - Port redundancy +- `aside_ap_type` - Fabric Cloud Router type +- `zside_ap_type` - Z side access point type +- `zside_ap_authentication_key` - Oracle authorization key following a pattern, like **ocid1.virtualcircuit.oc1.phx.aaaaaaaa62hgxtczqwpaour5gnaq4qn2wupjwpqtsknr2mvxblrcdtusda1a** +- `zside_ap_profile_type` - Service profile type +- `fabric_sp_name` - Service profile name, fetched based on Service Profile get call using Service Profile search schema +- `zside_location` - Seller location +- `seller_region` - Seller region code ## Oracle login @@ -31,12 +28,12 @@ Log in to Oracle Cloud portal use account that has permission to create necessar ## Initialize - First step is to initialize the terraform directory/resource we are going to work on. - In the given example, the folder to perform CRUD operations on a fcr2port connection can be found at examples/fcr2port/. + In the given example, the folder to perform CRUD operations on a fcr2oracle connection can be found at examples/fabric/v4/cloudRouterConnectivity/cloudRouter2oracle/. -- Change directory into - `CD cloudRouter2oracle` +- Change directory into - ` CD examples/fabric/v4/cloudRouterConnectivity/cloudRouter2oracle/` - Initialize Terraform plugins - `terraform init` -## Fabric Cloud Router to port connection : Create, Read, Update and Delete(CRUD) operations +## Fabric Cloud Router to Oracle connection : Create, Read, Update and Delete(CRUD) operations Note: `–auto-approve` command does not prompt the user for validating the applying config. Remove it to get a prompt to confirm the operation. | Operation | Command | Description | diff --git a/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2port/README.md b/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2port/README.md index 2a93d5643..61b699108 100644 --- a/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2port/README.md +++ b/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2port/README.md @@ -5,23 +5,20 @@ This example shows how create connection from Fabric Cloud Router to port, on EC ## Adjust variables At minimum, you must set below variables in `terraform.tfvars` file: -* `equinix_client_id` - Equinix client ID (consumer key), obtained after - registering app in the developer platform -* `equinix_client_secret` - Equinix client secret ID (consumer secret), - obtained same way as above - -`fcr_uuid` - UUID of ECX Fabric Cloud Router on a-side -`zside_port_name` - Name of ECX Fabric z-side port , i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-000 -`connection_name` - the name of the connection -`connection_type` - connection type, please refer schema -`notifications_type` - notification type -`notifications_emails` - List of emails -`bandwidth` - bandwidth in MBs -`redundancy` - Port redundancy -`aside_ap_type` - Fabric Cloud Router type -`zside_ap_type` - Z side access point type -`zside_link_protocol_tag` - z-side vlan tag number -`zside_location` - Seller location +- `equinix_client_id` - Equinix client ID (consumer key), obtained after registering app in the developer platform +- `equinix_client_secret` - Equinix client secret ID (consumer secret), obtained same way as above +- `fcr_uuid` - UUID of ECX Fabric Cloud Router on a-side +- `zside_port_name` - Name of ECX Fabric z-side port , i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-000 +- `connection_name` - the name of the connection +- `connection_type` - connection type, please refer schema +- `notifications_type` - notification type +- `notifications_emails` - List of emails +- `bandwidth` - bandwidth in MBs +- `redundancy` - Port redundancy +- `aside_ap_type` - Fabric Cloud Router type +- `zside_ap_type` - Z side access point type +- `zside_link_protocol_tag` - z-side vlan tag number +- `zside_location` - Seller location ## Initialize - First step is to initialize the terraform directory/resource we are going to work on. diff --git a/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2serviceprofile/README.md b/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2serviceprofile/README.md index 1567460a0..ad9b40aa1 100644 --- a/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2serviceprofile/README.md +++ b/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2serviceprofile/README.md @@ -5,23 +5,20 @@ This example shows how create single connection from Fabric Cloud Router to Sell ## Adjust variables At minimum, you must set below variables in `terraform.tfvars` file: -* `equinix_client_id` - Equinix client ID (consumer key), obtained after - registering app in the developer platform -* `equinix_client_secret` - Equinix client secret ID (consumer secret), - obtained same way as above - -`fcr_uuid` - UUID of ECX Fabric Cloud Router on a-sideshow -`connection_name` - the name of the connection -`connection_type` - connection type, please refer schema -`notifications_type` - notification type -`notifications_emails` - List of emails -`bandwidth` - bandwidth in MBs -`redundancy` - Port redundancy -`aside_ap_type` - Fabric Cloud Router type -`zside_ap_type` - Z side access point type -`zside_ap_profile_type` - Service profile type -`fabric_sp_name` - Service profile name, fetched based on Service Profile get call using Service Profile search schema -`zside_location` - Seller location +- `equinix_client_id` - Equinix client ID (consumer key), obtained after registering app in the developer platform +- `equinix_client_secret` - Equinix client secret ID (consumer secret), obtained same way as above +- `fcr_uuid` - UUID of ECX Fabric Cloud Router on a-sideshow +- `connection_name` - the name of the connection +- `connection_type` - connection type, please refer schema +- `notifications_type` - notification type +- `notifications_emails` - List of emails +- `bandwidth` - bandwidth in MBs +- `redundancy` - Port redundancy +- `aside_ap_type` - Fabric Cloud Router type +- `zside_ap_type` - Z side access point type +- `zside_ap_profile_type` - Service profile type +- `fabric_sp_name` - Service profile name, fetched based on Service Profile get call using Service Profile search schema +- `zside_location` - Seller location ## Initialize - First step is to initialize the terraform directory/resource we are going to work on. diff --git a/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2serviceprofile/main.tf b/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2serviceprofile/main.tf index 003236e2e..d9b98c46f 100644 --- a/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2serviceprofile/main.tf +++ b/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2serviceprofile/main.tf @@ -7,7 +7,7 @@ data "equinix_fabric_service_profiles" "sp" { filter { property = "/name" operator = "=" - values = [var.fabric_sp_name] + values = [var.fabric_sp_name] } } @@ -15,17 +15,17 @@ resource "equinix_fabric_connection" "fcr2profile" { name = var.connection_name type = var.connection_type notifications{ - type=var.notifications_type - emails=var.notifications_emails + type = var.notifications_type + emails = var.notifications_emails } bandwidth = var.bandwidth - redundancy {priority= var.redundancy} + redundancy {priority = var.redundancy} order { - purchase_order_number= var.purchase_order_number + purchase_order_number = var.purchase_order_number } a_side { access_point { - type= var.aside_ap_type + type = var.aside_ap_type router { uuid = var.fcr_uuid } @@ -33,13 +33,13 @@ resource "equinix_fabric_connection" "fcr2profile" { } z_side { access_point { - type= var.zside_ap_type + type = var.zside_ap_type profile { - type= var.zside_ap_profile_type - uuid= data.equinix_fabric_service_profiles.sp.id + type = var.zside_ap_profile_type + uuid = data.equinix_fabric_service_profiles.sp.id } location { - metro_code= var.zside_location + metro_code = var.zside_location } } } diff --git a/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/README.md b/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/README.md index 56e653068..799890635 100644 --- a/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/README.md +++ b/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/README.md @@ -1,37 +1,35 @@ # ECX Fabric Cloud Router Connection BGP CRUD operations -This example shows how to create Config BGP on FCR connection . +This example shows how to Config BGP Routing Protocol details for an existing FCR connection. Note: Each time you need to create a BGP resource add-on -make a copy of the base folder - examples/routing-protocol-bgp/ and CD into this folder to perform all the CRUD operations. +make a copy of the base folder - examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/ and CD into this folder to perform all the CRUD operations. ## Define values for the Fabric Cloud Router create At minimum, you must set below variables in `terraform.tfvars` file: -- `equinix_client_id` - Equinix client ID (consumer key), obtained after - registering app in the developer platform -- `equinix_client_secret` - Equinix client secret ID (consumer secret), - obtained same way as above -- `rp_name`- Name of routing Protocol -- `rp_type`- Type of routing Protocol entity, "BGP" -- connection_uuid = "d557cb4c-9052-4298-b5ca-8a9ed914cf03" - rp_type = "DIRECT" - rp_name = "FCR-RP" - customer_peer_ipv4 = "192.1.1.2" - customer_peer_ipv6 = "192::1:2" - customer_asn = "100" +- `equinix_client_id` - Equinix client ID (consumer key), obtained after registering app in the developer platform +- `equinix_client_secret` - Equinix client secret ID (consumer secret), obtained same way as above +- `rp_name` - Name of routing Protocol +- `rp_type` - Type of routing Protocol entity, "BGP" +- `connection_uuid` - FCR Connection UUID +- `customer_peer_ipv4` - Customer Side IpV4 Address +- `customer_peer_ipv6` - Customer Side IpV6 Address +- `bgp_enabled_ipv4` - Enable BGP IpV4 session from customer side +- `bgp_enabled_ipv6` - Enable BGP IpV6 session from customer side +- `customer_asn` - Customer ASN Number ## Initialize - First step is to initialize the terraform directory/resource we are going to work on. - In the given example, the folder to perform CRUD operations on an RP resource can be found at examples/routing-protocol-bgp/. + In the given example, the folder to perform CRUD operations on an RP resource can be found at examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/. -- Change directory into - `CD examples/routing-protocol-bgp/` +- Change directory into - `CD examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/` - Initialize Terraform plugins - `terraform init` ## Routing-protocol BGP : Create, Read, Update and Delete(CRUD) operations Note: `–auto-approve` command does not prompt the user for validating the applying config. Remove it to get a prompt to confirm the operation. -| Operation | Command | Description | -|:----------|:---------------------------------:|--------------------------------------------------------------------------:| -| CREATE | `terraform apply –auto-approve` | Creates an FCR resource | -| READ | `terraform show` | Reads/Shows the current state of the FCR resource | -| UPDATE | `terraform apply -refresh` | Updates the FCR resource with values provided in the terraform.tfvars file | -| DELETE | `terraform destroy –auto-approve` | Deletes the created FCR resource | \ No newline at end of file +| Operation | Command | Description | +|:----------|:---------------------------------:|--------------------------------------------------------------------------------------------:| +| CREATE | `terraform apply –auto-approve` | Creates a BGP Routing Protocol resource | +| READ | `terraform show` | Reads/Shows the current state of the BGP Routing Protocol resource | +| UPDATE | `terraform apply -refresh` | Updates the BGP Routing Protocol resource with values provided in the terraform.tfvars file | +| DELETE | `terraform destroy –auto-approve` | Deletes the created BGP Routing Protocol resource | \ No newline at end of file diff --git a/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/main.tf b/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/main.tf index 7a220b7dc..64d90d053 100644 --- a/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/main.tf +++ b/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/main.tf @@ -3,15 +3,17 @@ provider "equinix" { client_secret = var.equinix_client_secret } -resource "equinix_fabric_routing_protocol" "test"{ +resource "equinix_fabric_routing_protocol" "test" { connection_uuid = var.connection_uuid - type = var.rp_type - name = var.rp_name + type = var.rp_type + name = var.rp_name bgp_ipv4 { - customer_peer_ip = var.customer_peer_ipv4 + customer_peer_ip = var.customer_peer_ipv4 + enabled = var.bgp_enabled_ipv4 } - bgp_ipv6{ - customer_peer_ip = var.customer_peer_ipv6 + bgp_ipv6 { + customer_peer_ip = var.customer_peer_ipv6 + enabled = var.bgp_enabled_ipv6 } customer_asn = var.customer_asn } diff --git a/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/terraform.tfvars.example b/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/terraform.tfvars.example index 4a6e8510c..62fcef274 100644 --- a/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/terraform.tfvars.example +++ b/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/terraform.tfvars.example @@ -1,9 +1,11 @@ -equinix_client_id = "MyEquinixClientId" -equinix_client_secret = "MyEquinixSecret" +equinix_client_id = "MyEquinixClientId" +equinix_client_secret = "MyEquinixSecret" -connection_uuid = "bfa41c64-3720-4cef-88dd-ec795ba36800" -rp_type = "BGP" -rp_name = "FCR-Con-BGP" +connection_uuid = "bfa41c64-3720-4cef-88dd-ec795ba36800" +rp_type = "BGP" +rp_name = "FCR-Con-BGP" customer_peer_ipv4 = "190.1.1.2" customer_peer_ipv6 = "190::1:2" -customer_asn = "100" +bgp_enabled_ipv4 = true +bgp_enabled_ipv6 = true +customer_asn = "100" diff --git a/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/variables.tf b/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/variables.tf index 44c4db4f6..1b2c978a9 100644 --- a/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/variables.tf +++ b/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-bgp/variables.tf @@ -6,4 +6,6 @@ variable "rp_type" {} variable "rp_name" {} variable "customer_peer_ipv4" {} variable "customer_peer_ipv6" {} +variable "bgp_enabled_ipv4" {} +variable "bgp_enabled_ipv6" {} variable "customer_asn" {} diff --git a/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-direct/README.md b/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-direct/README.md index a4ba1a62c..70a09e801 100644 --- a/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-direct/README.md +++ b/examples/fabric/v4/cloudRouterConnectivity/routing-protocol-direct/README.md @@ -1,37 +1,33 @@ # ECX Fabric Cloud Router Connection RP CRUD operations -This example shows how to create Config Direct RP on FCR connection . +This example shows how to Config Direct Routing Protocol details for an existing FCR connection . -Note: Each time you need to create a RP resource add-on -make a copy of the base folder - examples/routing-protocol-direct/ and CD into this folder to perform all the CRUD operations. +Note: Each time you need to create a Direct RP resource add-on +make a copy of the base folder - examples/fabric/v4/cloudRouterConnectivity/routing-protocol-direct/ and CD into this folder to perform all the CRUD operations. ## Define values for the Fabric Cloud Router create At minimum, you must set below variables in `terraform.tfvars` file: -- `equinix_client_id` - Equinix client ID (consumer key), obtained after - registering app in the developer platform -- `equinix_client_secret` - Equinix client secret ID (consumer secret), - obtained same way as above +- `equinix_client_id` - Equinix client ID (consumer key), obtained after registering app in the developer platform +- `equinix_client_secret` - Equinix client secret ID (consumer secret),obtained same way as above - `rp_name`- Name of routing Protocol - `rp_type`- Type of routing Protocol entity, "DIRECT" or "BGP" -- connection_uuid = "d557cb4c-9052-4298-b5ca-8a9ed914cf03" - rp_type = "DIRECT" - rp_name = "FCR-RP" - equinix_ipv4_ip = "192.1.1.1/30" - equinix_ipv6_ip = "192::1:1/126" +- `connection_uuid` = FCR Connection UUID +- `equinix_ipv4_ip` = Equinix Side IpV4 Address +- `equinix_ipv6_ip` = Equinix Side IpV6 Address ## Initialize - First step is to initialize the terraform directory/resource we are going to work on. - In the given example, the folder to perform CRUD operations on an RP resource can be found at examples/routing-protocol-direct/. + In the given example, the folder to perform CRUD operations on an RP resource can be found at examples/fabric/v4/cloudRouterConnectivity/routing-protocol-direct/. -- Change directory into - `CD examples/routing-protocol-direct/` +- Change directory into - `CD examples/fabric/v4/cloudRouterConnectivity/routing-protocol-direct/` - Initialize Terraform plugins - `terraform init` ## Routing-protocol Direct IP : Create, Read, Update and Delete(CRUD) operations Note: `–auto-approve` command does not prompt the user for validating the applying config. Remove it to get a prompt to confirm the operation. -| Operation | Command | Description | -|:----------|:---------------------------------:|--------------------------------------------------------------------------:| -| CREATE | `terraform apply –auto-approve` | Creates an FCR resource | -| READ | `terraform show` | Reads/Shows the current state of the FCR resource | -| UPDATE | `terraform apply -refresh` | Updates the FCR resource with values provided in the terraform.tfvars file | -| DELETE | `terraform destroy –auto-approve` | Deletes the created FCR resource | \ No newline at end of file +| Operation | Command | Description | +|:----------|:---------------------------------:|---------------------------------------------------------------------------------------------------------------------------------------:| +| CREATE | `terraform apply –auto-approve` | Creates a Direct Routing Protocol resource | +| READ | `terraform show` | Reads/Shows the current state of the Direct Routing Protocol resource | +| UPDATE | `terraform apply -refresh` | Updates the Direct Routing Protocol resource with values provided in the terraform.tfvars file | +| DELETE | `terraform destroy –auto-approve` | Deletes the created Direct Routing Protocol resource | \ No newline at end of file diff --git a/examples/fabric/v4/portConnectivity/alibaba/README.md b/examples/fabric/v4/portConnectivity/alibaba/README.md index e6ed195d9..b71381aa6 100644 --- a/examples/fabric/v4/portConnectivity/alibaba/README.md +++ b/examples/fabric/v4/portConnectivity/alibaba/README.md @@ -1,38 +1,33 @@ # ECX Fabric Layer2 Connection to Alibaba -This example shows how to create layer 2 connection between ECX Fabric port -and Alibaba Cloud Express. +This example shows how to create layer 2 connection between ECX Fabric port and Alibaba Cloud Express. Example covers **provisioning of both sides** of the connection. ## Adjust variables At minimum, you must set below variables in `terraform.tfvars` file: -* `equinix_client_id` - Equinix client ID (consumer key), obtained after -registering app in the developer platform -* `equinix_client_secret` - Equinix client secret ID (consumer secret), -obtained same way as above - -`fabric_sp_name` - Service profile name like i.e. Alibaba Cloud Express Connect -`equinix_port_name` - Name of ECX Fabric port that should be - connected to Alibaba, i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-199 -`connection_name` - the name of the connection -`connection_type` - connection type, please refer schema -`notifications_type` - notification type -`notifications_emails` - List of emails -`bandwidth` - bandwidth in MBs -`redundancy` - Port redundancy -`aside_ap_type` - Access point type -`aside_port_uuid` - Port uuid, fetched based on port call using Port resource -`aside_link_protocol_type` - link protocol type -`aside_link_protocol_stag` - s tag number -`aside_link_protocol_ctag` - c tag number -`zside_ap_type` - Z side access point type -`zside_ap_authentication_key` - Alibaba authorization key, account number like 5562571083982132 -`zside_ap_profile_type` - Service profile type -`zside_ap_profile_uuid` - Service profile uuid, fetched based on Service Profile get call using Service Profile search schema -`zside_location` - Seller location -`seller_region` - Seller region code +- `equinix_client_id` - Equinix client ID (consumer key), obtained after registering app in the developer platform +- `equinix_client_secret` - Equinix client secret ID (consumer secret), obtained same way as above +- `fabric_sp_name` - Service profile name like i.e. Alibaba Cloud Express Connect +- `equinix_port_name` - Name of ECX Fabric port that should be connected to Alibaba, i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-199 +- `connection_name` - the name of the connection +- `connection_type` - connection type, please refer schema +- `notifications_type` - notification type +- `notifications_emails` - List of emails +- `bandwidth` - bandwidth in MBs +- `redundancy` - Port redundancy +- `aside_ap_type` - Access point type +- `aside_port_uuid` - Port uuid, fetched based on port call using Port resource +- `aside_link_protocol_type` - link protocol type +- `aside_link_protocol_stag` - s tag number +- `aside_link_protocol_ctag` - c tag number +- `zside_ap_type` - Z side access point type +- `zside_ap_authentication_key` - Alibaba authorization key, account number like 5562571083982132 +- `zside_ap_profile_type` - Service profile type +- `zside_ap_profile_uuid` - Service profile uuid, fetched based on Service Profile get call using Service Profile search schema +- `zside_location` - Seller location +- `seller_region` - Seller region code ## Alibaba login @@ -40,11 +35,18 @@ Log in to Aliaba portal use account that has permission to create necessary resources. ## Initialize +- First step is to initialize the terraform directory/resource we are going to work on. + In the given example, the folder to perform CRUD operations for port2alibaba connection can be found at examples/fabric/v4/portConnectivity/alibaba/. -Change directory to project root to run terra test or change to example directory and initialize Terraform plugins -by running `terraform init`. +- Change directory into - `CD examples/fabric/v4/portConnectivity/alibaba/` +- Initialize Terraform plugins - `terraform init` -## Deploy template +## Port to Alibaba connection : Create, Read, Update and Delete(CRUD) operations +Note: `–auto-approve` command does not prompt the user for validating the applying config. Remove it to get a prompt to confirm the operation. -Apply changes by running `terraform apply`, then **inspect proposed plan** -and approve it. +| Operation | Command | Description | +|:----------|:---------------------------------:|---------------------------------------------------------------------------:| +| CREATE | `terraform apply –auto-approve` | Creates a port2alibaba connection resource | +| READ | `terraform show` | Reads/Shows the current state of the port2alibaba connection resource | +| UPDATE | `terraform apply -refresh` | Updates the port2alibaba with values provided in the terraform.tfvars file | +| DELETE | `terraform destroy –auto-approve` | Deletes the created port2alibaba connection resource | diff --git a/examples/fabric/v4/portConnectivity/aws/README.md b/examples/fabric/v4/portConnectivity/aws/README.md index d8670e374..520d59dd5 100644 --- a/examples/fabric/v4/portConnectivity/aws/README.md +++ b/examples/fabric/v4/portConnectivity/aws/README.md @@ -1,49 +1,51 @@ # ECX Fabric Layer2 Connection to AWS -This example shows how to create layer 2 connection between ECX Fabric port -and AWS Cloud. +This example shows how to create layer 2 connection between ECX Fabric port and AWS Cloud. Example covers **provisioning of both sides** of the connection. ## Adjust variables At minimum, you must set below variables in `terraform.tfvars` file: -* `equinix_client_id` - Equinix client ID (consumer key), obtained after - registering app in the developer platform -* `equinix_client_secret` - Equinix client secret ID (consumer secret), - obtained same way as above - -`fabric_sp_name` - Service profile name like i.e. AWS -`equinix_port_name` - Name of ECX Fabric port that should be -connected to AWS, i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-199 -`connection_name` - the name of the connection -`connection_type` - connection type, please refer schema -`notifications_type` - notification type -`notifications_emails` - List of emails -`bandwidth` - bandwidth in MBs -`redundancy` - Port redundancy -`aside_ap_type` - Access point type -`aside_port_uuid` - Port uuid, fetched based on port call using Port resource -`aside_link_protocol_type` - link protocol type -`aside_link_protocol_stag` - s tag number -`aside_link_protocol_ctag` - c tag number -`zside_ap_type` - Z side access point type -`zside_ap_authentication_key` - AWS authorization key, account number like 357848912121 -`zside_ap_profile_type` - Service profile type -`zside_ap_profile_uuid` - Service profile uuid, fetched based on Service Profile get call using Service Profile search schema -`zside_location` - Seller location -`seller_region` - Seller region code +- `equinix_client_id` - Equinix client ID (consumer key), obtained after registering app in the developer platform +- `equinix_client_secret` - Equinix client secret ID (consumer secret), obtained same way as above +- `fabric_sp_name` - Service profile name like i.e. AWS +- `equinix_port_name` - Name of ECX Fabric port that should be connected to AWS, i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-199 +- `connection_name` - the name of the connection +- `connection_type` - connection type, please refer schema +- `notifications_type` - notification type +- `notifications_emails` - List of emails +- `bandwidth` - bandwidth in MBs +- `redundancy` - Port redundancy +- `aside_ap_type` - Access point type +- `aside_port_uuid` - Port uuid, fetched based on port call using Port resource +- `aside_link_protocol_type` - link protocol type +- `aside_link_protocol_stag` - s tag number +- `aside_link_protocol_ctag` - c tag number +- `zside_ap_type` - Z side access point type +- `zside_ap_authentication_key` - AWS authorization key, account number like 357848912121 +- `zside_ap_profile_type` - Service profile type +- `zside_ap_profile_uuid` - Service profile uuid, fetched based on Service Profile get call using Service Profile search schema +- `zside_location` - Seller location +- `seller_region` - Seller region code ## AWS login Log in to AWS portal use account that has permission to create necessary resources. ## Initialize +- First step is to initialize the terraform directory/resource we are going to work on. + In the given example, the folder to perform CRUD operations for port2aws connection can be found at examples/fabric/v4/portConnectivity/aws/. -Change directory to project root to run terra test or change to example directory and initialize Terraform plugins -by running `terraform init`. +- Change directory into - `CD examples/fabric/v4/portConnectivity/aws/` +- Initialize Terraform plugins - `terraform init` -## Deploy template +## Port to AWS connection : Create, Read, Update and Delete(CRUD) operations +Note: `–auto-approve` command does not prompt the user for validating the applying config. Remove it to get a prompt to confirm the operation. -Apply changes by running `terraform apply`, then **inspect proposed plan** -and approve it. +| Operation | Command | Description | +|:----------|:---------------------------------:|-----------------------------------------------------------------------:| +| CREATE | `terraform apply –auto-approve` | Creates a port2aws connection resource | +| READ | `terraform show` | Reads/Shows the current state of the port2aws connection resource | +| UPDATE | `terraform apply -refresh` | Updates the port2aws with values provided in the terraform.tfvars file | +| DELETE | `terraform destroy –auto-approve` | Deletes the created port2aws connection resource | diff --git a/examples/fabric/v4/portConnectivity/azure/README.md b/examples/fabric/v4/portConnectivity/azure/README.md index 5727093ae..688a19d09 100644 --- a/examples/fabric/v4/portConnectivity/azure/README.md +++ b/examples/fabric/v4/portConnectivity/azure/README.md @@ -1,49 +1,51 @@ # ECX Fabric Layer2 Connection to Azure -This example shows how to create layer 2 connection between ECX Fabric port -and AZURE Cloud. +This example shows how to create layer 2 connection between ECX Fabric port and AZURE Cloud. Example covers **provisioning of both sides** of the connection. ## Adjust variables At minimum, you must set below variables in `terraform.tfvars` file: -* `equinix_client_id` - Equinix client ID (consumer key), obtained after - registering app in the developer platform -* `equinix_client_secret` - Equinix client secret ID (consumer secret), - obtained same way as above - -`fabric_sp_name` - Service profile name like i.e. AZURE -`equinix_port_name` - Name of ECX Fabric port that should be -connected to AZURE, i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-199 -`connection_name` - the name of the connection -`connection_type` - connection type, please refer schema -`notifications_type` - notification type -`notifications_emails` - List of emails -`bandwidth` - bandwidth in MBs -`redundancy` - Port redundancy -`aside_ap_type` - Access point type -`peering_type` - Peering type -`aside_port_uuid` - Port uuid, fetched based on port call using Port resource -`aside_link_protocol_type` - link protocol type -`aside_link_protocol_stag` - s tag number -`aside_link_protocol_ctag` - c tag number -`zside_ap_type` - Z side access point type -`zside_ap_authentication_key` - AZURE authorization key, like c620477c-3f30-41e8-a0b9-cfdb4a12121d -`zside_ap_profile_type` - Service profile type -`zside_ap_profile_uuid` - Service profile uuid, fetched based on Service Profile get call using Service Profile search schema -`zside_location` - Seller location +- `equinix_client_id` - Equinix client ID (consumer key), obtained after registering app in the developer platform +- `equinix_client_secret` - Equinix client secret ID (consumer secret), obtained same way as above +- `fabric_sp_name` - Service profile name like i.e. AZURE +- `equinix_port_name` - Name of ECX Fabric port that should be connected to AZURE, i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-199 +- `connection_name` - the name of the connection +- `connection_type` - connection type, please refer schema +- `notifications_type` - notification type +- `notifications_emails` - List of emails +- `bandwidth` - bandwidth in MBs +- `redundancy` - Port redundancy +- `aside_ap_type` - Access point type +- `peering_type` - Peering type +- `aside_port_uuid` - Port uuid, fetched based on port call using Port resource +- `aside_link_protocol_type` - link protocol type +- `aside_link_protocol_stag` - s tag number +- `aside_link_protocol_ctag` - c tag number +- `zside_ap_type` - Z side access point type +- `zside_ap_authentication_key` - AZURE authorization key, like c620477c-3f30-41e8-a0b9-cfdb4a12121d +- `zside_ap_profile_type` - Service profile type +- `zside_ap_profile_uuid` - Service profile uuid, fetched based on Service Profile get call using Service Profile search schema +- `zside_location` - Seller location ## Azure login Log in to Azure portal use account that has permission to create necessary resources. ## Initialize +- First step is to initialize the terraform directory/resource we are going to work on. + In the given example, the folder to perform CRUD operations for port2azure connection can be found at examples/fabric/v4/portConnectivity/azure/. -Change directory to project root to run terra test or change to example directory and initialize Terraform plugins -by running `terraform init`. +- Change directory into - `CD examples/fabric/v4/portConnectivity/azure/` +- Initialize Terraform plugins - `terraform init` -## Deploy template +## Port to Azure connection : Create, Read, Update and Delete(CRUD) operations +Note: `–auto-approve` command does not prompt the user for validating the applying config. Remove it to get a prompt to confirm the operation. -Apply changes by running `terraform apply`, then **inspect proposed plan** -and approve it. +| Operation | Command | Description | +|:----------|:---------------------------------:|-------------------------------------------------------------------------:| +| CREATE | `terraform apply –auto-approve` | Creates a port2azure connection resource | +| READ | `terraform show` | Reads/Shows the current state of the port2azure connection resource | +| UPDATE | `terraform apply -refresh` | Updates the port2azure with values provided in the terraform.tfvars file | +| DELETE | `terraform destroy –auto-approve` | Deletes the created port2azure connection resource | diff --git a/examples/fabric/v4/portConnectivity/google/README.md b/examples/fabric/v4/portConnectivity/google/README.md index bf939feae..a52d3a8b9 100644 --- a/examples/fabric/v4/portConnectivity/google/README.md +++ b/examples/fabric/v4/portConnectivity/google/README.md @@ -1,49 +1,51 @@ # ECX Fabric Layer2 Connection to Google -This example shows how to create layer 2 connection between ECX Fabric port -and Google Cloud. +This example shows how to create layer 2 connection between ECX Fabric port and Google Cloud. Example covers **provisioning of both sides** of the connection. ## Adjust variables At minimum, you must set below variables in `terraform.tfvars` file: -* `equinix_client_id` - Equinix client ID (consumer key), obtained after - registering app in the developer platform -* `equinix_client_secret` - Equinix client secret ID (consumer secret), - obtained same way as above - -`fabric_sp_name` - Service profile name like i.e. **Google Cloud Partner Interconnect Zone 1** -`equinix_port_name` - Name of ECX Fabric port that should be -connected to Google, i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-000 -`connection_name` - the name of the connection -`connection_type` - connection type, please refer schema -`notifications_type` - notification type -`notifications_emails` - List of emails -`bandwidth` - bandwidth in MBs -`redundancy` - Port redundancy -`aside_ap_type` - Access point type -`aside_port_uuid` - Port uuid, fetched based on port call using Port resource -`aside_link_protocol_type` - link protocol type -`aside_link_protocol_stag` - s tag number -`aside_link_protocol_ctag` - c tag number -`zside_ap_type` - Z side access point type -`zside_ap_authentication_key` - Google authorization key following a pattern, like **9da09fe8-a33b-4457-ab7d-d91f83152276/us-west1/1** -`zside_ap_profile_type` - Service profile type -`zside_ap_profile_uuid` - Service profile uuid, fetched based on Service Profile get call using Service Profile search schema -`zside_location` - Seller location -`seller_region` - Seller region code +- `equinix_client_id` - Equinix client ID (consumer key), obtained after registering app in the developer platform +- `equinix_client_secret` - Equinix client secret ID (consumer secret), obtained same way as above +- `fabric_sp_name` - Service profile name like i.e. **Google Cloud Partner Interconnect Zone 1** +- `equinix_port_name` - Name of ECX Fabric port that should be connected to Google, i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-000 +- `connection_name` - the name of the connection +- `connection_type` - connection type, please refer schema +- `notifications_type` - notification type +- `notifications_emails` - List of emails +- `bandwidth` - bandwidth in MBs +- `redundancy` - Port redundancy +- `aside_ap_type` - Access point type +- `aside_port_uuid` - Port uuid, fetched based on port call using Port resource +- `aside_link_protocol_type` - link protocol type +- `aside_link_protocol_stag` - s tag number +- `aside_link_protocol_ctag` - c tag number +- `zside_ap_type` - Z side access point type +- `zside_ap_authentication_key` - Google authorization key following a pattern, like **9da09fe8-a33b-4457-ab7d-d91f83152276/us-west1/1** +- `zside_ap_profile_type` - Service profile type +- `zside_ap_profile_uuid` - Service profile uuid, fetched based on Service Profile get call using Service Profile search schema +- `zside_location` - Seller location +- `seller_region` - Seller region code ## Google login Log in to Google portal use account that has permission to create necessary resources. ## Initialize +- First step is to initialize the terraform directory/resource we are going to work on. + In the given example, the folder to perform CRUD operations for port2google connection can be found at examples/fabric/v4/portConnectivity/google/. -Change directory to project root to run terra test or change to example directory and initialize Terraform plugins -by running `terraform init`. +- Change directory into - `CD examples/fabric/v4/portConnectivity/google/` +- Initialize Terraform plugins - `terraform init` -## Deploy template +## Port to Google connection : Create, Read, Update and Delete(CRUD) operations +Note: `–auto-approve` command does not prompt the user for validating the applying config. Remove it to get a prompt to confirm the operation. -Apply changes by running `terraform apply`, then **inspect proposed plan** -and approve it. +| Operation | Command | Description | +|:----------|:---------------------------------:|--------------------------------------------------------------------------:| +| CREATE | `terraform apply –auto-approve` | Creates a port2google connection resource | +| READ | `terraform show` | Reads/Shows the current state of the port2google connection resource | +| UPDATE | `terraform apply -refresh` | Updates the port2google with values provided in the terraform.tfvars file | +| DELETE | `terraform destroy –auto-approve` | Deletes the created port2google connection resource | diff --git a/examples/fabric/v4/portConnectivity/oracle/README.md b/examples/fabric/v4/portConnectivity/oracle/README.md index e7ee2d942..db7f2e880 100644 --- a/examples/fabric/v4/portConnectivity/oracle/README.md +++ b/examples/fabric/v4/portConnectivity/oracle/README.md @@ -8,41 +8,44 @@ Example covers **provisioning of both sides** of the connection. At minimum, you must set below variables in `terraform.tfvars` file: -* `equinix_client_id` - Equinix client ID (consumer key), obtained after - registering app in the developer platform -* `equinix_client_secret` - Equinix client secret ID (consumer secret), - obtained same way as above - -`fabric_sp_name` - Service profile name like i.e. **Oracle Cloud Infrastructure -OCI- FastConnect** -`equinix_port_name` - Name of ECX Fabric port that should be -connected to Oracle, i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-000 -`connection_name` - the name of the connection -`connection_type` - connection type, please refer schema -`notifications_type` - notification type -`notifications_emails` - List of emails -`bandwidth` - bandwidth in MBs -`redundancy` - Port redundancy -`aside_ap_type` - Access point type -`aside_port_uuid` - Port uuid, fetched based on port call using Port resource -`aside_link_protocol_type` - link protocol type -`aside_link_protocol_tag` - tag number -`zside_ap_type` - Z side access point type -`zside_ap_authentication_key` - Oracle authorization key following a pattern, like **ocid1.virtualcircuit.oc1.phx.aaaaaaaa62hgxtczqwpaour5gnaq4qn2wupjwpqtsknr2mvxblrcdtusda1a** -`zside_ap_profile_type` - Service profile type -`zside_ap_profile_uuid` - Service profile uuid, fetched based on Service Profile get call using Service Profile search schema -`zside_location` - Seller location -`seller_region` - Seller region code +- `equinix_client_id` - Equinix client ID (consumer key), obtained after registering app in the developer platform +- `equinix_client_secret` - Equinix client secret ID (consumer secret), obtained same way as above +- `fabric_sp_name` - Service profile name like i.e. **Oracle Cloud Infrastructure -OCI- FastConnect** +- `equinix_port_name` - Name of ECX Fabric port that should be connected to Oracle, i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-000 +- `connection_name` - the name of the connection +- `connection_type` - connection type, please refer schema +- `notifications_type` - notification type +- `notifications_emails` - List of emails +- `bandwidth` - bandwidth in MBs +- `redundancy` - Port redundancy +- `aside_ap_type` - Access point type +- `aside_port_uuid` - Port uuid, fetched based on port call using Port resource +- `aside_link_protocol_type` - link protocol type +- `aside_link_protocol_tag` - tag number +- `zside_ap_type` - Z side access point type +- `zside_ap_authentication_key` - Oracle authorization key following a pattern, like **ocid1.virtualcircuit.oc1.phx.aaaaaaaa62hgxtczqwpaour5gnaq4qn2wupjwpqtsknr2mvxblrcdtusda1a** +- `zside_ap_profile_type` - Service profile type +- `zside_ap_profile_uuid` - Service profile uuid, fetched based on Service Profile get call using Service Profile search schema +- `zside_location` - Seller location +- `seller_region` - Seller region code ## Oracle login Log in to Oracle portal use account that has permission to create necessary resources. ## Initialize +- First step is to initialize the terraform directory/resource we are going to work on. + In the given example, the folder to perform CRUD operations for port2oracle connection can be found at examples/fabric/v4/portConnectivity/oracle/. -Change directory to project root to run terra test or change to example directory and initialize Terraform plugins -by running `terraform init`. +- Change directory into - `CD examples/fabric/v4/portConnectivity/oracle/` +- Initialize Terraform plugins - `terraform init` -## Deploy template +## Port to Oracle connection : Create, Read, Update and Delete(CRUD) operations +Note: `–auto-approve` command does not prompt the user for validating the applying config. Remove it to get a prompt to confirm the operation. -Apply changes by running `terraform apply`, then **inspect proposed plan** -and approve it. +| Operation | Command | Description | +|:----------|:---------------------------------:|--------------------------------------------------------------------------:| +| CREATE | `terraform apply –auto-approve` | Creates a port2oracle connection resource | +| READ | `terraform show` | Reads/Shows the current state of the port2oracle connection resource | +| UPDATE | `terraform apply -refresh` | Updates the port2oracle with values provided in the terraform.tfvars file | +| DELETE | `terraform destroy –auto-approve` | Deletes the created port2oracle connection resource | \ No newline at end of file diff --git a/examples/fabric/v4/portConnectivity/port2portself/README.md b/examples/fabric/v4/portConnectivity/port2portself/README.md index 594fbb083..bb632f35b 100644 --- a/examples/fabric/v4/portConnectivity/port2portself/README.md +++ b/examples/fabric/v4/portConnectivity/port2portself/README.md @@ -5,34 +5,37 @@ This example shows how create layer 2 connection between two, own ECX Fabric por ## Adjust variables At minimum, you must set below variables in `terraform.tfvars` file: -* `equinix_client_id` - Equinix client ID (consumer key), obtained after - registering app in the developer platform -* `equinix_client_secret` - Equinix client secret ID (consumer secret), - obtained same way as above - -`aside_port_name` - Name of ECX Fabric a-side port i.e. ops-user100-CX-SV5-NL-Qinq-STD-1G-SEC-JP-111 -`zside_port_name` - Name of ECX Fabric z-side port , i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-000 - -`connection_name` - the name of the connection -`connection_type` - connection type, please refer schema -`notifications_type` - notification type -`notifications_emails` - List of emails -`bandwidth` - bandwidth in MBs -`redundancy` - Port redundancy -`aside_ap_type` - Access point type -`aside_port_uuid` - Port uuid, fetched based on port call using Port resource -`aside_link_protocol_type` - link protocol type -`aside_link_protocol_stag` - a-side s tag number -`zside_ap_type` - Z side access point type -`aside_link_protocol_stag` - z-side s tag number -`zside_location` - Seller location +- `equinix_client_id` - Equinix client ID (consumer key), obtained after registering app in the developer platform +- `equinix_client_secret` - Equinix client secret ID (consumer secret), obtained same way as above +- `aside_port_name` - Name of ECX Fabric a-side port i.e. ops-user100-CX-SV5-NL-Qinq-STD-1G-SEC-JP-111 +- `zside_port_name` - Name of ECX Fabric z-side port , i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-000 +- `connection_name` - the name of the connection +- `connection_type` - connection type, please refer schema +- `notifications_type` - notification type +- `notifications_emails` - List of emails +- `bandwidth` - bandwidth in MBs +- `redundancy` - Port redundancy +- `aside_ap_type` - Access point type +- `aside_port_uuid` - Port uuid, fetched based on port call using Port resource +- `aside_link_protocol_type` - link protocol type +- `aside_link_protocol_stag` - a-side s tag number +- `zside_ap_type` - Z side access point type +- `aside_link_protocol_stag` - z-side s tag number +- `zside_location` - Seller location ## Initialize +- First step is to initialize the terraform directory/resource we are going to work on. + In the given example, the folder to perform CRUD operations for port2portself connection can be found at examples/fabric/v4/portConnectivity/port2portself/. -Change directory to project root to run terra test or change to example directory and initialize Terraform plugins -by running `terraform init`. +- Change directory into - `CD examples/fabric/v4/portConnectivity/port2portself/` +- Initialize Terraform plugins - `terraform init` -## Deploy template +## Port to Port2Portself connection : Create, Read, Update and Delete(CRUD) operations +Note: `–auto-approve` command does not prompt the user for validating the applying config. Remove it to get a prompt to confirm the operation. -Apply changes by running `terraform apply`, then **inspect proposed plan** -and approve it. +| Operation | Command | Description | +|:----------|:---------------------------------:|----------------------------------------------------------------------------:| +| CREATE | `terraform apply –auto-approve` | Creates a port2portself connection resource | +| READ | `terraform show` | Reads/Shows the current state of the port2portself connection resource | +| UPDATE | `terraform apply -refresh` | Updates the port2portself with values provided in the terraform.tfvars file | +| DELETE | `terraform destroy –auto-approve` | Deletes the created port2portself connection resource | \ No newline at end of file diff --git a/examples/fabric/v4/portConnectivity/port2serviceprofileprivate/README.md b/examples/fabric/v4/portConnectivity/port2serviceprofileprivate/README.md index 807bac451..31620f489 100644 --- a/examples/fabric/v4/portConnectivity/port2serviceprofileprivate/README.md +++ b/examples/fabric/v4/portConnectivity/port2serviceprofileprivate/README.md @@ -1,37 +1,40 @@ # ECX Fabric Layer2 private seller profile -This example shows how to create layer2 public seller profile. +This example shows how to create layer2 between ECX Fabric Port and Private Seller Profile. ## Adjust variables -* `equinix_client_id` - Equinix client ID (consumer key), obtained after - registering app in the developer platform -* `equinix_client_secret` - Equinix client secret ID (consumer secret), - obtained same way as above - -`fabric_sp_name` - Service profile name like i.e. **Equinix Direct Connect - Private** -`aside_port_name` - Name of ECX Fabric port that should be connected used for the connection, i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-000 - -`connection_name` - the name of the connection -`connection_type` - connection type, please refer schema -`notifications_type` - notification type -`notifications_emails` - List of emails -`bandwidth` - bandwidth in MBs -`redundancy` - Port redundancy -`aside_ap_type` - Access point type -`aside_port_uuid` - Port uuid, fetched based on port call using Port resource -`aside_link_protocol_type` - link protocol type -`aside_link_protocol_tag` - tag number -`zside_ap_type` - Z side access point type -`zside_ap_profile_type` - Service profile type -`zside_ap_profile_uuid` - Service profile uuid, fetched based on Service Profile get call using Service Profile search schema -`zside_location` - Seller location +- `equinix_client_id` - Equinix client ID (consumer key), obtained after registering app in the developer platform +- `equinix_client_secret` - Equinix client secret ID (consumer secret), obtained same way as above +- `fabric_sp_name` - Service profile name like i.e. **Equinix Direct Connect - Private** +- `aside_port_name` - Name of ECX Fabric port that should be connected used for the connection, i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-000 +- `connection_name` - the name of the connection +- `connection_type` - connection type, please refer schema +- `notifications_type` - notification type +- `notifications_emails` - List of emails +- `bandwidth` - bandwidth in MBs +- `redundancy` - Port redundancy +- `aside_ap_type` - Access point type +- `aside_port_uuid` - Port uuid, fetched based on port call using Port resource +- `aside_link_protocol_type` - link protocol type +- `aside_link_protocol_tag` - tag number +- `zside_ap_type` - Z side access point type +- `zside_ap_profile_type` - Service profile type +- `zside_ap_profile_uuid` - Service profile uuid, fetched based on Service Profile get call using Service Profile search schema +- `zside_location` - Seller location ## Initialize +- First step is to initialize the terraform directory/resource we are going to work on. + In the given example, the folder to perform CRUD operations for port2serviceprofileprivate connection can be found at examples/fabric/v4/portConnectivity/port2serviceprofileprivate/. -Change directory to example directory and initialize Terraform plugins -by running `terraform init`. +- Change directory into - `CD examples/fabric/v4/portConnectivity/port2serviceprofileprivate/` +- Initialize Terraform plugins - `terraform init` -## Deploy template +## Port to Service Profile Private connection : Create, Read, Update and Delete(CRUD) operations +Note: `–auto-approve` command does not prompt the user for validating the applying config. Remove it to get a prompt to confirm the operation. -Apply changes by running `terraform apply`, then **inspect proposed plan** -and approve it. +| Operation | Command | Description | +|:----------|:---------------------------------:|-----------------------------------------------------------------------------------------:| +| CREATE | `terraform apply –auto-approve` | Creates a port2serviceprofileprivate connection resource | +| READ | `terraform show` | Reads/Shows the current state of the port2serviceprofileprivate connection resource | +| UPDATE | `terraform apply -refresh` | Updates the port2serviceprofileprivate with values provided in the terraform.tfvars file | +| DELETE | `terraform destroy –auto-approve` | Deletes the created port2serviceprofileprivate connection resource | \ No newline at end of file diff --git a/examples/fabric/v4/portConnectivity/port2serviceprofilepublic/README.md b/examples/fabric/v4/portConnectivity/port2serviceprofilepublic/README.md index 713e14c1a..94186fe13 100644 --- a/examples/fabric/v4/portConnectivity/port2serviceprofilepublic/README.md +++ b/examples/fabric/v4/portConnectivity/port2serviceprofilepublic/README.md @@ -1,37 +1,40 @@ # ECX Fabric Layer2 public seller profile -This example shows how to create layer2 public seller profile. +This example shows how to create layer2 between ECX Fabric Port and Public Seller Profile. ## Adjust variables -* `equinix_client_id` - Equinix client ID (consumer key), obtained after - registering app in the developer platform -* `equinix_client_secret` - Equinix client secret ID (consumer secret), - obtained same way as above - -`fabric_sp_name` - Service profile name like i.e. **Cross Cust SP** -`aside_port_name` - Name of ECX Fabric port that should be connected used for the connection, i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-000 - -`connection_name` - the name of the connection -`connection_type` - connection type, please refer schema -`notifications_type` - notification type -`notifications_emails` - List of emails -`bandwidth` - bandwidth in MBs -`redundancy` - Port redundancy -`aside_ap_type` - Access point type -`aside_port_uuid` - Port uuid, fetched based on port call using Port resource -`aside_link_protocol_type` - link protocol type -`aside_link_protocol_tag` - tag number -`zside_ap_type` - Z side access point type -`zside_ap_profile_type` - Service profile type -`zside_ap_profile_uuid` - Service profile uuid, fetched based on Service Profile get call using Service Profile search schema -`zside_location` - Seller location +- `equinix_client_id` - Equinix client ID (consumer key), obtained after registering app in the developer platform +- `equinix_client_secret` - Equinix client secret ID (consumer secret), obtained same way as above +- `fabric_sp_name` - Service profile name like i.e. **Cross Cust SP** +- `aside_port_name` - Name of ECX Fabric port that should be connected used for the connection, i.e. ops-user100-CX-SV5-NL-Qinq-BO-10G-SEC-JP-000 +- `connection_name` - the name of the connection +- `connection_type` - connection type, please refer schema +- `notifications_type` - notification type +- `notifications_emails` - List of emails +- `bandwidth` - bandwidth in MBs +- `redundancy` - Port redundancy +- `aside_ap_type` - Access point type +- `aside_port_uuid` - Port uuid, fetched based on port call using Port resource +- `aside_link_protocol_type` - link protocol type +- `aside_link_protocol_tag` - tag number +- `zside_ap_type` - Z side access point type +- `zside_ap_profile_type` - Service profile type +- `zside_ap_profile_uuid` - Service profile uuid, fetched based on Service Profile get call using Service Profile search schema +- `zside_location` - Seller location ## Initialize +- First step is to initialize the terraform directory/resource we are going to work on. + In the given example, the folder to perform CRUD operations for port2serviceprofilepublic connection can be found at examples/fabric/v4/portConnectivity/port2serviceprofilepublic/. -Change directory to example directory and initialize Terraform plugins -by running `terraform init`. +- Change directory into - `CD examples/fabric/v4/portConnectivity/port2serviceprofilepublic/` +- Initialize Terraform plugins - `terraform init` -## Deploy template +## Port to Service Profile Public connection : Create, Read, Update and Delete(CRUD) operations +Note: `–auto-approve` command does not prompt the user for validating the applying config. Remove it to get a prompt to confirm the operation. -Apply changes by running `terraform apply`, then **inspect proposed plan** -and approve it. +| Operation | Command | Description | +|:----------|:---------------------------------:|----------------------------------------------------------------------------------------:| +| CREATE | `terraform apply –auto-approve` | Creates a port2serviceprofilepublic connection resource | +| READ | `terraform show` | Reads/Shows the current state of the port2serviceprofilepublic connection resource | +| UPDATE | `terraform apply -refresh` | Updates the port2serviceprofilepublic with values provided in the terraform.tfvars file | +| DELETE | `terraform destroy –auto-approve` | Deletes the created port2serviceprofilepublic connection resource |