RE: Issues Found Apache CloudStack 4.15.1.0 (RC2)

2021-06-22 Thread Corey, Mike
Thanks for the update and testing it out.  It may be my browser/issue only.

I have 3 physical networks and for whatever reason only 1 of them didn’t save.  
Even going next and previous in the wizard it would show sometimes and others 
not show.  Its not a show stopper since I know what to look for now.  For the 
record it occurred with physical network instance 2.

MC

From: Andrija Panic 
Sent: Monday, June 21, 2021 11:20 AM
To: users 
Cc: dev@cloudstack.apache.org; Corey, Mike 
Subject: Re: Issues Found Apache CloudStack 4.15.1.0 (RC2)

Hi Mike,

as for the first issue, I have deployed a Zone manually with RC2 - and my label 
(for KVM is there). I've also deployed a zone with VMware - and again 
everything is OK - traffic label is there (I had 2 physical networks, with 
different traffic labels - and all good)

If you can please advise on how different your setup might be - let's try to 
reproduce the issue - otherwise, I don't see an issue with RC2.
(screenshot below)

Best,

[cid:image001.png@01D76695.39B17390]

On Fri, 18 Jun 2021 at 23:01, Corey, Mike 
mailto:mike.co...@sap.com.invalid>> wrote:
Well - I found a "workaround", but it really can't be explained.  I reverted to 
a snapshot THREE times and retraced my steps just to validate what I'm seeing.

Short summary - When the zone is enabled and the systemvms are created a folder 
is created at /var/cloudstack/mnt/VM/.  This folder has the 
nobody:nobody attribute and the error Unable to copy systemvm ISO on secondary 
storage.  Next, I removed the Secondary Storage entry, restarted services, 
re-added Secondary Storage, restarted services, AND systemvms deploy.

Attributes of UID Folder at initial systemvm build:
drwxr-xr-x. 3 cloud  cloud34 Jun 18 16:27 .
drwxrwx---. 3 root   cloud16 Jun 18 16:27 ..
drwxrwxrwt. 6 nobody nobody 4096 Jun 18 15:51 345050034639.51841a7

*** ACS tries to set perms on this folder but fails ***
2021-06-18 16:27:25,862 DEBUG [c.c.h.v.m.VmwareManagerImpl] 
(DirectAgent-3:ctx-a90e1ecb usphlmvesxt01.phl.global.corp.sap, job-9/job-51, 
cmd: CopyCommand) (logid:3d148cdf) chmod: changing permissions of 
‘/var/cloudstack/mnt/VM/345050034639.51841a7’: Operation not permitted
2021-06-18 16:27:25,865 WARN  [c.c.h.v.m.VmwareManagerImpl] 
(DirectAgent-3:ctx-a90e1ecb usphlmvesxt01.phl.global.corp.sap, job-9/job-51, 
cmd: CopyCommand) (logid:3d148cdf) Unable to set permissions for 
/var/cloudstack/mnt/VM/345050034639.51841a7 due to chmod: changing permissions 
of ‘/var/cloudstack/mnt/VM/345050034639.51841a7’: Operation not permitted

***When you remove the SS in UI and restart the services, ACS will clear this 
folder***
2021-06-18 16:31:07,962 INFO  [c.c.h.v.m.VmwareManagerImpl] 
(SpringContextShutdownHook:null) (logid:) shutting down scheduled tasks
2021-06-18 16:31:07,962 INFO  [c.c.h.v.m.VmwareManagerImpl] 
(SpringContextShutdownHook:null) (logid:) Cleanup mounted NFS mount points used 
in current session
2021-06-18 16:31:07,962 INFO  [c.c.h.v.m.VmwareManagerImpl] 
(SpringContextShutdownHook:null) (logid:) umount NFS mount: 
/var/cloudstack/mnt/VM/345050034639.51841a7
2021-06-18 16:31:07,962 DEBUG [c.c.h.v.m.VmwareManagerImpl] 
(SpringContextShutdownHook:null) (logid:) Executing: sudo umount 
/var/cloudstack/mnt/VM/345050034639.51841a7

