Re: [VOTE] Apache CloudStack 4.15.1.0 (RC2)

[Rohit Yadav]

I think the issue cannot be classified as blocker as it's specific to just UI, 
a user may still use the API for the specific case where offering has root 
disk. There are some other issues reported like this as well.

RC3 may not be strictly necessary but I'm willing to cut it, but let's do it on 
Monday. Let's keep testing, reporting bugs until then.

Regards.

Regards,
Rohit Yadav


From: Gabriel Bräscher 
Sent: Thursday, June 24, 2021 3:52:43 AM
To: dev 
Cc: users@cloudstack.apache.org 
Subject: Re: [VOTE] Apache CloudStack 4.15.1.0 (RC2)

I hate to bring bad news, but I found an issue caused by PR #5085 [1].

The issue affects only VM deployment via UI when using an offering that has
root disk size.
I've just opened PR #5150 [2]; tested it and this fixes the issue.
Sorry for the inconvenience but this might require a third round. What do
you think?

The good news: all raised issues on RC1 have been correctly addressed and
RC2 works as expected.
Apart from the issue raised in #5150, all tests look good.

[1] https://github.com/apache/cloudstack/pull/5085
[2] https://github.com/apache/cloudstack/pull/5150

Regards,
Gabriel.

Em qua., 23 de jun. de 2021 às 09:45, Abhishek Kumar <
abhishek.ku...@shapeblue.com> escreveu:

> +1
>
> Did some manual tests with RC2 packages deploying a new environment.
>
> (Advanced zone with 2x XCP-ng 8.2 hosts, 2x NFS storage pools)
>
>   *   VM - deploy, stop-start, reset, migrate, expunge
>   *   Volumes - attach, detach, migrate
>   *   Templates - register, delete
>   *   Network - restart, cleanup
>   *   k8s cluster - start, upgrade, destroy
>   *   Hosts - maintenance, enable-disable
>   *   SystemVMs - destroy, migrate
>   *   Some basic UI - accounts, domains, offerings, config, etc
>
> Regards,
> Abhishek
>
> 
> From: Rohit Yadav 
> Sent: 16 June 2021 21:57
> To: d...@cloudstack.apache.org ;
> users@cloudstack.apache.org 
> Subject: [VOTE] Apache CloudStack 4.15.1.0 (RC2)
>
> Hi All,
>
> I've created a 4.15.1.0 release, with the following artifacts up for a
> vote:
>
> Git Branch:
> https://github.com/apache/cloudstack/tree/4.15.1.0-RC20210616T2128
> Commit SHA:
> 3afd37022b9dac52cd146dccada6012e47a80232
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.15.1.0/
>
> PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> The vote will be open for the next week until 22 June 2021.
>
> 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)
>
> For users convenience, the packages from this release candidate and 4.15.1
> systemvmtemplates are available here:
> https://download.cloudstack.org/testing/4.15.1.0-RC2/
> https://download.cloudstack.org/systemvm/4.15/
>
> Documentation is not published yet, but the following may be referenced for
> upgrade related tests: (there's a new 4.15.1 systemvmtemplate to be
> registered prior to upgrade)
>
> https://github.com/apache/cloudstack-documentation/tree/4.15/source/upgrading/upgrade
>
> Regards.
>
>
>
>

 

Re: [VOTE] Apache CloudStack 4.15.1.0 (RC2)

[Gabriel Bräscher]

I hate to bring bad news, but I found an issue caused by PR #5085 [1].

The issue affects only VM deployment via UI when using an offering that has
root disk size.
I've just opened PR #5150 [2]; tested it and this fixes the issue.
Sorry for the inconvenience but this might require a third round. What do
you think?

The good news: all raised issues on RC1 have been correctly addressed and
RC2 works as expected.
Apart from the issue raised in #5150, all tests look good.

[1] https://github.com/apache/cloudstack/pull/5085
[2] https://github.com/apache/cloudstack/pull/5150

Regards,
Gabriel.

Em qua., 23 de jun. de 2021 às 09:45, Abhishek Kumar <
abhishek.ku...@shapeblue.com> escreveu:

> +1
>
> Did some manual tests with RC2 packages deploying a new environment.
>
> (Advanced zone with 2x XCP-ng 8.2 hosts, 2x NFS storage pools)
>
>   *   VM - deploy, stop-start, reset, migrate, expunge
>   *   Volumes - attach, detach, migrate
>   *   Templates - register, delete
>   *   Network - restart, cleanup
>   *   k8s cluster - start, upgrade, destroy
>   *   Hosts - maintenance, enable-disable
>   *   SystemVMs - destroy, migrate
>   *   Some basic UI - accounts, domains, offerings, config, etc
>
> Regards,
> Abhishek
>
> 
> From: Rohit Yadav 
> Sent: 16 June 2021 21:57
> To: d...@cloudstack.apache.org ;
> users@cloudstack.apache.org 
> Subject: [VOTE] Apache CloudStack 4.15.1.0 (RC2)
>
> Hi All,
>
> I've created a 4.15.1.0 release, with the following artifacts up for a
> vote:
>
> Git Branch:
> https://github.com/apache/cloudstack/tree/4.15.1.0-RC20210616T2128
> Commit SHA:
> 3afd37022b9dac52cd146dccada6012e47a80232
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.15.1.0/
>
> PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> The vote will be open for the next week until 22 June 2021.
>
> 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)
>
> For users convenience, the packages from this release candidate and 4.15.1
> systemvmtemplates are available here:
> https://download.cloudstack.org/testing/4.15.1.0-RC2/
> https://download.cloudstack.org/systemvm/4.15/
>
> Documentation is not published yet, but the following may be referenced for
> upgrade related tests: (there's a new 4.15.1 systemvmtemplate to be
> registered prior to upgrade)
>
> https://github.com/apache/cloudstack-documentation/tree/4.15/source/upgrading/upgrade
>
> Regards.
>
>
>
>

[PROPOSE] RM for 4.16

[Nicolas Vazquez]

Dear All,

I’d like to put myself forward as the release manager for 4.16.0.0 and my 
colleagues Suresh Anaparti and Rohit Yadav as the co-RMs.

For 4.16.0.0 my colleague Suresh will assist me during the process for 
reviewing/testing/merging the PRs, others will be welcome to support as well.

I propose we have a window of at least 8 weeks (2 months) to allow community 
and users to test and report issues and aim to cut RC1 in Q3 2021 (September or 
onwards). I'll propose timeline and details by the end of July.

I hope to have your support. Any thoughts, feedback, comments? Thanks.


Regards,

Nicolas Vazquez

 

Re: [VOTE] Apache CloudStack 4.15.1.0 (RC2)

[Abhishek Kumar]

+1

Did some manual tests with RC2 packages deploying a new environment.

(Advanced zone with 2x XCP-ng 8.2 hosts, 2x NFS storage pools)

  *   VM - deploy, stop-start, reset, migrate, expunge
  *   Volumes - attach, detach, migrate
  *   Templates - register, delete
  *   Network - restart, cleanup
  *   k8s cluster - start, upgrade, destroy
  *   Hosts - maintenance, enable-disable
  *   SystemVMs - destroy, migrate
  *   Some basic UI - accounts, domains, offerings, config, etc

Regards,
Abhishek


From: Rohit Yadav 
Sent: 16 June 2021 21:57
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: [VOTE] Apache CloudStack 4.15.1.0 (RC2)

Hi All,

I've created a 4.15.1.0 release, with the following artifacts up for a vote:

Git Branch:
https://github.com/apache/cloudstack/tree/4.15.1.0-RC20210616T2128
Commit SHA:
3afd37022b9dac52cd146dccada6012e47a80232

Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.15.1.0/

PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open for the next week until 22 June 2021.

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)

For users convenience, the packages from this release candidate and 4.15.1
systemvmtemplates are available here:
https://download.cloudstack.org/testing/4.15.1.0-RC2/
https://download.cloudstack.org/systemvm/4.15/

Documentation is not published yet, but the following may be referenced for
upgrade related tests: (there's a new 4.15.1 systemvmtemplate to be
registered prior to upgrade)
https://github.com/apache/cloudstack-documentation/tree/4.15/source/upgrading/upgrade

Regards.

 

Re: [DISCUSS] Rocky 8.4 and CloudStack

[Sven Vogel]

Maybe Rocky is a good replacement for CentOS. We will see. We dont
have so much choices. For me its important to support the Commercial
RHEL one besides the Community.


Thanks and 



Cheers,

Sven Vogel
Apache CloudStack PMC member



On Wednesday, 06/23/2021 at 06:40 David Jumani wrote:


+1
I think that since Cenots8 / Rocky / Alma are binary compatible it
would be sufficient to support Rocky since it is looking like the go
to alternative, and supporting any one would pretty much be supporting
the other
About dropping support, I'm for supporting it until EOL this year

From: Rohit Yadav 
Sent: Tuesday, June 22, 2021 1:11 PM
To: d...@cloudstack.apache.org ; users@cloudstack.apache.org 
Subject: [DISCUSS] Rocky 8.4 and CloudStack

All,

With GA release of Rocky Linux 8.4
(https://docs.rockylinux.org/release_notes/8.4) does it make sense now
to completely drop support for CentOS8 in the next major release? I
did a quick test and it seems rpms built on centos8 container continue
to work on Rocky release. Thoughts?

Regards,
Rohit Yadav

Re: [VOTE] Apache CloudStack 4.15.1.0 (RC2)

[Rohit Yadav]

The voting window has finished, the vote now remains open until we've lazy 
consensus (min. 3 +1/binding and no -1s/vetos). Thanks to all those who have 
tested and voted, kindly continue testing/voting.

I'll add mine based on automated smoketests results and manually testing 
template registration and VM deployment on an isolated network with VMware 
6.7u3 adv zone.

+1 (binding)


Regards.


From: Vladimir Petrov 
Sent: Wednesday, June 23, 2021 14:49
To: users@cloudstack.apache.org 
Cc: dev ; users 
Subject: Re: [VOTE] Apache CloudStack 4.15.1.0 (RC2)

+1

The following upgrades has been tested and passed successfully:
Upgrade from 4.11.3:
Xen 7.1
VMWare: 60u2
KVM CentOS7

Upgrade from 4.13.1:
Xen 7.2
XCP-NG 7.4
VMWare 65u2
KVM CentOS7

Upgrade from 4.14.1:
Xen 7.4
XCP-NG 8.1
KVM CentOS8

Upgrade from 4.15.0:
Xen 8.1
VMWare 67u3
KVM CentOS7
KVM CentOS8

Also various smoke tests of the core functionalities did not show any 
regressions.
Regards.




 

On Jun 21 2021, at 3:23 pm, Rohit Yadav  wrote:
> All,
>
> We've not got any confirmation for a blocker on RC2 yet, kindly raise and 
> report any blockers if you've found in RC2.
> And please also continue testing and voting. Thanks.
>
> Regards.
> 
> From: Rohit Yadav 
> Sent: Friday, June 18, 2021 17:00
> To: Andrija Panic ; dev 
> ; Corey, Mike 
> Cc: users 
> Subject: Re: [VOTE] Apache CloudStack 4.15.1.0 (RC2)
>
> Since there are two thread on this, I request Mike to test ACS 4.15/older 
> versions UI/API and 4.15.1.0 RC2 legacy and new UI. Thanks.
>
> Regards.
> 
> From: Andrija Panic 
> Sent: Friday, June 18, 2021 04:15
> To: dev ; Rohit Yadav 
> ; Corey, Mike 
> Cc: users 
> Subject: Re: [VOTE] Apache CloudStack 4.15.1.0 (RC2)
>
> @Rohit Yadav we might have a UI blocker, 
> I'm waiting for Mike to report the issue - it seems (per his separate email 
> to this ML) that the Traffic Labels are not persisted after the Zone 
> deployment (UI doesn't show traffic labels) - I do recall an issue in 4.15.0 
> where similar was happening and one could not update the Traffic label in new 
> UI (old UI had to be used)
> @Corey, Mike please report here with the problem - 
> thx.
>
>
>
>
>
>
> On Wed, 16 Jun 2021 at 18:28, Rohit Yadav 
> mailto:ro...@apache.org>> wrote:
> Hi All,
>
> I've created a 4.15.1.0 release, with the following artifacts up for a vote:
> Git Branch:
> https://github.com/apache/cloudstack/tree/4.15.1.0-RC20210616T2128
> Commit SHA:
> 3afd37022b9dac52cd146dccada6012e47a80232
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.15.1.0/
>
> PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> The vote will be open for the next week until 22 June 2021.
> 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)
>
> For users convenience, the packages from this release candidate and 4.15.1
> systemvmtemplates are available here:
> https://download.cloudstack.org/testing/4.15.1.0-RC2/
> https://download.cloudstack.org/systemvm/4.15/
>
> Documentation is not published yet, but the following may be referenced for
> upgrade related tests: (there's a new 4.15.1 systemvmtemplate to be
> registered prior to upgrade)
> https://github.com/apache/cloudstack-documentation/tree/4.15/source/upgrading/upgrade
>
> Regards.
>
> --
> Andrija Panić

Re: [VOTE] Apache CloudStack 4.15.1.0 (RC2)

[Vladimir Petrov]

+1

The following upgrades has been tested and passed successfully:
Upgrade from 4.11.3:
Xen 7.1
VMWare: 60u2
KVM CentOS7

Upgrade from 4.13.1:
Xen 7.2
XCP-NG 7.4
VMWare 65u2
KVM CentOS7

Upgrade from 4.14.1:
Xen 7.4
XCP-NG 8.1
KVM CentOS8

Upgrade from 4.15.0:
Xen 8.1
VMWare 67u3
KVM CentOS7
KVM CentOS8

Also various smoke tests of the core functionalities did not show any 
regressions.
Regards.

 

On Jun 21 2021, at 3:23 pm, Rohit Yadav  wrote:
> All,
>
> We've not got any confirmation for a blocker on RC2 yet, kindly raise and 
> report any blockers if you've found in RC2.
> And please also continue testing and voting. Thanks.
>
> Regards.
> 
> From: Rohit Yadav 
> Sent: Friday, June 18, 2021 17:00
> To: Andrija Panic ; dev 
> ; Corey, Mike 
> Cc: users 
> Subject: Re: [VOTE] Apache CloudStack 4.15.1.0 (RC2)
>
> Since there are two thread on this, I request Mike to test ACS 4.15/older 
> versions UI/API and 4.15.1.0 RC2 legacy and new UI. Thanks.
>
> Regards.
> 
> From: Andrija Panic 
> Sent: Friday, June 18, 2021 04:15
> To: dev ; Rohit Yadav 
> ; Corey, Mike 
> Cc: users 
> Subject: Re: [VOTE] Apache CloudStack 4.15.1.0 (RC2)
>
> @Rohit Yadav we might have a UI blocker, 
> I'm waiting for Mike to report the issue - it seems (per his separate email 
> to this ML) that the Traffic Labels are not persisted after the Zone 
> deployment (UI doesn't show traffic labels) - I do recall an issue in 4.15.0 
> where similar was happening and one could not update the Traffic label in new 
> UI (old UI had to be used)
> @Corey, Mike please report here with the problem - 
> thx.
>
>
>
>
>
>
> On Wed, 16 Jun 2021 at 18:28, Rohit Yadav 
> mailto:ro...@apache.org>> wrote:
> Hi All,
>
> I've created a 4.15.1.0 release, with the following artifacts up for a vote:
> Git Branch:
> https://github.com/apache/cloudstack/tree/4.15.1.0-RC20210616T2128
> Commit SHA:
> 3afd37022b9dac52cd146dccada6012e47a80232
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.15.1.0/
>
> PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> The vote will be open for the next week until 22 June 2021.
> 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)
>
> For users convenience, the packages from this release candidate and 4.15.1
> systemvmtemplates are available here:
> https://download.cloudstack.org/testing/4.15.1.0-RC2/
> https://download.cloudstack.org/systemvm/4.15/
>
> Documentation is not published yet, but the following may be referenced for
> upgrade related tests: (there's a new 4.15.1 systemvmtemplate to be
> registered prior to upgrade)
> https://github.com/apache/cloudstack-documentation/tree/4.15/source/upgrading/upgrade
>
> Regards.
>
> --
> Andrija Panić

AW: [VOTE] Apache CloudStack 4.15.1.0 (RC2)

[Brussk, Michael]

Hi Rohit,

+1 from our side, too.

All our reported issues from rc1 are solved in rc2 and our tests (mostly VMware 
related) passed successful.
Many thanks for great support and hard work.

Regards,
Michael


Geschäftsführung: Mirko Kruse, André Walter
Sitz und Amtsgericht: Dresden, HRB 21356

This email and any attachments are sent in strictest confidence for the sole 
use of the addressee and may contain legally privileged, confidential, and 
proprietary data. If you are not the intended recipient, then you have received 
this email in error If this is the case please advise the sender by replying 
promptly to this email and then permanently delete this email and any 
attachments without any use, dissemination, printing, copying or forwarding. 
Copyright NTT DATA Business Solutions. All rights reserved.
-Ursprüngliche Nachricht-
Von: Rohit Yadav 
Gesendet: Montag, 21. Juni 2021 14:23
An: dev ; users 
Betreff: Re: [VOTE] Apache CloudStack 4.15.1.0 (RC2)

EXTERNAL MAIL:

All,

We've not got any confirmation for a blocker on RC2 yet, kindly raise and 
report any blockers if you've found in RC2.

And please also continue testing and voting. Thanks.


Regards.


From: Rohit Yadav 
Sent: Friday, June 18, 2021 17:00
To: Andrija Panic ; dev ; 
Corey, Mike 
Cc: users 
Subject: Re: [VOTE] Apache CloudStack 
https://urldefense.com/v3/__http://4.15.1.0__;!!B0kNdk3R__Efj5F6ERhD!oYWYWmDHgEvywwRFGJVU3y5YgQeJpN-x4ql-_iSZAPoHNtHD3t1kZxmzKGGfboGU_9wYM6zK$
  (RC2)

Since there are two thread on this, I request Mike to test ACS 4.15/older 
versions UI/API and 
https://urldefense.com/v3/__http://4.15.1.0__;!!B0kNdk3R__Efj5F6ERhD!oYWYWmDHgEvywwRFGJVU3y5YgQeJpN-x4ql-_iSZAPoHNtHD3t1kZxmzKGGfboGU_9wYM6zK$
  RC2 legacy and new UI. Thanks.


Regards.


From: Andrija Panic 
Sent: Friday, June 18, 2021 04:15
To: dev ; Rohit Yadav ; 
Corey, Mike 
Cc: users 
Subject: Re: [VOTE] Apache CloudStack 
https://urldefense.com/v3/__http://4.15.1.0__;!!B0kNdk3R__Efj5F6ERhD!oYWYWmDHgEvywwRFGJVU3y5YgQeJpN-x4ql-_iSZAPoHNtHD3t1kZxmzKGGfboGU_9wYM6zK$
  (RC2)

@Rohit Yadav we might have a UI blocker, I'm 
waiting for Mike to report the issue - it seems (per his separate email to this 
ML) that the Traffic Labels are not persisted after the Zone deployment (UI 
doesn't show traffic labels) - I do recall an issue in 4.15.0 where similar was 
happening and one could not update the Traffic label in new UI (old UI had to 
be used)

@Corey, Mike please report here with the problem - 
thx.







On Wed, 16 Jun 2021 at 18:28, Rohit Yadav 
mailto:ro...@apache.org>> wrote:
Hi All,

I've created a 
https://urldefense.com/v3/__http://4.15.1.0__;!!B0kNdk3R__Efj5F6ERhD!oYWYWmDHgEvywwRFGJVU3y5YgQeJpN-x4ql-_iSZAPoHNtHD3t1kZxmzKGGfboGU_9wYM6zK$
  release, with the following artifacts up for a vote:

Git Branch:
https://urldefense.com/v3/__https://github.com/apache/cloudstack/tree/4.15.1.0-RC20210616T2128__;!!B0kNdk3R__Efj5F6ERhD!oYWYWmDHgEvywwRFGJVU3y5YgQeJpN-x4ql-_iSZAPoHNtHD3t1kZxmzKGGfboGU_6TSDZfJ$
Commit SHA:
3afd37022b9dac52cd146dccada6012e47a80232

Source release (checksums and signatures are available at the same
location):
https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/cloudstack/4.15.1.0/__;!!B0kNdk3R__Efj5F6ERhD!oYWYWmDHgEvywwRFGJVU3y5YgQeJpN-x4ql-_iSZAPoHNtHD3t1kZxmzKGGfboGU_ypHRC8K$

PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884):
https://urldefense.com/v3/__https://dist.apache.org/repos/dist/release/cloudstack/KEYS__;!!B0kNdk3R__Efj5F6ERhD!oYWYWmDHgEvywwRFGJVU3y5YgQeJpN-x4ql-_iSZAPoHNtHD3t1kZxmzKGGfboGU_5NjvX_O$

The vote will be open for the next week until 22 June 2021.

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)

For users convenience, the packages from this release candidate and 4.15.1 
systemvmtemplates are available here:
https://urldefense.com/v3/__https://download.cloudstack.org/testing/4.15.1.0-RC2/__;!!B0kNdk3R__Efj5F6ERhD!oYWYWmDHgEvywwRFGJVU3y5YgQeJpN-x4ql-_iSZAPoHNtHD3t1kZxmzKGGfboGU_1GKuv9b$
https://urldefense.com/v3/__https://download.cloudstack.org/systemvm/4.15/__;!!B0kNdk3R__Efj5F6ERhD!oYWYWmDHgEvywwRFGJVU3y5YgQeJpN-x4ql-_iSZAPoHNtHD3t1kZxmzKGGfboGU_4dkT33M$

Documentation is not published yet, but the following may be referenced for 
upgrade related tests: (there's a new 4.15.1 systemvmtemplate to be registered 
prior to upgrade) 
https://urldefense.com/v3/__https://github.com/apache/cloudstack-documentation/tree/4.15/source/upgrading/upgrade__;!!B0kNdk3R__Efj5F6ERhD!oYWYWmDHgEvywwRFGJVU3y5YgQeJpN-x4ql-_iSZAPoHNtHD3t1kZxmzKGGfboGU_2ZNaMMB$

Regards.


--

Andrija Panić




Michael Brußk
Administration - Network Services
GMS Cloud Infrastructure Services

michael.bru...@nttdata.com
Tel: +49 359129522555

NTT DATA Business Solu

Re: [VOTE] Apache CloudStack 4.15.1.0 (RC2)

[Boris Stoyanov]

+1 (binding)

We’ve done upgrade tests from major previous versions and number of smoketests 
executions. Also some manual verification was done around lifecycle operations 
for: VMs, Volumes, Networks, Infrastructure and others.

Thanks,
Bobby.

From: Rohit Yadav 
Date: Monday, 21 June 2021, 15:23
To: dev , users 
Subject: Re: [VOTE] Apache CloudStack 4.15.1.0 (RC2)
All,

We've not got any confirmation for a blocker on RC2 yet, kindly raise and 
report any blockers if you've found in RC2.

And please also continue testing and voting. Thanks.


Regards.


From: Rohit Yadav 
Sent: Friday, June 18, 2021 17:00
To: Andrija Panic ; dev ; 
Corey, Mike 
Cc: users 
Subject: Re: [VOTE] Apache CloudStack 4.15.1.0 (RC2)

Since there are two thread on this, I request Mike to test ACS 4.15/older 
versions UI/API and 4.15.1.0 RC2 legacy and new UI. Thanks.


Regards.


From: Andrija Panic 
Sent: Friday, June 18, 2021 04:15
To: dev ; Rohit Yadav ; 
Corey, Mike 
Cc: users 
Subject: Re: [VOTE] Apache CloudStack 4.15.1.0 (RC2)

@Rohit Yadav we might have a UI blocker, I'm 
waiting for Mike to report the issue - it seems (per his separate email to this 
ML) that the Traffic Labels are not persisted after the Zone deployment (UI 
doesn't show traffic labels) - I do recall an issue in 4.15.0 where similar was 
happening and one could not update the Traffic label in new UI (old UI had to 
be used)

@Corey, Mike please report here with the problem - 
thx.








 

On Wed, 16 Jun 2021 at 18:28, Rohit Yadav 
mailto:ro...@apache.org>> wrote:
Hi All,

I've created a 4.15.1.0 release, with the following artifacts up for a vote:

Git Branch:
https://github.com/apache/cloudstack/tree/4.15.1.0-RC20210616T2128
Commit SHA:
3afd37022b9dac52cd146dccada6012e47a80232

Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.15.1.0/

PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open for the next week until 22 June 2021.

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)

For users convenience, the packages from this release candidate and 4.15.1
systemvmtemplates are available here:
https://download.cloudstack.org/testing/4.15.1.0-RC2/
https://download.cloudstack.org/systemvm/4.15/

Documentation is not published yet, but the following may be referenced for
upgrade related tests: (there's a new 4.15.1 systemvmtemplate to be
registered prior to upgrade)
https://github.com/apache/cloudstack-documentation/tree/4.15/source/upgrading/upgrade

Regards.


--

Andrija Panić

Re: Unable to add template to new deployment

[Joshua Schaeffer]

 A thing that I briefly touched somewhere upstairs ^^^ - for each
 traffic
 type you have defined - you need to define a traffic label - my
 deduction
 capabilities make me believe you are using KVM, so you need to set
 your KVM
 traffic label for all your network traffic (traffic label, in you case
 =
 exact name of the bridge as visible in Linux) - I recall there are
 some new
 UI issues when it comes to tags, so go to your
 :8080/client/legacy
 - and check your traffic label there - and set it there, UI in
 4.15.0.0
 doesn't allow you to update/set it after the zone is created - but old
 UI
 will allow you to do it.

