search

edgexr / edge-cloud-platform

Apache License 2.0
1 stars 0 forks source link

Consolidate external network configuration during cloudlet creation #337

Open levshvarts opened 5 months ago

levshvarts commented 5 months ago

We have a common way of specifying external network, which can be set with external_network_name. However crm only looks at VMProviderProps env vars for the network to be used in the creation of rootLB VMs(including shared VM). The result of this is that if only external_network_name is set, only the platform VM will be created with the correct network, but the sharedLB VM will be created with the default external-network-shared network, which is the default. This can lead to the confusing results as well as make the crm incapable to communicate with the rootLBs, if the networks are prevented to directly communicated.

Was this the original intent, or is this a bug? In any case, we should make sure both the platform VM and rootLB instances are created on the same network.

gainsley commented 2 months ago

I remember we did have a case where one Operator wanted the CRM on a separate protected network (control plane) from the rest of the VMs (data plane) and the CRM was behind some kind of NAT/firewall. I don't remember the specifics. But if that were the case here, the variable names here should have reflected that, which they don't. So not sure either what's going on here.