diff --git a/docs/_deploy_gcp_conductor_network_design.md b/docs/_deploy_gcp_conductor_network_design.md new file mode 100644 index 0000000000..0c9e168353 --- /dev/null +++ b/docs/_deploy_gcp_conductor_network_design.md @@ -0,0 +1,13 @@ + + +The following IP addressing and naming scheme is used consistently throughout this guide. Substitute your own values when configuring your network. + +| Parameter | Example Value | Description | +|-----------|--------------|-------------| +| 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 | +| External IP | `35.X.X.X` | Conductor `nic0` public IP address assigned by GCP | +| Authority Name | `Authority128` | Organizational authority name | +| Conductor Node Name | `node0` | Conductor node name | diff --git a/docs/deploy_appendix_gcp_conductor.mdx b/docs/deploy_appendix_gcp_conductor.mdx new file mode 100644 index 0000000000..821664ca84 --- /dev/null +++ b/docs/deploy_appendix_gcp_conductor.mdx @@ -0,0 +1,58 @@ +--- +title: Appendix - GCP Conductor Configuration +sidebar_label: Appendix - GCP Conductor Configuration +--- + +This appendix contains the complete Terraform variable reference for the GCP conductor deployment described in this guide. Use it when creating the `ssr-variables.tfvars` file in [Step 2 — Create the GCP VM](deploy_gcp_conductor_install.mdx#deploy-a-gcp-conductor-vm-using-the-command-line-interface). + +## Deployment Parameters + +The following table describes all supported Terraform variables for the BYOL conductor deployment in GCP. Variables marked **Required** must be present in `ssr-variables.tfvars`. All others are optional and fall back to defaults when omitted. + +| GCP Marketplace Name | Terraform Variable | Required | Description | +|----------------------|--------------------|----------|-------------| +| Deployment Name | `goog_cm_deployment_name` | Yes | Name of the conductor VM instance displayed in GCP and the conductor UI. | +| Machine Type | `machine_type` | Yes | GCP machine type for the conductor VM (for example, `c2-standard-4`). | +| Region | `region` | Yes | GCP region where the conductor VM is deployed. | +| Zone | `zone` | Yes | GCP zone within the selected region. | +| Boot Disk Size | `boot_disk_size` | Yes | Boot disk size in GB. Minimum `60` is recommended. | +| SSR Mode | `ssr_mode` | Yes | Set to `conductor` for a conductor deployment. | +| SSR Version | `ssr_version` | Yes | SSR software version to install on the conductor (for example, `7.1.4`). | +| Artifactory Username | `artifactory_user` | Yes | Username for Juniper BYOL repository access. | +| Artifactory Token | `artifactory_token` | Yes | Token or password for Juniper BYOL repository access. | +| SSH Public Key | `ssh_public_key` | Yes | Public SSH key added for administrator access to the conductor VM. | +| Admin Allowed CIDR | `admin_allowed_cidr` | Yes | Source CIDR range allowed for SSH and HTTPS administration access. | +| Control Interface Network | `control_nic_network` | Yes | List containing the VPC network name for the conductor control interface. | +| Control Interface Subnet | `control_nic_subnet` | Yes | List containing the subnet name for the conductor control interface. | +| Control Allowed CIDR | `control_nic_allowed_cidr` | Yes | Source CIDR range allowed to reach the conductor on ports 930, 4505, and 4506. | + +## Sample `ssr-variables.tfvars` + +The following sample file reflects the network design used in this guide. Replace each value with your own before running `terraform apply`. + +```text +goog_cm_deployment_name = "conductor" +machine_type = "c2-standard-4" +region = "us-west2" +zone = "us-west2-a" +boot_disk_size = "60" +ssr_mode = "conductor" +ssr_version = "7.1.4" +artifactory_user = "" +artifactory_token = "" +ssh_public_key = "" +admin_allowed_cidr = "0.0.0.0/0" +control_nic_network = ["conductor-vpc"] +control_nic_subnet = ["conductor-subnet"] +control_nic_allowed_cidr = "0.0.0.0/0" +``` + +:::caution +Replace `admin_allowed_cidr` and `control_nic_allowed_cidr` with appropriately restricted CIDR ranges for your environment before deploying to production. Using `0.0.0.0/0` permits access from any source address. +::: + +## Related Documentation + +- [Step 2 — Deploy via GCP Marketplace](deploy_gcp_conductor_install.mdx) +- [Installing a BYOL Conductor-managed Router in GCP](intro_installation_byol_gcp_conductor.md) +- [System Requirements](intro_system_reqs.md) diff --git a/docs/deploy_gcp_conductor.mdx b/docs/deploy_gcp_conductor.mdx new file mode 100644 index 0000000000..511e5678d4 --- /dev/null +++ b/docs/deploy_gcp_conductor.mdx @@ -0,0 +1,80 @@ +--- +title: GCP Conductor Deployment Overview +sidebar_label: Overview +--- + +This guide walks you through deploying a **Session Smart Conductor on the 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. + +## Guide Topics + +| 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. | +| 3 | [Configure the Conductor](deploy_gcp_conductor_config.mdx) | Set the authority name, conductor address, and assign the asset ID. | +| — | [Appendix — GCP Conductor Configuration](deploy_appendix_gcp_conductor.mdx) | Complete Terraform variable reference for the GCP conductor deployment. | + +## Network Topology + +The diagram below shows the logical network of the GCP conductor deployed in this guide. + +```mermaid +graph TD + Internet((Internet)) + Admin["Administrator\n(SSH / HTTPS)"] + subgraph GCP["GCP Project"] + subgraph VPC["conductor-vpc"] + subgraph Subnet["conductor-subnet\n192.168.1.0/24"] + ConductorVM["SSR Conductor VM\nconductor\ge-0-0: 192.168.1.2 internal\ge-0-0: 35.X.X.X external"] + end + end + end + SSRRouters["SSR Routers\nbranch sites"] + + Internet <-->|"Internet"| ConductorVM + Admin -->|"HTTPS / SSH"| ConductorVM + SSRRouters <-->|"Port 930 / 4505 / 4506\nrouter-to-conductor"| ConductorVM +``` + +## Roles + +| Device | Type | Role | +|--------|------|------| +| `conductor` | GCP VM (Marketplace) | Standalone SSR Conductor — centralized management and provisioning | + +## Prerequisites + +Before beginning, ensure the following are available: + +- **GCP access** — access to a GCP project with permissions to create VPC networks, subnets, VM instances, and service accounts. +- **Juniper software access credentials** — Artifactory username and token for software downloads and provisioning. +- **SSH key pair** — an RSA key pair for authenticating to the conductor VM. Steps to create one are in [Step 1 — Configure the GCP Prerequisites](deploy_gcp_conductor_prereqs.mdx). + +## Instance Size + +Select a GCP machine type that meets your network scale requirements. The following instance types are supported for virtual SSR in GCP. + +| GCP Machine Type | Max vNICs | vCPU Cores | Memory | +|------------------|-----------|-----------|--------| +| `c2-standard-4` | 4 | 4 | 16 GB | +| `c2-standard-8` | 8 | 8 | 32 GB | +| `c2-standard-16` | 10 | 16 | 64 GB | +| `c2-standard-30` | 10 | 30 | 120 GB | + +For additional guidance, see [System Requirements](intro_system_reqs.md) and the [GCP machine type documentation](https://cloud.google.com/compute/docs/compute-optimized-machines#c2_machine_types). + +## Software Version Requirements + +- This guide installs **SSR 7.1.4** on the conductor. + +- The router software version must be lower than or equal to the conductor software version. + +- BYOL instances require the conductor to run SSR 6.3.0-R1 or newer. SSR 7.1.4 satisfies this requirement. + + +## Related Documentation + +- [Installing a BYOL Conductor-managed Router in GCP](intro_installation_byol_gcp_conductor.md) +- [System Requirements](intro_system_reqs.md) +- [Conductor Deployment Best Practices](bcp_conductor_deployment.md) +- [Onboard an SSR Device to a Conductor](onboard_ssr_to_conductor.md) diff --git a/docs/deploy_gcp_conductor_config.mdx b/docs/deploy_gcp_conductor_config.mdx new file mode 100644 index 0000000000..860739cb26 --- /dev/null +++ b/docs/deploy_gcp_conductor_config.mdx @@ -0,0 +1,99 @@ +--- +title: "Step 3: Configure the Conductor" +sidebar_label: "Configure the Conductor" +--- +import NetworkDesign from './_deploy_gcp_conductor_network_design.md'; + +This step accesses the conductor web GUI and configures the authority name, conductor address, and asset ID. All steps are performed from a browser unless otherwise noted. + +## Network Design Reference + + + +## 1. Access the Conductor GUI + +1. In the GCP Console, navigate to the VM Instance created in [Step 2 — Create the GCP VM](deploy_gcp_conductor_install.mdx). Copy the external IP of the the conductor VM. + +2. In a browser, navigate to: + + ``` + https:// + ``` + +3. On the conductor login page, enter the default credentials: + + | Field | Value | + |-------|-------| + | Username | `admin` | + | Password | `128Tadmin` | + + :::important + Change the default password immediately after your first login. This **must** be changed. The new password has the following minimum requirements: A minimum of 9 characters; Contain 1 upper case letter, 1 lower case letter, and 1 number. + ::: + +## 2. Set the Authority Name + +The authority name identifies your organization within the SSR configuration model. It applies globally to all routers managed by this conductor and cannot be changed after routers have been provisioned without re-onboarding them. + +1. In the left menu, click **Authority** under **Configuration**. + +2. Click **Authority**. + + ![Authority Name](/img/deploy-gcp-conductor-config3.png) + +3. In the **Basic Information** section, update the **Name** field to your organization's name. This guide uses the default value `Authority128`. + + ![Authority128](/img/deploy-gcp-conductor-config4.png) + +## 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. + +1. Scroll down to the **Conductor Addresses** section, click **Add**. + + ![Add conductor address](/img/deploy-gcp-conductor-config5.png) + +2. In the **New Conductor Address** window, enter the conductor VM's external IP address and click **Save**. + + ![External IP Address](/img/deploy-gcp-conductor-config6.png) + +3. In the top-right corner, click **Validate** and then **Commit**. In the confirmation window, click **Proceed Commit**. + + ![Commit the Config](/img/deploy-gcp-conductor-config7.png) + +## 4. Assign the Asset ID and Confirm the Role + +1. In the left menu, click **Authority** under **Configuration**, then click **conductor** under **Routers**. + + ![Authority view](/img/deploy-gcp-conductor-config8.png) + +2. In the **Nodes** section, click **node0**. + + ![node0](/img/deploy-gcp-conductor-config9.png) + +3. In the **Basic Information** section: + - In the **Associated Asset ID** field, select the conductor VM name. + - Verify that the **Role** field shows `conductor`. + + ![Node Basic Info](/img/deploy-gcp-conductor-config10.png) + +4. In the top-right corner, click **Validate** and then **Commit**. In the confirmation window, click **Proceed Commit**. + +## What Was Configured + +At the end of this step your authority contains: + +| Object | Name | Value | +|--------|------|-------| +| Authority | `Authority128` | | +| Conductor Address | | `35.X.X.X` (external IP) | +| Node Asset ID | `node0` | Linked to conductor VM | +| Node Role | `node0` | `conductor` | + +The conductor is now fully deployed and ready to onboard SSR routers. + +## Related Topics + +- [Onboard an SSR Device to a Conductor](onboard_ssr_to_conductor.md) +- [Conductor Deployment Best Practices](bcp_conductor_deployment.md) +- [Appendix — Deployment Parameters](deploy_appendix_gcp_conductor.mdx) diff --git a/docs/deploy_gcp_conductor_install.mdx b/docs/deploy_gcp_conductor_install.mdx new file mode 100644 index 0000000000..1c465bc59c --- /dev/null +++ b/docs/deploy_gcp_conductor_install.mdx @@ -0,0 +1,82 @@ +--- +title: "Step 2: Create the GCP VM" +sidebar_label: "Create the GCP VM" +--- +import NetworkDesign from './_deploy_gcp_conductor_network_design.md'; + +This step deploys the BYOL Session Smart Conductor VM from the GCP Marketplace. The deployment template creates the VM, assigns a static public IP to the management interface, and configures a network security group. SSR version 7.1.4 is automatically installed and the node is initialized as a conductor. + + +The following procedure deploys a GCP Conductor VM using the GUI. + +### Select the BYOL Plan + +1. In the GCP console, search for **Marketplace** in the search bar. Click the Marketplace listing in the results. + +![GCP Marketplace](/img/deploy-gcp-conductor-web1.png) + +2. Enter **Session Smart Networking Platform – BYOL** in the Marketplace search tool, and select the **Session Smart Networking Platform – BYOL** result. + +![marketplace Search](/img/deploy-gcp-conductor-web2.png) + +3. On the product details page, click **Launch**. + +![Product Details Panel](/img/deploy-gcp-conductor-web3.png) + +### Configure the Deployment + +Under the **New Session Smart Networking Platform – BYOL deployment**, provide the following: + +**Add a table here, using the same format as the Azure tables + +1. **Deployment Name** — enter a name for the conductor VM instance. This name appears in GCP and in the conductor UI (for example, `conductor`). + + ![Deployment Name](/img/deploy-gcp-conductor-web4.png) + +2. **Deployment Service Account** — in the **Deployment Service Account** section, select **New account** and provide a name for the new service account. This creates a service account with the required IAM roles automatically. + + ![Service Account](/img/deploy-gcp-conductor-web5.png) + +3. **Machine Type** — select the instance size that best meets your network requirements and select the desired **Region** and **Zone**. See the [Instance Size](deploy_gcp_conductor.mdx#instance-size) table in the Overview for guidance. + + ![Machine Type](/img/deploy-gcp-conductor-web6.png) + +4. **SSR Configuration** — in the **Session Smart Router BYOL Configuration** section: + - Set **SSR Mode** to `conductor`. + - Enter the desired **SSR Version** - `7.1.4`. + + ![Mode and Version](/img/deploy-gcp-conductor-web7.png) + +5. **SSH Access Control** — in the **SSH Access Control** section: + - Enter the **Admin Allowed CIDR** — the source IP range permitted for SSH and HTTPS access. + - Paste the SSH public key you created in [Step 1](deploy_gcp_conductor_prereqs.mdx) into the **SSH Public Key** field. + + ![SSH Access Control](/img/deploy-gcp-conductor-web8.png) + +6. **Conductor Configuration and Networking** — in the **SSR Mode: Conductor Configuration Options** section: + - Enter your **Artifactory Username** and **Artifactory Token**. + - Enter the **Conductor Control Allowed CIDR** — the source IP range permitted to connect to the conductor on ports 930, 4505, and 4506. + - Click **Add a network interface**, select the VPC you created in [Step 1](deploy_gcp_conductor_prereqs.mdx) for **Network**, and the subnet for **Subnetwork**. Click **Done**. + + ![SSR Mode](/img/deploy-gcp-conductor-web9.png) + +### Deploy + +Once all sections are complete, scroll to the bottom and click **Deploy**. + +:::important +Leave the Mist-managed and Conductor-managed router sections empty. Providing inputs for a conductor deployment will cause the deployment to fail. +::: + +![GCP Marketplace common template fields](/img/deploy-gcp-conductor-web9a.png) +![GCP Marketplace conductor-specific fields](/img/deploy-gcp-conductor-web9b.png) + +A green checkmark appears under **Status** for each successfully created resource. After the VM is created, the the SSR software installation and initialization process automatically runs. Allow 10-15 minutes for this to complete before proceeding. + + ![Conductor Complete](/img/deploy-gcp-conductor-web10.png) + +After the VM is created, it automatically runs its initialization process to install the SSR software. **Allow an additional 20 minutes for initialization to complete** before proceeding to [Step 3 — Configure the Conductor](deploy_gcp_conductor_config.mdx). + +## Next Step + +Proceed to [Step 3 — Verify the Installation](deploy_gcp_conductor_verification.md). diff --git a/docs/deploy_gcp_conductor_prereqs.mdx b/docs/deploy_gcp_conductor_prereqs.mdx new file mode 100644 index 0000000000..d912ffa0b8 --- /dev/null +++ b/docs/deploy_gcp_conductor_prereqs.mdx @@ -0,0 +1,86 @@ +--- +title: "Step 1: Configure the GCP Prerequisites" +sidebar_label: "Configure the GCP Prerequisites" +--- +import NetworkDesign from './_deploy_gcp_conductor_network_design.md'; + +Before deploying the SSR conductor on GCP you must create the required VPCs, SSH public/private key pair, and the GCP service account used for deployment. + +## Network Design Reference + + + +## 1. Create a VPC and Subnet + +The conductor VM requires a single network interface (`ge-0-0`) that will be automatically created during deployment. This interface receives an internal IP address within the subnet you specify, and an external (public) IP address for management access — including SSH, HTTPS (web console), and communication with the routers. + +Create the VPC and subnet in your GCP project before beginning the Marketplace deployment. + +1. In the GCP console, search for **VPC networks** in the search bar and click on **VPC Networks**. + +![VPC Networks](/img/deploy-gcp-create-vpc1.png) + +2. On the Google Cloud dashboard under VPC networks, click **Create VPC Network**. + +![Create VPC Network](/img/deploy-gcp-create-vpc2.png) + +3. Under **Create a VPC network**, enter the following information: + - VPC Name: `conductor-vpc` + - Subnet Name: `conductor-subnet` + - Subnet Region + - An IPv4 range for the subnet (for example, `10.0.1.0/24`) + +![Define the VPC Network](/img/deploy-gcp-create-vpc3.png) + +4. Scroll to the bottom and click **Create**. + + After the VPC is created it appears on the VPC networks page. + +![VPC Networks Page](/img/deploy-gcp-create-vpc4.png) + +:::note +An existing VPC and subnet can be used instead of creating a new one. In that case, skip this section and use your existing VPC and subnet names during the Marketplace deployment. +::: + +## 2. Create an SSH Key Pair + +An SSH key pair is required to authenticate to the conductor VM after deployment. The public key is provided to the Marketplace deployment form; the private key stays on your local machine. + +The following example uses a macOS terminal. + +1. Open a terminal on your local machine and run: + + ``` + ssh-keygen -t rsa -b 4096 + ``` + +2. When prompted, enter a name for the key pair and a passphrase. The key files are saved to your home directory. + +3. Display the public key by running the following command, replacing `` with the filename you chose: + + ``` + cat .pub + ``` + +4. Copy the key output for use later. You will paste this value into the **SSH Public Key** field during the Marketplace deployment. + +:::note +An existing SSH key pair can be used instead of creating a new one. In that case, skip this section and use your existing public key during deployment. +::: + +## 3. Create the GCP Service Account + +The deployment requires a GCP service account with the following IAM roles: + +| Role | Purpose | +|------|---------| +| `roles/config.agent` | Required for GCP deployment manager operations | +| `roles/compute.admin` | Required to create and manage compute resources | +| `roles/iam.serviceAccountUser` | Required to act as the service account | +| `roles/storage.objectViewer` | Required to read deployment objects from storage | + +You can create the service account directly within the Marketplace deployment form during [Step 2 — Create the GCP VM](deploy_gcp_conductor_install.mdx). A separate pre-creation step in the GCP console is not required. + +## Next Step + +Proceed to [Step 2 — Create the GCP VM](deploy_gcp_conductor_install.mdx). diff --git a/docs/deploy_gcp_conductor_verification.md b/docs/deploy_gcp_conductor_verification.md new file mode 100644 index 0000000000..083468256f --- /dev/null +++ b/docs/deploy_gcp_conductor_verification.md @@ -0,0 +1,57 @@ +--- +title: "Step 3: Verify the Installation" +sidebar_label: "Verify the Installation" +--- + +This step verifies that the BYOL installation has completed successfully, confirms the conductor is running, and walks you through logging in to the conductor GUI for the first time. + +## Wait for Installation to Complete + +The BYOL bootstrapper installs SSR 7.1.4 automatically after the VM is deployed. This process takes approximately **20 minutes** after the VM first starts. The SSR Install screens do not open - this process takes place behind the scenes. + +## Verify the Successful Conductor Installation + +You can verify the successful conductor installation by logging in to the Conductor GUI using the Conductor Primary NIC public IP address. + +**Add Conductor IP address graphic here + +:::important +Attempting to open the Conductor GUI before the installation has completed - i.e., not waiting 20 minutes - will result in an error message. This DOES NOT mean the installation failed, it means it has not completed yet. If you get an error message, wait longer, then try again. +::: + +1. Open a browser and navigate to `https://`. + + :::note + The conductor uses a self-signed certificate. If your browser presents an "unsafe connection" warning, click through to continue. You can replace the certificate later. + ::: + +2. Log in with the following default credentials: + + | Field | Value | + | :-----| :------| + | Username | `admin` | + | Password | `128Tadmin` | + + :::important + You must change the default password immediately after first login. The new password requires a minimum of 9 characters containing at least 1 uppercase letter, 1 lowercase letter, and 1 number. + ::: + +3. A successful login confirms the conductor is running and reachable on the public IP. + +## Troubleshooting the Installation + +### Device Does Not Initialize Properly + +Once the instance is launched with the correct parameters, the device will begin to install the SSR software. After installing the software, the device will initialize as a Conductor. This process can take up to 20 minutes to complete. + +If the instance does not install SSR as expected, SSH into the instance using the credentials provided during VM creation. + +`ssh -i t128@` + +- Try to log into the pcli, run `su admin`, enter your password, and then `show system`. + +- If the pcli is not accessible or the status and necessary action is not obvious, capture the Hardware Bootstrapper tech support (`/var/log/128T-hardware-bootstrapper/hardware-bootstrapper-tech-support.zip`) and examine the journal for `128T-hardware-bootstrapper`, and `ember`. + +## Next Step + +Proceed to [Step 3 — Configure the Conductor](deploy_gcp_conductor_config.mdx). diff --git a/docs/deploy_guides_overview.md b/docs/deploy_guides_overview.md index b8765228c8..b73703a355 100644 --- a/docs/deploy_guides_overview.md +++ b/docs/deploy_guides_overview.md @@ -5,7 +5,7 @@ sidebar_label: Overview Conductor and Router Deployment Guides are provided to help walk a network engineer through the steps required to stand up a conductor-managed SSR network. -Conductor deployment guides are available for VMware ESXi and Azure. Each conductor guide explains how to install and configure a conductor to be ready for a branch router to onboard and come online, managed by the conductor, forwarding internet traffic for LAN users, and reachable by the conductor over the same WAN interface used for internet breakout. +Conductor deployments currently include VMware ESXi, Azure, and Google Cloud Platform (GCP). In each guide the conductor will have a configuration ready for a branch router to onboard and come online, managed by the conductor, forwarding internet traffic for LAN users, and reachable by the conductor over the same WAN interface used for internet breakout. Router deployment guides include VMWare ESXi spoke and hub configurations. By the end of the guide, the VMware router VM will be running SSR 7.1.4-3.r2, managed by an existing SSR conductor, and forwarding internet traffic from LAN users with management traffic returning to the conductor over the same WAN interface used for internet breakout. diff --git a/sidebars.js b/sidebars.js index b5a59d073a..e35a719a50 100644 --- a/sidebars.js +++ b/sidebars.js @@ -206,7 +206,7 @@ module.exports = { "deploy_appendix_vmware_conductor", ], }, - { + { "type": "category", "label": "Azure Conductor", "items": [ @@ -217,6 +217,18 @@ module.exports = { "deploy_appendix_azure_conductor", ], }, + { + "type": "category", + "label": "GCP Conductor", + "items": [ + "deploy_gcp_conductor", + "deploy_gcp_conductor_prereqs", + "deploy_gcp_conductor_install", + "deploy_gcp_conductor_verification", + "deploy_gcp_conductor_config", + "deploy_appendix_gcp_conductor", + ], + }, ], }, { diff --git a/static/img/deploy-gcp-conductor-cli10.png b/static/img/deploy-gcp-conductor-cli10.png new file mode 100644 index 0000000000..86671968ed Binary files /dev/null and b/static/img/deploy-gcp-conductor-cli10.png differ diff --git a/static/img/deploy-gcp-conductor-cli11.png b/static/img/deploy-gcp-conductor-cli11.png new file mode 100644 index 0000000000..247e49e308 Binary files /dev/null and b/static/img/deploy-gcp-conductor-cli11.png differ diff --git a/static/img/deploy-gcp-conductor-cli4.png b/static/img/deploy-gcp-conductor-cli4.png new file mode 100644 index 0000000000..3e7ba2e066 Binary files /dev/null and b/static/img/deploy-gcp-conductor-cli4.png differ diff --git a/static/img/deploy-gcp-conductor-cli5.png b/static/img/deploy-gcp-conductor-cli5.png new file mode 100644 index 0000000000..9115aae818 Binary files /dev/null and b/static/img/deploy-gcp-conductor-cli5.png differ diff --git a/static/img/deploy-gcp-conductor-cli6.png b/static/img/deploy-gcp-conductor-cli6.png new file mode 100644 index 0000000000..19cca3f338 Binary files /dev/null and b/static/img/deploy-gcp-conductor-cli6.png differ diff --git a/static/img/deploy-gcp-conductor-cli7.png b/static/img/deploy-gcp-conductor-cli7.png new file mode 100644 index 0000000000..9a56756bd8 Binary files /dev/null and b/static/img/deploy-gcp-conductor-cli7.png differ diff --git a/static/img/deploy-gcp-conductor-cli8.png b/static/img/deploy-gcp-conductor-cli8.png new file mode 100644 index 0000000000..1ea05a7ebf Binary files /dev/null and b/static/img/deploy-gcp-conductor-cli8.png differ diff --git a/static/img/deploy-gcp-conductor-cli9.png b/static/img/deploy-gcp-conductor-cli9.png new file mode 100644 index 0000000000..bcd03ed659 Binary files /dev/null and b/static/img/deploy-gcp-conductor-cli9.png differ diff --git a/static/img/deploy-gcp-conductor-config1.png b/static/img/deploy-gcp-conductor-config1.png new file mode 100644 index 0000000000..dc641e8d06 Binary files /dev/null and b/static/img/deploy-gcp-conductor-config1.png differ diff --git a/static/img/deploy-gcp-conductor-config10.png b/static/img/deploy-gcp-conductor-config10.png new file mode 100644 index 0000000000..aca6641e6b Binary files /dev/null and b/static/img/deploy-gcp-conductor-config10.png differ diff --git a/static/img/deploy-gcp-conductor-config2.png b/static/img/deploy-gcp-conductor-config2.png new file mode 100644 index 0000000000..7fbe7fc952 Binary files /dev/null and b/static/img/deploy-gcp-conductor-config2.png differ diff --git a/static/img/deploy-gcp-conductor-config3.png b/static/img/deploy-gcp-conductor-config3.png new file mode 100644 index 0000000000..7f38382650 Binary files /dev/null and b/static/img/deploy-gcp-conductor-config3.png differ diff --git a/static/img/deploy-gcp-conductor-config4.png b/static/img/deploy-gcp-conductor-config4.png new file mode 100644 index 0000000000..ba7be41aca Binary files /dev/null and b/static/img/deploy-gcp-conductor-config4.png differ diff --git a/static/img/deploy-gcp-conductor-config5.png b/static/img/deploy-gcp-conductor-config5.png new file mode 100644 index 0000000000..d4972433c2 Binary files /dev/null and b/static/img/deploy-gcp-conductor-config5.png differ diff --git a/static/img/deploy-gcp-conductor-config6.png b/static/img/deploy-gcp-conductor-config6.png new file mode 100644 index 0000000000..d510cc7ca2 Binary files /dev/null and b/static/img/deploy-gcp-conductor-config6.png differ diff --git a/static/img/deploy-gcp-conductor-config7.png b/static/img/deploy-gcp-conductor-config7.png new file mode 100644 index 0000000000..b3da72dc99 Binary files /dev/null and b/static/img/deploy-gcp-conductor-config7.png differ diff --git a/static/img/deploy-gcp-conductor-config8.png b/static/img/deploy-gcp-conductor-config8.png new file mode 100644 index 0000000000..a4b8f47a8c Binary files /dev/null and b/static/img/deploy-gcp-conductor-config8.png differ diff --git a/static/img/deploy-gcp-conductor-config9.png b/static/img/deploy-gcp-conductor-config9.png new file mode 100644 index 0000000000..dfca5b2e5f Binary files /dev/null and b/static/img/deploy-gcp-conductor-config9.png differ diff --git a/static/img/deploy-gcp-conductor-web1.png b/static/img/deploy-gcp-conductor-web1.png new file mode 100644 index 0000000000..cc7d6c6ecf Binary files /dev/null and b/static/img/deploy-gcp-conductor-web1.png differ diff --git a/static/img/deploy-gcp-conductor-web10.png b/static/img/deploy-gcp-conductor-web10.png new file mode 100644 index 0000000000..aba0be9b4a Binary files /dev/null and b/static/img/deploy-gcp-conductor-web10.png differ diff --git a/static/img/deploy-gcp-conductor-web2.png b/static/img/deploy-gcp-conductor-web2.png new file mode 100644 index 0000000000..71491c35e2 Binary files /dev/null and b/static/img/deploy-gcp-conductor-web2.png differ diff --git a/static/img/deploy-gcp-conductor-web3.png b/static/img/deploy-gcp-conductor-web3.png new file mode 100644 index 0000000000..6d6b8c5cb5 Binary files /dev/null and b/static/img/deploy-gcp-conductor-web3.png differ diff --git a/static/img/deploy-gcp-conductor-web4.png b/static/img/deploy-gcp-conductor-web4.png new file mode 100644 index 0000000000..5e63b2abef Binary files /dev/null and b/static/img/deploy-gcp-conductor-web4.png differ diff --git a/static/img/deploy-gcp-conductor-web5.png b/static/img/deploy-gcp-conductor-web5.png new file mode 100644 index 0000000000..7d1fe2c6dd Binary files /dev/null and b/static/img/deploy-gcp-conductor-web5.png differ diff --git a/static/img/deploy-gcp-conductor-web6.png b/static/img/deploy-gcp-conductor-web6.png new file mode 100644 index 0000000000..92554e91a2 Binary files /dev/null and b/static/img/deploy-gcp-conductor-web6.png differ diff --git a/static/img/deploy-gcp-conductor-web7.png b/static/img/deploy-gcp-conductor-web7.png new file mode 100644 index 0000000000..6e62e2b8f1 Binary files /dev/null and b/static/img/deploy-gcp-conductor-web7.png differ diff --git a/static/img/deploy-gcp-conductor-web8.png b/static/img/deploy-gcp-conductor-web8.png new file mode 100644 index 0000000000..be388aec89 Binary files /dev/null and b/static/img/deploy-gcp-conductor-web8.png differ diff --git a/static/img/deploy-gcp-conductor-web9.png b/static/img/deploy-gcp-conductor-web9.png new file mode 100644 index 0000000000..fc3b8b43b2 Binary files /dev/null and b/static/img/deploy-gcp-conductor-web9.png differ diff --git a/static/img/deploy-gcp-conductor-web9a.png b/static/img/deploy-gcp-conductor-web9a.png new file mode 100644 index 0000000000..6057a9c810 Binary files /dev/null and b/static/img/deploy-gcp-conductor-web9a.png differ diff --git a/static/img/deploy-gcp-conductor-web9b.png b/static/img/deploy-gcp-conductor-web9b.png new file mode 100644 index 0000000000..ae00e1f4a1 Binary files /dev/null and b/static/img/deploy-gcp-conductor-web9b.png differ diff --git a/static/img/deploy-gcp-create-vpc1.png b/static/img/deploy-gcp-create-vpc1.png new file mode 100644 index 0000000000..a6002fc610 Binary files /dev/null and b/static/img/deploy-gcp-create-vpc1.png differ diff --git a/static/img/deploy-gcp-create-vpc2.png b/static/img/deploy-gcp-create-vpc2.png new file mode 100644 index 0000000000..974cf5ccd3 Binary files /dev/null and b/static/img/deploy-gcp-create-vpc2.png differ diff --git a/static/img/deploy-gcp-create-vpc3.png b/static/img/deploy-gcp-create-vpc3.png new file mode 100644 index 0000000000..81ae00ae20 Binary files /dev/null and b/static/img/deploy-gcp-create-vpc3.png differ diff --git a/static/img/deploy-gcp-create-vpc4.png b/static/img/deploy-gcp-create-vpc4.png new file mode 100644 index 0000000000..9abe1ee286 Binary files /dev/null and b/static/img/deploy-gcp-create-vpc4.png differ