Sorry Andrija, I did not explain it correctly. I was trying to create 2 public physical adapters so that I could create 2 different network offerings one for each.
My use case is being able to select "type" of public IP address. Imagine creating an Isolated network been able to select: IsolatedNetworkOfferingForPremiumFiberProvider IsolatedNetworkOfferingForBackupConnectivityProvider IsolatedNetworkOfferingForCompanyIntranet in each case the Virtual router would get an IP from different vlan_ip_range. Or being able to acquire an IP with ansible module: with tag: PremiumFiber or tag: BackupConnectivity. Non of the strategies do what I thought would be possible. The only strategy that seems viable is to pass on the knowledge of which IP is from where and use explicit IP acquisition. I guess the Company Intranet could be modelled differently (as a shared network on a well known VLAN?, or as an L2 Network...., not sure). Regards, Rafael On Fri, 2020-09-11 03:16 PM, Andrija Panic <andrija.pa...@gmail.com> wrote: > I'm not sure that I have got all your points (after a very quick read), but I can advise on the following: > " But Cloudstack complaints if I try to create 2 public networks on the same zone" > This is only true of they are overlapping - or having the same gateway, etc. Make sure to have each Public network on a separate VLAN (even though not required technically in the real world, it is required by ACS) That would allow you to run multiple Public network ranges > best, > > On Mon, 7 Sep 2020 at 10:31, Rafael del Valle <rva...@privaz.io.invalid> wrote: > > Hi! > > We have multiple public networks, and we would like to model them in ACS. > > We find references in the Documentation that seem to suggest it is possible: such as creating network offerings with a tag meant to identify the physical network. > > There are several use cases for which we want this: fail tolerance between different connectivity providers, creating instances/networks accessible from corporate network hosting ACS only, etc. > > Currently the public networks are on different VLANs, accessible trough the same network card (which ACS refers to as physical nets). > > I can see that the Physical Network has a TAG, and the docs seem to imply that a tag can be used to identify the public network. But Cloudstack complaints if I try to create 2 public networks on the same zone. > > The most intuitive solution would be to tag the vlan_ip_range and create network offerings that pick IPs with a given tag, but they don't seem to take tags. > > I can assign IPs from different providers to an account, and they can manually create network/VMs using them. But there seems to be no way to tell ACS that I want a VM/IP assignment on connectivity provider A/B, or use affinity rules, etc. > > How is this done with ACS? Is it possible? > > Rafael > > > > > > -- Andrija Panić
