initial gcp docs#993
Conversation
There was a problem hiding this comment.
Pull request overview
Adds initial BYOL installation documentation for deploying Session Smart Router (SSR) in GCP, and updates navigation to surface the new GCP (and AWS BYOL) guides.
Changes:
- Update
sidebars.jsto include new BYOL install docs for AWS and add a new “Installing In GCP” section. - Add new GCP BYOL deployment guides for Conductor-managed and Mist-managed SSR.
- Add new AWS BYOL deployment guides for Conductor-managed and Mist-managed SSR, plus a small Azure wording correction.
Reviewed changes
Copilot reviewed 4 out of 6 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| sidebars.js | Renames AWS BYOL doc IDs and adds a new GCP install category in the sidebar. |
| docs/intro_installation_byol_gcp_mist.md | New guide for deploying a BYOL Mist-managed SSR in GCP. |
| docs/intro_installation_byol_gcp_conductor.md | New guide for deploying a BYOL Conductor and Conductor-managed SSR in GCP. |
| docs/intro_installation_byol_azure_mist.md | Corrects an Azure-specific wording issue in the intro. |
| docs/intro_installation_byol_aws_mist.md | New guide for deploying a BYOL Mist-managed SSR in AWS. |
| docs/intro_installation_byol_aws_conductor.md | New guide for deploying a BYOL Conductor and Conductor-managed SSR in AWS. |
| "label": "Installing In AWS", | ||
| "items": [ | ||
| "intro_installation_quickstart_aws", | ||
| "intro_installation_quickstart_mist_aws", | ||
| "intro_installation_quickstart_byol_conductor_aws", | ||
| "intro_installation_quickstart_byol_mist_aws", | ||
| "intro_installation_byol_aws_conductor", | ||
| "intro_installation_byol_aws_mist", |
| title: Installing a BYOL Conductor-managed Router in GCP | ||
| sidebar_label: Installing a BYOL Conductor-managed Router in GCP |
| * SSR software version | ||
| 6. Specify whether the router is High Availability (HA). | ||
| 7. Provide administrative access settings: | ||
| * Allowed CIDR(s) for SSH/HTTPS access | ||
| * SSH public key |
| ### Failed deployment in GCP Marketplace | ||
| If the deployment failed in the GCP Marketplace, a required parameter is likely missing. To view the error | ||
| 1. Select **View Logs** in the upper right corner | ||
| 2. In the **Build Summary** step, search for the phrase `Error: Resource precondition failed` |
| ```yaml | ||
| #cloud-config | ||
| write_files: | ||
| - path: /etc/128T-hardware-bootstrapper/onboarding-config.json | ||
| content: | | ||
| { | ||
| "name": "<conductor-name>", | ||
| "ssr-version": "<version>", | ||
| "mode": "conductor", | ||
| "artifactory-user": "<username>", | ||
| "artifactory-password": "<password>", | ||
| "node-name": "node0", | ||
| "cloud-provider": "gcp" | ||
| } |
|
|
||
| ### Deployment Fails in Google Cloud Marketplace | ||
|
|
||
| If the deployment failed in the GCP Marketplace, a required parameter is likely missing. To view the error |
|
|
||
| The following instance types are supported for virtual SSR in GCP. Choose the size that best meets your requirements. For additional machine type details, refer to the [GCP machine type documentation](https://docs.cloud.google.com/compute/docs/compute-optimized-machines#c2_machine_types). | ||
|
|
||
| | Recommended VM Size | Max vNICs Supported | vCPU Cores | Memory | |
There was a problem hiding this comment.
These are the instance sizes we recommend, but for what size deployment? For conductors? For routers? I think it would be good to provide a link to our conductor scaling recommendations, if this is to be for a conductor GCP instance: intro_system_reqs.md#conductor-scaling-recommendations
|
|
||
| The following instance types are supported for virtual SSR in GCP. Choose the size that best meets your requirements. More information can be found in the [GCP Documentation](https://docs.cloud.google.com/compute/docs/compute-optimized-machines#c2_machine_types). | ||
|
|
||
| | Recommended VM Size | Max vNICs Supported | vCPU Cores | Memory | |
There was a problem hiding this comment.
Similar to my sizing comment from before, since we don't have router sizing on our docs site, perhaps provide another column with the equivalent SSR product? (e.g., SSR120, SSR130, etc.)
|
|
||
| Interface names start at `ge-0-0` and increment in the same order shown above. | ||
|
|
||
| Example: if an HA SSR is deployed with one Management interface, two WAN interfaces, and two LAN interfaces, names map as follows: |
There was a problem hiding this comment.
If an HA SSR is deployed with one Management interface, two WAN interfaces, and two LAN interfaces, the names map as follows:
Initial GCP docs
TODO: