[PROPOSE] RM for CloudMonkey v6.2.0

2021-07-08 Thread Pearl d'Silva
Hi All, I'd like to put myself forward as the release manager for CloudMonkey 6.2.0. Our last release was almost a year ago, and since then we've had a few minor fixes that have gone in, and it seems about the right time to have the next release for CloudMonkey. There are a few open issues

Re: Reg : Novnc + KVM [Cent OS 8]

2021-07-08 Thread David Jumani
Hi Pavan, It does work with Centos8 as a KVM host From: pavan aravapalli Sent: Friday, July 9, 2021 10:35 AM To: users@cloudstack.apache.org ; dev Subject: Reg : Novnc + KVM [Cent OS 8] Hi, I saw below that PR is tested with kvm, but no specific version of

Reg : Novnc + KVM [Cent OS 8]

2021-07-08 Thread pavan aravapalli
Hi, I saw below that PR is tested with kvm, but no specific version of KVM is mentioned. Does NoVnc Supported in CentOS 8. https://github.com/apache/cloudstack/pull/3967 Regards, Pavan.

snapshot compression

2021-07-08 Thread Andrei Mikhailovsky
Hello everyone, Is there a way to enable compression on the KVM+Ceph snapshot volumes when they are being copied to the secondary storage? As far as I can see, this useful feature is not enabled by default, which could unnecessarily waste both network and storage resources. It could save tons

RE: NFS Error Ubuntu 20.4

2021-07-08 Thread Corey, Mike
John, Have you set the global settings parameter secstorage.nfs.version? I had to set it as 3 for my environment as NFS4 isn’t used yet. However, I’m using an external storage system, not KVM as the NFS host. Mike From: John Sent: Thursday, July 8, 2021 7:54 AM To:

Re: NFS Error Ubuntu 20.4

2021-07-08 Thread John
Thank you both for your advice. What did was add a second private IP to both KVM host and Management Host as both had public IPs. I then removed the secondary storage and added it back and this time used the private IP ( in the range is the CS internal subnet ) and everything started

Re: NFS Error Ubuntu 20.4

2021-07-08 Thread Vivek Kumar
Yes, it looks like some permission issue from NFS side, just try to mount manually from the host and see. Regards, Vivek Kumar > On 08-Jul-2021, at 5:59 PM, Daniel Augusto Veronezi Salvador > wrote: > > Hello John, > > > This mount is done by the SSVM. Does the SSVM has access to the NFS

Re: NFS Error Ubuntu 20.4

2021-07-08 Thread Daniel Augusto Veronezi Salvador
Hello John, This mount is done by the SSVM. Does the SSVM has access to the NFS you trying to use as a secondary storage? Best regards, Daniel Salvador On 08/07/2021 08:53, John wrote: We are having some issues with the latest CS 4.15.1 which we never had before. We are using the

NFS Error Ubuntu 20.4

2021-07-08 Thread John
We are having some issues with the latest CS 4.15.1 which we never had before. We are using the following:- Ubuntu 20.4 CS 4.15.1 NFS is on the same host as the KVM server. We can mount the /export/secondary directory successfully from the management host. But when CS tries to mount it we get

Re: Need some clarification on | expunge.interval | expunge.delay

2021-07-08 Thread Vivek Kumar
Thanks mate.!  > On 08-Jul-2021, at 5:05 PM, Yordan Kostov wrote: > > You got that right. > Expunge process for that VM will be done in the time range from 24 to 48 > hours depending on when the thread runs. > > Regards, > Jordan > > -Original Message- > From: Vivek Kumar > Sent:

RE: Need some clarification on | expunge.interval | expunge.delay

2021-07-08 Thread Yordan Kostov
You got that right. Expunge process for that VM will be done in the time range from 24 to 48 hours depending on when the thread runs. Regards, Jordan -Original Message- From: Vivek Kumar Sent: 08 юли 2021 г. 14:31 To: users@cloudstack.apache.org Subject: Re: Need some clarification on

Re: Need some clarification on | expunge.interval | expunge.delay

2021-07-08 Thread Vivek Kumar
Hey Jordan, Thanks for the response..!! It clarifies my doubt. So basically, after expunge.delay ( 24 hours in my case ), expunge.interval will be execute. So if I delete the VM now, it will be qualified to be expunged after 24 hours, and later after 24 hours, it will be deleted whenever

RE: Need some clarification on | expunge.interval | expunge.delay

2021-07-08 Thread Yordan Kostov
Hi Vivek, Expunge delay - means after what time the VM will be qualified to be deleted. If you set this value to 604800 (7 days). This means the VM that is destroyed will be kept for no less than 7 days in cloudstack before being expunged. Expunge interval - is responsible

Need some clarification on | expunge.interval | expunge.delay

2021-07-08 Thread Vivek Kumar
Hey Guys, I need some clarification on the global setting i.e expunge.delay and expunge.intervals - So how does this both work. Let’s say if I set values 86400( 24 hours) in both settings. So When I destroy my VM today, it will get expunged after 24 hours as per the expunge.intervel. So what’s

[ANNOUCE] Apache CloudStack 4.15.1.0 LTS Release

2021-07-08 Thread Rohit Yadav
# Apache CloudStack LTS Maintenance Release 4.15.1.0 The Apache CloudStack project is pleased to announce the release of CloudStack 4.15.1.0. The CloudStack 4.15.1.0 release is a maintenance release as part of its 4.15.x LTS branch and contains more than 350 fixes and improvements since the