MAAS global deployment Supported Model - Question

Users
,
#1

Hello,
I have a single maas region control server in a central location behind a firewall.
I then have a rack control server at site 1 on public IP forwarded to private IP 192.168.1.101 and everything is working fine.

I now need to deploy a second site (in fact many sites globally dispersed) with exactly identical IP config as the first site:
Site 1 public IP forward to private IP 192.168.1.101
Site 2 public IP forward to private IP 192.168.1.101

So my question is 1, is this supported?

  • and -
    2 if it is supported, please point me in the direction of some reference material regarding how to make this config?

I have already tested this config and I am having fabric, subnet, and vlan issues.

Ultimately if looks like maas rack install 192.168.1.101 fine I can see both in the region dashboard but the subnet is where is gets messy.

Appreciate any help!
MAAS SNAP Version 3

1 Like
#2

Hi,
MAAS currently assumes that subnets are globally unique, so if you have two subnets in different locations with the same CIDR, MAAS will think they’re the same.
This could lead to issues as racks will assume they can talk to any host on the same subnet.

#3

Thanks for the reply, I really appreciate it.

Not the news I was hoping for but not your fault.

Are there any future plans to create “isolation groups” or “site boundaries” to allow for the same private IP CIDR settings at each site?

We have a global footprint rolling out and each site has exactly the same private IP ranges. the only difference is the public IP (gateway) on a /30 or /32 with a NAT.

Thanks!

#4

@t-n-f, the MAAS team has a features forum. i don’t think they actively scan this forum for actual features. could you repost this over there?