Skip to content

initial gcp docs#993

Open
haberkornsam wants to merge 5 commits intomasterfrom
shaberkorn/gcp-byol
Open

initial gcp docs#993
haberkornsam wants to merge 5 commits intomasterfrom
shaberkorn/gcp-byol

Conversation

@haberkornsam
Copy link
Copy Markdown
Contributor

Initial GCP docs

TODO:

  • Add screenshots of deployment page

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.js to 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.

Comment thread sidebars.js
Comment on lines 137 to +142
"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",
Comment on lines +2 to +3
title: Installing a BYOL Conductor-managed Router in GCP
sidebar_label: Installing a BYOL Conductor-managed Router in GCP
Comment on lines +59 to +63
* 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
Comment on lines +224 to +227
### 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`
Comment on lines +127 to +140
```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 |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If an HA SSR is deployed with one Management interface, two WAN interfaces, and two LAN interfaces, the names map as follows:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants