Skip to content
This repository has been archived by the owner on Jul 26, 2024. It is now read-only.

[feature] New landing_zone for networking using hub spoke with Azure Virtual WAN #41

Closed
arnaudlh opened this issue May 19, 2020 · 1 comment · Fixed by #49
Closed

[feature] New landing_zone for networking using hub spoke with Azure Virtual WAN #41

arnaudlh opened this issue May 19, 2020 · 1 comment · Fixed by #49
Assignees
Labels
Milestone

Comments

@arnaudlh
Copy link
Member

arnaudlh commented May 19, 2020

Proposal

Create a model for Azure to deploy a regional hub and spoke model using Azure Virtual WAN using architecture as described here: https://docs.microsoft.com/en-us/azure/virtual-wan/virtual-wan-about.

This landing zone should allow you to easily create a Virtual WAN (Standard SKU) environment as well as flexible structure to onboard new HUB iteratively with its associated features:

Pseudo code

Pseudo code for variable structure:

virtual_hub_config = {
  virtual_wan = {
    resource_group_name = "virtualwan-ns"
    name                = "ContosovWAN"
    dns_name            = "private.contoso.com"

    hubs = {
      hub1 = {
        hub_name           = "SEA-HUB"
        region             = "southeastasia"
        hub_address_prefix = "10.0.3.0/24"
        deploy_firewall    = true
        firewall_name      = "azfwvhub-sea"
        peerings = {     
          spoke1 = {
            hub_to_vitual_network_traffic_allowed          = true
            vitual_network_to_hub_gateways_traffic_allowed = true
            internet_security_enabled                      = false
          }
        }

        deploy_p2s = true
        p2s_config = { #config details }
        deploy_s2s = false
        s2s_config = { #config details }
        deploy_er  = false
        er_config  = { #config details }

Provisionning a new hub done with declaring another hub structure in the hubs object.

@arnaudlh arnaudlh added the enhancement New feature or request label May 19, 2020
@arnaudlh arnaudlh self-assigned this Jun 17, 2020
@arnaudlh arnaudlh added epic and removed enhancement New feature or request labels Jun 17, 2020
@arnaudlh arnaudlh added this to the 2006 milestone Jun 17, 2020
@arnaudlh
Copy link
Member Author

@arnaudlh arnaudlh linked a pull request Jul 1, 2020 that will close this issue
@arnaudlh arnaudlh mentioned this issue Jul 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant