RE: [VOTE][RESULT] Apache CloudStack 4.11.3.0

[Paul Angus]

Thanks everyone, we'll go with that option.

Cheers!

paul.an...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


-Original Message-
From: Will Stevens  
Sent: 24 June 2019 16:20
To: dev@cloudstack.apache.org
Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0

+1 for keeping 4.11.3.0 and rereleasing...

On Mon, Jun 24, 2019, 10:38 AM Gabriel Beims Bräscher 
wrote:

> +1 on keeping the release name as 4.11.3.0.
>
> Em seg, 24 de jun de 2019 às 11:27, Wei ZHOU 
> escreveu:
>
> > I vote for 4.11.3.0
> >
> > -Wei
> >
> >
> >
> > Paul Angus  于2019年6月24日周一 下午3:43写道：
> >
> > > Hi,
> > >
> > > Does anyone have any strong views on whether we should look to 
> > > nullify
> > > 4.11.3.0 as it was never in the wild, or should be go to 4.11.3.1 ?
> > >
> > > Many thanks
> > >
> > >
> > > Paul Angus
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > paul.an...@shapeblue.com
> > > www.shapeblue.com
> > > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
> > >
> > >
> > >
> > >
> > > -Original Message-
> > > From: Rohit Yadav 
> > > Sent: 24 June 2019 12:13
> > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> > > Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0
> > >
> > > Thanks for sharing Gregor. My/our bad, I was suspicious of how the
> > > templates were setup based on your emails and did not think what you
> > shared
> > > could be something to do with the DB upgrade path bug.
> > >
> > >
> > > Regards,
> > >
> > > Rohit Yadav
> > >
> > > Software Architect, ShapeBlue
> > >
> > > https://www.shapeblue.com
> > >
> > > 
> > > From: Riepl, Gregor (SWISS TXT) 
> > > Sent: Monday, June 24, 2019 3:23:23 PM
> > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> > > Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0
> > >
> > >
> > > > https://github.com/apache/cloudstack/pull/3417
> > > >
> > > >
> > > > The issue only affects 4.11.2.0 users for which the upgrade path does
> > > > not run (a noop upgrade path runs) and it does not automatically fix
> > > > any registered 4.11.3 systemvmtemplate to be used post-upgrade. I've
> > > > mentioned workaround steps on the PR.
> > >
> > > This sounds pretty much exactly like the issue we had...
> > >
> > >
> > >
> >
> https://lists.apache.org/thread.html/3a6ba604a77c944640cb159d7a55bda2c4646afa32bd494e3072e012@%3Cdev.cloudstack.apache.org%3E
> > >
> > >
> >
> https://lists.apache.org/thread.html/94d226e7cd832cda45c877db7f3d40c4802812da1a09b14ba63ccaf7@%3Cdev.cloudstack.apache.org%3E
> > >
> > >
> >
> https://lists.apache.org/thread.html/17d603ed695ce926ced124dc99cf41102f763e9dffc4e08259d74a44@%3Cusers.cloudstack.apache.org%3E
> > >
> > > rohit.ya...@shapeblue.com
> > > www.shapeblue.com
> > > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
> > >
> > >
> > >
> > >
> >
>

Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0

[Will Stevens]

+1 for keeping 4.11.3.0 and rereleasing...

On Mon, Jun 24, 2019, 10:38 AM Gabriel Beims Bräscher 
wrote:

> +1 on keeping the release name as 4.11.3.0.
>
> Em seg, 24 de jun de 2019 às 11:27, Wei ZHOU 
> escreveu:
>
> > I vote for 4.11.3.0
> >
> > -Wei
> >
> >
> >
> > Paul Angus  于2019年6月24日周一 下午3:43写道：
> >
> > > Hi,
> > >
> > > Does anyone have any strong views on whether we should look to nullify
> > > 4.11.3.0 as it was never in the wild, or should be go to 4.11.3.1 ?
> > >
> > > Many thanks
> > >
> > >
> > > Paul Angus
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > paul.an...@shapeblue.com
> > > www.shapeblue.com
> > > Amadeus House, Floral Street, London  WC2E 9DPUK
> > > @shapeblue
> > >
> > >
> > >
> > >
> > > -Original Message-
> > > From: Rohit Yadav 
> > > Sent: 24 June 2019 12:13
> > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> > > Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0
> > >
> > > Thanks for sharing Gregor. My/our bad, I was suspicious of how the
> > > templates were setup based on your emails and did not think what you
> > shared
> > > could be something to do with the DB upgrade path bug.
> > >
> > >
> > > Regards,
> > >
> > > Rohit Yadav
> > >
> > > Software Architect, ShapeBlue
> > >
> > > https://www.shapeblue.com
> > >
> > > 
> > > From: Riepl, Gregor (SWISS TXT) 
> > > Sent: Monday, June 24, 2019 3:23:23 PM
> > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> > > Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0
> > >
> > >
> > > > https://github.com/apache/cloudstack/pull/3417
> > > >
> > > >
> > > > The issue only affects 4.11.2.0 users for which the upgrade path does
> > > > not run (a noop upgrade path runs) and it does not automatically fix
> > > > any registered 4.11.3 systemvmtemplate to be used post-upgrade. I've
> > > > mentioned workaround steps on the PR.
> > >
> > > This sounds pretty much exactly like the issue we had...
> > >
> > >
> > >
> >
> https://lists.apache.org/thread.html/3a6ba604a77c944640cb159d7a55bda2c4646afa32bd494e3072e012@%3Cdev.cloudstack.apache.org%3E
> > >
> > >
> >
> https://lists.apache.org/thread.html/94d226e7cd832cda45c877db7f3d40c4802812da1a09b14ba63ccaf7@%3Cdev.cloudstack.apache.org%3E
> > >
> > >
> >
> https://lists.apache.org/thread.html/17d603ed695ce926ced124dc99cf41102f763e9dffc4e08259d74a44@%3Cusers.cloudstack.apache.org%3E
> > >
> > > rohit.ya...@shapeblue.com
> > > www.shapeblue.com
> > > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
> > >
> > >
> > >
> > >
> >
>

Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0

[Gabriel Beims Bräscher]

+1 on keeping the release name as 4.11.3.0.

Em seg, 24 de jun de 2019 às 11:27, Wei ZHOU 
escreveu:

> I vote for 4.11.3.0
>
> -Wei
>
>
>
> Paul Angus  于2019年6月24日周一 下午3:43写道：
>
> > Hi,
> >
> > Does anyone have any strong views on whether we should look to nullify
> > 4.11.3.0 as it was never in the wild, or should be go to 4.11.3.1 ?
> >
> > Many thanks
> >
> >
> > Paul Angus
> >
> >
> >
> >
> >
> >
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Rohit Yadav 
> > Sent: 24 June 2019 12:13
> > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> > Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0
> >
> > Thanks for sharing Gregor. My/our bad, I was suspicious of how the
> > templates were setup based on your emails and did not think what you
> shared
> > could be something to do with the DB upgrade path bug.
> >
> >
> > Regards,
> >
> > Rohit Yadav
> >
> > Software Architect, ShapeBlue
> >
> > https://www.shapeblue.com
> >
> > 
> > From: Riepl, Gregor (SWISS TXT) 
> > Sent: Monday, June 24, 2019 3:23:23 PM
> > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> > Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0
> >
> >
> > > https://github.com/apache/cloudstack/pull/3417
> > >
> > >
> > > The issue only affects 4.11.2.0 users for which the upgrade path does
> > > not run (a noop upgrade path runs) and it does not automatically fix
> > > any registered 4.11.3 systemvmtemplate to be used post-upgrade. I've
> > > mentioned workaround steps on the PR.
> >
> > This sounds pretty much exactly like the issue we had...
> >
> >
> >
> https://lists.apache.org/thread.html/3a6ba604a77c944640cb159d7a55bda2c4646afa32bd494e3072e012@%3Cdev.cloudstack.apache.org%3E
> >
> >
> https://lists.apache.org/thread.html/94d226e7cd832cda45c877db7f3d40c4802812da1a09b14ba63ccaf7@%3Cdev.cloudstack.apache.org%3E
> >
> >
> https://lists.apache.org/thread.html/17d603ed695ce926ced124dc99cf41102f763e9dffc4e08259d74a44@%3Cusers.cloudstack.apache.org%3E
> >
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
> >
> >
> >
> >
>

Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0

[Wei ZHOU]

I vote for 4.11.3.0

-Wei



Paul Angus  于2019年6月24日周一 下午3:43写道：

> Hi,
>
> Does anyone have any strong views on whether we should look to nullify
> 4.11.3.0 as it was never in the wild, or should be go to 4.11.3.1 ?
>
> Many thanks
>
>
> Paul Angus
>
>
>
>
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Rohit Yadav 
> Sent: 24 June 2019 12:13
> To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0
>
> Thanks for sharing Gregor. My/our bad, I was suspicious of how the
> templates were setup based on your emails and did not think what you shared
> could be something to do with the DB upgrade path bug.
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> 
> From: Riepl, Gregor (SWISS TXT) 
> Sent: Monday, June 24, 2019 3:23:23 PM
> To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0
>
>
> > https://github.com/apache/cloudstack/pull/3417
> >
> >
> > The issue only affects 4.11.2.0 users for which the upgrade path does
> > not run (a noop upgrade path runs) and it does not automatically fix
> > any registered 4.11.3 systemvmtemplate to be used post-upgrade. I've
> > mentioned workaround steps on the PR.
>
> This sounds pretty much exactly like the issue we had...
>
>
> https://lists.apache.org/thread.html/3a6ba604a77c944640cb159d7a55bda2c4646afa32bd494e3072e012@%3Cdev.cloudstack.apache.org%3E
>
> https://lists.apache.org/thread.html/94d226e7cd832cda45c877db7f3d40c4802812da1a09b14ba63ccaf7@%3Cdev.cloudstack.apache.org%3E
>
> https://lists.apache.org/thread.html/17d603ed695ce926ced124dc99cf41102f763e9dffc4e08259d74a44@%3Cusers.cloudstack.apache.org%3E
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>
>
>
>

Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0

[Daan Hoogland]

Paul, a commitsgh has been published and could be used from just that mail.
I would go for a new release name. Whether that is 4.11.3.1 or something
else is of little consequence. (€0.02)

On Mon, Jun 24, 2019 at 3:43 PM Paul Angus  wrote:

> Hi,
>
> Does anyone have any strong views on whether we should look to nullify
> 4.11.3.0 as it was never in the wild, or should be go to 4.11.3.1 ?
>
> Many thanks
>
>
> Paul Angus
>
>
>
>
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Rohit Yadav 
> Sent: 24 June 2019 12:13
> To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0
>
> Thanks for sharing Gregor. My/our bad, I was suspicious of how the
> templates were setup based on your emails and did not think what you shared
> could be something to do with the DB upgrade path bug.
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> 
> From: Riepl, Gregor (SWISS TXT) 
> Sent: Monday, June 24, 2019 3:23:23 PM
> To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0
>
>
> > https://github.com/apache/cloudstack/pull/3417
> >
> >
> > The issue only affects 4.11.2.0 users for which the upgrade path does
> > not run (a noop upgrade path runs) and it does not automatically fix
> > any registered 4.11.3 systemvmtemplate to be used post-upgrade. I've
> > mentioned workaround steps on the PR.
>
> This sounds pretty much exactly like the issue we had...
>
>
> https://lists.apache.org/thread.html/3a6ba604a77c944640cb159d7a55bda2c4646afa32bd494e3072e012@%3Cdev.cloudstack.apache.org%3E
>
> https://lists.apache.org/thread.html/94d226e7cd832cda45c877db7f3d40c4802812da1a09b14ba63ccaf7@%3Cdev.cloudstack.apache.org%3E
>
> https://lists.apache.org/thread.html/17d603ed695ce926ced124dc99cf41102f763e9dffc4e08259d74a44@%3Cusers.cloudstack.apache.org%3E
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>
>
>
>

-- 
Daan

RE: [VOTE][RESULT] Apache CloudStack 4.11.3.0

[Paul Angus]

Hi,

Does anyone have any strong views on whether we should look to nullify 4.11.3.0 
as it was never in the wild, or should be go to 4.11.3.1 ?

Many thanks


Paul Angus







paul.an...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


-Original Message-
From: Rohit Yadav  
Sent: 24 June 2019 12:13
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0

Thanks for sharing Gregor. My/our bad, I was suspicious of how the templates 
were setup based on your emails and did not think what you shared could be 
something to do with the DB upgrade path bug.


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Riepl, Gregor (SWISS TXT) 
Sent: Monday, June 24, 2019 3:23:23 PM
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0


> https://github.com/apache/cloudstack/pull/3417
>
>
> The issue only affects 4.11.2.0 users for which the upgrade path does 
> not run (a noop upgrade path runs) and it does not automatically fix 
> any registered 4.11.3 systemvmtemplate to be used post-upgrade. I've 
> mentioned workaround steps on the PR.

This sounds pretty much exactly like the issue we had...

https://lists.apache.org/thread.html/3a6ba604a77c944640cb159d7a55bda2c4646afa32bd494e3072e012@%3Cdev.cloudstack.apache.org%3E
https://lists.apache.org/thread.html/94d226e7cd832cda45c877db7f3d40c4802812da1a09b14ba63ccaf7@%3Cdev.cloudstack.apache.org%3E
https://lists.apache.org/thread.html/17d603ed695ce926ced124dc99cf41102f763e9dffc4e08259d74a44@%3Cusers.cloudstack.apache.org%3E

rohit.ya...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
  
 

Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0

[Rohit Yadav]

Thanks for sharing Gregor. My/our bad, I was suspicious of how the templates 
were setup based on your emails and did not think what you shared could be 
something to do with the DB upgrade path bug.


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Riepl, Gregor (SWISS TXT) 
Sent: Monday, June 24, 2019 3:23:23 PM
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0


> https://github.com/apache/cloudstack/pull/3417
>
>
> The issue only affects 4.11.2.0 users for which the upgrade path does
> not run (a noop upgrade path runs) and it does not automatically fix
> any registered 4.11.3 systemvmtemplate to be used post-upgrade. I've
> mentioned workaround steps on the PR.

This sounds pretty much exactly like the issue we had...

https://lists.apache.org/thread.html/3a6ba604a77c944640cb159d7a55bda2c4646afa32bd494e3072e012@%3Cdev.cloudstack.apache.org%3E
https://lists.apache.org/thread.html/94d226e7cd832cda45c877db7f3d40c4802812da1a09b14ba63ccaf7@%3Cdev.cloudstack.apache.org%3E
https://lists.apache.org/thread.html/17d603ed695ce926ced124dc99cf41102f763e9dffc4e08259d74a44@%3Cusers.cloudstack.apache.org%3E

rohit.ya...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0

[Riepl, Gregor (SWISS TXT)]

> https://github.com/apache/cloudstack/pull/3417
> 
> 
> The issue only affects 4.11.2.0 users for which the upgrade path does
> not run (a noop upgrade path runs) and it does not automatically fix
> any registered 4.11.3 systemvmtemplate to be used post-upgrade. I've
> mentioned workaround steps on the PR.

This sounds pretty much exactly like the issue we had...

https://lists.apache.org/thread.html/3a6ba604a77c944640cb159d7a55bda2c4646afa32bd494e3072e012@%3Cdev.cloudstack.apache.org%3E
https://lists.apache.org/thread.html/94d226e7cd832cda45c877db7f3d40c4802812da1a09b14ba63ccaf7@%3Cdev.cloudstack.apache.org%3E
https://lists.apache.org/thread.html/17d603ed695ce926ced124dc99cf41102f763e9dffc4e08259d74a44@%3Cusers.cloudstack.apache.org%3E

Is there any way to create VM with multiple GPUs ?

[Haijiao]

Hi,  Community 


We have a environment with XenServer 7.1LTS + ACS 4.11.2,  some hosts has 
multiple Nividia P4 graphic cards installed. 


Per business requirement,  we need provision VM with passthrough GPUs.  We 
expect to provide users various offerings,  e.g.  1GPU/VM,   2GPU/VM... but it 
seems ACS currently only support 1GPU/VM by default. 


Is there any way we can specifiy the number of GPUs during VM creation ?   I 
guess we may leverage XenServer CLI to do that,  but would be much more 
consistent and efficient if we are allowed to make it happen via ACS. 


Thanks !

Re: KVM HA fails under multiple management services

[Andrija Panic]

Li,

please test with  Indirect.agent.lb.check.interval=60 or similar, not 0
(zero), since that means it won't reconnect - this should solve your
concern.

As for the what is in what rack, it is your responsibility to disperse
infrastructure components appropriately, i.e. across racks and such.
We can't handle every case in that regards, hope you understand

Andrija

On Mon, 24 Jun 2019 at 02:24, li jerry  wrote:

> Thank you Nicolas and Andrija.
>
> Even if indirect.agent.lb.algorithm is configured as roundrobin, the
> probability of failure can only be reduced. But it does not solve 100% of
> the failure of KVM HA;
>
> Because in extreme cases, the management server and the kvm host may fail
> at the same time (for example, the management server and the KVM HOST are
> placed in the same rack, and the RACK will fail at the same time after the
> power failure)
>
>
> E.g;
>
> H1 is assigned and connected to M2
> H2 is assigned and connected to M3
> H3 is assigned and connected to M1
>
> When H1 and M2 fail simultaneously, HOST HA of H1 will be invalid;
>
> Should we have other protection mechanisms to avoid this?
>
> 发件人: Nicolas Vazquez
> 发送时间: 2019年6月23日 23:31
> 收件人: dev@cloudstack.apache.org;
> users
> 抄送: dev@cloudstack.apache.org
> 主题: Re: KVM HA fails under multiple management services
>
> As Andrija mentioned that is expected behavior as the global setting is
> 'static'. It is also expected that your agents connect to the next
> management server on the 'host' list once the management server they are
> connected to is down.
> You can find more information of this feature on this link:
> https://www.shapeblue.com/software-based-agent-lb-for-cloudstack/
>
> Please note this is a different feature than host HA, in which CloudStack
> will try to recover hosts which are off via ipmi
>
> Obtener Outlook para Android
>
>
>
> De: Andrija Panic
> Enviado: domingo, 23 de junio 11:03
> Asunto: Re: KVM HA fails under multiple management services
> Para: users
> Cc: dev@cloudstack.apache.org
>
>
> Li,
>
> based on the Global Setting description for those 2, I would say that is
> the expected behaviour.
> i.e. change Indirect.agent.lb.check.interval to some other value, since 0
> means "don't check, don't reconnect" per what I read.
>
> Also, you might want to change from  Indirect.agent.lb.algorithm=static to
> some other value, since static means all your KVM agents will always
> connect to that one mgmt host that is the first one in the in the "host"
> list.
>
> Regards,
> Andrija
>
>
> nicolas.vazq...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
> On Sat, 22 Jun 2019 at 06:19, li jerry  wrote:
>
> >
> > Hello everyone
> > I recently tested the multiple management services, based on agent lb
> HOST
> > HA (KVM). It was found that in extreme cases, HA would fail; the details
> > are as follows:
> >
> >
> > Two management nodes, M1 (172.17.1.141) and M2 (172.17.1.142), share an
> > external database cluster
> > Three KVM nodes, H1, H2, H3
> > An external NFS primary storage
> >
> >
> > CLOUDSTACK parameter configuration
> > Indirect.agent.lb.algorithm=static
> > Indirect.agent.lb.check.interval=0
> > host=172.17.1.141,172.17.1.142
> >
> >
> > Through the agent.log analysis, all kvm agents are connected to the first
> > selection management node M1 (172.17.1.141):
> >
> > INFO [cloud.agent.Agent] (agentRequest-Handler-1:null) (logid:b30323e4)
> > Processed new management server list: 172.17.1.141,172.17.1.142@static
> >
> >
> >
> > In extreme cases:
> > KVM HOST and the preferred management server fail at the same time, KVM
> > HOST will not trigger HA detection
> >
> > E.g:
> >
> > M1+H1, power off at the same time; the state of H1 remains Disconnected,
> > and all VMs on H1 will not restart on other KVM nodes;
> > M1+H2, power off at the same time; the state of H1 remains Disconnected,
> > and all VMs on H2 will not restart on other KVM nodes;
> > M1+H3, power off at the same time; the state of H1 remains Disconnected,
> > and all VMs on H3 will not restart on other KVM nodes;
> >
>
>
> --
>
> Andrija Panić
>
>
>

-- 

Andrija Panić

Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0

[Rohit Yadav]

Thanks Paul, however, I've found a bug in 4.11.3.0 packages that I could only 
find while upgrading my local ci-test env:


https://github.com/apache/cloudstack/pull/3417


The issue only affects 4.11.2.0 users for which the upgrade path does not run 
(a noop upgrade path runs) and it does not automatically fix any registered 
4.11.3 systemvmtemplate to be used post-upgrade. I've mentioned workaround 
steps on the PR.


Given the release/tag is not announced, not the release/upgrade notes and nor 
the packages available in the wild yet. I request to recall RC1 and cut 
4.11.3.0 RC2 after merging the above PR on 4.11 (it also reverts the 
4.11.4.0-SNAPSHOT renaming). I'm also fine if we want to do a 4.11.3.1 instead.


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Paul Angus 
Sent: Saturday, June 22, 2019 1:02:23 AM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: [VOTE][RESULT] Apache CloudStack 4.11.3.0

Hi everyone,

After more than 72hrs the vote for CloudStack 4.11.3.0 *passes* with
3 PMC + 1 non-PMC votes.

+1 (PMC / binding)
Rohit Yadav
Milamber (Bruno Demion)
Nux (Lucian)

+1 (non binding)
Gregor Riepl

0
none

-1
none

Thanks to everyone participating.

I will now prepare the release announcement to go out after 24 hours to give 
the mirrors time to catch up.







paul.an...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue




rohit.ya...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


-Original Message-
From: Nux! 
Sent: 20 June 2019 09:35
To: dev 
Subject: Re: [VOTE] 4.11.3.0 RC1

+1 (binding)

KVM, CentOS7, local storage.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Milamber" 
> To: "dev" 
> Sent: Wednesday, 19 June, 2019 22:35:50
> Subject: Re: [VOTE] 4.11.3.0 RC1

> Hello,
>
> +1 (binding)
>
>
> Tested on KVM + NFS installation
>
>
> Milamber
>
> On 11/06/2019 10:57, Paul Angus wrote:
>> Hi All,
>>
>> I've created a 4.11.3.0 release (RC1), with the following artefacts
>> up for testing and a vote:
>>
>>
>> Git Branch and Commit SH:
>> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=ref
>> s/heads/4.11.3.0-RC20190610T1615
>> Commit: 51124b7b35f47089b2e51a93b2094ea93dd15302
>>
>> Source release (checksums and signatures are available at the same
>> location):
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.11.3.0/
>>
>> PGP release keys (signed using 51EE0BC8):
>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>
>> The vote will be open until end of 16 June 2019.
>>
>> For sanity in tallying the vote, can PMC members please be sure to
>> indicate "(binding)" with their vote?
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>> Additional information:
>>
>> For users' convenience, I've built packages from
>> 51124b7b35f47089b2e51a93b2094ea93dd15302 and published RC1 repository here:
>> http://packages.shapeblue.com/testing/41130rc1/
>>
>> The release notes are still work-in-progress, but the systemvm
>> template upgrade section has been updated. You may refer the
>> following for systemvm template upgrade testing:
>> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/e
>> n/latest/index.html
>>
>> 4.11.3.0 systemvm templates are available from here:
>> http://packages.shapeblue.com/testing/systemvm/41130rc1/
>>
>>
>>
>> PRs in 4.11.3.0:
>> +==+
>>
>> +-+--++
>> | Version | Github   | Description
>> | |
>> +=+==+===
>> +=+
>> | 4.11.3.0| `#3381`_ | schema: add 4.11.2 to 4.11.3
>> | systemvmtemplate upgrade path |
>> +-+--++
>> | 4.11.3.0| `#3075`_ | KVM: Prevent regenerating keystore on
>> | provisionCertificate |
>> | |  | API   
>>  |
>> +-+--++
>> | 4.11.3.0| `#3373`_ | router: support multi-homed VMs in VPC
>> | |
>> +-+--++
>> | 4.11.3.0| `#3366`_ | Fix rule duplication with static NAT 
>> rules
>> | |
>> +-+--++
>> | 4.11.3.0| `#3194`_ | Suspending a VM before snapshot 
>> deletion
>> | (see PR #3193)|
>>