I changed over all the bonds to the standard naming convention and that did the 
trick. I also added the storage network back as you suggested. Thanks again for 
those pointers. However, I may have discovered a bug. I'm actually trying to 
test an LXC hypervisor instead of KVM and it isn't using the network labels. 
There seems to be two problems:

1. You can't actually set the LXC network label in the new UI because there is 
no option for it. There is an option in the legacy UI, however it doesn't 
actually update the database and throws a warning in the management logs.
2. Even if you set the labels directly in the database ACS doesn't seem to use 
them. I'm not 100% sure but it looks like it defaults to the settings on the 
compute host. In my case this is causing problems with the storage network.

For the first problem, If all the labels are set to NULL:

user@dbserver:~$ sudo mysql -D cloud -e "SELECT id, traffic_type, 
lxc_network_label FROM physical_network_traffic_types;"
++--+---+
| id | traffic_type | lxc_network_label |
++--+---+
| 11 | Management   | NULL  |
| 12 | Public   | NULL  |
| 13 | Guest    | NULL  |
| 14 | Storage  | NULL  |
++--+---+

and I attempt to set the LXC network label in the legacy UI it remains NULL in 
the database and I see this warning in the logs:

2021-06-23 05:42:20,977 WARN  [c.c.a.d.ParamGenericValidationWorker] 
(qtp1644231115-887:ctx-a97e9424 ctx-5d6ce3c6) (logid:3e68476e) Received unknown 
parameters for command updateTrafficType. Unknown parameters : lxcnetworklabel

In order to get the right labels I updated the database manually:

user@dbserver:~$ sudo mysql -D cloud -e "UPDATE physical_network_traffic_types 
SET lxc_network_label = 'cloudbr0' WHERE id = 11;"
user@dbserver:~$ sudo mysql -D cloud -e "UPDATE physical_network_traffic_types 
SET lxc_network_label = 'cloudbr1' WHERE id in (12,13);"
user@dbserver:~$ sudo mysql -D cloud -e "UPDATE physical_network_traffic_types 
SET lxc_network_label = 'cloudbr2' WHERE id = 14;"
user@dbserver:~$ sudo mysql -D cloud -e "SELECT id, traffic_type, 
lxc_network_label FROM physical_network_traffic_types;"
++--+---+
| id | traffic_type | lxc_network_label |
++--+---+
| 11 | Management   | cloudbr0  |
| 12 | Public   | cloudbr1  |
| 13 | Guest    | cloudbr1  |
| 14 | Storage  | cloudbr2  |
++--+---+

However, this leads to my second problem; it doesn't seem to actually use the 
correct network interface. I think it uses the default that is set on the 
compute (maybe as a fallback), but I could be wrong about that. This is what is 
set on my compute in the agent.properties file:

user@cmpserver:~$ sudo cat /etc/cloudstack/agent/agent.properties | egrep 
'(network\.device|hypervisor\.type)'
private.network.device=cloudbr0
guest.network.device=cloudbr1
hypervisor.type=lxc
public.network.device=cloudbr1

And I can see in virsh that the management and public interfaces use cloudbr0 
and cloudbr1 respectively, however the storage interface for the VM uses 
cloudbr0 when it should use cloudbr2:

root@s-38-VM:~# ip --brief link show eth3
eth3 UP 1e:00:ac:00:03:6a 


root@bllcloudcmp01:~# virsh dumpxml s-38-VM | grep -B 1 -A 8 '1e:00:ac:00:03:6a'
    
  
  
  
  
  
  
  
  
    

I setup another cluster and host with the exact same configuration except 
running KVM instead of LXC and set the KVM labels to the same as the LXC labels 
as a test. I then started the system VM's on the new host. You can see that 
virsh is using the cloudbr2 bridge for the VM:

root@s-32-VM:~# ip --brief link show eth3
eth3 UP 1e:00:f8:00:03:df 


root@bllcloudcmp02:~# virsh dumpxml s-32-VM | grep -B 1 -A 8 '1e:00:f8:00:03:df'
    
  
  
  
  
  
  
  
  
    

Notice the  is set to cloudbr2 now with the only difference in 
the hypervisor.

Is LXC still supported (it is still mentioned in the docs)? If not then I'll 
just switch to using KVM.

-- 
Thanks,
Joshua Schaef