DOCS-531 Azure Conductor/hub/spoke Deployment guides - #1122
DOCS-531 Azure Conductor/hub/spoke Deployment guides#1122Chr1st0ph3rTurn3r wants to merge 2 commits into
Conversation
There was a problem hiding this comment.
Pull request overview
Adds new Azure-focused deployment documentation to the Docusaurus docs site, covering both an Azure conductor deployment and an Azure hub/spoke router topology, and exposes these guides through the sidebar navigation.
Changes:
- Added Azure Conductor deployment guide set (overview + step-by-step pages + appendix + network design partial).
- Added Azure Hub-and-Spoke router deployment guide set (overview + step-by-step pages + appendix + network design partial).
- Updated the Deployment Guides overview page and sidebar to include the new Azure guide categories.
Reviewed changes
Copilot reviewed 16 out of 16 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| sidebars.js | Adds new “Azure Conductor” and “Azure Hub and Spoke Routers” categories and registers all new doc IDs. |
| docs/deploy_guides_overview.md | Updates the overview text to reflect Azure availability for conductor/router deployment guides. |
| docs/deploy_azure_conductor.mdx | New Azure Conductor deployment guide landing page with topology, prerequisites, and guide index. |
| docs/deploy_azure_conductor_vm.mdx | New Step 1 for deploying the conductor VM via Portal/automation. |
| docs/deploy_azure_conductor_install.mdx | New Step 2 for verifying install completion and initial GUI access. |
| docs/deploy_azure_conductor_config.mdx | New Step 3 for authority-level conductor configuration (imports existing partials). |
| docs/deploy_azure_conductor_router.mdx | New Step 4 for deploying/configuring a conductor-managed Azure router (single-router pattern). |
| docs/deploy_appendix_azure_conductor.mdx | New appendix with complete example PCLI config for the Azure conductor + router. |
| docs/_deploy_azure_conductor_network_design.md | New partial defining consistent Azure conductor guide addressing/naming conventions. |
| docs/deploy_azure_hub_spoke_overview.mdx | New Azure hub/spoke router guide landing page with topology, prerequisites, and guide index. |
| docs/deploy_azure_hub_spoke_hub_vm.mdx | New Step 1 for deploying the hub router VM. |
| docs/deploy_azure_hub_spoke_spoke_vm.mdx | New Step 2 for deploying the spoke router VM. |
| docs/deploy_azure_hub_spoke_vmbus.mdx | New Step 3 for verifying install/onboarding and discovering VMBus UUID mappings. |
| docs/deploy_azure_hub_spoke_config.mdx | New Step 4 for conductor GUI configuration of hub/spoke tenants, interfaces, SVR peering, and routing. |
| docs/deploy_appendix_azure_hub_spoke.mdx | New appendix with complete example PCLI config for the hub/spoke topology. |
| docs/_deploy_azure_hub_spoke_network_design.md | New partial defining consistent hub/spoke guide addressing/naming conventions. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| - A VNet where the Conductor will be deployed (`SSR-VNet` in this guide). | ||
| - A subnet within that VNet reachable via SSH and HTTPS for administration (`ssr-conductor-subnet`). | ||
| - The subnet must be reachable from the WAN interface of every SSR router this conductor will manage. | ||
| - A **Managed Identity** assigned the following minimum read permissions: |
|
|
||
| 5. Launch the deployment: | ||
|
|
||
| ```bash |
|
|
||
| Launch the deployment: | ||
|
|
||
| ```bash |
|
|
||
| Launch the deployment: | ||
|
|
||
| ```bash |
|
|
||
| Launch the deployment: | ||
|
|
||
| ```bash |
|
|
||
| <NetworkDesign/> | ||
|
|
||
| ## Applying This Configuration |
There was a problem hiding this comment.
Is this config 100% the same as the conductor guide? It likely should be. As such, do you think it makes sense to duplicate it? Why not just point them to the conductor guide? This guide should follow best practices, which is to configure everything through the conductor.
| | Instance Size | `Standard_F8s_v2` | | | ||
| | Instance Name | `azure-router-1` | | | ||
| | SSR Version | `7.1.4` | | | ||
| | Artifactory Username | _(your username)_ | | |
There was a problem hiding this comment.
Artifactory -> SSN Cloud Software Repository
| | Instance Name | `azure-router-1` | | | ||
| | SSR Version | `7.1.4` | | | ||
| | Artifactory Username | _(your username)_ | | | ||
| | Artifactory Token | _(your token)_ | | |
There was a problem hiding this comment.
SSN Cloud Software Repository
| | Instance Size | `Standard_F8s_v2` | | | ||
| | Instance Name | `Conductor` | VM display name | | ||
| | SSR Version | `7.1.4` | The BYOL version to install | | ||
| | Artifactory Username | _(your username)_ | Juniper software access | |
There was a problem hiding this comment.
Artifactory -> SSN Cloud Software Repository
Please scrub all references.
| |-------|-------|-------| | ||
| | Type | `external` | | | ||
| | DHCP | `v4` | Azure assigns an IP via DHCP | | ||
| | Global-ID | `1` | | |
There was a problem hiding this comment.
Please double-check, but I don't believe this field should be edited by the user. It is automatically created for them. If so, please remove all references.
| | Standard_F32s_v2 | 8 | 32 | 64 GB | | ||
| | Standard_D8s_v5 | 4 | 8 | 32 GB | | ||
|
|
||
| For guidance on sizing for larger deployments, see [System Requirements](intro_system_reqs.md). |
There was a problem hiding this comment.
This table is inadequate for a customer to determine the resources needed for their deployment. If we are going to be providing this table, which we should, then we need to specify some dimensioning (e.g., number of users in the network) to serve as approximate guidelines for which instance type to choose.
No description provided.