Not 4.11.3.  porting the changes is in progress to 4.11.2 in our company

Sent from my iPhone

> On 03-Apr-2019, at 5:26 PM, Nux! <n...@li.nux.ro> wrote:
> 
> Hi Wei,
> 
> 4.11.3 you mean? 4.11.2 is already released.
> 
> Anyway, last I tried, a couple of years back, this was not supported at all, 
> hence me getting my hopes up.
> You could add multiple networks, but the VM had to connect only in 1 at any 
> given time.
> Looking forward to your port.
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> ----- Original Message -----
>> From: "Wei ZHOU" <ustcweiz...@gmail.com>
>> To: "dev" <dev@cloudstack.apache.org>
>> Sent: Wednesday, 3 April, 2019 15:51:49
>> Subject: Re: Multiple networks support in SG zone - half baked?
> 
>> Was it supported before ? I do not think so.
>> 
>> We have made some changes to support it in cloudstack 4.7.1. We are going
>> to port our changes to cloudstack 4.11.2 LTS.
>> 
>> -Wei
>> 
>> Nux! <n...@li.nux.ro> 于2019年4月3日周三 下午4:47写道:
>> 
>>> Hi,
>>> 
>>> (ACS 4.11.2, KVM)
>>> 
>>> I noticed (with enthusiasm) that I can now add a second network to a VM in
>>> Adv + SG zones.[1]
>>> I then noticed (with less enthusiasm) that while indeed a new NIC into the
>>> said network is added, Security Groups for it are not set up at all, i.e.
>>> DHCP is broken.
>>> 
>>> Can anyone shed some light on this feature, where it's going and so on?
>>> 
>>> I would have killed for this feature a few years back and it was one of
>>> the reasons we failed to adopt Cloudstack properly, as we require a
>>> secondary network for private/backup usage.
>>> 
>>> Also noticed "Add L2 network" button, but gives an error[2], so I reckon
>>> it can't be used.
>>> 
>>> Are things any better in 4.12? With improved IPv6 support I am already
>>> considering to ditch the LTS for it.
>>> 
>>> 
>>> [1] http://tmp.nux.ro/J4M-Selection_058.png
>>> [2] http://tmp.nux.ro/Mx9-Selection_059.png
>>> 
>>> --
>>> Sent from the Delta quadrant using Borg technology!
>>> 
>>> Nux!
>>> www.nux.ro

Reply via email to