***Re-adding the SS in the UI and restarting services ACS CAN set the perms for 
the new folder ***
2021-06-18 16:38:56,254 DEBUG [c.c.h.v.m.VmwareManagerImpl] 
(DirectAgent-15:ctx-f9c800cf usphlmvesxt02.phl.global.corp.sap, job-9/job-58, 
cmd: StartCommand) (logid:3d148cdf) Executing: sudo chmod 1777 
/var/cloudstack/mnt/VM/345050034639.50b47f15
2021-06-18 16:38:56,269 DEBUG [c.c.h.v.m.VmwareManagerImpl] 
(DirectAgent-15:ctx-f9c800cf usphlmvesxt02.phl.global.corp.sap, job-9/job-58, 
cmd: StartCommand) (logid:3d148cdf) Executing while with timeout : 144
2021-06-18 16:38:56,293 DEBUG [c.c.h.v.m.VmwareManagerImpl] 
(DirectAgent-15:ctx-f9c800cf usphlmvesxt02.phl.global.corp.sap, job-9/job-58, 
cmd: StartCommand) (logid:3d148cdf) Execution is successful.


Attributes after SS removed, services restarted, SS added, services restarted:
drwxr-xr-x. 3 cloud cloud   35 Jun 18 16:38 .
drwxrwx---. 3 root  cloud   16 Jun 18 16:27 ..
drwxrwxrwt. 6 root  root  4096 Jun 18 15:51 345050034639.50b47f15

So you can see that root:root is applied AFTER the original SS is removed and 
readded into the zone.  I don't why the original attempt by ACS to build this 
directory fails.  Look forward to your thoughts!

Have a great weekend!

Mike



-Original Message-
From: Corey, Mike 
mailto:mike.co...@sap.com.INVALID>>
Sent: Friday, June 18, 2021 11:47 AM
To: us...@cloudstack.apache.org; 
dev@cloudstack.apache.org
Subject: [CAUTION] RE: Issues Found Apache CloudStack 4.15.1.0 (RC2)

Honestly, I can live with having to go in after the wizard completes and modify 
the traffic labels.  What I'm hitting regarding permissions on the Second

[DISCUSS] Rocky 8.4 and CloudStack

2021-06-22 Thread Rohit Yadav
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

 



[GitHub] [cloudstack-kubernetes-provider] davidjumani commented on pull request #32: Update Kubernetes version to 1.20.6

2021-06-22 Thread GitBox


davidjumani commented on pull request #32:
URL: 
https://github.com/apache/cloudstack-kubernetes-provider/pull/32#issuecomment-865517226


   @rhtyd @joschi36 Can this be merged after 1.0 is released? Since there only 
exist isos for 1.16. Post release isos for 1.18, 1.20 can be created and tested


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




Re: [DISCUSS] Rocky 8.4 and CloudStack

2021-06-22 Thread Rudraksh MK
+1. We were planning to run a few experiments with Rocky on ACS 4.15 sometime 
this week, across VMware, Xen and KVM to make sure there are no kinks around 
RPM packages, cloud-init and so on. Will message on this thread if something 
does come up.


Best!

Rudraksh Mukta Kulshreshtha
Vice-President - DevOps & R&D
IndiQus Technologies
O +91 11 4055 1411 | M +91 99589 54879
indiqus.com

This message is intended only for the use of the individual or entity to which 
it is addressed and may contain information that is confidential and/or 
privileged. If you are not the intended recipient please delete the original 
message and any copy of it from your computer system. You are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited unless proper authorization has been obtained for such 
action. If you have received this communication in error, please notify the 
sender immediately. Although IndiQus attempts to sweep e-mail and attachments 
for viruses, it does not guarantee that both are virus-free and accepts no 
liability for any damage sustained as a result of viruses.
On 22 Jun 2021, 1:12 PM +0530, Rohit Yadav , wrote:
> 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
>
>
>


[GitHub] [cloudstack-documentation] Spaceman1984 opened a new pull request #223: Host ha an multiple management server internal load balancing

2021-06-22 Thread GitBox


