feat: adding BGP enable/disable functionality to routing-protocol-bgp (…

…#392) Update: Adding BGP enable/disable functionality to BGP Routing Protocol Updating README.md files for Fabric Examples
equinix · Sep 27, 2023 · 89a5a51 · 89a5a51
2 parents 97e8ea6 + 872618d
commit 89a5a51
Show file tree

Hide file tree

Showing 21 changed files with 461 additions and 462 deletions.
diff --git a/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2aws/README.md b/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2aws/README.md
@@ -5,44 +5,41 @@ 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
 
 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 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 |
+| 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 |
diff --git a/...fabric/v4/cloudRouterConnectivity/cloudRouter2azure/single-connection/README.md b/...fabric/v4/cloudRouterConnectivity/cloudRouter2azure/single-connection/README.md
@@ -5,38 +5,35 @@ 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
 
 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 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/...s/fabric/v4/cloudRouterConnectivity/cloudRouter2azure/two-connections/README.md b/...s/fabric/v4/cloudRouterConnectivity/cloudRouter2azure/two-connections/README.md
@@ -5,41 +5,38 @@ 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
 
 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 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
@@ -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 |
+| 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 |
diff --git a/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2oracle/README.md b/examples/fabric/v4/cloudRouterConnectivity/cloudRouter2oracle/README.md
@@ -5,38 +5,35 @@ 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
 
 Log in to Oracle Cloud 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 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 |