Repository navigation
Docs 544 GCP Conductor Deployment Guide Draft - #1148
Chr1st0ph3rTurn3r wants to merge 9 commits into
Conversation
| sidebar_label: Overview | ||
| --- | ||
|
|
||
| This guide walks a network engineer through deploying a **standalone SSR Conductor in Google Cloud Platform (GCP)** using the GCP Marketplace. You can choose between two deployment methods: a graphical user interface or a command-line (Terraform) workflow. When you complete the steps in this guide, the conductor will be running SSR 7.1.4, configured with an authority name and conductor address, and ready for SSR routers to onboard. |
There was a problem hiding this comment.
Rephrase to
This guide walks you through deploying a Juniper Session Smart Conductor in Google Cloud Platform (GCP) using the Bring Your Own License (BYOL) plan. When you complete the steps in this guide, the conductor will be running SSR software version 7.1.4, configured with an authority name and conductor address, and ready for SSR routers to onboard.
| | Step | Topic | Description | | ||
| |------|-------|-------------| | ||
| | 1 | [Configure the GCP Prerequisites](deploy_gcp_conductor_prereqs.mdx) | Create the required VPCs, SSH public/private key pair, and the GCP service account used for deployment. | | ||
| | 2 | [Create the GCP VM](deploy_gcp_conductor_install.mdx) | Launch the conductor VM using the GCP GUI or CLI (Terraform). | |
There was a problem hiding this comment.
Launch the conductor VM using the GCP GUI
| subgraph GCP["GCP Project"] | ||
| subgraph VPC["conductor-vpc"] | ||
| subgraph Subnet["conductor-subnet\n192.168.1.0/24"] | ||
| ConductorVM["SSR Conductor VM\nconductor\nnic0: 192.168.1.2 internal\nnic0: 35.X.X.X external"] |
| :::note | ||
| The router software version must be lower than or equal to the conductor software version. | ||
| ::: | ||
|
|
There was a problem hiding this comment.
Add this note from conductor guide
BYOL instances require the conductor to run SSR 6.3.0-R1 or newer. SSR 7.1.4 satisfies this requirement.
| - VPC Name: `conductor-vpc` | ||
| - Subnet Name: `conductor-subnet` | ||
| - Subnet Region | ||
| - An IPv4 range for the subnet (for example, `192.168.1.0/24`) |
There was a problem hiding this comment.
We should be consistent across deployment guides and always use 10.0.x.y subnets
| ## 3. Add the Conductor Address | ||
|
|
||
| The conductor address is the IP address that managed routers use to reach this conductor. Use the conductor VM's external IP address. | ||
|
|
There was a problem hiding this comment.
Add the similar note from azure doc
If all managed routers reside in the same GCP VPC and communicate over private addressing, you may use the conductor's private IP (10.0.0.10 in this guide) instead.
|
|
||
| ## 4. Assign the Asset ID and Confirm the Role | ||
|
|
||
| 1. In the left menu, click **Authority** under **Configuration**, then click **conductor** under **Routers**. |
There was a problem hiding this comment.
Use the navigation from azure conductor guide. It is easier to follow
- Select the Conductor from the Authority menu on the left side of the GUI.
- Select the Configure icon.
- Select the node for the conductor - in this example it is node0.
- Under Associated Asset ID select the asset id for the conductor.
|
|
||
| 4. In the top-right corner, click **Validate** and then **Commit**. In the confirmation window, click **Proceed Commit**. | ||
|
|
||
| ## What Was Configured |
There was a problem hiding this comment.
Azure doc continues with corp tenant and other things. Should this one too?
| | Deployment Name | `conductor` | VM instance name displayed in GCP and the conductor UI | | ||
| | VPC | `conductor-vpc` | Global private network in GCP | | ||
| | Subnet | `conductor-subnet` | Regional segment within the VPC (`192.168.1.0/24`) | | ||
| | Internal IP | `192.168.1.2` | Conductor `nic0` private IP address assigned by GCP | |
There was a problem hiding this comment.
Lets standardize all this stuff across the guides
ssr-conductor-vpc
ssr-conductor-subnet
10.0.0.x ips
etc
| | VPC | `conductor-vpc` | Global private network in GCP | | ||
| | Subnet | `conductor-subnet` | Regional segment within the VPC (`192.168.1.0/24`) | | ||
| | Internal IP | `192.168.1.2` | Conductor `nic0` private IP address assigned by GCP | | ||
| | External IP | `35.X.X.X` | Conductor `nic0` public IP address assigned by GCP | |
This branch has not been deployed
2 participants
No description provided.