Spaceman1984 opened a new pull request #223:
URL: https://github.com/apache/cloudstack-documentation/pull/223


   Added some documentation around Host HA and management-server internal load 
balancing


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




Re: [DISCUSS] Rocky 8.4 and CloudStack

2021-06-22 Thread nux

Hi,

Drop support for CentOS8, 8-Stream or both?

Regards

On 2021-06-22 08:41, Rohit Yadav wrote:

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: [DISCUSS] Rocky 8.4 and CloudStack

2021-06-22 Thread Rohit Yadav
Both I guess, 8-Stream may not same kind of stability like an LTS release.

Regards.

Regards,
Rohit Yadav


From: n...@li.nux.ro 
Sent: Tuesday, June 22, 2021 8:11:45 PM
To: dev@cloudstack.apache.org 
Cc: us...@cloudstack.apache.org 
Subject: Re: [DISCUSS] Rocky 8.4 and CloudStack

Hi,

Drop support for CentOS8, 8-Stream or both?

Regards

On 2021-06-22 08:41, Rohit Yadav wrote:
> 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: [DISCUSS] Rocky 8.4 and CloudStack

2021-06-22 Thread nux
Outraged as I was initially, having thought more about CentOS Stream now 
that the dust has settled imho it should continue to be supported as 
first class platform.
For most/many intents and purposes it'll be RHEL, only supported for 5 
years.
I think it's going to be as good or better (considering RedHat QA) than 
Ubuntu LTS, quality wise.


I guess both CentOS Stream and RHEL clones will have to prove themselves 
in the near/mid future and we should be watching carefully.
BTW, we should also keep an eye on AlmaLinux which released well before 
Rocky and it's also backed by a charity.


Regards

On 2021-06-22 16:40, Rohit Yadav wrote:
Both I guess, 8-Stream may not same kind of stability like an LTS 
release.


Regards.

Regards,
Rohit Yadav


From: n...@li.nux.ro 
Sent: Tuesday, June 22, 2021 8:11:45 PM
To: dev@cloudstack.apache.org 
Cc: us...@cloudstack.apache.org 
Subject: Re: [DISCUSS] Rocky 8.4 and CloudStack

Hi,

Drop support for CentOS8, 8-Stream or both?

Regards

On 2021-06-22 08:41, Rohit Yadav wrote:

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: [DISCUSS] Rocky 8.4 and CloudStack

2021-06-22 Thread Nathan McGarvey
All,
Since CentOS8 (not stream) is officially EOL at the end of this
year, I'd say keep supporting it until then, but don't support it past
then. This may be a good 6-month transition to support
Rocky/Alma/Springdale/whatever. Realistically, I'd be surprised if one
of those worked and one didn't since they should be by-and-large
binary-compatible rebuilds from RHEL sources. Possibly slightly lagging
in release times, but compatible.

Rocky is nice since it isn't "tied" to another company, which is the
obvious double-edged sword of funding, etc. But it may mean it aligns
with the ASF more closely in spirit.

   Alma has only said they'll support it through the RHEL 8 lifecycle
(2029): https://almalinux.org/  "Until when will we support AlmaLinux
OS? AlmaLinux partners has committed to supporting AlmaLinux OS until
2029, ...", which is generous, but they do stem from selling CloudLinux.
So it could become paid-for pretty easily.

   CentOS Stream could be fine or a disaster, and it is hard to tell: "a
