Let's say this is true, I cannot deploy here because the the KVM is disabled, but there is no such think in my setup which is allowing to deploy systemvms only on KVM.
In order to avoid this, I just removed the KVM host from this setup, not sure why is trying to deploy the router on KVM over and over. - Restarted the network, the router deploy works fine, I can use the networks with tags in my test environment with 1 zone. (cloudstack 4.15.2) Now I have to figure out why the same configuration is not working in a different environment, the only difference is multiple zones and cloudstack version (cloudstack 4.15.1 only with VMware) Thank you, Cristian -----Original Message----- From: Wei ZHOU <ustcweiz...@gmail.com> Sent: Tuesday, October 12, 2021 4:01 PM To: users <users@cloudstack.apache.org> Subject: Re: Multiple Network labels - custom Hi Cristian, The configuration looks good. It looks like cloudstack cannot start the router because the router is allocated to be deployed on a KVM hypervisor but the only kvm host is disabled. so it is a capacity issue. -Wei On Tue, 12 Oct 2021 at 14:41, <cristian.c@istream.today> wrote: > Hi Wei, > > > > Yes, of course 😊 > > > > I'm able to create the network with any of the network offering, > which are with tags, the problem is when the router is starting to > deploy, I get the same error without to many details, tested in 2 > cloudstack environment > 4.15.1 and 4.15.2, in 1 I have multiple zones and in the test one I > have only 1 zone with 2 hosts KVM and VMware. > > > > For me is pretty simple: > > > > Zone X: > > > > 1 . Assign a tag to each physical network, for the default 1 and for > any additional network. > > 2. Create a network offering with the corresponding tags, I also saw > that you can update the tags for default network offering. > > 3. Create network with any of those offerings > > > > Here I attached screenshots : https://imgur.com/a/VtvYsvS I do not see > any issue in my configuration. > > > > Regards, > > Cristian > > > > -----Original Message----- > From: Wei ZHOU <ustcweiz...@gmail.com> > Sent: Tuesday, October 12, 2021 3:21 PM > To: users <users@cloudstack.apache.org> > Subject: Re: Multiple Network labels - custom > > > > Hi Cristian, > > > > I think it is good. You do not need to change the physical networks. > > > > Have you created a new "network offering" with a tag (A or B) ? > > > > -Wei > > > > On Tue, 12 Oct 2021 at 14:02, < <mailto:cristian.c@istream.today> > cristian.c@istream.today> wrote: > > > > > I have only 1 network by default : > > > > > > 1. Management / Storage / Public / Guest - Tag A > > > 2. Guest - Tag B > > > > > > Now, if I understand right, this is not working in this way? I > > should > > > have separated network for guest from the beginning? > > > > > > 1 . Management / Storage /Public - Tag A 2. Guest - Tag B 3. Guest > > - > > > Tag C > > > > > > > > > Regarding running networks, I will try to rebuild after I have the > > > current issue fixed. > > > > > > Zone, I think the same, but not sure yet.... > > > > > > Thank you, > > > Cristian > > > > > > > >