rolling preview of future RHEL kernels and features." as the RedHat CTO
said seems to imply cloudstack might run into a lot more issues due to
the squishy nature of kernel releases, kvm/libvirt, etc. I don't think
it will be unusable, but it will be hard to say what is supported. (E.g.
what version is "Centos 8 Stream"? Stuff can change out from under you
pretty quickly in that paradigm. Even rolling distros like Debian have
point releases.


My $0.02 would likely to transition to Rocky, but it may be prudent
to wait a month or two to make sure it really is stable since they
*just* released a GA.



How hard would it be to make a test build on the new Rocky GA and
see if it looks similar/identical to the CentOS 8.4? Not sure how
CloudStack's CICD is setup, internally.


Thanks,
-Nathan McGarvey



On 6/22/21 9:41 AM, n...@li.nux.ro wrote:
> Hi,
> 
> Drop support for CentOS8, 8-Stream or both?
> 
> Regards
> 
> On 2021-06-22 08:41, Rohit Yadav wrote:
>> 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: [DISCUSS] Rocky 8.4 and CloudStack

2021-06-22 Thread Rudraksh MK
I’m also not sure how CloudStack’s CI/CD setup works and how easy/complicated 
it may be to run a full build on Rocky. But we could always run a build of the 
4.15.0 release on a standalone Rocky server - planning to do that in the next 
couple of days, once I build a Rocky template on our test infrastructure.

Got Rocky to work just fine on an advanced networking zone in CloudStack 
powered by KVM. Pretty normal. Trying Xen now.

On another note - the whole point about versioning is to avoid situations where 
something new breaks what’s working just fine. I’m honestly not sure what Red 
Hat is driving at with this stream approach, and I’m willing to bet it will be 
a disaster.


Best!

Rudraksh Mukta Kulshreshtha
Vice-President - DevOps & R&D
IndiQus Technologies
O +91 11 4055 1411 | M +91 99589 54879
indiqus.com

This message is intended only for the use of the individual or entity to which 
it is addressed and may contain information that is confidential and/or 
privileged. If you are not the intended recipient please delete the original 
message and any copy of it from your computer system. You are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited unless proper authorization has been obtained for such 
action. If you have received this communication in error, please notify the 
sender immediately. Although IndiQus attempts to sweep e-mail and attachments 
for viruses, it does not guarantee that both are virus-free and accepts no 
liability for any damage sustained as a result of viruses.
On 22 Jun 2021, 11:20 PM +0530, Nathan McGarvey , 
wrote:
> All,
> Since CentOS8 (not stream) is officially EOL at the end of this
> year, I'd say keep supporting it until then, but don't support it past
> then. This may be a good 6-month transition to support
> Rocky/Alma/Springdale/whatever. Realistically, I'd be surprised if one
> of those worked and one didn't since they should be by-and-large
> binary-compatible rebuilds from RHEL sources. Possibly slightly lagging
> in release times, but compatible.
>
> Rocky is nice since it isn't "tied" to another company, which is the
> obvious double-edged sword of funding, etc. But it may mean it aligns
> with the ASF more closely in spirit.
>
> Alma has only said they'll support it through the RHEL 8 lifecycle
> (2029): https://almalinux.org/ "Until when will we support AlmaLinux
> OS? AlmaLinux partners has committed to supporting AlmaLinux OS until
> 2029, ...", which is generous, but they do stem from selling CloudLinux.
> So it could become paid-for pretty easily.
>
> CentOS Stream could be fine or a disaster, and it is hard to tell: "a
> rolling preview of future RHEL kernels and features." as the RedHat CTO
> said seems to imply cloudstack might run into a lot more issues due to
> the squishy nature of kernel releases, kvm/libvirt, etc. I don't think
> it will be unusable, but it will be hard to say what is supported. (E.g.
> what version is "Centos 8 Stream"? Stuff can change out from under you
> pretty quickly in that paradigm. Even rolling distros like Debian have
> point releases.
>
>
> My $0.02 would likely to transition to Rocky, but it may be prudent
> to wait a month or two to make sure it really is stable since they
> *just* released a GA.
>
>
>
> How hard would it be to make a test build on the new Rocky GA and
> see if it looks similar/identical to the CentOS 8.4? Not sure how
> CloudStack's CICD is setup, internally.
>
>
> Thanks,
> -Nathan McGarvey
>
>
>
> On 6/22/21 9:41 AM, n...@li.nux.ro wrote:
> > Hi,
> >
> > Drop support for CentOS8, 8-Stream or both?
> >
> > Regards
> >
> > On 2021-06-22 08:41, Rohit Yadav wrote:
> > > 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: [DISCUSS] Rocky 8.4 and CloudStack

2021-06-22 Thread David Jumani
+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: dev@cloudstack.apache.org ; 
us...@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