Re: SSL Medium Strength Cipher Suites Supported | port 8250 on Management servers

[Rohit Yadav]

Hi Vivek,

I think you can tune the following global settings to regenerate CloudStack's 
root-ca certificates with chosen cipher/algorithm and key size: (depending on 
the ACS version if it has CA framework)

ca.framework.cert.signature.algorithm
ca.framework.cert.keysize

(for an already deployed cloudstack env, after changing this you may need to 
delete old root-ca keypair for this to regenerate new server certificates and 
CA certificate, by removing the configurations found out by: `select * from 
configuration where name like 'ca.plugin.root%' and category='Hidden'\G;`; and 
then restarting management servers one by one).
​
Alternatively, you can also test and disable cipher algorithm via 
/etc/cloudstack/management/java.security.ciphers that you don't want. And of 
course, you want to test and validate these in a test environment before 
applying in production (and take db backups just in case).


Regards.

 



From: Vivek Kumar 
Sent: Monday, April 29, 2024 15:27
To: CloudStack Users Mailing list 
Subject: SSL Medium Strength Cipher Suites Supported | port 8250 on Management 
servers

Hello Folks,

Our security team has highlighted that services running on port 8250 supports 
the use of SSL ciphers that offer medium strength encryption. Nessus regards 
medium strength as any encryption  that uses key lengths at least 64 bits and 
less than 112 bits,

It is considerably easier to circumvent medium strength encryption if the 
attacker is on the same physical network.


Our security team has recommended to reconfigure the affected application if 
possible to avoid use of medium strength ciphers, so we do something about it 
or not ?




Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 





--
This message is intended only for the use of the individual or entity to
which it is addressed and may contain confidential and/or privileged
information. 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.

Re: Deploy Cloudstack on Debian 12

[Rohit Yadav]

I've some notes on Debian here - 
https://gist.github.com/rohityadavcloud/fc401a0fe8e8ea16b4b3a4e3d149ce0c

Last time I tested it worked for me.



Regards.

 



From: lists 
Sent: Thursday, April 25, 2024 13:25
To: users 
Subject: Re: Deploy Cloudstack on Debian 12




Hi

Ive deployed recent on both 11 and 12. What issue on 12 did you encounter?











>
> On Apr 25, 2024 at 1:59 PM, Khang Nguyen Phuc
> wrote:
>
>
>  Hello everyone,
>
> I'm a newbie, and I mainly use Debian servers. So I want to deploy
> CloudStack on Debian. I've experimented with CloudStack 4.19 on Debian 11 ,
> it works fine, but I noticed that CloudStack doesn't officially support
> Debian (CloudStack's documentation recommends using Ubuntu or CentOS
> without mentioning Debian). Additionally, I encountered errors when
> deploying CloudStack on Debian 12. I wonder why seems inconvenient to use
> CloudStack on Debian. Should I deploy CloudStack on Debian 12 for
> production? Can anyone with experience share some tips on deploying
> CloudStack on Debian 12?
>
> Thank you all very much.
>

Re: CloudStack managing KVM Hypervisors on multiple architectures?

[Rohit Yadav]

Hi Rishi,

There may be approaches you can consider;


  1.
Arch-specific cluster:
CloudStack assumes clusters are homogenous; so you can start with arch-specific 
cluster - one cluster of x86 hosts and another one of arm64, within the same 
zone. You'll then need to decide which arch you want to be standard as part of 
systemvm deployment and must tag other arch hosts with some hosttag. This way 
you can have for example systemvms always run on x86, but on arm64 hosts having 
tags such that only offerings/templates matching the host tag are deployed on 
it. Using service offerings + tags you can force which template must go on 
which arch/hosts, and clearly marking which template is x86 vs arm64. However, 
this approach can be brittle if someone (user) mixes offerings with templates.

  2.
Arch-specific zone:
The other option could be to have arch-specific zones; so one zone for x86 and 
another for arm64 and you register zone specific templates to begin with. The 
systemvm template would be tricky in this case; and for arch-specific zone, 
before you deploy the zone for a particular type you can seed arch-specific 
systemvmtemplates for the zone-specific secondary storage. For example, refer 
the seeding steps for arm64 here - 
https://rohityadav.cloud/blog/cloudstack-arm64-kvm/#storage-setup

  3.
Arch-specific installation (or region):
The cleanest approach could be you keep two separate ACS regions, or 
installations; one for arm64 and another for x86.


I think if CloudStack can support architecture as a property in templates, in 
future it might make mixing archs better. We also have an upcoming feature that 
makes host tags strict vs non-strict and resource limit tags, which can be used 
to enforce feature that accounts are allowed to deploy X number of VMs on one 
host-tag (that could related to an arch) vs deploy Y number of VMs on others.


Regards.

 



From: Wei ZHOU 
Sent: Friday, April 19, 2024 21:45
To: users@cloudstack.apache.org ; Rohit Yadav 

Subject: Re: CloudStack managing KVM Hypervisors on multiple architectures?

different clusters should be fine.

maybe @Rohit Yadav can give some advice.


-Wei

On Fri, Apr 19, 2024 at 4:56 PM Daan Hoogland  wrote:
>
> good point Rishi,
> I think you would have to separate the hardware into different
> clusters at least, but maybe even separate zones. I never heard of
> anybody doing a setup like yours.
>
> On Wed, Apr 10, 2024 at 6:56 PM Rishi Misra  
> wrote:
> >
> > Can a CloudStack instance running on x86 manage deployments on both x86 and
> > Raspberry Pi (or any other archs)?
> >
> > I am not sure how it will affect management SystemVMs given the different
> > archs in the mix?
> >
> > Any pointers are greatly appreciated.
> >
> > Thanks!
>
>
>
> --
> Daan

Re: cloudstack-agent mismatch size

[Rohit Yadav]

Hi Francisco, all,

We've in process of publishing the new 4.18.2.0 release, due to which the repo 
metadata has been changed.

The download.cloudstack.org repo is served by CDN77 (I've purged the cache and 
changed caching timeout from 12hrs to 1hr) and can have caching issue around 
the time an existing/already published repo has new packages (like in this case 
we added new 4.18.2.0 deb pkgs in the existing pool dirs for focal, bionic and 
jammy).

I've removed the .cache now for 4.18 and rebuilding the index now: 
http://download.cloudstack.org/ubuntu/.cache/

Can you try again in an hours time? Alternatively, users can use the generic 
deb repo: http://packages.shapeblue.com/cloudstack/upstream/debian/4.18/


Regards.

 



From: Francisco Arencibia Quesada 
Sent: Thursday, April 18, 2024 17:10
To: users@cloudstack.apache.org 
Subject: cloudstack-agent mismatch size

Good morning guys,

I'm having this problem:

Get:16 https://download.cloudstack.org/ubuntu jammy/4.18 all Packages
[5.626 B]
Err:16 https://download.cloudstack.org/ubuntu jammy/4.18 all Packages

  File has unexpected size (6832 != 5626). Mirror sync in progress? [IP:
185.76.11.112 443]
  Hashes of expected file:
   - Filesize:5626 [weak]
   -
SHA512:d6df6ec9be5c09dd1d863e3c4b9b492de1229d8f2d928edb5ed2bb9d756383811a0a4a18d603d127487c069214e827da14bd54819ced97eaedec84341cc272c7
   - SHA256:7568d203313ffa158981b9ffd57462fa52f2531afdf2958c3452e32528fc8622
   - SHA1:4f4f56dc1f9cc98d93d9f71c72e4598b9c3bc3a3 [weak]
   - MD5Sum:0d24415641060895fbca39abe11a3176 [weak]
  Release file created at: Wed, 03 Apr 2024 17:37:05 +
Hit:17 https://packagecloud.io/slacktechnologies/slack/debian jessie
InRelease
Reading package lists... Done
N: Skipping acquire of configured file '4.18/binary-i386/Packages' as
repository 'https://download.cloudstack.org/ubuntu jammy InRelease' doesn't
support architecture 'i386'
E: Failed to fetch
https://download.cloudstack.org/ubuntu/dists/jammy/4.18/binary-all/Packages.bz2
 File has unexpected size (6832 != 5626). Mirror sync in progress? [IP:
185.76.11.112 443]
   Hashes of expected file:
- Filesize:5626 [weak]
-
SHA512:d6df6ec9be5c09dd1d863e3c4b9b492de1229d8f2d928edb5ed2bb9d756383811a0a4a18d603d127487c069214e827da14bd54819ced97eaedec84341cc272c7
-
SHA256:7568d203313ffa158981b9ffd57462fa52f2531afdf2958c3452e32528fc8622
- SHA1:4f4f56dc1f9cc98d93d9f71c72e4598b9c3bc3a3 [weak]
- MD5Sum:0d24415641060895fbca39abe11a3176 [weak]
   Release file created at: Wed, 03 Apr 2024 17:37:05 +
E: Some index files failed to download. They have been ignored, or old ones
used instead.

Regards

--
*Francisco Arencibia Quesada.*
*DevOps Engineer*

Re: [VOTE] Apache CloudStack 4.18.2.0 RC2

[Rohit Yadav]

+1 (binding)

I've built and uploaded the 4.18.2.0 RC2 packages here for people's convenience 
- http://cloudstack.apt-get.eu/testing/4.18.2.0-rc2/

  *
Tested upgrade from 4.18.1.1 to 4.18.2.0 RC packages -ok
  *
Rebuilt systemvms (ssvm and cpvm) - ok
  *
Restart network - ok
  *
New VM deployment on existing network post-upgrade using pre-upgrade template - 
ok
  *
Login as normal and admin users - ok
  *
cmk CLI test - ok
  *
Tested on a arm64/RPi platform - ok (caveat, had to build this 
http://cloudstack.apt-get.eu/rpi4/systemvmtemplate/4.18/systemvmtemplate-4.18.1-kvm-arm64.qcow2
 and ensure before starting the mgmt server post-upgrade, had to copy the file 
to /usr/share/cloudstack-management/templates/systemvm and fix/tricky the md5 
hash in the metadata.ini)

Regards.

 



From: Jithin Raju 
Sent: Wednesday, April 17, 2024 13:54
To: users@cloudstack.apache.org ; 
d...@cloudstack.apache.org 
Subject: Re: [VOTE] Apache CloudStack 4.18.2.0 RC2

+1 tested the usual VM, network, and storage operations.


-Jithin

From: João Jandre 
Date: Friday, 12 April 2024 at 5:07 PM
To: d...@cloudstack.apache.org , 
users@cloudstack.apache.org 
Subject: [VOTE] Apache CloudStack 4.18.2.0 RC2
Hi All,

I've created a 4.18.2.0 release (RC2), with the following artifacts up
for a vote:

Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.18.2.0-RC20240412T0825
Commit: 154566f914c778d448d4ab07b47b2db874bbf982

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

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

Vote will be open for 120 hours (due to the weekend).

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)

Re: ACS 4.16 - Change SystemVM template for CKS

[Rohit Yadav]

Benoit,

I haven't tested it but could work - worth testing. CAPC was tested on 
4.17/4.18+.


Regards.

 



From: benoit lair 
Sent: Thursday, April 11, 2024 17:09
To: users@cloudstack.apache.org 
Cc: dev 
Subject: Re: ACS 4.16 - Change SystemVM template for CKS

Rohit,

It is possible to install  CAPC on a CS 4.16 ?

Le jeu. 11 avr. 2024 à 12:03, Rohit Yadav  a
écrit :

> Hi Benoit,
>
> The CKS feature has been improving over versions, I don't know if what
> you're trying to achieve is possible with it. Maybe try a different version
> of the data iso:
> http://download.cloudstack.org/cks/
>
> Alternatively, you can also have a look at the CAPC project:
> https://cluster-api-cloudstack.sigs.k8s.io
>
>
> Regards.
>
>
>
>
> 
> From: benoit lair 
> Sent: Thursday, April 11, 2024 14:16
> To: users@cloudstack.apache.org ; dev <
> d...@cloudstack.apache.org>
> Subject: Re: ACS 4.16 - Change SystemVM template for CKS
>
> Any advices ?
>
> Best regards
>
> Le lun. 8 avr. 2024 à 16:53, benoit lair  a écrit :
>
> > I am opened to every alternatives of changing system vm templates
> > I just need to run K8s clyusters 1.28 with my CS 4.16 :)
> >
> > Le lun. 8 avr. 2024 à 16:52, benoit lair  a
> écrit :
> >
> >> Hello Folks,
> >>
> >> I am trying to install K8s cluster with community iso 1.28.4
> >> I am with a ACS 4.16.0 environment
> >> It seems K8S is not working out of the box with v > 1.23.3 due to
> >> containerd.io version
> >>
> >> I would like to release a template who will work with K8s > 1.23.3 on
> acs
> >> 4.16
> >> How can i tell CS to take another system vm template, avoiding to mess
> >> normal features with VR and VPC VR keeping the systemvm template issued
> >> with CS 4.16 ?
> >>
> >> I am with XCP-NG 8.2.1 in production
> >>
> >> Thanks for your help or advises
> >> Best regards,
> >> Benoit
> >>
> >
>

Re: [RESULT] [VOTE] Release Apache CloudStack Terraform Provider v0.5.0

[Rohit Yadav]

Thanks Kiran and all for the excellent release work.

There has been some issue with publishing the v0.5.0 on the Terraform registry, 
for this I've logged a support ticket with the TF Registry.

In the meanwhile, users can use the following to install the provider locally 
using artifacts from the Github release;
https://github.com/apache/cloudstack-terraform-provider?tab=readme-ov-file#installing-from-github-release
https://github.com/apache/cloudstack-terraform-provider/wiki#installing-from-github-release

Regards.
 



From: Kiran Chavala 
Sent: Tuesday, April 9, 2024 11:52
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: [RESULT] [VOTE] Release Apache CloudStack Terraform Provider v0.5.0

Hi All

After more than 72 hours, the vote for CloudStack Terraform Provider v0.5.0 
*passes* with

5 PMC + 2 non-PMC votes.

+1 (PMC / binding)
5 persons (Rohit, Daan, Boris, Hari, Nux)

+1 (non binding)
2 persons (Jithin, Suresh)

0
none

-1
none

Thanks to everyone participating.

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

Regards,
Kiran Chavala

Re: ACS 4.16 - Change SystemVM template for CKS

[Rohit Yadav]

Hi Benoit,

The CKS feature has been improving over versions, I don't know if what you're 
trying to achieve is possible with it. Maybe try a different version of the 
data iso:
http://download.cloudstack.org/cks/

Alternatively, you can also have a look at the CAPC project: 
https://cluster-api-cloudstack.sigs.k8s.io


Regards.

 



From: benoit lair 
Sent: Thursday, April 11, 2024 14:16
To: users@cloudstack.apache.org ; dev 

Subject: Re: ACS 4.16 - Change SystemVM template for CKS

Any advices ?

Best regards

Le lun. 8 avr. 2024 à 16:53, benoit lair  a écrit :

> I am opened to every alternatives of changing system vm templates
> I just need to run K8s clyusters 1.28 with my CS 4.16 :)
>
> Le lun. 8 avr. 2024 à 16:52, benoit lair  a écrit :
>
>> Hello Folks,
>>
>> I am trying to install K8s cluster with community iso 1.28.4
>> I am with a ACS 4.16.0 environment
>> It seems K8S is not working out of the box with v > 1.23.3 due to
>> containerd.io version
>>
>> I would like to release a template who will work with K8s > 1.23.3 on acs
>> 4.16
>> How can i tell CS to take another system vm template, avoiding to mess
>> normal features with VR and VPC VR keeping the systemvm template issued
>> with CS 4.16 ?
>>
>> I am with XCP-NG 8.2.1 in production
>>
>> Thanks for your help or advises
>> Best regards,
>> Benoit
>>
>

Re: Repositories

[Rohit Yadav]

Hi Jimmy,

They both are largely hosting the same upstream packages with some differences.

Those on the download.cloudstack.org are built and maintained by the wider 
community largely comprising of the ACS PMC members (many of whom are ShapeBlue 
colleagues).

The ShapeBlue packages are built, maintained and hosted by the sponsoring 
(employee-owned) company and always ships full builds of CloudStack that 
includes non-oss components such as support for VMware and we also ship 
customer patches for fixes and improvements on top of upstream releases which 
can't make community release fast enough as community release processes take 
time and due diligence, but even those make upstream releases eventually (I.e. 
we don't fork CloudStack).

SB patch releases are published publicly here 
https://github.com/shapeblue/cloudstack/releases that any user can audit and 
use/benefit. ShapeBlue customers are notified privately when we ship those as 
part of our support offerings (such as SB-led proactive patches and emergency 
patches/hotfixes).

Regards.

Regards.
 



From: Jimmy Huybrechts 
Sent: Wednesday, April 10, 2024 3:03:04 PM
To: users@cloudstack.apache.org 
Subject: Repositories

Hi,

I’m wondering, as I know there are 2 repositories I know of, do they have the 
exact same packages (outside the name).

http://packages.shapeblue.com/cloudstack/upstream/debian/4.19
https://download.cloudstack.org/ubuntu jammy 4.19

--
Jimmy

Re: New PMC member: Slavka Peleva

[Rohit Yadav]

Welcome aboard Slavka!

Regards.
 



From: Kiran Chavala 
Sent: Wednesday, April 10, 2024 6:16:00 PM
To: users@cloudstack.apache.org ; 
d...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: Re: New PMC member: Slavka Peleva

Congratulations Slavka!

Regards
Kiran

From: Nicolas Vazquez 
Date: Wednesday, 10 April 2024 at 6:01 PM
To: users@cloudstack.apache.org , 
d...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: Re: New PMC member: Slavka Peleva
Congratulations Slavka!

Regards,
Nicolas Vazquez


From: Rene Peinthor 
Date: Wednesday, 10 April 2024 at 09:13
To: d...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: Re: New PMC member: Slavka Peleva
:clap: Slavka!

Cheers,
Rene

On Wed, Apr 10, 2024 at 2:04 PM Suresh Kumar Anaparti <
sureshanapa...@apache.org> wrote:

> Congratulations Slavka!
>
> Regards,
> Suresh
>
> On Wed, Apr 10, 2024 at 4:41 PM Ivet Petrova 
> wrote:
>
> > Hello all,
> >
> > The Project Management Committee (PMC) for Apache CloudStack
> > has invited Slavka Peleva to become a PMC member and we are pleased
> > to announce that they have accepted.
> >
> > Slavka has contributed in the past and has shown effort to make the
> > project run smoothly
> >
> > Please join me in congratulating Slavka!
> >
> >
> > Best regards,
> >
> >
> >
> >
> >
>

[ADVISORY] Apache CloudStack Security Releases 4.18.1.1 and 4.19.0.1

[Rohit Yadav]

Apache CloudStack security releases 4.18.1.1 and 4.19.0.1 address the
CVEs listed below. Affected users are recommended to upgrade their
CloudStack installations.

1. CVE-2024-29006: x-forwarded-for HTTP header parsed by default

Severity: moderate

Description:

By default the CloudStack management server honours the
x-forwarded-for HTTP header and logs it as the source IP of an API
request. This could lead to authentication bypass and other
operational problems should an attacker decide to spoof their IP
address this way.

Affected versions: Apache CloudStack 4.11.0.0 through 4.18.1.0, and 4.19.0.0

Credit: Yuyang Xiao  (finder)

https://www.cve.org/CVERecord?id=CVE-2024-29006

2. CVE-2024-29007: When downloading templates or ISOs, the management
server and SSVM follow HTTP redirects with potentially dangerous
consequences

Severity: moderate

Affected versions: Apache CloudStack 4.9.1.0 through 4.18.1.0, and 4.19.0.0

Description:

The CloudStack management server and secondary storage VM could be
tricked into making requests to restricted or random resources by
means of following 301 HTTP redirects presented by external servers
when downloading templates or ISOs. Users are recommended to upgrade
to version 4.18.1.1 or 4.19.0.1, which fixes this issue.

Credit: Yuyang Xiao  (finder)

https://www.cve.org/CVERecord?id=CVE-2024-29007

3. CVE-2024-29008: The extraconfig feature can be abused to load
hypervisor resources on a VM instance

Severity: critical

Affected versions: Apache CloudStack 4.14.0.0 through 4.18.1.0, and 4.19.0.0

Description:

A problem has been identified in the CloudStack additional VM
configuration (extraconfig) feature which can be misused by anyone who
has privilege to deploy a VM instance or configure settings of an
already deployed VM instance, to configure additional VM configuration
even when the feature is not explicitly enabled by the administrator.
In a KVM based CloudStack environment, an attacker can exploit this
issue to attach host devices such as storage disks, and PCI and USB
devices such as network adapters and GPUs, in a regular VM instance
that can be further exploited to gain access to the underlying network
and storage infrastructure resources, and access any VM instance disks
on the local storage.

Credit: Wei Zhou  (finder)

https://www.cve.org/CVERecord?id=CVE-2024-29008

--

[ADVISORY] Apache CloudStack Security Releases 4.18.1.1 and 4.19.0.1

[Rohit Yadav]

Apache CloudStack security releases 4.18.1.1 and 4.19.0.1 address the
CVEs listed below. Affected users are recommended to upgrade their
CloudStack installations.

1. CVE-2024-29006: x-forwarded-for HTTP header parsed by default

Severity: moderate

Description:

By default the CloudStack management server honours the
x-forwarded-for HTTP header and logs it as the source IP of an API
request. This could lead to authentication bypass and other
operational problems should an attacker decide to spoof their IP
address this way.

Affected versions: Apache CloudStack 4.11.0.0 through 4.18.1.0, and 4.19.0.0

Credit: Yuyang Xiao  (finder)

https://www.cve.org/CVERecord?id=CVE-2024-29006

2. CVE-2024-29007: When downloading templates or ISOs, the management
server and SSVM follow HTTP redirects with potentially dangerous
consequences

Severity: moderate

Affected versions: Apache CloudStack 4.9.1.0 through 4.18.1.0, and 4.19.0.0

Description:

The CloudStack management server and secondary storage VM could be
tricked into making requests to restricted or random resources by
means of following 301 HTTP redirects presented by external servers
when downloading templates or ISOs. Users are recommended to upgrade
to version 4.18.1.1 or 4.19.0.1, which fixes this issue.

Credit: Yuyang Xiao  (finder)

https://www.cve.org/CVERecord?id=CVE-2024-29007

3. CVE-2024-29008: The extraconfig feature can be abused to load
hypervisor resources on a VM instance

Severity: critical

Affected versions: Apache CloudStack 4.14.0.0 through 4.18.1.0, and 4.19.0.0

Description:

A problem has been identified in the CloudStack additional VM
configuration (extraconfig) feature which can be misused by anyone who
has privilege to deploy a VM instance or configure settings of an
already deployed VM instance, to configure additional VM configuration
even when the feature is not explicitly enabled by the administrator.
In a KVM based CloudStack environment, an attacker can exploit this
issue to attach host devices such as storage disks, and PCI and USB
devices such as network adapters and GPUs, in a regular VM instance
that can be further exploited to gain access to the underlying network
and storage infrastructure resources, and access any VM instance disks
on the local storage.

Credit: Wei Zhou  (finder)

https://www.cve.org/CVERecord?id=CVE-2024-29008

--

Re: cloudstack 4.19 filesize mismatch

[Rohit Yadav]

Thanks for checking - could you try again, I've purged the old cdn cache. It 
should be fixed now.


Regards.

 



From: Francisco Arencibia Quesada 
Sent: Wednesday, April 3, 2024 21:55
To: users@cloudstack.apache.org 
Subject: Re: cloudstack 4.19 filesize mismatch

now are failing both 4.18 and 4.19

Regards

On Wed, Apr 3, 2024 at 6:13 PM Rohit Yadav 
wrote:

> Hi Francisco,
>
> The repo CDN is being updated, sometimes files are out of sync. Can you
> run apt-get update and try again and keep us posted if you still face the
> issue.
>
> Regards.
>
>
>
> 
> From: Francisco Arencibia Quesada 
> Sent: Wednesday, April 3, 2024 8:39:23 PM
> To: users@cloudstack.apache.org 
> Subject: cloudstack 4.19 filesize mismatch
>
> Good morning guys,
>
> I want to report an issue with deb packages for 4.19 release.
>
> Please see details below:
>
> https://pastes.io/utzcxtyako-to check all output
>
> Get:1 https://download.cloudstack.org/ubuntu jammy/4.19 all
> cloudstack-common all 4.19.0.1 [117 MB]
> Err:1 https://download.cloudstack.org/ubuntu jammy/4.19 all
> cloudstack-common all 4.19.0.1
>   File has unexpected size (116922362 != 116919496). Mirror sync in
> progress? [IP: 195.181.167.51 443]
>   Hashes of expected file:
>-
>
> SHA512:00d5571a65ef8029ce668fe2f8769326253615a282e0c6b155410460e7b3d288b062b1d434962b98b26b2be764867010c42fcf39f6ebae68b1bc7e43ea523894
>-
> SHA256:1f0805bfe95351fe30b55999235fc0e398201d1e3131ad7fd1538ef1b7a144be
>- SHA1:496ff9dffbd6299d1efa0b1c788318fbb04c57fa [weak]
>- MD5Sum:f162ade7affd9f8a5b8f358e1674f25f [weak]
>- Filesize:116919496 [weak]
> Get:2 https://download.cloudstack.org/ubuntu jammy/4.19 all
> cloudstack-management all 4.19.0.1 [1441 MB]
> Err:2 https://download.cloudstack.org/ubuntu jammy/4.19 all
> cloudstack-management all 4.19.0.1
>   File has unexpected size (1440658214 != 1440655316). Mirror sync in
> progress? [IP: 195.181.167.51 443]
>   Hashes of expected file:
>-
>
> SHA512:352a5133cc06b5ca05b097b9dce9e7d670ec89b7602729a9557f69876fe9f8dba568e0008065535c7f3daed4651a97deb18be1849e8bc64459784ba0ed9e20b3
>-
> SHA256:2f2216acda05088ec39c0157c09e0169fa9b5d30dbeb15cb074e743785f5a6ab
>- SHA1:31a04c5f4b271d7bf4cb0919293b3df0fa27e4c1 [weak]
>- MD5Sum:f8ce84b0b14e6ef64d235e78ee2a8af6 [weak]
>- Filesize:1440655316 [weak]
> E: Failed to fetch
>
> https://download.cloudstack.org/ubuntu/dists/jammy/4.19/pool/cloudstack-common_4.19.0.1_all.deb
>  File has unexpected size (116922362 != 116919496). Mirror sync in
> progress? [IP: 195.181.167.51 443]
>Hashes of expected file:
> -
>
> SHA512:00d5571a65ef8029ce668fe2f8769326253615a282e0c6b155410460e7b3d288b062b1d434962b98b26b2be764867010c42fcf39f6ebae68b1bc7e43ea523894
> -
> SHA256:1f0805bfe95351fe30b55999235fc0e398201d1e3131ad7fd1538ef1b7a144be
> - SHA1:496ff9dffbd6299d1efa0b1c788318fbb04c57fa [weak]
> - MD5Sum:f162ade7affd9f8a5b8f358e1674f25f [weak]
> - Filesize:116919496 [weak]
> E: Failed to fetch
>
> https://download.cloudstack.org/ubuntu/dists/jammy/4.19/pool/cloudstack-management_4.19.0.1_all.deb
>  File has unexpected size (1440658214 != 1440655316). Mirror sync in
> progress? [IP: 195.181.167.51 443]
>Hashes of expected file:
> -
>
> SHA512:352a5133cc06b5ca05b097b9dce9e7d670ec89b7602729a9557f69876fe9f8dba568e0008065535c7f3daed4651a97deb18be1849e8bc64459784ba0ed9e20b3
> -
> SHA256:2f2216acda05088ec39c0157c09e0169fa9b5d30dbeb15cb074e743785f5a6ab
> - SHA1:31a04c5f4b271d7bf4cb0919293b3df0fa27e4c1 [weak]
> - MD5Sum:f8ce84b0b14e6ef64d235e78ee2a8af6 [weak]
> - Filesize:1440655316 [weak]
>
> Kind regards
>
> --
> *Francisco Arencibia Quesada.*
> *DevOps Engineer*
>


--
*Francisco Arencibia Quesada.*
*DevOps Engineer*

Re: cloudstack 4.19 filesize mismatch

[Rohit Yadav]

Hi Francisco,

The repo CDN is being updated, sometimes files are out of sync. Can you run 
apt-get update and try again and keep us posted if you still face the issue.

Regards.
 



From: Francisco Arencibia Quesada 
Sent: Wednesday, April 3, 2024 8:39:23 PM
To: users@cloudstack.apache.org 
Subject: cloudstack 4.19 filesize mismatch

Good morning guys,

I want to report an issue with deb packages for 4.19 release.

Please see details below:

https://pastes.io/utzcxtyako-to check all output

Get:1 https://download.cloudstack.org/ubuntu jammy/4.19 all
cloudstack-common all 4.19.0.1 [117 MB]
Err:1 https://download.cloudstack.org/ubuntu jammy/4.19 all
cloudstack-common all 4.19.0.1
  File has unexpected size (116922362 != 116919496). Mirror sync in
progress? [IP: 195.181.167.51 443]
  Hashes of expected file:
   -
SHA512:00d5571a65ef8029ce668fe2f8769326253615a282e0c6b155410460e7b3d288b062b1d434962b98b26b2be764867010c42fcf39f6ebae68b1bc7e43ea523894
   - SHA256:1f0805bfe95351fe30b55999235fc0e398201d1e3131ad7fd1538ef1b7a144be
   - SHA1:496ff9dffbd6299d1efa0b1c788318fbb04c57fa [weak]
   - MD5Sum:f162ade7affd9f8a5b8f358e1674f25f [weak]
   - Filesize:116919496 [weak]
Get:2 https://download.cloudstack.org/ubuntu jammy/4.19 all
cloudstack-management all 4.19.0.1 [1441 MB]
Err:2 https://download.cloudstack.org/ubuntu jammy/4.19 all
cloudstack-management all 4.19.0.1
  File has unexpected size (1440658214 != 1440655316). Mirror sync in
progress? [IP: 195.181.167.51 443]
  Hashes of expected file:
   -
SHA512:352a5133cc06b5ca05b097b9dce9e7d670ec89b7602729a9557f69876fe9f8dba568e0008065535c7f3daed4651a97deb18be1849e8bc64459784ba0ed9e20b3
   - SHA256:2f2216acda05088ec39c0157c09e0169fa9b5d30dbeb15cb074e743785f5a6ab
   - SHA1:31a04c5f4b271d7bf4cb0919293b3df0fa27e4c1 [weak]
   - MD5Sum:f8ce84b0b14e6ef64d235e78ee2a8af6 [weak]
   - Filesize:1440655316 [weak]
E: Failed to fetch
https://download.cloudstack.org/ubuntu/dists/jammy/4.19/pool/cloudstack-common_4.19.0.1_all.deb
 File has unexpected size (116922362 != 116919496). Mirror sync in
progress? [IP: 195.181.167.51 443]
   Hashes of expected file:
-
SHA512:00d5571a65ef8029ce668fe2f8769326253615a282e0c6b155410460e7b3d288b062b1d434962b98b26b2be764867010c42fcf39f6ebae68b1bc7e43ea523894
-
SHA256:1f0805bfe95351fe30b55999235fc0e398201d1e3131ad7fd1538ef1b7a144be
- SHA1:496ff9dffbd6299d1efa0b1c788318fbb04c57fa [weak]
- MD5Sum:f162ade7affd9f8a5b8f358e1674f25f [weak]
- Filesize:116919496 [weak]
E: Failed to fetch
https://download.cloudstack.org/ubuntu/dists/jammy/4.19/pool/cloudstack-management_4.19.0.1_all.deb
 File has unexpected size (1440658214 != 1440655316). Mirror sync in
progress? [IP: 195.181.167.51 443]
   Hashes of expected file:
-
SHA512:352a5133cc06b5ca05b097b9dce9e7d670ec89b7602729a9557f69876fe9f8dba568e0008065535c7f3daed4651a97deb18be1849e8bc64459784ba0ed9e20b3
-
SHA256:2f2216acda05088ec39c0157c09e0169fa9b5d30dbeb15cb074e743785f5a6ab
- SHA1:31a04c5f4b271d7bf4cb0919293b3df0fa27e4c1 [weak]
- MD5Sum:f8ce84b0b14e6ef64d235e78ee2a8af6 [weak]
- Filesize:1440655316 [weak]

Kind regards

--
*Francisco Arencibia Quesada.*
*DevOps Engineer*

Re: [VOTE] Release Apache CloudStack Terraform Provider v0.5.0

[Rohit Yadav]

+1 (binding)

Tested vm deployment using 0.5.0-pre.

Regards.
 



From: Kiran Chavala 
Sent: Tuesday, April 2, 2024 2:55:40 PM
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: [VOTE] Release Apache CloudStack Terraform Provider v0.5.0

Hi ALL

I've created a CloudStack Terraform Provider v0.5.0 release, with the following 
artifacts up for a vote:

Git Branch and Commit SH:

https://github.com/cloudstack/terraform-provider-cloudstack

Commit: 7c682bf17bebf40837a30ebcca811fc7b8785a15

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

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

Vote will be open for 72 hours.

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, they can use this 0.5.0-pre build 
https://registry.terraform.io/providers/cloudstack/cloudstack/0.5.0-pre for 
testing purposes.
The binaries are here: 
https://github.com/apache/cloudstack-terraform-provider/releases/tag/v0.5.0-pre


Regards
Kiran Chavala

[ANNOUNCE] Apache CloudStack CloudMonkey v6.4.0

[Rohit Yadav]

# Apache CloudStack CloudMonkey v6.4.0 Release

Apache CloudStack, proven as one of the most scalable, free and open
source cloud computing operating system for large scale private,
public, and hybrid clouds, today announced the availability of the
latest release of Apache CloudMonkey v6.4.0, the latest version of the
turnkey enterprise Cloud orchestration platform's command line
interface tool.

Apache CloudMonkey v6.4.0 is the latest maintenance release since the
previous v6.1.0 release in July 2020. CloudMonkey v6.4.0 can be used
both as an interactive shell and as a command line tool that
simplifies CloudStack configuration and management.

The release includes the following changes:
- Improve CLI mode usage and output handling
- Add support for http POST handling for password and user-data
- Optimise async API jobs polling
- Better interrupt handling of Ctrl+C to cancel on-going API request
but not crash cmk
- Remove unnecessary call to listApis (sync) when using CLI mode with
url, api key, secret key
- Updates inbuilt API precache to ACS v4.19

## Downloads and Documentation

The official source code for CloudMonkey v6.4.0 can be downloaded from
http://cloudstack.apache.org/downloads.html

The community-maintained builds are available at the project's Github
release page at:
https://github.com/apache/cloudstack-cloudmonkey/releases/tag/6.4.0

CloudMonkey's usage details are documented at
https://github.com/apache/cloudstack-cloudmonkey/wiki

--

[VOTE][RESULT] Release Apache CloudStack CloudMonkey 6.4.0 - RC1

[Rohit Yadav]

Hi All,

The vote for CloudStack CloudMonkey v6.4.0 *passes* with 5 PMC + 1
non-PMC votes.

+1 (PMC / binding)
5 persons (Boris, Harikrishna, Lucian, Wei, Nicolas)

+1 (non binding)
1 persons (Suresh)

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. And I'll publish the Github
release as latest.

Regards,
Rohit Yadav

On Thu, 21 Mar 2024 at 16:08, Rohit Yadav  wrote:
>
> Hi All,
>
> I've created a v6.4.0 release of CloudMonkey, with the following
> artifacts up for a vote:
>
> Git Branch and commit SHA:
> https://github.com/apache/cloudstack-cloudmonkey/commit/df65df7cfe331c5af5d39743717e3d58df921a48
>
> Commit:
> df65df7cfe331c5af5d39743717e3d58df921a48
>
> GitHub pre-release (contains changelog,
> artifacts/binaries to test, checksums/usage details):
> https://github.com/apache/cloudstack-cloudmonkey/releases/tag/6.4.0
>
> Source release (checksums and signatures are available at the same location):
> https://dist.apache.org/repos/dist/dev/cloudstack/cloudmonkey-6.4.0/
>
> PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884)
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> The vote will be open until 27th March, 2024.
>
> 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 the reason why)
>
> Convenience binaries are available from here:
> https://github.com/apache/cloudstack-cloudmonkey/releases/tag/6.4.0
>
> Regards.

Re: [VOTE] Release Apache CloudStack CloudMonkey 6.4.0 - RC1

[Rohit Yadav]

All,

Reminder - cmk 6.4.0 RC1 is up for testing and voting.

Regards.
 



From: Rohit Yadav 
Sent: Thursday, March 21, 2024 4:08:29 PM
To: dev ; users 
Subject: [VOTE] Release Apache CloudStack CloudMonkey 6.4.0 - RC1

Hi All,

I've created a v6.4.0 release of CloudMonkey, with the following
artifacts up for a vote:

Git Branch and commit SHA:
https://github.com/apache/cloudstack-cloudmonkey/commit/df65df7cfe331c5af5d39743717e3d58df921a48

Commit:
df65df7cfe331c5af5d39743717e3d58df921a48

GitHub pre-release (contains changelog,
artifacts/binaries to test, checksums/usage details):
https://github.com/apache/cloudstack-cloudmonkey/releases/tag/6.4.0

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

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

The vote will be open until 27th March, 2024.

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 the reason why)

Convenience binaries are available from here:
https://github.com/apache/cloudstack-cloudmonkey/releases/tag/6.4.0

Regards.

[ANNOUNCE] New PMC Chair & VP Apache CloudStack Project - Daniel Salvador

[Rohit Yadav]

All,

It gives me great pleasure to announce that the ASF board has
accepted CloudStack PMC resolution of Daniel Augusto Veronezi Salvador as
the next PMC Chair / VP of the Apache CloudStack project.

I would like to thank everyone for the support I've received over the past
year.

Please join me in congratulating Daniel, the new CloudStack PMC Chair / VP.

Best Regards,
Rohit Yadav

[VOTE] Release Apache CloudStack CloudMonkey 6.4.0 - RC1

[Rohit Yadav]

Hi All,

I've created a v6.4.0 release of CloudMonkey, with the following
artifacts up for a vote:

Git Branch and commit SHA:
https://github.com/apache/cloudstack-cloudmonkey/commit/df65df7cfe331c5af5d39743717e3d58df921a48

Commit:
df65df7cfe331c5af5d39743717e3d58df921a48

GitHub pre-release (contains changelog,
artifacts/binaries to test, checksums/usage details):
https://github.com/apache/cloudstack-cloudmonkey/releases/tag/6.4.0

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

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

The vote will be open until 27th March, 2024.

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 the reason why)

Convenience binaries are available from here:
https://github.com/apache/cloudstack-cloudmonkey/releases/tag/6.4.0

Regards.

Re: [DISCUSS] Next cmk release

[Rohit Yadav]

All,

Since we haven't heard of any issue/feature requests and the ones in the 
current milestone are all done. I'll start a vote on this today.

https://github.com/apache/cloudstack-cloudmonkey/milestone/5

Thanks and regards.
 



From: Rohit Yadav 
Sent: Tuesday, January 30, 2024 15:06
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: [DISCUSS] Next cmk release

All,

Anybody have any feature/improvements requests and bugs to report for the next 
cmk release? (RM/release timeline yet to be discussed/determined).

Please add them here - https://github.com/apache/cloudstack-cloudmonkey/issues


Regards.

Re: [PROPOSE] RM for Cloudstack Terraform Provider

[Rohit Yadav]

All,

Update - Terraform Registry support is looking into it, meanwhile they've done 
sometime to effect trigger to have the pre/alpha build available publicly now - 
https://registry.terraform.io/providers/cloudstack/cloudstack/0.5.0-pre

Please continue testing and help report any issues/regressions at 
https://github.com/apache/cloudstack-terraform-provider/issues


Regards.

 



From: Rohit Yadav 
Sent: Friday, March 15, 2024 18:34
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: Re: [PROPOSE] RM for Cloudstack Terraform Provider

All,

Kiran is release manager for the next Terraform provider release (v0.5.0) but 
isn't a committer to have commit privileges to the upstream repo (something PMC 
can help into?).

To assist him, I've created a pre-RC (alpha) build for testing purposes and we 
encourage users to test and report regressions/bugs. The binaries are here: 
https://github.com/apache/cloudstack-terraform-provider/releases/tag/v0.5.0-pre

For some reason, Terraform registry isn't picking up the Github release from 
the 'cloudstack' org which is used because of Terraform registry's strict repo 
naming convention -
https://registry.terraform.io/providers/cloudstack/cloudstack/latest (which 
should pick release information from 
https://github.com/cloudstack/terraform-provider-cloudstack/releases/tag/v0.5.0-pre).
 I've logged a ticket with Hashicorp to look into the resync/sync issue.

In the meantime, users can use the following alpha/pre-rc builds for testing 
from:
https://registry.terraform.io/providers/shapeblue/cloudstack/latest
or, binaries from:
https://github.com/apache/cloudstack-terraform-provider/releases/tag/v0.5.0-pre

Users are welcome to report any regressions or issues here: 
https://github.com/apache/cloudstack-terraform-provider/issues


Thanks and regards,

Rohit & Kiran





From: Kiran Chavala 
Sent: Monday, March 4, 2024 17:29
To: users@cloudstack.apache.org ; 
d...@cloudstack.apache.org 
Subject: [PROPOSE] RM for Cloudstack Terraform Provider

Hi All,

Greetings

I'd like to propose and put myself forward as the release manager for v0.5.0 
release of  
cloudstack-terraform-provider(https://github.com/apache/cloudstack-terraform-provider)
  if no objections are there.


Since the last release of the cloudstack-terraform-provider (v0.4.0) was in 
2022. I am proposing to have the v0.5.0 as a quicker release.


I am also proposing the keep the scope of v0.5 release minimal and it should 
only contain minor improvements and bug fixes


Regarding timeline for the v0.5.0 release, I am targeting it by March 25th 2024.

We can have a alpha release of v0.5.0 by March 18th 2024 which allows the 
community users to test and report any issues.


After the v0.5 release we can spend some more time on adding new features and 
improvements to the cloudstack-terraform-provider and do a proper release of 
v0.6.0 in the coming months


Please ping me (@kiranchavala) on GitHub, in case you want to include any 
Issue/PR in the v0.5.0 release.

Please let me know if you have any thoughts/comments.



[1] 
https://github.com/apache/cloudstack-terraform-provider/compare/v0.4.0...main

[2] https://github.com/apache/cloudstack-terraform-provider/milestone/2

[3] https://github.com/apache/cloudstack-terraform-provider/issues





Regards
Kiran

Re: [PROPOSE] RM for Cloudstack Terraform Provider

[Rohit Yadav]

All,

Kiran is release manager for the next Terraform provider release (v0.5.0) but 
isn't a committer to have commit privileges to the upstream repo (something PMC 
can help into?).

To assist him, I've created a pre-RC (alpha) build for testing purposes and we 
encourage users to test and report regressions/bugs. The binaries are here: 
https://github.com/apache/cloudstack-terraform-provider/releases/tag/v0.5.0-pre

For some reason, Terraform registry isn't picking up the Github release from 
the 'cloudstack' org which is used because of Terraform registry's strict repo 
naming convention -
https://registry.terraform.io/providers/cloudstack/cloudstack/latest (which 
should pick release information from 
https://github.com/cloudstack/terraform-provider-cloudstack/releases/tag/v0.5.0-pre).
 I've logged a ticket with Hashicorp to look into the resync/sync issue.

In the meantime, users can use the following alpha/pre-rc builds for testing 
from:
https://registry.terraform.io/providers/shapeblue/cloudstack/latest
or, binaries from:
https://github.com/apache/cloudstack-terraform-provider/releases/tag/v0.5.0-pre

Users are welcome to report any regressions or issues here: 
https://github.com/apache/cloudstack-terraform-provider/issues


Thanks and regards,

Rohit & Kiran

 



From: Kiran Chavala 
Sent: Monday, March 4, 2024 17:29
To: users@cloudstack.apache.org ; 
d...@cloudstack.apache.org 
Subject: [PROPOSE] RM for Cloudstack Terraform Provider

Hi All,

Greetings

I'd like to propose and put myself forward as the release manager for v0.5.0 
release of  
cloudstack-terraform-provider(https://github.com/apache/cloudstack-terraform-provider)
  if no objections are there.


Since the last release of the cloudstack-terraform-provider (v0.4.0) was in 
2022. I am proposing to have the v0.5.0 as a quicker release.


I am also proposing the keep the scope of v0.5 release minimal and it should 
only contain minor improvements and bug fixes


Regarding timeline for the v0.5.0 release, I am targeting it by March 25th 2024.

We can have a alpha release of v0.5.0 by March 18th 2024 which allows the 
community users to test and report any issues.


After the v0.5 release we can spend some more time on adding new features and 
improvements to the cloudstack-terraform-provider and do a proper release of 
v0.6.0 in the coming months


Please ping me (@kiranchavala) on GitHub, in case you want to include any 
Issue/PR in the v0.5.0 release.

Please let me know if you have any thoughts/comments.



[1] 
https://github.com/apache/cloudstack-terraform-provider/compare/v0.4.0...main

[2] https://github.com/apache/cloudstack-terraform-provider/milestone/2

[3] https://github.com/apache/cloudstack-terraform-provider/issues





Regards
Kiran

Re: [VOTE] next version 20 instead of 4.20

[Rohit Yadav]

As I understand Daan's vote proposal and from the previous discussion thread, 
the current scheme that results in a release like 4.20.x.y would simply become 
20.a.b, wherein "a" is for maintenance release (counter, starting with 0) and 
"b" is only used for security releases (counter, starting with 0).

The voting thread is about "deciding to drop the 4 from our versioning scheme", 
wherein the next CloudStack version would become "20" instead of "4.20". By 
agreeing to drop the "4" I think we're effectively voting and agreeing that 
we'll not be breaking APIs. Some other opensource projects have done something 
similar too. Of course, this needs to be properly explained and documented both 
by a blog article and on the project wiki.

Paul - are you satisfied with the explanations and discussions, are you still 
blocking this vote thead or do you want to reconsider your vote?


Regards.

 



From: Paul Angus 
Sent: Tuesday, February 20, 2024 15:55
To: d...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: RE: [VOTE] next version 20 instead of 4.20

Hi Daan,


From our wiki page:

-- Quote
For those that may not be familiar with Semantic Versioning, the number format 
is: X.Y.Z, where X is the major version, Y is the minor version, Z is the patch 
number. The community strives to ensure backward API compatibility within each 
major version (i.e.: code written against the CloudStack 4.0.0-incubating API 
should work with all future 4.y.z versions). The community may decide to 
increment the major version number in situations where underlying 
implementation details require a cloud operator to face significant challenges 
in upgrading from one version to the next. This should be rare situation.

In practice, feature releases will normally be an increment of the minor 
version number of the project. Feature releases that break backward 
compatibility will cause the major version number to be incremented. Bug fix 
releases will never increment anything except the patch number.
-- End quote.


Specifically:
The community may decide to increment the major version number in situations 
where underlying implementation details require a cloud operator to face 
significant challenges in upgrading from one version to the next. This should 
be rare situation.


From this I can't see how we have broken the versioning.  Have we introduced 
anything that meets the criteria above?  Again, the term 'minor version' is an 
unfortunate one because it makes it sound like it wouldn’t contain big new 
features.  However, that isn't the case, it can and should.

Also, I'd like to see fully laid out for the next few versions, how versioning 
is proposed to work, and what each part of x.y.z.n is then going to denote.

- Paul

-Original Message-
From: Daan Hoogland 
Sent: Tuesday, February 20, 2024 10:05 AM
To: users@cloudstack.apache.org
Cc: d...@cloudstack.apache.org
Subject: Re: [VOTE] next version 20 instead of 4.20

Vivek, we could, but the main idea is that we repair our versioning system and 
make clear how we are actually dealing with our current system, which is major 
- new , possibly breaking features minor - improvements and enhancements tiny - 
urgent (security) fixes

and in addition we would go to 20 to indicate that is the follower of
4.19 not of 4. Someone may implement a new cloudstack (cloudstack5 for
instance) but this would not have anything to do with our current versioning 
system.

On Tue, Feb 20, 2024 at 5:06 AM Vivek Kumar  
wrote:
>
> Why not 5.0 ? Then it will be like 5.1, 5.2 in the future.  Just asking ..!
>
>
> > On 19-Feb-2024, at 10:49 PM, Paul Angus  wrote:
> >
> > Hi Daan,
> >
> > Can you clarify what we are actually voting on please.
> >
> > In thread that is linked I've seen:
> >
> > "[the vote] will be to adjust to the semantic versioning system."
> > - you can't go to 20 AND keep semantic versioning. The act of going to 20 
> > breaks semantic versioning [1].
> >
> > " drop the 4 at version 20 and continue as usual with minor and patch level 
> > updates as we have in the past."
> > - what's supposed to come next ? in lieu of what would have been 4.21 will 
> > it be 21 ?  is it going to be 20.1 then 20.2 ?
> >
> > From the thread and how people are referring to 'minor versions', there is 
> > a misunderstanding as to what semantic versioning means. For our project 
> > its explained here [1].   Major versions meaning "probably going to break a 
> > load of people's stuff', with minor versions not breaking stuff (at least 
> > not on purpose). So I get calling them minor versions really underplays the 
> > changes it can hold.
> >
> >
> > I'm going to stick in a -1.  Not as hard 'no' to any changes, but I think 
> > the vote should be on 'A change to the version numbering scheme' and then 
> > what is proposed properly laid out.
> >
> >
> >
> >
> > [1]   https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases 
> > (section on 

Re: /dev/sdX passthrough to vm

[Rohit Yadav]

Hi Piotr,

Is should be possible via domain XML manupulation: 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/virtualization_administration_guide/sect-virtualization-adding_storage_devices_to_guests-adding_hard_drives_and_other_block_devices_to_a_guest

I'm not sure if extraconfig can allow that though, however, you can use the 
agent hooks feature to rewrite parts of the domain XML: 
https://github.com/apache/cloudstack/blob/main/agent/conf/agent.properties#L110



Regards.

 



From: Piotr Pisz 
Sent: Saturday, March 2, 2024 15:24
To: users@cloudstack.apache.org 
Subject: /dev/sdX passthrough to vm

Hi



Is it possible to add the /dev/sdx disk from host to the VM via extra
config?

Could I ask for an example?



Regards,

Piotr

Re: [PROPOSE] RM for Cloudstack Terraform Provider

[Rohit Yadav]

Thanks for stepping up and sharing your plan.

Regards.
 



From: Suresh Kumar Anaparti 
Sent: Monday, March 4, 2024 5:36:55 PM
To: users@cloudstack.apache.org 
Cc: d...@cloudstack.apache.org 
Subject: Re: [PROPOSE] RM for Cloudstack Terraform Provider

+1, on the timelines.

Nice to see terraform provider release after a long time, thanks for
volunteering Kiran!

Regards,
Suresh

On Mon, Mar 4, 2024 at 5:30 PM Kiran Chavala 
wrote:

> Hi All,
>
> Greetings
>
> I'd like to propose and put myself forward as the release manager for
> v0.5.0 release of  cloudstack-terraform-provider(
> https://github.com/apache/cloudstack-terraform-provider)  if no
> objections are there.
>
>
> Since the last release of the cloudstack-terraform-provider (v0.4.0) was
> in 2022. I am proposing to have the v0.5.0 as a quicker release.
>
>
> I am also proposing the keep the scope of v0.5 release minimal and it
> should only contain minor improvements and bug fixes
>
>
> Regarding timeline for the v0.5.0 release, I am targeting it by March 25th
> 2024.
>
> We can have a alpha release of v0.5.0 by March 18th 2024 which allows the
> community users to test and report any issues.
>
>
> After the v0.5 release we can spend some more time on adding new features
> and improvements to the cloudstack-terraform-provider and do a proper
> release of v0.6.0 in the coming months
>
>
> Please ping me (@kiranchavala) on GitHub, in case you want to include any
> Issue/PR in the v0.5.0 release.
>
> Please let me know if you have any thoughts/comments.
>
>
>
> [1]
> https://github.com/apache/cloudstack-terraform-provider/compare/v0.4.0...main
>
> [2] https://github.com/apache/cloudstack-terraform-provider/milestone/2
>
> [3] https://github.com/apache/cloudstack-terraform-provider/issues
>
>
>
>
>
> Regards
> Kiran
>
>
>
>

Re: [PROPOSAL] version naming : drop the 4.

[Rohit Yadav]

(+ users)

All,

Generally speaking, any versioning/styling change can be perceived as a big or 
concerning change by users (those existing or new ones trying/adopting). So, we 
must get our message across properly and correctly.

I'm not for or against cosmetics change in versioning, but I'm really keen if 
we want to discuss if we can use this opportunity to streamline our LTS 
release, improve how we upgrade CloudStack (i.e relook at our DB/upgrade 
approach), make releases more linear and faster (avoid forking branches for 
example), and try to change new defaults and drop some old API/arch things 
(such as default API response type to json, but largely be backward 
compatible). Some of these suggestions may be too large an undertaking and make 
not be worth it.


Overall, I've no objections if the consensus is to drop the "4." version 
prefix. I also want to hear from our users if they've any feedback for us.


Regards.

 



From: Guto Veronezi 
Sent: Tuesday, February 13, 2024 18:34
To: d...@cloudstack.apache.org 
Subject: Re: [PROPOSAL] version naming : drop the 4.

Daan,

As we still plan to introduce disruptive changes (in a cautious and
structured way) in the major versions, all my concerns are met; I do not
have further technical reasons to keep the "4.".

Best regards,
Daniel Salvador (gutoveronezi)

On 2/12/24 11:55, Daan Hoogland wrote:
> bump,
> @Daniel Salvador is there any technical reason to keep the 4? any
> reason why there must be a 5 instead of a 21, 22 or 23? We are
> maintaining 4 number semantic versioning for no reason, as I see it.
>
> On Tue, Jan 30, 2024 at 12:02 PM Daan Hoogland  
> wrote:
>> Daniel, "technical" reasons for dropping the 4 are all in the field of
>> social engineering. In practice (as I think Wei also described) we are
>> already treating the "minor" version number as major version. Since
>> 4.0 or 4.1 (don´t remember) there has been renewed talk of a 5 , but
>> never enough reason and or commitment to make it real. We could argue
>> about it a lot.
>>
>> so
>> ¨¨¨
>> The main point is: *we have to understand the technical reasons for
>> the proposal and what we expect from it before deciding anything.
>> ¨¨¨
>> The most important point is that we expect that people understand that
>> we treat the number that now seems to be "minor" as major release
>> numbers.
>>
>>
>> On Fri, Jan 26, 2024 at 7:42 PM Wei ZHOU  wrote:
>>> Hi Daniel,
>>>
>>> If we are discussing 5.0, I would have the same concern as you.
>>> What we are discussing is dropping 4.x. The fact is, we will never release
>>> 5.0 (anyone disagree ?)
>>> In this case, the major version 4.x becomes useless.
>>> If we compare 4.20.0/4.21.0 with 20.0/21.0, it is obvious which is better.
>>> IMHO due to the similar reason, the Java version has been changed from 1.x
>>> to java 1.7/1.8 (=java 7/8) then to java 11/14/17.
>>> of course there will be some issues if semantic changes, I think it is
>>> under control.
>>>
>>>
>>>
>>> Regarding the compatibility, I think we can change the APIs gradually.
>>> I noticed the following recently when I tested VR upgrade to
>>> debian12/python3
>>>
>>> root@r-431-VM:~# python
>>> Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] on linux
>>> Type "help", "copyright", "credits" or "license" for more information.
>> import cgi
>>> :1: DeprecationWarning: 'cgi' is deprecated and slated for removal
>>> in Python 3.13
>>>
>>> For the API changes you mentioned, we could try the similar
>>> - in version X, add new APIs, mark the old APIs as deprecated
>>> - tell users the old APIs will be removed in version Y, please use new APIs
>>> instead.
>>> - in version Y, remove the old APIs.
>>>
>>> This can be done in each major/minor release. No need to wait for 5.0.
>>>
>>>
>>> -Wei
>>>
>>> On Fri, 26 Jan 2024 at 18:51, Guto Veronezi  wrote:
>>>
 Exactly, so you understand now why we must discuss what we intend.
 Although, incompatibilities are needed sometimes so we can evolve,
 leaving old ways and deprecated technologies and techniques in the past.

 *The main point is: *we have to understand the technical reasons for the
 proposal and what we expect from it before deciding anything.

 Best regards,
 Daniel Salvador (gutoveronezi)



>>
>>
>> --
>> Daan
>
>

Re: [PROPOSE] RM for 4.19.1.0

[Rohit Yadav]

Thanks for volunteering Suresh. Agree as Daan has mentioned, community would 
benefit to have the 4.18.2.0 first with some gap to then have 4.19.1.0. The 
4.19.1 RC by May end or early June LGTM.

Regards.
 



From: Daan Hoogland 
Sent: Monday, February 12, 2024 5:25:44 PM
To: d...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: Re: [PROPOSE] RM for 4.19.1.0

no worries as João proposed to release 4.18.2 in march, but let's
make sure we have a good period between the two.

On Mon, Feb 12, 2024 at 12:50 PM Suresh Anaparti
 wrote:
>
> Hi All,
>
> CloudStack 4.19.0.0 is the latest LTS release. There are already some open 
> issues [1]  and pull requests [2] targeted for 4.19.1.0 [3] release.
>
> I'd like to propose and put myself forward as the release manager for 
> 4.19.1.0 if no objections there. Please ping me (@sureshanaparti) on GitHub, 
> in case you want to include any Issue/PR in 4.19.1.0.
>
> I propose to have a window of at least 8 weeks (2 months), which allows the 
> community / users to test, use 4.19.0.0 and report any issues. We can aim to 
> cut RC1 in Q2 2024 (maybe, sometime in May-2024). I'll propose the timeline 
> details soon. I hope to have your support.
>
> Please let me know if you have any thoughts/comments.
>
> [1] 
> https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.19.1.0
> [2] 
> https://github.com/apache/cloudstack/pulls?q=is%3Apr+milestone%3A4.19.1.0+is%3Aopen
> [3] https://github.com/apache/cloudstack/milestone/31
>
>
> Regards,
> Suresh
>
>
>


--
Daan

Re: Discussion: CloudStack upgrade to JRE17 and Debian12/python3

[Rohit Yadav]

Hi Wei, all,

Thanks for the thread, I've no objections to either of the options, but option2 
is preferred as Debian 11 security will EOL mid of this year. So, if not in 
4.20, eventually we'll need to migrate systemvmtemplate base OS to Debian 12 at 
some point in future.

The bigger implication for users will be doubling of their memory consumption 
in their env for VRs.


Regards.

 



From: Wei ZHOU 
Sent: Tuesday, February 6, 2024 17:33
To: dev ; users 
Subject: Discussion: CloudStack upgrade to JRE17 and Debian12/python3

Hi all,

My colleagues and I are working on upgrading CloudStack to support the more
recent JRE version, python version and Debian version for the systemvm
template.
We already have made some changes, if you are interested, please review the
pull request: https://github.com/apache/cloudstack/pull/8497

Here are what we want to achieve in CloudStack 4.20

*1. Upgrade CloudStack to run with JRE17.*

Currently we use JRE11 to build the CloudStack packages starting in 2020.
CloudStack mgmt servers/usage/kvm agents run with JRE11 as well. However,
JRE11 is EOL in September 2023 [1].
In CloudStack 4.20, we will build CloudStack using JRE11 (because old
4.17/4.18/4/19 systemvm template do not have JRE17 installed) , but enforce
user to install JRE17 on mgmt server and kvm hosts when upgrade to
CloudStack 4.20
It requires a lot of changes to build CloudStack using JRE17, so it will be
mostly like done in CloudStack 4.21 or later.


*2. Upgrade CloudStack VR to use python3*

python2 is currently used in CloudStack VR, which is already EOL in 2020
[2]. We must migrate to python3 as soon as possible.
All python scripts used in CloudStack VR will be migrated to python3.
If you use a Debian11 systemvm template (4.17/4.18/4.19), you need to
recreate or patch the System VMs and Virtual routers after upgrading to
CloudStack 4.20.
If you choose to patch a System VM and Virtual router, two packages will be
installed: python-is-python3 and python3-netaddr


*3. Upgrade CloudStack VR to Debian12*

The more recent operating system provides more features and security. This
is not urgent as Debian11 will be supported until 2026 [3].
We have tested the Debian12 systemvm templates, and found only two issues
- OpenSSL has been upgraded from 1.1.0 to 3.0 in Debian12. Some
algorithms are deprecated. We have to set "@SECLEVEL=0" in apache2 config
and "PubkeyAcceptedAlgorithms=+ssh-rsa" to sshd config to support some old
SSH keys and certificates.
- The current default memory size (256MB) of virtual routers is not big
enough. The Debian document says 780MB memory is required [4]. We have
tested that 512MB/384MB memory is enough. It also works if memory is 320MB.
But with 256MB, we got "kernel panic" when system VMs/VRs start.

The memory upgrade should not be a problem for most users. If users have
thousands of virtual routers, they might need to add more memory.
The new debian12 template might have an impact on CKS (cloudstack
kubernetes service).  Until now, we have not found any issue in our testing
with multiple hypervisors (ubuntu22/20, rocky8/alma8/ol8, alma9/ol9,
xenserver-71, vmware 67u3/70u3/80)


What's your opinion on the following two options ?

- Option 1: Upgrade to JRE17 and python3 (still use Debian11)
- Option 2: Upgrade to JRE17 and python3 and Debian12

Thank you !



[1] https://www.oracle.com/be/java/technologies/java-se-support-roadmap.html
[2] https://www.python.org/doc/sunset-python-2/
[3] https://wiki.debian.org/LTS
[4] https://www.debian.org/releases/bookworm/amd64/ch02s05.en.html

Re: new website is life

[Rohit Yadav]

Fantastic! Great to see the new website finally go live after a decade, 
congratulations everybody!


Regards.

 



From: Daan Hoogland 
Sent: Wednesday, February 7, 2024 13:52
To: dev ; users 
Subject: new website is life

People,
we brought the new website. Please all have a look at
https://cloudstack.apache.org

thanks for any feedback

--
Daan

Re: [RESULT][VOTE] Apache CloudStack 4.19.0.0

[Rohit Yadav]

Thanks Abhishek and everyone involved in the effort.

And congratulations everyone !

Regards.
 



From: Abhishek Kumar 
Sent: Friday, February 2, 2024 5:48:54 PM
To: d...@cloudstack.apache.org ; users 

Subject: [RESULT][VOTE] Apache CloudStack 4.19.0.0

Hi all,

After more than 72 hours, the vote for CloudStack 4.19.0.0 *passes* with
7 PMC + 3 non-PMC votes.

+1 (PMC / binding)
* Daan
* Rohit
* Nicolas
* Nux
* Harikrishna
* Boris
* Wei


+1 (non binding)
* Vladimir
* Pearl
* Suresh

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.

Regards,
Abhishek

Re: [VOTE] Apache CloudStack 4.19.0.0 RC4

[Rohit Yadav]

+1 (binding)

Tested 4.19.0.0 RC4 packages with EL8 (Alma Linux) + KVM using mbx.

Tested the following:

Registered new template
Registered ssh public key
Created isolated network in VM deploy form
Deployed VM as root admin
Allow egress rules for isolated network
Created PF and FW rules, was able to ssh to instance and wget/ping Internet IPs

Created normal user account
Register ssh public key
Created isolated network in VM deploy form
Deployed VM as normal user with ssh key
Allow egress rules for isolated network
Acquire new public IP and SNAT that to the VM
Created FW rules, was able to ssh to instance and wget/ping Internet IPs

Found some UI quirks, issues, but none of them are blockers. Reported them 
here: https://github.com/apache/cloudstack/issues/8576


Regards.

 



From: Abhishek Kumar 
Sent: Monday, January 29, 2024 12:28
To: users ; d...@cloudstack.apache.org 

Cc: PMC 
Subject: [VOTE] Apache CloudStack 4.19.0.0 RC4

Hi All,

I've created a 4.19.0.0 release (RC4), with the following artifacts up for
a vote:

Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.19.0.0-RC20240129T1021
Commit: 2746225b999612f156e421199e34ef8de98a3664

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

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

For testing purposes, I have uploaded the different distro packages to:
http://download.cloudstack.org/testing/4.19.0.0-RC4/

Since 4.16 the system VM template registration is no longer mandatory
before upgrading, however, it can be downloaded from here if needed:
https://download.cloudstack.org/systemvm/4.19/

The vote will be open for 72 hours.

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)

Regards,
Abhishek

[DISCUSS] Next cmk release

[Rohit Yadav]

All,

Anybody have any feature/improvements requests and bugs to report for the next 
cmk release? (RM/release timeline yet to be discussed/determined).

Please add them here - https://github.com/apache/cloudstack-cloudmonkey/issues


Regards.

 

CloudStack India User Group Meetup

[Rohit Yadav]

Dear all,

Reminder - today is the deadline for the CloudStack India User Group meetup 
CFP. The meetup is on the 23rd Feb 2024 in Hyderabad, India.

Kindly submit your talk ideas by today, or RSVP your physical attendance on the 
meetup link - 
https://www.meetup.com/india-cloudstack-user-group/events/298324389/


I look forward to meeting you all!


Thanks and regards.

 

Re: 4.19 - New Release Announcement

[Rohit Yadav]

Here's a quote you can use:

"4.19 is a fantastic release that is culmination of all our efforts from much 
of last year coming together with a ton of exciting new features and benefits 
for existing and new users such as VMware to KVM instance migration, a new 
pluggable object storage framework with support for Minio, hypervisor-agnostic 
DRS, support for VNF appliances, DR as a service with multi-zone snapshot copy, 
OAuth2, KVM ingestion, VM action scheduler, a redesigned dashboard, and much 
more!"


Regards.

 



From: Ivet Petrova 
Sent: Monday, January 29, 2024 20:52
To: users@cloudstack.apache.org 
Cc: Jamie Pell 
Subject: 4.19 - New Release Announcement

Hi all,

With Jamie we are working on creating a blog post for the new release - 4.19 to 
be ready and published immediately after the release is live, which I think 
will happen very very soon.
I would like to kindly ask for some help - can some community members send me 
some quotes about the new release, new ACS capabilities, the market dynamics, 
how we fit, etc.

Can I get some quotes for the new release announcement article please?

Best regards,

Re: [VOTE] Apache CloudStack 4.19.0.0 RC3

[Rohit Yadav]

Thanks Abhishek and all involved for your hard work - it's not uncommon to 
create multiple RCs for a major .0 release - hope to get there with the next 
one.


Regards.


From: Abhishek Kumar 
Sent: Tuesday, January 23, 2024 18:55
To: users ; d...@cloudstack.apache.org 

Cc: PMC 
Subject: Re: [VOTE] Apache CloudStack 4.19.0.0 RC3

Hi all,

We have found an issue with RC3 which would cause regression for UEFI
functionality on KVM hosts and VM deployment.
We already have a pull request to fix it,
https://github.com/apache/cloudstack/pull/8547
I'll work with contributors and cut a new RC with this fix.

Regards,
Abhishek


 

On Mon, 22 Jan 2024 at 16:27, Abhishek Kumar  wrote:

> Hi All,
>
> I've created a 4.19.0.0 release (RC3), with the following artifacts up for
> a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/tree/4.19.0.0-RC20240122T1028
> Commit: 43066e4020cf48108e6d0bb125be7d24fc2d609f
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.19.0.0/
>
> PGP release keys (signed using 65518106473A09D7AF26B384A70BD2EAA74E2866):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> For testing purposes, I have uploaded the different distro packages to:
> http://download.cloudstack.org/testing/4.19.0.0-RC3/
>
> Since 4.16 the system VM template registration is no longer mandatory
> before upgrading, however, it can be downloaded from here if needed:
> https://download.cloudstack.org/systemvm/4.19/
>
> The vote will be open for 72 hours.
>
> 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)
>
> Regards,
> Abhishek
>

Re: new website design

[Rohit Yadav]

+1 overall, but there are a few things I would consider blockers:

1.  the blog page doesn't look same as on current blog (prod).

https://cloudstack.staged.apache.org/blog (staging blog)

versus

https://cloudstack.apache.org/blog/ (current blog/prod.)

If we can fix the blog listing and the  that should be okay.

2. The colour of the buttons in some places are different shades of blue, for 
example on https://cloudstack.staged.apache.org the download/documentation 
button and scroll down, we see button with a violet/navy-blue shade. Minor css 
issue? I would expect button to match the theme, for example button colour as 
in https://cloudstack.apache.org/blog/india-user-group-2024

3. Fact check all pages, for example the staging landing says 4.18.0.0 is 
latest release and link/content around events. Before we migrate/transition, 
all data must be latest/accurate as possible.

4. Minor issue - the logo on the staging site's landing page, uses old 
dashboard, that could be replaced with what the latest/most-recent dashboard 
looks like.



Regards.


From: Sven Vogel 
Sent: Monday, January 22, 2024 18:30
To: d...@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Cc: users 
Subject: Re: new website design

+1 looks nice

Am Montag, den 01/22/2024 um 11:46 schrieb Nux:



+1 - do it.

On 2024-01-19 14:50, Daan Hoogland wrote:
> As we get no major issues on it and we already voted to have this
> design applied, is it alright to deploy this in the coming weeks?
>
> On Wed, Jan 17, 2024 at 8:31 PM Daan Hoogland
> wrote:
>>
>> devs and users,
>>
>> back in august we had a small discussion about a new website
design,
>> led by Ivet [1]. In the meanwhile Rohit had investigated using
>> docusaurus as a publishing mechanism for the site. After the last
few
>> weeks I have been working on integrating the two. The result so far
>> can be viewed on the staging site [2]
>>
>> Please all have a look and give me any feedback you may have, so we
>> can move this forward.
>>
>> [1]
https://lists.apache.org/thread/fopjc3r4hjkp9nbkj9xzoxv406rowkso
>> [2] https://cloudstack.staged.apache.org/
>>
>> --
>> Daan

 

Re: Setup Linstor Plugin for ACS

[Rohit Yadav]

Hi,

I got my rough notes here; 
https://gist.github.com/rohityadavcloud/7844bfa8cbc9586408ce3596c71caa50

And there is a guide here - 
https://linbit.com/drbd-user-guide/linstor-guide-1_0-en


Regards.


From: Technology Rss 
Sent: Tuesday, January 23, 2024 12:40
To: users@cloudstack.apache.org ; 
d...@cloudstack.apache.org 
Subject: Setup Linstor Plugin for ACS

Hello community!

I want to setup Linstorplugin for my ACS environment. Please let me know
any user experience for any issue for production uses.

Also please share any technical details for setup it.

--

*Thanks & Regards.*

*Support Admin*



*Facebook  | Twitter
 | YouTube
 | LinkedIn
*

*Address : *116/1 West Malibagh, D. I. T Road

Dhaka-1217, Bangladesh

*Mob :* +88 01716915504

*Email :* support.ad...@technologyrss.com

*Web :* www.technologyrss.com

 

Re: New committer: Alexandre Mattioli

[Rohit Yadav]

Congratulations Alex!


Regards.


From: João Jandre Paraquetti 
Sent: Friday, January 12, 2024 18:34
To: users@cloudstack.apache.org 
Subject: Re: New committer: Alexandre Mattioli

Congrats, Alexandre!

Best regards,
João Jandre

On 1/10/24 19:27, Nux wrote:
> All,
>
> The Project Management Committee (PMC) for Apache CloudStack
> has invited Alexandre Mattioli to become a committer and we are pleased
> to announce that they have accepted.
>
> Alex has been instrumental in many features present today in
> Cloudstack, with a focus on networking and VMWare:
> - IPv6 static routing
> - Edge Zones
> - Autoscaling with VR
> - VNF appliances
> - VMWare NSX support
> - Tungsten Fabric / OpenSDN
> - Backup & recovery framework
> - VLAN trunking and security policies in ESX
> and so on.
>
>
> Please join me in congratulating Alex!
>

 

Re: CloudStack India User Group (CSIUG) Meetup

[Rohit Yadav]

All,

With help from Ivet and Jamie, I'm organising the next CloudStack India User 
Group event in Hyderabad on Friday, 23rd Feb 2024. The meetup event details are 
here: https://www.meetup.com/india-cloudstack-user-group/events/298324389 (many 
thanks to Venkata and his team at Apple/Hyd who are supporting and sponsoring 
the event venue!)

We also have the CFP open here: 
https://docs.google.com/forms/d/1jqEGPG6Xf2MwR5_u0RKySkNOti-pzxvDYQBYkCAV6o0

This will be a physical event, but we're planning to livestream the event (if 
equipment/logistics would allow), so we may be joined audience online. By the 
end of the month the CFP will close, and we'll be able to publish the schedule 
in early Feb.

I'm happy to invite and encourage the community to submit your talks/ideas 
before CFP closes and to also attend the meetup in person. Please let us know 
if you have any questions.


Regards.


From: Rohit Yadav 
Sent: Tuesday, December 12, 2023 17:48
To: Apache CloudStack Marketing 
Subject: CloudStack India User Group (CSIUG) Meetup

All,





I would like to propose organising the next CSIUG meetup in India. Ours last 
one in Bangalore was very successful and some of us had to stand and get extra 
chairs in the room.

We think the next one can be in Hyderabad (Bangalore's tech-city cousin) or in 
the NCR (national capital region, such as Delhi, Gurgaon), during late Feb or 
early March 2024.

Are there others interested in these cities and want to collaborate for the 
same. I'll also start a discussion thread on our meetup page.

[1] https://www.meetup.com/india-cloudstack-user-group/


Regards.

 

Re: [PROPOSE] ACS 4.19.0.0 release

[Rohit Yadav]

Thanks Abhishek, looking forward to RC1.

Regards.

From: Abhishek Kumar 
Sent: Thursday, December 14, 2023 6:14:43 PM
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: Re: [PROPOSE] ACS 4.19.0.0 release

Hi all,

I would like to announce the code freeze now.
From now onwards, we will only accept critical/blocker issues or any 
stabilization fixes. We have over 100 open items in the 4.19.0.0 milestone [1] 
at the moment. Most of them will be moved to the next milestone.
Currently, as reported yesterday there is one blocker issue [2]. We are working 
on a fix for the same. We may also need some stabilization concerning the 
integration test.
I expect support from all of you to work towards cutting RC1 in the coming week.

Regards,
Abhishek

[1] https://github.com/apache/cloudstack/milestone/24
[2] https://github.com/apache/cloudstack/issues/8352

From: Abhishek Kumar 
Sent: 13 December 2023 18:16
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: Re: [PROPOSE] ACS 4.19.0.0 release

Hi all,

Due to some privately sent requests to postpone the code freeze, I propose 
postponing the code freeze date by a day.
Also, we already have a possible blocker [1] reported on the main branch so 
looking into getting that fixed.

I'll send an email tomorrow to announce the code freeze and will move the 
remaining open items to the next milestone.
We will still work towards cutting RC1 in the coming week.

Regards,
Abhishek

[1] https://github.com/apache/cloudstack/issues/8352



From: Abhishek Kumar 
Sent: 07 December 2023 18:02
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: Re: [PROPOSE] ACS 4.19.0.0 release

Hi all,

To update you on the status of the 4.19.0.0 milestone [1], currently, we have 
nearly 127 open items in the milestone.
Many of them have not seen any update or progress lately so we will have to 
move them out of the milestone. Also, quite a few are now just waiting for 
integration test results or in the final phase.
Based on this, I would like to propose,

  *
Code freeze on the main branch starting 13 Dec 2023, accepting only 
critical/blocker issues (if any)
  *   Cut RC1 in the week of 18-24 Dec 2023

Please let me know your thoughts.

Also, if you have a PR/issue marked for the 4.19.0.0/4.18.2 milestone please 
keep an eye on any updates on it.
Some of us have also got our feature/improvements already merged but 
documentation for the same is still pending so kindly make sure to progress on 
that.

Regards,
Abhishek

[1] https://github.com/apache/cloudstack/milestone/24


From: Abhishek Kumar 
Sent: 21 November 2023 17:11
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: Re: [PROPOSE] ACS 4.19.0.0 release

Hi all,

Thanks a lot Daan for cleaning up the 4.19.0.0 milestone [1].
Now we have around 123 open items in the milestone. We still have some 
interesting features and enhancements in progress.
In addition to this, we are seeing some recurring test failures on the PRs 
including health-check which would need some work.
Also, rest of this week a lot of us will be busy with CloudStack Collab 2023.
Considering these I propose moving the timeline to the following,

  *   Announce code freeze in early December 2023
  *   Cut RC1 thereafter in the first half of December 2023

Thank you for your understanding and support. Looking forward to meeting 
community folks in person in the next few days.


Regards,
Abhishek

[1] https://github.com/apache/cloudstack/milestone/24

From: Daan Hoogland 
Sent: 10 November 2023 15:22
To: d...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: Re: [PROPOSE] ACS 4.19.0.0 release

After consulting with Abhishek I have started to move PRs and issues out of
the 4.19 and 4.18.2 milestones. I think we are not going to make the dates
mentioned anyway but want to reduce the delay as much as possible.

Please be responsive on your PRs and issues if you want them in, I will not
touch the milestones of any item that has had activity in the last week.

hope you all forgive me one day,

On Thu, Oct 26, 2023 at 12:50 PM Abhishek Kumar <
abhishek.ku...@shapeblue.com> wrote:

> Hi all,
>
> Update on the current state of the 4.19.0.0 milestone. Currently, there
> are still 179 open items in the 4.19.0.0 milestone [1]. We still have many
> exciting new features which need some work in the form code-changes or
> review and testing.
> Also, there are some issues and PRs in 4.18.2.0 milestone [2] which are
> marked major in severity.
> Based on this I would like to propose moving the earlier suggested
> timeline further and the revised timeline can be,
>
> - Announce code freeze around mid of the next month, November 2023
> - RC1 can be expected thereafter in the second half of November 2023
>
> If you have got an active PR 

Re: new committer Vladimir Petrov

[Rohit Yadav]

Congratulations and well done Vladi !



Regards.


From: Nux 
Sent: Tuesday, December 12, 2023 15:27
To: users@cloudstack.apache.org 
Cc: dev 
Subject: Re: new committer Vladimir Petrov

Well done, Vladi! :)

On 2023-12-12 09:52, Daan Hoogland wrote:
> community,
>
> The PMC has decided Vladi to become a committer and he has gracefully
> accepted. Please join me in welcoming Vladi to the project as
> committer.
> Congratulations Vladi

 

Re: [VOTE] Adopt Github Discusssions as Users Forum

[Rohit Yadav]

Update - Github Discussions is enabled now for apache/cloudstack repository. 
Some of us have tested to find the Github Dicussions updates are synchronised 
from Github to the users mailing list only (similar to issues and pull 
requests).

You're all welcome to try it here, or start new discussions:
https://github.com/apache/cloudstack/discussions/8343


Regards.


From: Rohit Yadav 
Sent: Monday, December 11, 2023 14:50
To: d...@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: Re: [VOTE] Adopt Github Discusssions as Users Forum

The motion passes with the following votes:

5votes: +1 (binding) - Wei, Bobby, Abhishek, Nicolas, Sven
3 votes: +1 (non-binding) Sina, Suresh, Pearl
1 vote: +0: Daan
2 votes: -0: Lucian, Wido

0 votes: -1 (binding & non-binding)


I'll work with ASF-infra to get the feature enabled in Github and let's start 
to try this.


If for any reasons it doesn't work out, we'll also have an option to get it 
removed. I encourage all PMCs and community at large to exchange feedback on 
this (on our mailing lists). Thank you all for your participation and voting.


Regards.


From: Pearl d'Silva 
Sent: Friday, December 8, 2023 22:21
To: d...@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: Re: [VOTE] Adopt Github Discusssions as Users Forum

+1

Regards,
Pearl Dsilva


From: Rohit Yadav 
Sent: December 4, 2023 3:01 AM
To: d...@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: [VOTE] Adopt Github Discusssions as Users Forum

All,

Following the discussion thread on adopting Github Discussions as users forum 
[1], I put the following proposal for a vote:


  1.  Adopt and use Github Discussions as user forums.
  2.  The Github Discussions feature is tied with the 
users@cloudstack.apache.org mailing list (PR: 
https://github.com/apache/cloudstack/pull/8274).
  3.  Any project governance and decision-making thread such as voting, 
releases etc. should continue to use the project mailing lists.

Vote will be open for 120 hours (by Friday, 8th Dec).

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)

[1] https://lists.apache.org/thread/hs0295hw9rnmhoh9l2qo5hc4b62hhvk8


Regards.










 

Re: [D] Test Discussion [cloudstack]

[Rohit Yadav]

Confirm - messages from Github Discussions end up on mailing list, but it's not 
two-way sync'd from users mailing list to Github.


Regards.


From: Nux 
Sent: Monday, December 11, 2023 17:22
To: users@cloudstack.apache.org 
Cc: NuxRo (via GitHub) 
Subject: Re: [D] Test Discussion [cloudstack]

test reply

On 2023-12-11 11:52, NuxRo wrote:
> GitHub user NuxRo added a comment to the discussion: Test Discussion
>
> yo
>
> GitHub link:
> https://github.com/apache/cloudstack/discussions/8344#discussioncomment-7818945
>
> 
> This is an automatically sent email for users@cloudstack.apache.org.
> To unsubscribe, please send an email to:
> users-unsubscr...@cloudstack.apache.org

 

Re: [VOTE] Adopt Github Discusssions as Users Forum

[Rohit Yadav]

The motion passes with the following votes:

5votes: +1 (binding) - Wei, Bobby, Abhishek, Nicolas, Sven
3 votes: +1 (non-binding) Sina, Suresh, Pearl
1 vote: +0: Daan
2 votes: -0: Lucian, Wido

0 votes: -1 (binding & non-binding)


I'll work with ASF-infra to get the feature enabled in Github and let's start 
to try this.


If for any reasons it doesn't work out, we'll also have an option to get it 
removed. I encourage all PMCs and community at large to exchange feedback on 
this (on our mailing lists). Thank you all for your participation and voting.


Regards.


From: Pearl d'Silva 
Sent: Friday, December 8, 2023 22:21
To: d...@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: Re: [VOTE] Adopt Github Discusssions as Users Forum

+1

Regards,
Pearl Dsilva


From: Rohit Yadav 
Sent: December 4, 2023 3:01 AM
To: d...@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: [VOTE] Adopt Github Discusssions as Users Forum

All,

Following the discussion thread on adopting Github Discussions as users forum 
[1], I put the following proposal for a vote:


  1.  Adopt and use Github Discussions as user forums.
  2.  The Github Discussions feature is tied with the 
users@cloudstack.apache.org mailing list (PR: 
https://github.com/apache/cloudstack/pull/8274).
  3.  Any project governance and decision-making thread such as voting, 
releases etc. should continue to use the project mailing lists.

Vote will be open for 120 hours (by Friday, 8th Dec).

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)

[1] https://lists.apache.org/thread/hs0295hw9rnmhoh9l2qo5hc4b62hhvk8


Regards.







 

[VOTE] Adopt Github Discusssions as Users Forum

[Rohit Yadav]

All,

Following the discussion thread on adopting Github Discussions as users forum 
[1], I put the following proposal for a vote:


  1.  Adopt and use Github Discussions as user forums.
  2.  The Github Discussions feature is tied with the 
users@cloudstack.apache.org mailing list (PR: 
https://github.com/apache/cloudstack/pull/8274).
  3.  Any project governance and decision-making thread such as voting, 
releases etc. should continue to use the project mailing lists.

Vote will be open for 120 hours (by Friday, 8th Dec).

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)

[1] https://lists.apache.org/thread/hs0295hw9rnmhoh9l2qo5hc4b62hhvk8


Regards.

 

Re: new committer Bryan Lima

[Rohit Yadav]

Congratulations Bryan on becoming a committer!


Regards.


From: Daan Hoogland 
Sent: Thursday, November 30, 2023 16:37
To: users@cloudstack.apache.org 
Subject: Re: new committer Bryan Lima

excuse me everybody, and mostly Bryan, for my C technology applied.
We have invited Bryan to become  a committer and not to the PMC (yet)

On Thu, Nov 30, 2023 at 10:11 AM Jimmy Huybrechts  wrote:
>
> Congratulations Bryan!
>
> --
> Jimmy
>
> Van: Daan Hoogland 
> Datum: donderdag, 30 november 2023 om 10:07
> Aan: dev , users 
> CC: PMC 
> Onderwerp: new committer Bryan Lima
> All,
>
> The Project Management Committee (PMC) for Apache CloudStack
> has invited Bryan Lima to become a PMC member and we are pleased
> to announce that they have accepted.
>
> Bryan has contributed himself and assisted in reviewing and testing
> the work of others. He has shown to be responsive, constructive and
> pleasant to work with.
>
> please join me in congratulating Bryan
>
> --
> Daan



--
Daan

 

Re: new PMC member: Abhishek Kumar

[Rohit Yadav]

Congratulations Abhishek, well deserved!


Regards.


From: Daman Arora 
Sent: Thursday, November 23, 2023 17:46
To: d...@cloudstack.apache.org 
Cc: users 
Subject: Re: new PMC member: Abhishek Kumar

Many congrats Abhishek!

On Thu, Nov 23, 2023, 9:25 p.m. Wei ZHOU  wrote:

> Congratulations Abhishek!
>
>
>
> 在 2023年11月23日星期四，Daan Hoogland  写道：
>
> > The Project Management Committee (PMC) for Apache CloudStack
> > has invited Abhishek Kumar to become a PMC member and we are pleased
> > to announce that they have accepted.
> >
> > Abhishek has contributed in the past and has shown effort to make the
> > project run smoothly. He is also the Release Manager for the upcoming
> > 4.19 release.
> >
> > please join me in congratulating Abhishek
> >
> > --
> > Daan
> >
>

 

Re: Need Assistance with CloudStack Instance

[Rohit Yadav]

Hi Punitha,

Thanks for sharing your testing and raising the issue. It's likely live storage 
migration is supported but not necessarily live VM migration with storage.


Regards.


From: Hs, Punitha 
Sent: Tuesday, November 7, 2023 21:05
To: users@cloudstack.apache.org 
Subject: RE: Need Assistance with CloudStack Instance

Hi,

There are 2 scenarios

1. Migration from one pool to other works perfectly when instance is not 
running.
2. When instance is a running
Individual volumes can be migrated without any issue.
If I perform instance migration to another host by selecting “migrate 
storage” its getting failed. Though storage pool is shared across all the KVM 
hosts.

This is the case I have raised for the same: 
https://github.com/apache/cloudstack/issues/8190

As I said I can do migration of either root/data disk separately even when VM 
is running, however if I select option "instance migration with storage" its 
giving error. Below are the steps I'm trying to achieve
select instance: click on migrate instance to another host option,
select target host and select migrate with storage option, choose 
storage and click okay.

EXPECTED RESULTS
instance should migrate to target host along with the volumes/disk migration as 
specified in the above steps.

Regards,
Punitha HS


Internal Use - Confidential
 


-Original Message-----
From: Rohit Yadav 
Sent: Tuesday, November 7, 2023 8:05 PM
To: users@cloudstack.apache.org
Subject: Re: Need Assistance with CloudStack Instance


[EXTERNAL EMAIL]

Hi Punitha,

It can depend on case-by-case basis for managed storage. For Powerflex live VM 
migration with storage between two storage pools seems to be supported as per:

https://urldefense.com/v3/__https://github.com/apache/cloudstack/pull/7408__;!!LpKI!jAqmOTlAzvlR0avgaUyh-aMePM5QvJFShB7Xxhbb840HnXMXtx98V28RduSdwqI9_4M097CNTwS33GVLMgBr-Bs$
 [github[.]com] and 
https://urldefense.com/v3/__https://docs.cloudstack.apache.org/en/4.18.1.0/adminguide/storage.html*migrating-a-instance-root-volume-to-a-new-storage-pool__;Iw!!LpKI!jAqmOTlAzvlR0avgaUyh-aMePM5QvJFShB7Xxhbb840HnXMXtx98V28RduSdwqI9_4M097CNTwS33GVLxSLjHRg$
 [docs[.]cloudstack[.]apache[.]org]

Quoting the docs: "In case of KVM and PowerFlex/ScaleIO storage, live migration 
of instance’s root disk is allowed from one PowerFlex/ScaleIO storage pool to 
another, without stopping the instance."

It could be that you've hit a limitation or even a bug. If your env matches the 
recommended and supported PowerFlex setup, then you could log an issue at 
Github.

Regards.


Internal Use - Confidential

From: Hs, Punitha 
Sent: Tuesday, November 7, 2023 16:56
To: users@cloudstack.apache.org 
Subject: RE: Need Assistance with CloudStack Instance

Hi,

I'm using PowerFlex storage.

Individually I'm able to migrate volumes from one storage pool to other pool. 
However when I select migrate storage during VM migration its giving error.

Failed to migrate VM [VM instance 
{"id":28,"instanceName":"i-2-28-VM","type":"User","uuid":"9babb438-0e57-4d1a-9551-09a17bcf8989"}]
 along with its volumes due to 
[com.cloud.utils.exception.CloudRuntimeException: Copy volume(s) to storage(s) 
[{volume: "45", from: "8", to:"7"},{volume: "44", from: "8", to:"7"}] and VM to 
host [{vm: "28", from: "9", to:"10"}] failed in 
StorageSystemDataMotionStrategy.copyAsync. Error message: [Migrating a volume 
online with KVM from managed storage is not currently supported.].].


Internal Use - Confidential



-Original Message-
From: Wei ZHOU 
Sent: Monday, November 6, 2023 10:21 PM
To: users@cloudstack.apache.org
Subject: Re: Need Assistance with CloudStack Instance


[EXTERNAL EMAIL]

Hi,

Do you use ceph ?

Can you file an issue on 
https://urldefense.com/v3/__https://github.com/apache/cloudstack/issues__;!!LpKI!jHngBIhIp1XmqveXl2VetKOyMjY5iCJ7cM9pFgj3Ec4FIfNPogBw9Sna5h7k_7fXPP2c8kQWKCQi_IenC-c$
 [github[.]com] ?

-Wei

On Mon, 6 Nov 2023 at 17:12, Hs, Punitha 
wrote:

> Hi,
>
> Thank you for the update.
>
> CloudStack version: 4.18.1.0
> Hypervisor : RHEL 8.6 with KVM
> Using shared block storage as primary storage.
>
> If I do storage migration between the storage pools when VM is running
> getting below error:
>
> Failed to migrate VM [VM instance
> {"id":16,"instanceName":"i-2-16-VM","type":"User","uuid":"3cd39dc2-1e7
> 0-4f36-8d42-4103fbe6bb34"}]
> along with its volumes due to
> [com.cloud.utils.exception.CloudRuntimeException: Copy volume(s) to
> storage(s) [{volume: "21", from: "4", to:"7"},{volume: "20", from:
> "4", to:"4&

Re: Snapshot revert is getting failed

[Rohit Yadav]

Hi Punitha,

Can you check in the logs, where this is originating from - it could be an 
issue originating from PowerFlex's side, or could be a limitation/regression in 
CloudStack. In case of snapshot using with PowerFlex, with kvm.snapshot.enabled 
and kvm.vmstoragesnapshot.enabled enabled, the volume snapshots are kept on the 
PowerFlex's side (not backed to secondary storage).

To confirm whether it's a regression you can test the supported lifecycles 
against PowerFlex version 3.5/3.6 that's been validated/tested with the current 
integration and advised in the docs: 
https://docs.cloudstack.apache.org/en/4.18.1.0/installguide/configuration.html#powerflex-plug-in


Design doc reference - 
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=158873968


Regards.


From: Hs, Punitha 
Sent: Tuesday, November 7, 2023 20:18
To: users@cloudstack.apache.org 
Subject: RE: Snapshot revert is getting failed

Hi ,

Even after stopping the VM revert is giving error "Failed to revert vm snapshot 
due to: Bad API request". Do I need to do any changes?

Note: In global setting "Kvm vmstoragesnapshot enabled" is enabled



Internal Use - Confidential
 


-Original Message-----
From: Rohit Yadav 
Sent: Tuesday, November 7, 2023 8:08 PM
To: users@cloudstack.apache.org
Subject: Re: Snapshot revert is getting failed


[EXTERNAL EMAIL]

I think volume snapshots on PowerFlex don't capture RAM - so reverting that 
should require stopping the VM. Are you able to revert volume snapshots after 
stopping the VM? Ideally this would be an issue originating from PowerFlex's 
side.


Regards.


Internal Use - Confidential

From: Hs, Punitha 
Sent: Tuesday, November 7, 2023 18:06
To: users@cloudstack.apache.org 
Subject: Snapshot revert is getting failed

Hi ,

When I try to perform snapshot revert operation when VM is not active getting 
error "Bad API request"

In logs I see below error:
failed in StorageSystemDataMotionStrategy.copyAsync. Error message: [Migrating 
a volume online with KVM from managed storage is not currently supported.].].

setup details:
version: 4.18.1.0
CloudStack managem server(VM) OS: RHEL 8.6
3 Hypervisor host: RHEL 8.6 with KVM
Basic network configuration with Shared network option is selected during zone 
configuration.
Primary storage(PowerFlex)

Could you please help me with this.

Regards,
Punitha HS

Internal Use - Confidential

Re: Snapshot revert is getting failed

[Rohit Yadav]

I think volume snapshots on PowerFlex don't capture RAM - so reverting that 
should require stopping the VM. Are you able to revert volume snapshots after 
stopping the VM? Ideally this would be an issue originating from PowerFlex's 
side.


Regards.


From: Hs, Punitha 
Sent: Tuesday, November 7, 2023 18:06
To: users@cloudstack.apache.org 
Subject: Snapshot revert is getting failed

Hi ,

When I try to perform snapshot revert operation when VM is not active getting 
error "Bad API request"

In logs I see below error:
failed in StorageSystemDataMotionStrategy.copyAsync. Error message: [Migrating 
a volume online with KVM from managed storage is not currently supported.].].

setup details:
version: 4.18.1.0
CloudStack managem server(VM) OS: RHEL 8.6
3 Hypervisor host: RHEL 8.6 with KVM
Basic network configuration with Shared network option is selected during zone 
configuration.
Primary storage(PowerFlex)

Could you please help me with this.

Regards,
Punitha HS

Internal Use - Confidential

 

Re: Need Assistance with CloudStack Instance

[Rohit Yadav]

Hi Punitha,

It can depend on case-by-case basis for managed storage. For Powerflex live VM 
migration with storage between two storage pools seems to be supported as per:

https://github.com/apache/cloudstack/pull/7408
and
https://docs.cloudstack.apache.org/en/4.18.1.0/adminguide/storage.html#migrating-a-instance-root-volume-to-a-new-storage-pool

Quoting the docs: "In case of KVM and PowerFlex/ScaleIO storage, live migration 
of instance’s root disk is allowed from one PowerFlex/ScaleIO storage pool to 
another, without stopping the instance."

It could be that you've hit a limitation or even a bug. If your env matches the 
recommended and supported PowerFlex setup, then you could log an issue at 
Github.

Regards.


From: Hs, Punitha 
Sent: Tuesday, November 7, 2023 16:56
To: users@cloudstack.apache.org 
Subject: RE: Need Assistance with CloudStack Instance

Hi,

I'm using PowerFlex storage.

Individually I'm able to migrate volumes from one storage pool to other pool. 
However when I select migrate storage during VM migration its giving error.

Failed to migrate VM [VM instance 
{"id":28,"instanceName":"i-2-28-VM","type":"User","uuid":"9babb438-0e57-4d1a-9551-09a17bcf8989"}]
 along with its volumes due to 
[com.cloud.utils.exception.CloudRuntimeException: Copy volume(s) to storage(s) 
[{volume: "45", from: "8", to:"7"},{volume: "44", from: "8", to:"7"}] and VM to 
host [{vm: "28", from: "9", to:"10"}] failed in 
StorageSystemDataMotionStrategy.copyAsync. Error message: [Migrating a volume 
online with KVM from managed storage is not currently supported.].].


Internal Use - Confidential
 


-Original Message-
From: Wei ZHOU 
Sent: Monday, November 6, 2023 10:21 PM
To: users@cloudstack.apache.org
Subject: Re: Need Assistance with CloudStack Instance


[EXTERNAL EMAIL]

Hi,

Do you use ceph ?

Can you file an issue on 
https://urldefense.com/v3/__https://github.com/apache/cloudstack/issues__;!!LpKI!jHngBIhIp1XmqveXl2VetKOyMjY5iCJ7cM9pFgj3Ec4FIfNPogBw9Sna5h7k_7fXPP2c8kQWKCQi_IenC-c$
 [github[.]com] ?

-Wei

On Mon, 6 Nov 2023 at 17:12, Hs, Punitha 
wrote:

> Hi,
>
> Thank you for the update.
>
> CloudStack version: 4.18.1.0
> Hypervisor : RHEL 8.6 with KVM
> Using shared block storage as primary storage.
>
> If I do storage migration between the storage pools when VM is running
> getting below error:
>
> Failed to migrate VM [VM instance
> {"id":16,"instanceName":"i-2-16-VM","type":"User","uuid":"3cd39dc2-1e7
> 0-4f36-8d42-4103fbe6bb34"}]
> along with its volumes due to
> [com.cloud.utils.exception.CloudRuntimeException: Copy volume(s) to
> storage(s) [{volume: "21", from: "4", to:"7"},{volume: "20", from:
> "4", to:"4"}] and VM to host [{vm: "16", from: "3", to:"9"}] failed in
> StorageSystemDataMotionStrategy.copyAsync. Error message: [Migrating a
> volume online with KVM from managed storage is not currently supported.].].
>
> Note: Both the storage pools are cluster wide and are shared
>
> Regards,
> Punitha HS
>
>
> Internal Use - Confidential
> -Original Message-
> From: Wei ZHOU 
> Sent: Monday, November 6, 2023 9:35 PM
> To: users@cloudstack.apache.org
> Subject: Re: Need Assistance with CloudStack Instance
>
>
> [EXTERNAL EMAIL]
>
> Hi,
>
> The credential of build-in CentOS 5.x template is root/password.
>
> Do you use local storage ? The live migration between hosts with local
> storage is supported in some recent releases.
> The live migration between shared storage is supported since the first
> releases.
> It would be good to share more information, for example cloudstack
> version, hypervisor type, OS distribution and version, local/shared storage.
>
> -Wei
>
>
> On Mon, 6 Nov 2023 at 15:08, Hs, Punitha 
> wrote:
>
> > Hi Team,
> >
> > I'm deploying CloudStack, with basic network configuration.
> > Appreciate if you could answer as soon as possible.
> >
> >
> > I have couple of doubts which I couldn't able to find answer in
> > document or I have missed it, so please guide me:
> >
> >
> >
> >   *   After deploying instance from existing CentOS or any other
> > registered ISO(eg: ubuntu), what will be the default credentials to
> > login to the instance.
> >   *   I tried doing live migration but its giving error to shut down the
> > instance and try it. Is b default Live migration is not possible? Or
> > planning for this in next version? Any dependency?
> >
> >
> >
> >
> >
> > Regards,
> >
> > Punitha HS
> >
> >
> >
> > Internal Use - Confidential
> >
>

Re: Usage for disks

[Rohit Yadav]

Hi Francisco,

Volumes in allocated state aren't physically created on primary storage, they 
exist only in CloudStack's database.


Regards.


From: Francisco Arencibia Quesada 
Sent: Tuesday, November 7, 2023 15:35
To: users@cloudstack.apache.org 
Subject: Usage for disks

Good morning guys,

I have a doubt with the usage metrics in disks. Cloudstack only bills disks
in ready status? What about disks in allocated status?

Kind regards



--
*Francisco Arencibia Quesada.*
*DevOps Engineer*

 

Re: Can't upload ova file format

[Rohit Yadav]

Hi,

OVA templates aren't supported for KVM. You could convert the ova/vmdk to 
qcow2/img to be able to use it with KVM.


Regards.


From: Technology Rss 
Sent: Sunday, November 5, 2023 11:25
To: users@cloudstack.apache.org ; 
d...@cloudstack.apache.org 
Subject: Can't upload ova file format

*Hi,*

My ACS version is 4.18.1.0, kvm Hypervisor, I try to upload ova format
template but I face below error.

https://prnt.sc/HeGZoHq-SQ-b

I see ova file is supported.

What can I do now? Please help me...

--

*Thanks & Regards.*

*Support Admin*



*Facebook  | Twitter
 | YouTube
 | LinkedIn
*

*Address : *116/1 West Malibagh, D. I. T Road

Dhaka-1217, Bangladesh

*Mob :* +88 01716915504

*Email :* support.ad...@technologyrss.com

*Web :* www.technologyrss.com

 

Re: KVM Backup solutions

[Rohit Yadav]

Hi Wally,

There is also Dell/EMC Networker - though I've not personally tested it.

There could also be adhoc backup strategies by using volume snapshot with 
replicated storage, or using a software defined storage (such as Ceph, Linstor 
and others) that offers some kind of replication (DR etc).


Regards.


From: Wally B 
Sent: Friday, November 3, 2023 23:04
To: users@cloudstack.apache.org 
Subject: KVM Backup solutions

Does anyone have an open source offering for KVM Backups that integrates
with CloudStack? The only thing I was able to find was Backroll; However,
it seems they are not currently integrated and the git repo seems to not
have much activity.

Thanks In advance
-Wally

 

Re: noVNC performance

[Rohit Yadav]

In case you've compared using KVM, by default the noVNC console is encrypted by 
CA framework b/w CPVM and the hypervisor host, which could induce some 
performance pressures.

Also bear in mind you may be comparing:

VM <- Proxmox vnc server -> novnc client in your browser (is this SSl enabled?)

versus

VM <- CloudStack KVM host encrypted qemu/vnc server -> vnc-over-TLS -> cpvm 
agent (reverse proxy) -> secured accessed your browser (in case of SSL enabled 
CPVM)

In the latter (case with CloudStack), there is a double encryption/decryption 
that happens on the CPVM side on both sides.


Regards.


From: Murilo Moura 
Sent: Wednesday, November 1, 2023 16:22
To: users@cloudstack.apache.org 
Subject: Re: noVNC performance

Hi Yadav!


Yes, I even made this comparison with the same server where I was running
Proxmox before. As for the client, I also accessed it from the same source
that I previously used with Proxmox noVNC.

I have the impression that there is some tuning opportunity that I haven't
found yet, given that the noVNC library is used in both projects (Proxmox &
Cloudstack), but with very different results.



On Wed, Nov 1, 2023 at 7:26 AM Rohit Yadav 
wrote:

> Hi Murilo,
>
> Have you tested/compared VNC based traffic between CloudStack VMs and
> proxmox (or others) from the same server and client locations?
>
> Depending on your env, if you've a busy console proxy you can try to
> upgrade the systemvm (CPVM) offering with more CPU (cores and speed) and
> look at the network setup.
>
> You could also explore alternatives, for example if the guest VMs have RDP
> setup/install such as in case of Windows VMs, you could use a RDP client
> such as the Microsoft remote desktop app on the client side. In my
> experience, RDP client with guest VMs have better performance and I/O
> (webcam, microphone, speaker) than compared with VNC (noVNC).
>
>
> Regards.
>
> 
> From: Murilo Moura 
> Sent: Wednesday, November 1, 2023 08:23
> To: users@cloudstack.apache.org 
> Subject: noVNC performance
>
> Is there any instruction to optimize the performance of the graphical
> console via noVNC? For virtual machines with desktop enabled, the
> performance of the noVNC console is very low.
>
> I came from experience with Proxmox and in it the noVNC console, even
> protected by SSL, is much superior. That's why I wondered if there was any
> way of tuning noVNC in ACS.
>
>
>
>

 

Re: noVNC performance

[Rohit Yadav]

Hi Murilo,

Have you tested/compared VNC based traffic between CloudStack VMs and proxmox 
(or others) from the same server and client locations?

Depending on your env, if you've a busy console proxy you can try to upgrade 
the systemvm (CPVM) offering with more CPU (cores and speed) and look at the 
network setup.

You could also explore alternatives, for example if the guest VMs have RDP 
setup/install such as in case of Windows VMs, you could use a RDP client such 
as the Microsoft remote desktop app on the client side. In my experience, RDP 
client with guest VMs have better performance and I/O (webcam, microphone, 
speaker) than compared with VNC (noVNC).


Regards.


From: Murilo Moura 
Sent: Wednesday, November 1, 2023 08:23
To: users@cloudstack.apache.org 
Subject: noVNC performance

Is there any instruction to optimize the performance of the graphical
console via noVNC? For virtual machines with desktop enabled, the
performance of the noVNC console is very low.

I came from experience with Proxmox and in it the noVNC console, even
protected by SSL, is much superior. That's why I wondered if there was any
way of tuning noVNC in ACS.

 

Re: CloudStack - TF Integration Status

[Rohit Yadav]

Hi Rohit P,

As I've shared in my earlier reply, CloudStack already supports Tungsten Fabric 
so given news on TF's website it's really up our community to discuss this 
further, propose and evaluate options.

Apart from TF, we do have alternative SDN support in CloudStack, first and 
foremost CloudStack's very own native virtual router and support for VPC, 
isolated, L2 and shared networks;  along with that, we've a bunch of network 
plugins for variety of network functions 
(https://github.com/apache/cloudstack/tree/main/plugins/network-elements) and 
an upcoming integration with VMware NSX (there's a talk proposes for CCC 
https://www.cloudstackcollab.org/#schedule and a work-in-progress pull request).

Generally speaking, as with any software project and integration dependencies, 
when there is lack of access to software or hardware and licenses (for testing, 
CI/CD) by the community, and lack of support by the vendor or users, the 
original integration may develop stability and maintenance issues longer term.


Regards.


From: Rohit Palsulkar 
Sent: Monday, October 30, 2023 16:20
To: users@cloudstack.apache.org 
Subject: Re: CloudStack - TF Integration Status

Hi Rohit,

Kindly help me with the query I have asked earlier.

"Could you please confirm if the development towards Tungsten Integration
will not happen going forward? If yes, do we have any alternatives to
Tungsten?"


On Fri, 27 Oct 2023 at 03:06, Rohit Palsulkar 
wrote:

> Thank you Stephan.
>
> Yes, Rohit Yadav
> I was referring to the *Tungsten Fabric* Website only. Wherein the
> Website's Landing page says -
>
> *"Thank you for your interest in Tungsten Fabric. The community has
> decided to shut down the project and will sunset this website on August 1,
> 2024."*
>
> Could you please confirm if the development towards Tungsten Integration
> will not happen going forward? If yes, do we have any alternatives to
> Tungsten?
>
> On Thu, 26 Oct 2023 at 19:30, Rohit Yadav 
> wrote:
>
>> Thanks Stephan, Rohit P. for the thread. I couldn't see the attached
>> screenshot which possibly got stripped from the mail (mailing lists doesn't
>> allow such attachments).
>>
>> Support for Tungsten Fabric already exists in CloudStack, but given the
>> new update on TF's website I suppose all of us in the community needs to
>> review this change and evaluate options.
>>
>>
>> Regards.
>>
>> 
>> From: Stephan Bienek 
>> Sent: Thursday, October 26, 2023 14:45
>> To: users@cloudstack.apache.org 
>> Subject: Re: CloudStack - TF Integration Status
>>
>> Rohit P. might be referring to Tungsten Fabric instead of Terraform.
>>
>> On the project website of Tungsten Fabric the project team states:
>>
>> "Thank you for your interest in Tungsten Fabric. The community has
>> decided to shut down the project and will sunset this website on August 1,
>> 2024."
>>
>> which would give the right relation to Rohit`s question of how this will
>> impact the integration with Cloudstack
>>
>> Best regards,
>> Stephan
>>
>> > Rohit Yadav  hat am 26.10.2023 10:59 CEST
>> geschrieben:
>> >
>> >
>> > Hi Rohit,
>> >
>> > Some triaging work was done last month, we hope to work towards the
>> next TF release v0.5.0 after ACS 4.19 release -
>> https://github.com/apache/cloudstack-terraform-provider/milestone/2
>> >
>> > In the meanwhile, any user efforts in testing and submitting
>> bugs/improvement requests on Github are welcome.
>> >
>> >
>> > Regards.
>> >
>> > 
>> > From: Rohit Palsulkar 
>> > Sent: Thursday, October 26, 2023 14:25
>> > To: users@cloudstack.apache.org 
>> > Subject: CloudStack - TF Integration Status
>> >
>> > Hi All,
>> >
>> > I just wanted to know the status of the CloudStack - TF Integration. Is
>> it still happening?
>> >
>> > I came across the TF Website and saw below message -
>> >
>> > [Screenshot 2023-10-26 at 2.07.48 PM.png]
>> >
>> > Kindly let us know if this will affect the ongoing development towards
>> the Integration with Cloudstack?
>> >
>> > --
>> > Regards,
>> > Rohit P
>> > [
>> https://ci3.googleusercontent.com/mail-sig/AIorK4yvCmOZqibK4B_l3XOxCFDHWF9Qo_rdu2JLbrcXZf9-hhM9s8z-Lg2J-zCpyobbFnVUAAzHtRg
>> ]
>> >
>> > This message is intended only for the use of the individual or entity
>> to which it is addressed and may contain confiden

Quotes for CloudStack Collaboration Conference 2023

[Rohit Yadav]

Dear all,

Hope you're all well.

As VP Apache CloudStack, I'm honoured to be delivering the State of
the Union talk at the CloudStack Collaboration Conference on 23rd
November 2023, in Paris. I'd love to include quotes from our
CloudStack users community. Your real-world experience and insights
would immensely showcase the impact of the opensource project, instill
confidence in the technology and promote its wider adoption.

If you're interested, could you privately share with me a few
sentences about how CloudStack has helped you and your organisation,
any unique use cases, or any challenges you've overcome. You can email
me your quotes to ro...@apache.org.

Thank you and I look forward to hearing from you as well as meeting
you at , during 23-24 Nov 2023 in Paris!

Regards,
Rohit Yadav

Re: CloudStack - TF Integration Status

[Rohit Yadav]

Thanks Stephan, Rohit P. for the thread. I couldn't see the attached screenshot 
which possibly got stripped from the mail (mailing lists doesn't allow such 
attachments).

Support for Tungsten Fabric already exists in CloudStack, but given the new 
update on TF's website I suppose all of us in the community needs to review 
this change and evaluate options.


Regards.


From: Stephan Bienek 
Sent: Thursday, October 26, 2023 14:45
To: users@cloudstack.apache.org 
Subject: Re: CloudStack - TF Integration Status

Rohit P. might be referring to Tungsten Fabric instead of Terraform.

On the project website of Tungsten Fabric the project team states:

"Thank you for your interest in Tungsten Fabric. The community has decided to 
shut down the project and will sunset this website on August 1, 2024."

which would give the right relation to Rohit`s question of how this will impact 
the integration with Cloudstack

Best regards,
Stephan

> Rohit Yadav  hat am 26.10.2023 10:59 CEST 
> geschrieben:
>
>
> Hi Rohit,
>
> Some triaging work was done last month, we hope to work towards the next TF 
> release v0.5.0 after ACS 4.19 release - 
> https://github.com/apache/cloudstack-terraform-provider/milestone/2
>
> In the meanwhile, any user efforts in testing and submitting bugs/improvement 
> requests on Github are welcome.
>
>
> Regards.
>
> 
> From: Rohit Palsulkar 
> Sent: Thursday, October 26, 2023 14:25
> To: users@cloudstack.apache.org 
> Subject: CloudStack - TF Integration Status
>
> Hi All,
>
> I just wanted to know the status of the CloudStack - TF Integration. Is it 
> still happening?
>
> I came across the TF Website and saw below message -
>
> [Screenshot 2023-10-26 at 2.07.48 PM.png]
>
> Kindly let us know if this will affect the ongoing development towards the 
> Integration with Cloudstack?
>
> --
> Regards,
> Rohit P
> [https://ci3.googleusercontent.com/mail-sig/AIorK4yvCmOZqibK4B_l3XOxCFDHWF9Qo_rdu2JLbrcXZf9-hhM9s8z-Lg2J-zCpyobbFnVUAAzHtRg]
>
> This message is intended only for the use of the individual or entity to 
> which it is addressed and may contain confidential and/or privileged 
> information. 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.

 

Re: CloudStack - TF Integration Status

[Rohit Yadav]

Hi Rohit,

Some triaging work was done last month, we hope to work towards the next TF 
release v0.5.0 after ACS 4.19 release - 
https://github.com/apache/cloudstack-terraform-provider/milestone/2

In the meanwhile, any user efforts in testing and submitting bugs/improvement 
requests on Github are welcome.


Regards.


From: Rohit Palsulkar 
Sent: Thursday, October 26, 2023 14:25
To: users@cloudstack.apache.org 
Subject: CloudStack - TF Integration Status

Hi All,

I just wanted to know the status of the CloudStack - TF Integration. Is it 
still happening?

I came across the TF Website and saw below message -

[Screenshot 2023-10-26 at 2.07.48 PM.png]

Kindly let us know if this will affect the ongoing development towards the 
Integration with Cloudstack?

--
Regards,
Rohit P
[https://ci3.googleusercontent.com/mail-sig/AIorK4yvCmOZqibK4B_l3XOxCFDHWF9Qo_rdu2JLbrcXZf9-hhM9s8z-Lg2J-zCpyobbFnVUAAzHtRg]

This message is intended only for the use of the individual or entity to which 
it is addressed and may contain confidential and/or privileged information. 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.

 

Re: CPU and Memory information in the startup dashboard

[Rohit Yadav]

Hi Murilo,

Yes indeed! A new redesigned dashboard is coming in the upcoming 4.19, you may 
check this here - https://github.com/apache/cloudstack/pull/7956


Regards.


From: Murilo Moura 
Sent: Wednesday, October 25, 2023 07:01
To: users@cloudstack.apache.org 
Subject: CPU and Memory information in the startup dashboard

Hi, everyone!


In the cloudstack roadmap, is there a plan to improve the dashboard on the
home screen? I'm referring to the RAM and CPU usage indicators (to show not
only the allocated but also the actual usage of each resource)...


Regards,

Murilo Moura

 

Re: API-driven Console Access createConsoleEndpoint

[Rohit Yadav]

Hi Swen,

The UI certainly uses the API to generate/get the URL to launch the 
web-console. However, in order to use the API, the API call must be 
authenticated.


Regards.


From: m...@swen.io 
Sent: Friday, October 20, 2023 15:35
To: users@cloudstack.apache.org 
Subject: API-driven Console Access createConsoleEndpoint

Hi,



does anybody using the new API-driven Console Access feature of Cloudstack?

https://www.shapeblue.com/api-driven-console-access/



I want to use a websocket session to send keyboard commands to the VM, but I
do not quite get it to work. I tried Postman to set up a connection, but I
get this error:

Error: Server sent a subprotocol but none was requested



I also tried https://www.piesocket.com/websocket-tester and I can establish
a connection, but I o not know how to send keyboard commands via this.



Thx for any help!



Best regards,

Swen


 

Re: Project Limits

[Rohit Yadav]

Hi Marty,

In addition to what Pearl has advised, the limits are defined in global 
settings (search for max.project or max.account) which can be overriden on per 
domain/account/project levels.


Regards.


From: Pearl d'Silva 
Sent: Saturday, September 30, 2023 03:49
To: users@cloudstack.apache.org 
Subject: Re: Project Limits

Hi Marty,

If you have a project in a domain with resource limit set greater that what the 
domain offers, then the resource limits of the domain apply within a project; 
i.e., taking your example, since the domain has a CPU limit of 20, despite the 
project having 40 CPUs as the upper limit, it will prevent creation of compute 
nodes once the 20 CPU mark (of the domain) is exceeded.

Regards,
Pearl

From: ma...@gonsource.com 
Sent: September 29, 2023 4:40 PM
To: users@cloudstack.apache.org 
Subject: Project Limits

Hello, community,



Quick question and clarification on my side. For projects, I know they have
their own resource limit settings. But is this limit technically set by the
domain? So, for example, if the domain has a limit of 20 CPUs, and the
project, in that domain, has 40 CPUs as a limit, will it stop the creation
of a compute node in the project if they hit the 20 limit or the 40 limit?



Thank you for the help.



Marty





 

Re: SAML Certificates Expired

[Rohit Yadav]

Hi Sean,

I think by default the expiry period is 10s of years. To re-generate new 
certificates, you can backup your DB and delete from the two saml related 
entries in cloud.keystore table and restart the management server(s) one by 
one. Next, you'll need to re-register the CloudStack SAML SP metadata to your 
IDP server.


Regards.


From: Sean Lair 
Sent: Friday, September 22, 2023 20:28
To: users@cloudstack.apache.org 
Subject: SAML Certificates Expired

Hi all, how are the SAML signing and encryption certificate renewals handled in 
CloudStack?  We use SAML and the certs show using the API command below just 
expired and now SAML logins don't work.  Are those supposed to auto-renew?

http://acs-server:8080/client/api?command=getSPMetadata


Thanks
Sean


 

Re: [ANNOUNCEMENT] Apache CloudStack LTS Maintenance Release 4.18.1.0

[Rohit Yadav]

Congratulations everyone on the new release, and thanks Wei and everyone 
involved in the release and voting process.


Regards.


From: Nicolas Vazquez 
Sent: Friday, September 15, 2023 20:36
To: users@cloudstack.apache.org 
Cc: Wei ZHOU 
Subject: Re: [ANNOUNCEMENT] Apache CloudStack LTS Maintenance Release 4.18.1.0

Great, thanks Wei!

Regards,
Nicolas Vazquez


On 15/9/23, 11:18, "Sina Kashipazha"  
wrote:

Congrats! Well done Wei!



--



 

- Original Message ---
On Friday, September 15th, 2023 at 3:56 PM, Nux 
mailto:n...@li.nux.ro>> wrote:


>

>

> That's amazing! Thanks, Wei!
>

>

>

> On 2023-09-15 14:44, Wei ZHOU wrote:
>

> > The Apache CloudStack project is pleased to announce the release of
> > CloudStack 4.18.1.0.
> >

> > The CloudStack 4.18.1.0 release is a maintenance release as part of
> > its 4.18.x LTS branch and contains around 200 fixes and
> > improvements since the CloudStack 4.18.0.0 release. Some of the
> > highlights include:
> >

> > - Support Managed User Data in AutoScale VM groups
> > - Support CKS (CloudStack Kubernetes Cluster) in VPC tiers
> > - Support for VMware 8.0.0.x
> > - Several Hypervisor (VMware, KVM, XenServer) fixes and improvements
> > - Several UI fixes and improvements
> > - Several Network (L2, VXLAN, etc) fixes and improvements
> > - Several System VM (CPVM, SSVM) fixes and improvements
> > - Improve Solidfire storage plugin integration on VMware
> > - Support volume migration in ScaleIO/PowerFlex within and across
> > ScaleIO/PowerFlex storage clusters
> > - Volume encryption support for StorPool
> > - Fix CloudStack upgrade with some MySQL versions
> > - Fix guest OSes and guest OS mappings in CloudStack database
> >

> > CloudStack LTS branches are supported for 18 months and will receive
> > updates for the first 12 months and only security updates in the last
> > 6 months.
> >

> > Apache CloudStack is an integrated Infrastructure-as-a-Service (IaaS)
> > software platform that allows users to build feature-rich public and
> > private cloud environments. CloudStack includes an intuitive user
> > interface and rich API for managing the compute, networking, software,
> > and storage resources. The project became an Apache top-level project
> > in March, 2013.
> >

> > More information about Apache CloudStack can be found at:
> > https://cloudstack.apache.org/
> >

> > # Documentation
> >

> > What's new in CloudStack 4.18.1.0:
> > https://docs.cloudstack.apache.org/en/4.18.1.0/releasenotes/about.html
> >

> > The 4.18.1.0 release notes include a full list of issues fixed, as
> > well as upgrade instructions from previous versions of Apache
> > CloudStack, and can be found at:
> > https://docs.cloudstack.apache.org/en/4.18.1.0/releasenotes/
> >

> > The official installation, administration, and API documentation for
> > each of the releases are available on our documentation page:
> > https://docs.cloudstack.apache.org/
> >

> > # Downloads
> >

> > The official source code for the 4.18.1.0 release can be downloaded
> > from our downloads page:
> > https://cloudstack.apache.org/downloads.html
> >

> > In addition to the official source code release, individual
> > contributors have also made convenience binaries available on the
> > Apache CloudStack download page, and can be found at:
> >

> > https://download.cloudstack.org/el/7/
> > https://download.cloudstack.org/el/8/
> > https://download.cloudstack.org/ubuntu/dists/
> > https://www.shapeblue.com/packages/

Re: GSOC 2023 Results

[Rohit Yadav]

Well done Ayush, thank you for your contribution! Looking forward to still 
seeing you around in the community even after the GSoC.


Regards.


From: Nicolas Vazquez 
Sent: Tuesday, September 12, 2023 19:40
To: users ; d...@cloudstack.apache.org 
; pandey@gmail.com 
Subject: GSOC 2023 Results

Hi all,

I’m happy to share with the community that our participation at the Google 
Summer of Code 2023 is finished with one successful project [1].

Please join me congratulating Ayush for his great work on extending the 
Import/Export Instances functionality to KVM [2]. Looking forward to seeing you 
around in the community!

[1] https://summerofcode.withgoogle.com/programs/2023/projects/f0gpheQM
[2] https://github.com/apache/cloudstack/pull/7712

Regards,
Nicolas Vazquez





 

Re: [VOTE][RESULT] Apache CloudStack 4.18.1.0 (RC3)

[Rohit Yadav]

Thanks Wei, and congratulations everyone!


Regards.


From: Wei ZHOU 
Sent: Tuesday, September 12, 2023 14:35
To: d...@cloudstack.apache.org ; users 

Subject: [VOTE][RESULT] Apache CloudStack 4.18.1.0 (RC3)

Hi all,

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

+1 (PMC / binding)
Rohit Yadav
Nux (Lucian)
Boris Stoyanov
Nicolas Vazquez
Wei Zhou

+1 (non binding)
Harikrishna Patnala

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.

-Wei



 

On Thu, 7 Sept 2023 at 10:34, Wei ZHOU  wrote:

> Hi all,
>
> I've created a 4.18.1.0-RC3, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230907T0850
> Commit: 4bdff06acd3630180f85ffe2f54add972607bbb4
>
> Source release (checksums and signatures are available at the following
> location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/
>
> PGP release keys (signed using 1503DFE7C8226103):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> Vote will be open for 72 hours.
>
> 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)
>

Re: Load Balancer in front of Console Proxy

[Rohit Yadav]

Hi Ricardo,

When using novnc, you'll need to open a few settings.
In this old thread, I've details how to setup an external nginx proxy server 
that does SSL offloading for both the novnc web service and websockets proxy:

https://www.mail-archive.com/users@cloudstack.apache.org/msg32064.html



Regards.


From: Kuasar 
Sent: Wednesday, September 6, 2023 01:04
To: users@cloudstack.apache.org 
Subject: Load Balancer in front of Console Proxy

Hi team,

On my KVM 4.18.0 ACS deploy a set a load balancer with port 80/443 with 
SystemVM console proxy as backend and I receive a 200 OK http code in response 
but the NoVNC got stuck in connecting, after a while I receive

websock.js:185 WebSocket connection to 'ws:/mydomain:8080 failed:

GET http://mydomain/resource/noVNC/app/images/error.svg 404 (Not Found)

I guess I have to open the port 8080 as well? Something is missing?


Atte,

Ricardo Pertuz



 

Re: Can I use KVM local storage for user vm

[Rohit Yadav]

Hi,

It appears you've selected the host ID c26965e6-bf5f-482e-9cff-849174f6f476 
when deploying the VM. Later in the logs it mentions:

2023-09-07 04:43:07,996 DEBUG [o.a.c.s.a.LocalStoragePoolAllocator] 
(API-Job-Executor-8:ctx-45334d86 job-14 ctx-c4c19ea4) (logid:28386839) 
LocalStoragePoolAllocator is returning null since the disk profile does not use 
local storage and bypassStorageTypeCheck is false.

And then:

No suitable pools found for volume: Vol[3|name=ROOT-3|vm=3|ROOT] under cluster: 
1

...snipped...

 Cannot deploy to specified host, returning.


Can you check if (a) you've local storage enabled for the zone and (b) there is 
local storage available from the selected host (you should see a local storage 
pool in CloudStack and it should mention a local storage uuid in the KVM host's 
/etc/cloudstack/agent/agent.properties).

If this is a test environment, you can attempt to setup again fresh.


Regards.


From: Technology Mail 
Sent: Thursday, September 7, 2023 14:17
To: Wei ZHOU ; users@cloudstack.apache.org 

Subject: Re: Can I use KVM local storage for user vm


I try to create vm using local storage zone, but not success,

See UI error > https://prnt.sc/tKSG6DR7wgw6

also see log file from attachment.

Please give me idea 

Thank you.

On 9/6/2023 2:22 PM, Wei ZHOU wrote:

Hi,

You can add kvm hosts with multiple local storages.
https://github.com/apache/cloudstack-documentation/pull/333/files

Each storage will be added as a storage pool.
You can deploy vms, migrate vms/volumes between pools.

-Wei

On Wed, 6 Sept 2023 at 09:52, Technology Mail 

wrote:



*Hi,*

My setup is AlmaLinux8, all are working fine using mgmt+nfs, but I have
8 NVME disk (every disk size 1.8TB) mount on kvm server, so I want to
use all disk as user vm storage disk separately.

*My idea is :* When setup zone then using enable local storage. But this
settings is only for one disk or all kvm server disk.

But I have 8 disk, so how to trace mgmt server my all 8 disk separately.
For example, I want 5 user vm for disk 1, another 5 user vm use disk 2,
as like another user vm disk 3...etc.

which process can I use this disk? give me some idea please ...

--

*Thanks & Regards.*

*Support Admin*



*Facebook 

 | Twitter
 | 
YouTube

 | LinkedIn
*

*Address : *116/1 West Malibagh, D. I. T Road

Dhaka-1217, Bangladesh

*Mob :* +88 01716915504

*Email :* 
support.ad...@technologyrss.com

*Web :* www.technologyrss.com






--

Thanks & Regards.

Support Admin



Facebook | 
Twitter | 
YouTube | 
LinkedIn

Address : 116/1 West Malibagh, D. I. T Road

Dhaka-1217, Bangladesh

Mob : +88 01716915504

Email : support.ad...@technologyrss.com

Web : www.technologyrss.com

 

Re: Rocky linux nuclei

[Rohit Yadav]

Hi Mariusz,

CloudStack doesn't directly manage/configure the network bridge say on KVM 
hosts or configures networking of management/usage server hosts. We assume the 
user would do that and then use mgmt/usage server or configure/add KVM hosts.

There might be suggestions in the docs/install guide, but I think nmcli can be 
used as well.


Regards.


From: Mariusz Wojtarek 
Sent: Thursday, September 7, 2023 20:09
To: users@cloudstack.apache.org 
Subject: Rocky linux nuclei


Does cloudstack supports nmcli ? or it must be network.service ?





[Support Online]

Mariusz Wojtarek

Administrator iT

P: 22 335 28 00

E: mariusz.wojta...@support-online.pl

www.support-online.pl

Poleczki 23 | 02-822 Warszawa

[cidimage005.png@01D77E41.D4CA7110]
   [cidimage007.png@01D77E41.D4CA7110] 







Support OnLine Sp. z o.o., ul. Poleczki 23, 02-822 Warszawa, NIP: 
951-20-32-692, Regon: 017431965, KRS: 078497,
XIII Wydział Gospodarczy Krajowego Rejestru Sądowego w Warszawie, Kapitał 
zakładowy: 50 000 PLN - opłacony w pełnej wysokości.
W przypadku podania w ramach niniejszej korespondencji Państwa danych 
osobowych, prosimy zapoznać się z następującą informacją 
https://www.support-online.pl/dane-osobowe
In case any of your private data was included within this conversation, please 
consult this website https://www.support-online.pl/en/personal-data

 

Re: [VOTE] Apache CloudStack 4.18.1.0 (RC3)

[Rohit Yadav]

+1 binding, have manually tested the new changes since RC2 in an adv zone KVM 
env with nfs and local storage.

Regards.

Regards.

From: Wei ZHOU 
Sent: Thursday, September 7, 2023 2:05:26 PM
To: d...@cloudstack.apache.org ; users 

Subject: Re: [VOTE] Apache CloudStack 4.18.1.0 (RC3)

Hi all,

You can find the (unofficial) packages at
http://download.cloudstack.org/testing/4.18.1.0-RC20230907T0850/ for your
convenience.

Kind regards
Wei





 

On Thu, 7 Sept 2023 at 10:34, Wei ZHOU  wrote:

> Hi all,
>
> I've created a 4.18.1.0-RC3, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230907T0850
> Commit: 4bdff06acd3630180f85ffe2f54add972607bbb4
>
> Source release (checksums and signatures are available at the following
> location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/
>
> PGP release keys (signed using 1503DFE7C8226103):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> Vote will be open for 72 hours.
>
> 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)
>

Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2)

[Rohit Yadav]

Thanks Wei.



Regards.


From: Wei ZHOU 
Sent: Wednesday, September 6, 2023 13:49
To: d...@cloudstack.apache.org ; users 

Subject: Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2)

Hi all,

Thanks a lot for your testing, Rohit, Hari, Lucian, Nicolas and Bobby.

Unfortunately Rohit found a critical issue that live migration failed
between kvm hosts with local storage pools:
https://github.com/apache/cloudstack/issues/7942
We have proposed a fix: https://github.com/apache/cloudstack/pull/7945

I will create RC3 when the fix is verified and merged. The issue impacts
kvm hosts with local storage only.

-Wei



 

On Fri, 1 Sept 2023 at 09:39, Wei ZHOU  wrote:

> Hi all,
>
> I've created a 4.18.1.0-RC2, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230901T0817
> Commit: 0e7f7d42f0ec68a360fafa7de21ea06577ed032c
>
> Source release (checksums and signatures are available at the following
> location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/
>
> PGP release keys (signed using 1503DFE7C8226103):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> Vote will be open for 72 hours.
>
> 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)
>

Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2)

[Rohit Yadav]

Wei pointed out privately to me that it's already in our docs at 
https://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-4.17.html#database-preparation

My bad, I didn't notice it earlier :)


Regards.


From: Nux 
Sent: Monday, September 4, 2023 19:44
To: d...@cloudstack.apache.org 
Cc: users 
Subject: Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2)

Cheers Rohit,

I'm for including the routines bit in the release or upgrade notes. We
haven't had such a gotcha until now, even though it's not strictly
within scope.

Regards

On 2023-09-04 14:03, Rohit Yadav wrote:
> +1 (binding)
>
> Upgraded a multi-zone (edge and core) KVM env with NFS, local storage
> and Linstor storage from 4.18.0.0 to 4.18.1.0. Post upgrade tested VM
> deployment as root admin and normal user account.
>
> I hit the issue of procedures not found as I had moved my DB from one
> host to another and didn't export the routines using mysqldump -R flag.
> I could apply them manually courtesy of Wei. I think we should document
> this that people moving their DBs must also backup/dump the routines
> (procedures), though I don't think that's a usual thing that users
> would normally do - and is outside of scope of CloudStack.
>
>
>
> Regards.
>
> 
> From: Wei ZHOU 
> Sent: Friday, September 1, 2023 13:09
> To: d...@cloudstack.apache.org ; users
> 
> Subject: [VOTE] Apache CloudStack 4.18.1.0 (RC2)
>
> Hi all,
>
> I've created a 4.18.1.0-RC2, with the following artifacts up for a
> vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230901T0817
> Commit: 0e7f7d42f0ec68a360fafa7de21ea06577ed032c
>
> Source release (checksums and signatures are available at the following
> location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/
>
> PGP release keys (signed using 1503DFE7C8226103):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> Vote will be open for 72 hours.
>
> 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)

 

Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2)

[Rohit Yadav]

+1 (binding)

Upgraded a multi-zone (edge and core) KVM env with NFS, local storage and 
Linstor storage from 4.18.0.0 to 4.18.1.0. Post upgrade tested VM deployment as 
root admin and normal user account.

I hit the issue of procedures not found as I had moved my DB from one host to 
another and didn't export the routines using mysqldump -R flag. I could apply 
them manually courtesy of Wei. I think we should document this that people 
moving their DBs must also backup/dump the routines (procedures), though I 
don't think that's a usual thing that users would normally do - and is outside 
of scope of CloudStack.



Regards.


From: Wei ZHOU 
Sent: Friday, September 1, 2023 13:09
To: d...@cloudstack.apache.org ; users 

Subject: [VOTE] Apache CloudStack 4.18.1.0 (RC2)

Hi all,

I've created a 4.18.1.0-RC2, with the following artifacts up for a vote:

Git Branch and Commit SH:
https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230901T0817
Commit: 0e7f7d42f0ec68a360fafa7de21ea06577ed032c

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

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

Vote will be open for 72 hours.

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)

 

Re: Reminder on triaging role to access and use Github better

[Rohit Yadav]

Hi Daan,

Sorry missed this email - yes we can put this somewhere on the project 
wiki/website if required or on Github's README.


Regards.


From: Daan Hoogland 
Sent: Friday, July 14, 2023 12:05
To: d...@cloudstack.apache.org ; Rohit Yadav 

Cc: users@cloudstack.apache.org 
Subject: Re: Reminder on triaging role to access and use Github better

@Rohit Yadav  is this worth mentioning on the website
somewhere?

On Tue, May 9, 2023 at 8:33 PM Rohit Yadav 
wrote:

> All,
>
> Reminder - we've ability to add frequent contributors and add them as
> collaborators [1] to our Github repos. This allows them to use project
> Github with ability to report issue with tags, and be assigned to issues
> and PRs. This is done via project repo specific .asf.yaml file.
>
> If you're a frequent contributor(s) and want to be able to add tags and be
> assigned on issues and PRs, you may share your github users ID or raise a
> Github issue. Thanks.
>
> [1]
> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-AssigningexternalcollaboratorswiththetriageroleonGitHub
>
>
> Regards.
>
>
>
>

--
Daan

 

Re: [DISCUSS] New Design for the Apache CloudStack Website

[Rohit Yadav]

Thanks Ivet, the new iterated design looks impressive especially some of the 
new graphical elements.

+1 to moving forward with the proposed design. Let's collect any further 
feedback and ideas from the community and if there are no objections go ahead 
with updating the preview/staging site (https://cloudstack.staged.apache.org/) 
and eventually publishing the website.

Just to be clear on the CMS integration - the ASF infra has declined supporting 
a 3rd party git-based CMS that can be used with the project website. This is 
such a shame as I had created PoCs with some rather okay-ist git-based CMS such 
as Netlify-CMS, TinaCMS and SpinalCMS which would give similar UI-based 
workflow like the old Roller-based blog did.

Nevertheless, for the purposes of publishing blogs the new Github-based 
document/markdown editor/CMS is fair enough and now allows uploading of assets 
(images, files etc.) and blog that can be edited directly for any committer 
incl. PMC members logged into Github and upon saving such changes the website 
is published by an automatic Github action that builds and published the 
websites. Unfortunately, any non-committer would need to follow the PR 
workflow. I had this documented at 
https://cloudstack.staged.apache.org/website-guide/ that I can help further 
update in this regard.


Regards.


From: Ivet Petrova 
Sent: Wednesday, August 30, 2023 19:04
To: Giles Sirett 
Cc: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org ; Marketing 

Subject: Re: [DISCUSS] New Design for the Apache CloudStack Website

Hi All,

I uploaded the design here: 
https://drive.google.com/file/d/1pef7xWWMPYAA5UkbS_XMUxrz53KB7J5t/view?usp=sharing


Kind regards,





 

On 30 Aug 2023, at 16:31, Giles Sirett 
mailto:giles.sir...@shapeblue.com>> wrote:

Hi Ivet – thanks for pushing forward with this – excited to review a new design.

On that note, I cant see a link in your mail ☹

Kind Regards
Giles


Giles Sirett
CEO
giles.sir...@shapeblue.com
www.shapeblue.com




From: Ivet Petrova 
mailto:ivet.petr...@shapeblue.com>>
Sent: Wednesday, August 30, 2023 10:14 AM
To: users@cloudstack.apache.org; Marketing 
mailto:market...@shapeblue.com>>
Cc: dev mailto:d...@cloudstack.apache.org>>
Subject: [DISCUSS] New Design for the Apache CloudStack Website

Hello,

I would like to start a discussion on the design of the Apache CloudStack 
Website and to propose a new design for it.

As we all know, the website has not been changed for years in terms of design 
and information. The biggest issue we know we have is that the website is not 
showing the full potential of CloudStack. In addition to it during discussions 
with many community members, I have noted the following issues:
- the existing website design is old-school
- the current homepage does not collect enough information to show CloudStack's 
strengths
- current website design is missing images from the ACS UI and cannot create a 
feel for the product in the users
- the website has issues on a mobile device
- we lack any graphic and diagrams
- some important information like how to download is not very visible

I collected a lot of feedback during last months and want to propose a new up 
to date design for the website, which is attached below. The new design will 
bring:
- improved UX
- look and feel corresponding to the CloudStack's capabilities and strengths
- more graphical elements, diagrams
- better branding
- more important information, easily accessible for the potential users

I hope you will like the new design – all feedback welcome. Once we have the 
design finalised, we will use Rohit’s proposal previously of a CMS, which is 
easy to edit.

[cid:B5517475-02DA-472A-BD1D-F3B600AD28ED]

Kind regards,

Re: [VOTE] Apache Cloudstack 4.18.1.0

[Rohit Yadav]

Thanks Wei.



Regards.


From: Wei ZHOU 
Sent: Thursday, August 31, 2023 14:27
To: d...@cloudstack.apache.org ; users 

Subject: Re: [VOTE] Apache Cloudstack 4.18.1.0

Hi all,

This vote has to be closed, as we found a critical issue that the
direct-download template cannot be registered for KVM.
Please get more information at
https://github.com/apache/cloudstack/issues/7929

-Wei



 

On Tue, 29 Aug 2023 at 09:56, Wei ZHOU  wrote:

> Hi all,
>
> I've created a 4.18.1.0-RC1, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230828T2026
> Commit: ff402faff06667e6e819eaee037400ed2005d5d2
>
> Source release (checksums and signatures are available at the following
> location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/
>
> PGP release keys (signed using 1503DFE7C8226103):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> Vote will be open for 72 hours.
>
> 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)
>

Re: Unable to add host error ACS

[Rohit Yadav]

Hi,

It appears there's something wrong in your 
/etc/cloudstack/agent/agent.properties, it can't find the passphrase to use 
cloud.jks as per:

2023-03-27 18:17:45,259 INFO  [kvm.resource.LibvirtComputingResource] 
(main:null) (logid:) Failed to find passphrase for keystore: cloud.jks

You may re-add the host, or try this workaround:


  1.  backup and then delete the cloud.* files from /etc/cloudstack/agent/ 
directory
  2.  change auth strictness global setting to false 
(ca.plugin.root.auth.strictness) in cloudstack temporarily
  3.  restart cloudstack agent on the KVM host, and once it's connected, in 
CloudStack go to the UI-> infra ->host -> select the specific host -> click 
button to re-provision certficates (this will resetup the cloud.jks and 
certificates on the kvm host)
  4.  finally, reset the ca.plugin.root.auth.strictness back to true


Regards.


From: Technology Mail 
Sent: Sunday, August 27, 2023 13:33
To: Rohit Yadav ; users@cloudstack.apache.org 
; d...@cloudstack.apache.org 

Subject: Re: Unable to add host error ACS


Now I am using 4.18, Ubuntu 20.04 server. KVM server cloud and libvirt agent 
service not start.

see error below:

Error:

++

root@kvm:~# tail -f /var/log/cloudstack/agent/agent.log
2023-03-27 18:17:43,962 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Implementation Version is 4.18.0.0
2023-03-27 18:17:43,979 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
agent.properties found at /etc/cloudstack/agent/agent.properties
2023-03-27 18:17:44,210 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Defaulting to using properties file for storage
2023-03-27 18:17:44,223 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Defaulting to the constant time backoff algorithm
2023-03-27 18:17:44,440 INFO  [cloud.utils.LogUtils] (main:null) (logid:) log4j 
configuration found at /etc/cloudstack/agent/log4j-cloud.xml
2023-03-27 18:17:44,441 INFO  [cloud.agent.AgentShell] (main:null) (logid:) 
Using default Java settings for IPv6 preference for agent connection
2023-03-27 18:17:44,951 INFO  [cloud.agent.Agent] (main:null) (logid:) id is
2023-03-27 18:17:45,018 ERROR [kvm.resource.LibvirtComputingResource] 
(main:null) (logid:) uefi properties file not found due to: Unable to find file 
uefi.properties.
2023-03-27 18:17:45,259 INFO  [kvm.resource.LibvirtComputingResource] 
(main:null) (logid:) Failed to find passphrase for keystore: cloud.jks
2023-03-27 18:17:45,280 INFO  [kvm.resource.LibvirtConnection] (main:null) 
(logid:) No existing libvirtd connection found. Opening a new one
+


Thanks.


On 6/27/2021 6:45 PM, Rohit Yadav wrote:
Thanks for sharing, glad the issue is resolved. The specific issue only affects 
4.15.0.0 and older releases, this issue is however fixed in 4.15.1.0.

After adding hosts you may actually revert the original sshd configuration.


Regards.






From: Technologyrss Mail 
<mailto:technologyrss.m...@gmail.com>
Sent: Sunday, June 27, 2021 13:03
To: Wei ZHOU <mailto:ustcweiz...@gmail.com>; 
d...@cloudstack.apache.org<mailto:d...@cloudstack.apache.org> 
<mailto:d...@cloudstack.apache.org>
Subject: Re: Unable to add host error ACS


Thank you so much!
This 3 lines add into sshd_config file and restart sshd service then solved!

PubkeyAcceptedKeyTypes=+ssh-dss
HostKeyAlgorithms=+ssh-dss
KexAlgorithms=+diffie-hellman-group1-sha1

I am always try to find out ACS properly working with latest OS with latest 
version. I have Tech blog with YouTube channel.
Always I am appropriate your help & working as previous.

---
Alamin

On 6/27/2021 1:15 PM, Wei ZHOU wrote:
Hi,

Have you tried with 
http://docs.cloudstack.apache.org/en/4.15.0.0/releasenotes/about.html#workaround-for-adding-newer-kvm-hosts
 ?

-Wei


 

On Sun, 27 Jun 2021 at 02:18, Technologyrss Mail 
mailto:technologyrss.m...@gmail.com>> wrote:

>From MGMT error log

[cid:part3.64E24953.345219EA@gmail.com]

>From KVM error log

[cid:part4.5B07A141.1406078A@gmail.com]

---Alamin

On 6/27/2021 12:24 AM, Wei ZHOU wrote:

Are you able to ssh into host using username/password ?

-Wei

On Sat, 26 Jun 2021 at 20:02, Technologyrss Mail <
technologyrss.m...@gmail.com<mailto:technologyrss.m...@gmail.com>> wrote:



Please see below error, This is from ACS MGMT log error.

2021-06-25 18:29:23,782 WARN [c.c.a.d.ParamGenericValidationWorker]
(qtp1644231115-18:ctx-ad53a30c ctx-da493b27) (logid:fc697fe9) Received
unknown parameters for command addHost. Unknown parameters : clustertype
2021-06-25 18:29:23,812 INFO  [c.c.r.ResourceManagerImpl]
(qtp1644231115-18:ctx-ad53a30c ctx-da493b27) (logid:fc697fe9) Trying to
add a new host at http://10.66.100.50 in data center 1
2021-06-25 18:29:24,034 WARN  [c.c.h.k.d.LibvirtServerDiscoverer]
(qtp1644231115-18:ctx-ad53a30c ctx-da493b27) (logid:fc697fe9) can't
setup agent, due to java.io.IOExcepti

Re: Query to Cloudstack API is degraded

[Rohit Yadav]

Hi Ricardo,

Thanks for sharing, in addition to what Simon has asked; can you also share if 
this behaviour is consistent across different types of account (root admin, 
domain admin and/or user accounts) and domains, was there any change in the 
infrastructure after which this was observed?

We've introduced a small optimisation with 
https://github.com/apache/cloudstack/pull/7911 that you've tested, this is 
coming in 4.18.1.0 and later which calls the listVirtualMachinesMetrics API 
with a limited details view, this is used to render the instance list page in 
the UI. I think most users could see 5-10x improvements in the instance page 
load times.


Regards.


From: Simon Weller 
Sent: Friday, August 25, 2023 19:18
To: users@cloudstack.apache.org 
Subject: Re: Query to Cloudstack API is degraded

Kuasar,

How big is your installation, and what do you have your MySQL
innodb_buffer_pool_size set to?

Are you running a single, or multiple management servers?

-Si


On Fri, Aug 25, 2023 at 8:43 AM Kuasar 
wrote:

> Hi Rohit,
>
> Thanks for you prompt reply.
>
> Could you say try with a MySQL 8.x?
>
> We are having this problem in production which is bigger and changing the
> db engine right now will take us weeks
>
> you could try Ubuntu 22.04/20.04
>
> Yes, we are using Ubuntu 20.04
>
> Can you measure (say using dev tools of your browser)
>
> List-vms always takes around 5.6s checking on the timing tab of the
> browser and
>
> http://:8080/client/#/vm?details=min
> http:// IP>:8080/client/#/vm?details=servoff,tmpl,nics
>
> Only 1 second, much better
>
>
> BR,
>
> Ricardo Pertuz
>
>
> On 25 Aug 2023, 6:41 AM -0500, Rohit Yadav ,
> wrote:
> > Hi Ricardo,
> >
> > Thanks for sharing. I can't say without more details on how to reproduce
> the env/condition, or look at the DB server. It might be statistics or
> something else, you could try to log mysql queries and see if they're
> slow(ing down).
> >
> > Could you say try with a MySQL 8.x server and use a different host
> server (for example, there is an issue reportedly affecting EL9 -
> https://github.com/apache/cloudstack/issues/7910; you could try Ubuntu
> 22.04/20.04 or EL8 to rule out the DB server).
> >
> > Can you measure (say using dev tools of your browser) the time it takes
> to render the list VM API call (specifically the API would be called
> listVirtualMachinesMetrics API), share the outcomes with us.
> >
> > Can you try the following URLs for the list instances page in the UI,
> see if any makes difference in loading times for you:
> >
> >
> > http://:8080/client/#/vm?details=min
> > http:// IP>:8080/client/#/vm?details=servoff,tmpl,nics
> >
> > Compared to the following that you've by default:
> >
> >
> > http://8080/client/#/vm
> >
> > I've raised a PR to explore an idea further:
> > https://github.com/apache/cloudstack/pull/7911
> >
> >
> > Regards.
> >
> > 
> > From: Kuasar 
> > Sent: Thursday, August 24, 2023 19:21
> > To: users@cloudstack.apache.org ;
> users@cloudstack.apache.org 
> > Subject: Re: Query to Cloudstack API is degraded
> >
> > Hi Rohit,
> >
> > Thanks for asking, my reply below
> >
> > - which APIs you think have degraded ->
> > listing instances
> >
> > - how have you concluded that they are degrading? ->
> > we have an upper app that has a configured timeout and it wasn’t firing,
> we had to change the value, and it is visible as well, it takes 5.6s
> bringing 5 vms.
> >
> > - are those list API or other async/action oriented APIs? ->
> > yes, it it async
> >
> > - which version of CloudStack and MySQL server is this, other details
> about your env (hypervisor, scale/size of resources etc).
> > ACS 4.18.0. —> 4GB 2Cores
> > Mariadb 10.5.x -> 4GB 2Cores
> > Hyp KVM
> >
> > - does restarting mgmt server help? any other information on how to
> reproduce this?
> > no change
> >
> > We are guessing it is related to database performance/index as it not
> happening in QA
> >
> >
> > Atte,
> >
> > Ricardo Pertuz
> >
> >
> > On 24 Aug 2023, 6:33 AM -0500, Rohit Yadav ,
> wrote:
> > > Hi Ricardo,
> > >
> > > Can you share more details, such as;
> > >
> > > - which APIs you think have degraded
> > > - how have you concluded that they are degrading?
> > > - are those list API or other async/action oriented APIs?
> > > - which version of CloudStack and MySQL server is this, othe

Re: Query to Cloudstack API is degraded

[Rohit Yadav]

Hi Ricardo,

Thanks for sharing. I can't say without more details on how to reproduce the 
env/condition, or look at the DB server. It might be statistics or something 
else, you could try to log mysql queries and see if they're slow(ing down).

Could you say try with a MySQL 8.x server and use a different host server (for 
example, there is an issue reportedly affecting EL9 - 
https://github.com/apache/cloudstack/issues/7910; you could try Ubuntu 
22.04/20.04 or EL8 to rule out the DB server).

Can you measure (say using dev tools of your browser) the time it takes to 
render the list VM API call (specifically the API would be called 
listVirtualMachinesMetrics API), share the outcomes with us.

Can you try the following URLs for the list instances page in the UI, see if 
any makes difference in loading times for you:


http://:8080/client/#/vm?details=min
http://:8080/client/#/vm?details=servoff,tmpl,nics

Compared to the following that you've by default:


http://8080/client/#/vm

I've raised a PR to explore an idea further:
https://github.com/apache/cloudstack/pull/7911


Regards.


From: Kuasar 
Sent: Thursday, August 24, 2023 19:21
To: users@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: Re: Query to Cloudstack API is degraded

Hi Rohit,

Thanks for asking, my reply below

- which APIs you think have degraded ->
 listing instances

- how have you concluded that they are degrading? ->
we have an upper app that has a configured timeout and it wasn’t 
firing, we had to change the value, and it is visible as well, it takes 5.6s 
bringing 5 vms.

- are those list API or other async/action oriented APIs? ->
 yes, it it async

- which version of CloudStack and MySQL server is this, other details about 
your env (hypervisor, scale/size of resources etc).
ACS 4.18.0.  —> 4GB 2Cores
Mariadb 10.5.x -> 4GB 2Cores
Hyp KVM

- does restarting mgmt server help? any other information on how to reproduce 
this?
no change

We are guessing it is related to database performance/index as it not happening 
in QA


Atte,

Ricardo Pertuz


On 24 Aug 2023, 6:33 AM -0500, Rohit Yadav , wrote:
> Hi Ricardo,
>
> Can you share more details, such as;
>
> - which APIs you think have degraded
> - how have you concluded that they are degrading?
> - are those list API or other async/action oriented APIs?
> - which version of CloudStack and MySQL server is this, other details about 
> your env (hypervisor, scale/size of resources etc)
> - does restarting mgmt server help? any other information on how to reproduce 
> this?
>
>
> Regards.
>
> 
> From: Kuasar 
> Sent: Wednesday, August 23, 2023 22:00
> To: users@cloudstack.apache.org 
> Subject: Query to Cloudstack API is degraded
>
> During the last weeks we have been experiencing a degrading performance in 
> API queries to Cloudstack, is there a procedure you recommend to check the 
> possible bottleneck?, we are checking database indices.
>
>
> BR,
>
> Ricardo Pertuz
>
>
>
>
>

 

Re: Query to Cloudstack API is degraded

[Rohit Yadav]

Hi Ricardo,

Can you share more details, such as;

- which APIs you think have degraded
- how have you concluded that they are degrading?
- are those list API or other async/action oriented APIs?
- which version of CloudStack and MySQL server is this, other details about 
your env (hypervisor, scale/size of resources etc)
- does restarting mgmt server help? any other information on how to reproduce 
this?


Regards.


From: Kuasar 
Sent: Wednesday, August 23, 2023 22:00
To: users@cloudstack.apache.org 
Subject: Query to Cloudstack API is degraded

During the last weeks we have been experiencing a degrading performance in API 
queries to Cloudstack, is there a procedure you recommend to check the possible 
bottleneck?, we are checking database indices.


BR,

Ricardo Pertuz



 

Re: [Consultation] Remove DB HA feature (db.ha.enabled)

[Rohit Yadav]

nently mentioned anywhere new
>>> adopters may go ahead with that on production. So I guess best to
>>> remove or at least mention that it is not production grade.
>>>
>>> Thanks
>>> Shiv
>>>
>>>
 

> On 22-Aug-2023, at 20:12, Nux  wrote:
>>>>
>>>> But what do you think of the removal of DB HA code?
>>>>
>>>> When using Galera you need to query against a single node, don't
>>>> spread the load among all 3, as this will break certain locking
>>>> functionality in Cloudstack and lead to problems.
>>>>
>>>> In a Haproxy configuration you should be keeping just one active, eg:
>>>> server galera1 10.0.3.2:3306 check
>>>> server galera2 10.0.3.3:3306 check backup
>>>> server galera3 10.0.3.4:3306 check backup
>>>>
>>>> Regards
>>>>
>>>> On 2023-08-22 15:36, K B Shiv Kumar wrote:
>>>>> We faced some issues when running Galera. We went back to master
>>>>> slave.
>>>>> Anyone using Galera in production for a long time?
>>>>> Regards,
>>>>> Shiv
>>>>>> On 22-Aug-2023, at 19:34, Nux  wrote:
>>>>>> Happy to contribute a doc on how to achieve HA if we decide to
>>>>>> remove this.
>>>>>> Thanks
>>>>>> On 2023-08-22 15:01, Rohit Yadav wrote:
>>>>>>> +1 it's a broken feature that at least doesn't work with MySQL 8.x,
>>>>>>> I'm not sure if it worked with prior versions of MySQL. However, we
>>>>>>> need to document some sort of suggested MySQL HA setup in our docs.
>>>>>>> Regards.
>>>>>>> 
>>>>>>> From: Nux 
>>>>>>> Sent: Tuesday, August 22, 2023 18:54
>>>>>>> To: users@cloudstack.apache.org ; Dev
>>>>>>> 
>>>>>>> Subject: [Consultation] Remove DB HA feature (db.ha.enabled)
>>>>>>> Hello everyone,
>>>>>>> A few weeks ago I asked you if you use or managed to use the DB HA
>>>>>>> Cloudstack feature (db.ha.enabled)[1] and after reading some of the
>>>>>>> replies and doing intensive testing myself I have found out that
>>>>>>> the
>>>>>>> feature is indeed non-functional, it's broken.
>>>>>>> In my testing I discovered DB HA can easily be done outside of
>>>>>>> Cloudstack by employing load balancers and other techniques.
>>>>>>> Personally I have achieved that by using Haproxy in front of Galera
>>>>>>> cluster, but also introduced Keepalived (vrrp) in my setup to
>>>>>>> "balance"
>>>>>>> multiple Haproxies which also worked well.
>>>>>>> As such, since the feature is basically broken, it will not be
>>>>>>> trivial
>>>>>>> to fix it and there are better ways of doing HA, then I propose to
>>>>>>> remove it altogether.
>>>>>>> Thoughts? Anyone against it?
>>>>>>> Cheers
>>>>>>> [1] -
>>>>>>>
>> https://docs.cloudstack.apache.org/en/latest/adminguide/reliability.html#database-high-availability
>>

Re: [PROPOSE] ACS 4.19.0.0 release

[Rohit Yadav]

Thanks for the proposal Abhishek, sounds good to me. Looking forward to 4.19!



Regards.


From: Abhishek Kumar 
Sent: Thursday, August 17, 2023 22:47
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: [PROPOSE] ACS 4.19.0.0 release

Hi,

Thanks all for your support on my 4.19 RM proposal thread!

I propose the following timeline for the 4.19.0.0 release. Keep in mind 
4.18.1.0 release work is also currently in progress and is being managed by Wei.

- (8 plus weeks) Ongoing – Mid-October 2023: Accept all bugs, issues, 
improvements allowed in LTS [1]
- (1 week) Stabilise the main (or 4.19) branch, accept only critical/blocker 
issues (if any)
- End October 2023 and onwards: Cut 4.19.0.0 RC1 and further RCs if necessary, 
start/conclude vote, and finish release work

I hope to get support from all active contributors during the process of 
reviewing/testing/merging the PRs. You can find the open issues and PRs at the 
4.19.0.0 Github milestone [2]. Ping me (@shwstppr) or Daan (@DaanHoogland) on 
your issues and PRs, that are to be included in 4.19.0.0.

Looking forward to your support on bug fixes, reviews, tests, etc. I'm happy to 
collaborate with others on the release management. Thanks.

[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS
[2] https://github.com/apache/cloudstack/milestone/24


Regards,
Abhishek





 

Re: [PROPOSE] ACS 4.18.1.0 release

[Rohit Yadav]

Thanks for the update Wei.


Regards.


From: Nux 
Sent: Tuesday, August 22, 2023 19:42
To: users@cloudstack.apache.org 
Cc: d...@cloudstack.apache.org 
Subject: Re: [PROPOSE] ACS 4.18.1.0 release

Thanks for the update, Wei.
Good job so far!

On 2023-08-21 12:48, Wei ZHOU wrote:
> Hi all,
>
> In the last weeks, we have merged a few bug fixes into the 4.18 branch.
> We
> are still working on remaining bug fixes and reviewing pull requests.
>
> 22 pull requests are open for review:
> https://github.com/apache/cloudstack/pulls?q=is%3Aopen+is%3Apr+milestone%3A4.18.1.0
>
> 51 issues are open (including 2 critical , 15 major, 33 minor issues):
> https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.18.1.0
>
> *The code freeze time of 4.18.1.0 will be 12:00pm UTC (1pm BST, 2pm
> CEST),
> 28th August*.  The open pull requests and issues after code freeze will
> be
> moved to 4.18.2.0 milestone.
>
> -Wei
>
>
>

 

> On Wed, 2 Aug 2023 at 03:22, Wei ZHOU  wrote:
>
>> Hi all,
>>
>> Here is an update of Apache CloudStack 4.18.1.0 release:
>>
>> There are some open PRs and issues on github:
>>
>> 37 pull requests are open for review:
>> https://github.com/apache/cloudstack/pulls?q=is%3Aopen+is%3Apr+milestone%3A4.18.1.0
>>
>> 66 issues are open (including 1 BLOCKER, 1 critical , 18 major, 39
>> minor
>> issues):
>> https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.18.1.0
>>
>>
>> We are busy with them. The processes need to be postponed for 2-4
>> weeks.
>>
>>
>> -Wei
>>
>>
>>
>>
>> On Thu, 4 May 2023 at 10:34, Wei ZHOU  wrote:
>>
>>> Hi all,
>>>
>>> Currently CloudStack 4.18.0.0 is the latest LTS release. There are
>>> some
>>> bugs and pull requests with 4.18.0.0 [1], including the fix for the
>>> upgrade
>>> issue if users use MySQL 5.6 and 5.7.
>>>
>>> I would like to propose the release of 4.18.1.0 and the timeline
>>>
>>> - from now till the end of July (3 months): accept bug fixes and
>>> minor
>>> improvements [2]
>>> - first week in Aug: stablisation efforts, accept only blocker and
>>> critical bug fixes.
>>> - Aug: start cutting RCs, vote and finish release work.
>>>
>>> I will push myself as the release manager (RM) of 4.18.1.0, if nobody
>>> objects.
>>> In case anyone wants to include a bug fix or a pull request in
>>> 4.18.1.0
>>> milestone, please mention me (weizhouapache) on github.
>>>
>>> [1] https://github.com/apache/cloudstack/milestone/27
>>> [2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS
>>>
>>>
>>> Any suggestions ?
>>>
>>> Kind regards,
>>> Wei
>>>
>>

Re: [Consultation] Remove DB HA feature (db.ha.enabled)

[Rohit Yadav]

Shiv, Lucian, all,

It's a known limitation for all available MySQL clustering solutions such as 
Galera, Percona XtraDB, Innodb Cluster that GET_LOCK [1] isn't supported 
[2][3]. The GET_LOCK is used by CloudStack for global locking critical code 
when more than one management server(s) are running against the same 
database/server.

(MySQL NDB, InnoDB cluster could be something to experiment, as well as, coming 
up with a locking service framework which could help get around the 
mysql/native get_lock limitations).

[1] 
https://dev.mysql.com/doc/refman/8.0/en/locking-functions.html#:~:text=MySQL%20enforces%20a%20maximum%20length,lock%20with%20the%20same%20name.

[2] https://mariadb.com/kb/en/mariadb-galera-cluster-known-limitations/

[3] https://docs.percona.com/percona-xtradb-cluster/8.0/limitation.html



Regards.


From: Nux 
Sent: Tuesday, August 22, 2023 20:12
To: d...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org ; K B Shiv Kumar 

Subject: Re: [Consultation] Remove DB HA feature (db.ha.enabled)

But what do you think of the removal of DB HA code?

When using Galera you need to query against a single node, don't spread
the load among all 3, as this will break certain locking functionality
in Cloudstack and lead to problems.

In a Haproxy configuration you should be keeping just one active, eg:
 server galera1 10.0.3.2:3306 check
 server galera2 10.0.3.3:3306 check backup
 server galera3 10.0.3.4:3306 check backup

Regards

On 2023-08-22 15:36, K B Shiv Kumar wrote:
> We faced some issues when running Galera. We went back to master slave.
>
> Anyone using Galera in production for a long time?
>
> Regards,
> Shiv
>
>
 

> On 22-Aug-2023, at 19:34, Nux  wrote:
>>
>> Happy to contribute a doc on how to achieve HA if we decide to remove
>> this.
>>
>> Thanks
>>
>> On 2023-08-22 15:01, Rohit Yadav wrote:
>>> +1 it's a broken feature that at least doesn't work with MySQL 8.x,
>>> I'm not sure if it worked with prior versions of MySQL. However, we
>>> need to document some sort of suggested MySQL HA setup in our docs.
>>> Regards.
>>> 
>>> From: Nux 
>>> Sent: Tuesday, August 22, 2023 18:54
>>> To: users@cloudstack.apache.org ; Dev
>>> 
>>> Subject: [Consultation] Remove DB HA feature (db.ha.enabled)
>>> Hello everyone,
>>> A few weeks ago I asked you if you use or managed to use the DB HA
>>> Cloudstack feature (db.ha.enabled)[1] and after reading some of the
>>> replies and doing intensive testing myself I have found out that the
>>> feature is indeed non-functional, it's broken.
>>> In my testing I discovered DB HA can easily be done outside of
>>> Cloudstack by employing load balancers and other techniques.
>>> Personally I have achieved that by using Haproxy in front of Galera
>>> cluster, but also introduced Keepalived (vrrp) in my setup to
>>> "balance"
>>> multiple Haproxies which also worked well.
>>> As such, since the feature is basically broken, it will not be
>>> trivial
>>> to fix it and there are better ways of doing HA, then I propose to
>>> remove it altogether.
>>> Thoughts? Anyone against it?
>>> Cheers
>>> [1] -
>>> https://docs.cloudstack.apache.org/en/latest/adminguide/reliability.html#database-high-availability

Re: [Consultation] Remove DB HA feature (db.ha.enabled)

[Rohit Yadav]

+1 it's a broken feature that at least doesn't work with MySQL 8.x, I'm not 
sure if it worked with prior versions of MySQL. However, we need to document 
some sort of suggested MySQL HA setup in our docs.


Regards.


From: Nux 
Sent: Tuesday, August 22, 2023 18:54
To: users@cloudstack.apache.org ; Dev 

Subject: [Consultation] Remove DB HA feature (db.ha.enabled)

Hello everyone,

A few weeks ago I asked you if you use or managed to use the DB HA
Cloudstack feature (db.ha.enabled)[1] and after reading some of the
replies and doing intensive testing myself I have found out that the
feature is indeed non-functional, it's broken.

In my testing I discovered DB HA can easily be done outside of
Cloudstack by employing load balancers and other techniques.
Personally I have achieved that by using Haproxy in front of Galera
cluster, but also introduced Keepalived (vrrp) in my setup to "balance"
multiple Haproxies which also worked well.

As such, since the feature is basically broken, it will not be trivial
to fix it and there are better ways of doing HA, then I propose to
remove it altogether.

Thoughts? Anyone against it?

Cheers

[1] -
https://docs.cloudstack.apache.org/en/latest/adminguide/reliability.html#database-high-availability

 

[DISCUSS] Simplifying constructs and UX

[Rohit Yadav]

All,

Request for comments on following ideas, largely in the UI:

  1.  Does it make sense to simply the Default View as a Project which cannot 
be deleted and primary space for the Account. Essentially, the default view is 
the logged in account/user's project with no other collaborators

  2.  Migrate all isolated network constructs as VPC with a single tier.

  3.  Simplify templates/isos that are listed in deploy VM form: as a user, the 
template/iso section of the deploy VM form is complicated, would it make sense 
to simplify the template/iso shown as groups of guest OS family (like several 
other portals) and templates uploaded/registered by the account separately.

  4.  Remove data disk from VM deploy form, or hide it by default (show a 
button - add volume):
Currently, the deploy VM form only supports one data disk, however API can 
multiple disks. One can always still use APIs, but deploy VM and later attach 
more disks; or deploy vm but not start it, attach as many data disks as we want 
and then start it.

  5.  Show user-data and affinity (placement) groups as a first-class step, not 
hidden under advanced menu.

  6.  Offering groups or bundles: introduce way to group/bundle compute/data 
offerings; for example, I want to see CPU optimised offerings, memory 
optimiised offerings, specialised offerings (say GPU) etc.


Regards.

 

Re: Apache CloudStack and Ceph

[Rohit Yadav]

Thanks Piotr for the explanation, images gets stripped on this mailing list - 
so I couldn't see it but your explanation made sense to me.

You'll be delighted to know that in fact there's an upcoming feature in 4.19 to 
support object storage framework and buckets as first-class feature in 
CloudStack for end-users, with APIs, UI, bucket/browser and usage support for 
buckets.

This is proposed with a PR raised now and aims to implement the feature in a 
framework-plugin model with support for minio as a supported provider in the 
first iterations. Perhaps you can put in a request via a Github issue to have 
Ceph supported as an object storage pool/provider.

As a workaround, while not ideal you could be able to mount cephfs and have the 
storage served via minio with the proposed PR - 
https://github.com/apache/cloudstack/pull/7752

Any feedback, testing and suggestions are welcome on this feature.

Reference - 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/%5BDRAFT%5D+CloudStack+Object+Store


Regards.


From: Piotr Pisz 
Sent: Thursday, August 10, 2023 18:05
To: users@cloudstack.apache.org 
Subject: RE: Apache CloudStack and Ceph


[cid:image001.png@01D9CB96.C6933790]

Hey Rohit,



As in the attached picture, OpenStack orchestrates the possibility of setting 
up a bucket (container) in Ceph object store via radosgw api. In this way, the 
user gets his own share, which he can mount eg in vm. He can also browse the 
contents of the bucket and upload/download files via the web interface (similar 
to azure blob and others).

It would be great if a similar possibility existed in the CS interface intended 
for ordinary users.

Of course, the role of the administrator (CS or project) would be to connect 
the correct ceph infrastructure.

Such functionality in CS is very much needed.



Regards,

Piotr



 


-Original Message-
From: Rohit Yadav 
Sent: Thursday, August 10, 2023 1:30 PM
To: users@cloudstack.apache.org
Subject: Re: Apache CloudStack and Ceph



Hi Piotr,



Thanks for sharing, could you explain what you mean by 'create ceph object 
shares in CloudStack'?



Do you mean, perhaps CloudStack create/orchestrates Ceph using containers 
without the user having to setup the infra manually and then add to cloudstack?





Regards.





From: Piotr Pisz mailto:pi...@piszki.pl>>

Sent: Thursday, August 10, 2023 16:24

To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org> 
mailto:users@cloudstack.apache.org>>

Subject: RE: Apache CloudStack and Ceph



Generally, it would be great if there was an option to create ceph object 
shares in CloudStack.

Similar to Openstack "create container" in horizon.



We also run clusters as CS+Ceph pairs.



Regards,

Piotr













-Original Message-

From: Abhishek Ranjan mailto:abhishek...@gmail.com>>

Sent: Thursday, August 10, 2023 11:28 AM

To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>

Subject: Re: Apache CloudStack and Ceph



Dear Ivet,



I had implemented ceph with cloudstack in CSC on the block store and we'd also 
built a small volume object store.

Let me know if you need any information on that.

regards

Abhishek Ranjan





On Wed, 9 Aug 2023 at 18:26, Ivet Petrova 
mailto:ivet.petr...@shapeblue.com>>

wrote:



> Hello all,

>

> Do we have any community members who are using both Apache CloudStack

> and Ceph as a storage?

> We are discussing organising a joint 1-day event with the Ceph

> community and I was wondering if I can get support from companies -

> join the event and have a talk over their ACS and Ceph usage?

>

> Kind regards,

>

>

>

>

>

Re: Apache CloudStack and Ceph

[Rohit Yadav]

Hi Piotr,

Thanks for sharing, could you explain what you mean by 'create ceph object 
shares in CloudStack'?

Do you mean, perhaps CloudStack create/orchestrates Ceph using containers 
without the user having to setup the infra manually and then add to cloudstack?


Regards.


From: Piotr Pisz 
Sent: Thursday, August 10, 2023 16:24
To: users@cloudstack.apache.org 
Subject: RE: Apache CloudStack and Ceph

Generally, it would be great if there was an option to create ceph object 
shares in CloudStack.
Similar to Openstack "create container" in horizon.

We also run clusters as CS+Ceph pairs.

Regards,
Piotr




 


-Original Message-
From: Abhishek Ranjan 
Sent: Thursday, August 10, 2023 11:28 AM
To: users@cloudstack.apache.org
Subject: Re: Apache CloudStack and Ceph

Dear Ivet,

I had implemented ceph with cloudstack in CSC on the block store and we'd also 
built a small volume object store.
Let me know if you need any information on that.
regards
Abhishek Ranjan


On Wed, 9 Aug 2023 at 18:26, Ivet Petrova 
wrote:

> Hello all,
>
> Do we have any community members who are using both Apache CloudStack
> and Ceph as a storage?
> We are discussing organising a joint 1-day event with the Ceph
> community and I was wondering if I can get support from companies -
> join the event and have a talk over their ACS and Ceph usage?
>
> Kind regards,
>
>
>
>
>

Re: set display_name as hostname to instances

[Rohit Yadav]

Hi Cristian,

The display name of a VM is used for presentation purpose and isn't passed to 
the VM. I think I understand the requirement (to set a fdqn as hostname, like 
domain.tld which cloudstack doesn't allow as (.) in the name) and it isn't 
supported, perhaps you can raise an issue on Github



Regards.


From: cristian.c@istream.today 
Sent: Thursday, August 10, 2023 12:11
To: users@cloudstack.apache.org 
Subject: RE: set display_name as hostname to instances

The reason why I asked for this it is because you can not have duplicated VM
names even if are different account, under /ROOT let say VM name "Linux"
beside this you can not put a name like "domain.tld"   only domain-tld,
which is quite annoying...
I understand the current purpose for display name,  this is the reason why I
asked if it is possible to set this as hostname on the VMs.

Regards,
Cristian



 


-Original Message-----
From: Rohit Yadav 
Sent: Wednesday, August 9, 2023 7:03 PM
To: users@cloudstack.apache.org
Subject: Re: set display_name as hostname to instances

Historically, the use of display name in case of instances and other
resources (such as offering, templates etc) was to allow the operator/admin
to the resources by name and end user to see by display name in upper UI/CMP
layers such as CPBM etc. There was even API/response keys such as displayvm
where the idea was a root admin (operator account) can deploy resources
without getting them listed in such upper UI/CMP layers.

I think it's completely redundant now in the current UI implementation
neither is actually followed or used (I think), or even needed. Upper layers
and CMP/billing portals can decide however they want to use these params.


Regards.


From: Pearl d'Silva 
Sent: Wednesday, August 9, 2023 18:06
To: users@cloudstack.apache.org 
Subject: Re: set display_name as hostname to instances

Display name is solely for UI purposes. In order to set the host name of a
VM to a desired value, you'll need to pass the name parameter(same as that
of the displayname). If the name parameter is not passed, the hostname would
default to VM-.

Regards,
Pearl

From: cristian.c@istream.today 
Sent: August 4, 2023 11:35 AM
To: users@cloudstack.apache.org 
Subject: RE: set display_name as hostname to instances

The metadata does not show the display name for local-hostname,  for both
parameters I see the name value of the VM, the deploy was made via API and I
provided only the display_name, where the display name is "displayname01".

As you see here, public and local have the same value, from vm name.

{"vm_ip_address":"51.89.84.82","vm_metadata":[["userdata","user-data",null],
["metadata","service-offering","S-2"],["metadata","availability-zone","DE-00
1"],["metadata","local-ipv4","51.89.xx.xx"],["metadata","local-hostname","VM
-c8c113e0-3277-425e-882b-44937413fd4a"],["metadata","public-ipv4","51.89.xx.
xx"],["metadata","public-hostname","VM-c8c113e0-3277-425e-882b-44937413fd4a"
],["metadata","instance-id","c8c113e0-3277-425e-882b-44937413fd4a"],["metada
ta","vm-id","c8c113e0-3277-425e-882b-44937413fd4a"]


Thank you,
Cristian







-Original Message-
From: Pearl d'Silva 
Sent: Friday, August 4, 2023 6:02 PM
To: users@cloudstack.apache.org
Subject: Re: set display_name as hostname to instances

If you are using the UI to create the VM, set the name of the VM - this
field sets the hostname and the display name. So you should see this value
in the local-hostname file in the VR metadata folder.
If you are using the API, explicitly set the name field.

Let us know if you see the desired name in the metadata after setting the
name parameter.

Thanks,

From: cristian.c@istream.today 
Sent: August 4, 2023 10:22 AM
To: users@cloudstack.apache.org 
Subject: RE: set display_name as hostname to instances

Hi Pearl,

   I will test this when I upgrade to 4.18.x I'm waiting for 4.18.1.

Thank you,
Cristian




-Original Message-
From: Pearl d'Silva 
Sent: Friday, August 4, 2023 4:24 PM
To: users@cloudstack.apache.org
Subject: Re: set display_name as hostname to instances

Hi Cristian,

In addition, in 4.18 a new feature - managed User data was introduced. This
can be used to register userdata with custom parameters - here, the
hostname. And when deploying the VM, the custom parameters could be set to
the desired values. You could refer to
https://www.shapeblue.com/cloudstack-managed-user-data/ for more
information.

Thanks,
Pearl

From: Rohit Yadav 
Sent: August 4, 2023 9:12 AM
To: users@clou

Re: Apache CloudStack and Ceph

[Rohit Yadav]

Great, thanks for sharing Ivet. Looking forward to it.


Regards.


From: Stackbill Sales 
Sent: Wednesday, August 9, 2023 18:59
To: users@cloudstack.apache.org 
Subject: Re: Apache CloudStack and Ceph

Yes, we have done several successful implementations with Apache Cloudstack
and Ceph as a storage.

We have also recommended our customers and they are running successfully.

Regard,
Rafi
StackBill.com


On Wed, Aug 9, 2023 at 6:26 PM Ivet Petrova 
wrote:

> Hello all,
>
> Do we have any community members who are using both Apache CloudStack and
> Ceph as a storage?
> We are discussing organising a joint 1-day event with the Ceph community
> and I was wondering if I can get support from companies - join the event
> and have a talk over their ACS and Ceph usage?
>
> Kind regards,
>
>
>
>
>

--




*This E-mail is confidential. It may also be legally privileged. If you
are not the addressee you may not copy, forward, disclose or use any part
of
it. If you have received this message in error, please delete it and all
copies
from your system and notify the sender immediately by return E-mail.
Internet
communications cannot be guaranteed to be timely, secure, error or
virus-free.
The sender does not accept liability for any errors or
omissions*

 

Re: set display_name as hostname to instances

[Rohit Yadav]

Historically, the use of display name in case of instances and other resources 
(such as offering, templates etc) was to allow the operator/admin to the 
resources by name and end user to see by display name in upper UI/CMP layers 
such as CPBM etc. There was even API/response keys such as displayvm where the 
idea was a root admin (operator account) can deploy resources without getting 
them listed in such upper UI/CMP layers.

I think it's completely redundant now in the current UI implementation neither 
is actually followed or used (I think), or even needed. Upper layers and 
CMP/billing portals can decide however they want to use these params.


Regards.


From: Pearl d'Silva 
Sent: Wednesday, August 9, 2023 18:06
To: users@cloudstack.apache.org 
Subject: Re: set display_name as hostname to instances

Display name is solely for UI purposes. In order to set the host name of a VM 
to a desired value, you'll need to pass the name parameter(same as that of the 
displayname). If the name parameter is not passed, the hostname would default 
to VM-.

Regards,
Pearl

From: cristian.c@istream.today 
Sent: August 4, 2023 11:35 AM
To: users@cloudstack.apache.org 
Subject: RE: set display_name as hostname to instances

The metadata does not show the display name for local-hostname,  for both
parameters I see the name value of the VM, the deploy was made via API and I
provided only the display_name, where the display name is "displayname01".

As you see here, public and local have the same value, from vm name.

{"vm_ip_address":"51.89.84.82","vm_metadata":[["userdata","user-data",null],
["metadata","service-offering","S-2"],["metadata","availability-zone","DE-00
1"],["metadata","local-ipv4","51.89.xx.xx"],["metadata","local-hostname","VM
-c8c113e0-3277-425e-882b-44937413fd4a"],["metadata","public-ipv4","51.89.xx.
xx"],["metadata","public-hostname","VM-c8c113e0-3277-425e-882b-44937413fd4a"
],["metadata","instance-id","c8c113e0-3277-425e-882b-44937413fd4a"],["metada
ta","vm-id","c8c113e0-3277-425e-882b-44937413fd4a"]


Thank you,
Cristian




 


-Original Message-
From: Pearl d'Silva 
Sent: Friday, August 4, 2023 6:02 PM
To: users@cloudstack.apache.org
Subject: Re: set display_name as hostname to instances

If you are using the UI to create the VM, set the name of the VM - this
field sets the hostname and the display name. So you should see this value
in the local-hostname file in the VR metadata folder.
If you are using the API, explicitly set the name field.

Let us know if you see the desired name in the metadata after setting the
name parameter.

Thanks,

From: cristian.c@istream.today 
Sent: August 4, 2023 10:22 AM
To: users@cloudstack.apache.org 
Subject: RE: set display_name as hostname to instances

Hi Pearl,

   I will test this when I upgrade to 4.18.x I'm waiting for 4.18.1.

Thank you,
Cristian




-Original Message-
From: Pearl d'Silva 
Sent: Friday, August 4, 2023 4:24 PM
To: users@cloudstack.apache.org
Subject: Re: set display_name as hostname to instances

Hi Cristian,

In addition, in 4.18 a new feature - managed User data was introduced. This
can be used to register userdata with custom parameters - here, the
hostname. And when deploying the VM, the custom parameters could be set to
the desired values. You could refer to
https://www.shapeblue.com/cloudstack-managed-user-data/ for more
information.

Thanks,
Pearl

From: Rohit Yadav 
Sent: August 4, 2023 9:12 AM
To: users@cloudstack.apache.org 
Subject: Re: set display_name as hostname to instances

Hi Cristian,

I'm not sure, but could you try user data (cloud-init data) when you deploy
a VM. In there, you'll have flexibility to set the hostname of the VM to
whatever you'd like.


Regards.


From: cristian.c@istream.today 
Sent: Thursday, August 3, 2023 20:28
To: users@cloudstack.apache.org 
Subject: set display_name as hostname to instances

Hello,



Is there a method to set as hostnames to the instances the display name? I
did not see the display name in the metadata.



I am asking this because the display name allows any format, such as
fqdn.tld, and it does not matter if it's a duplicate or not.

Thank you,

Cristian

Re: set display_name as hostname to instances

[Rohit Yadav]

Hi Cristian,

I'm not sure, but could you try user data (cloud-init data) when you deploy a 
VM. In there, you'll have flexibility to set the hostname of the VM to whatever 
you'd like.


Regards.


From: cristian.c@istream.today 
Sent: Thursday, August 3, 2023 20:28
To: users@cloudstack.apache.org 
Subject: set display_name as hostname to instances

Hello,



Is there a method to set as hostnames to the instances the display name? I
did not see the display name in the metadata.



I am asking this because the display name allows any format, such as
fqdn.tld, and it does not matter if it's a duplicate or not.

Thank you,

Cristian


 

Re: Rocky 9 management setup

[Rohit Yadav]

All,

I'm probably late to join this thread, I had some notes scribbled here on EL9 
setup (I actually setup RHEL9 with ACS 4.18): 
https://gist.github.com/rohityadavcloud/fc401a0fe8e8ea16b4b3a4e3d149ce0c


Regards.


From: Nux 
Sent: Tuesday, July 25, 2023 14:24
To: users@cloudstack.apache.org 
Cc: 김재종 
Subject: Re: Rocky 9 management setup

Hello,

Which problem do you have, the labels or libvirtd file?
The labels usually are a browser caching issue. Try to clear your
browser cache or try with a different browser or a private browsing
session.



On 2023-07-25 02:59, 김재종 wrote:
> I have same problem.
>
> Do you have any work around or plan to resolve it?
>
> I hope you can help me.
>
> good day!!
>
> -Original Message-
> From: "Jeremy Hansen"
> To: ;
> Cc:
> Sent: 2023-03-11 (토) 05:51:58 (GMT+09:00)
> Subject: Re: Rocky 9 management setup
>
>  Seeing some broken labels:
>
> Also noticed that /etc/sysconfig/libvirtd needs to exist.  The latest
> libvirt packages in Rocky 9 do not automatically place this file:
>
> From /var/log/cloudstack/agent/setup.log
>
> DEBUG:root:[Errno 2] No such file or directory:
> '/etc/sysconfig/libvirtd'
>   File
> "/usr/lib64/python3.9/site-packages/cloudutils/serviceConfig.py", line
> 38, in configuration
> result = self.config()
>   File
> "/usr/lib64/python3.9/site-packages/cloudutils/serviceConfig.py", line
> 635, in config
> cfo.save()
>   File
> "/usr/lib64/python3.9/site-packages/cloudutils/configFileOps.py", line
> 62, in save
> fp = open(self.fileName, "r")
>
> -jeremy
>
>
 

> On Friday, Mar 10, 2023 at 1:40 AM, Me  wrote:
>>
>> So I went through the process on both 4.17 and 4.18 and made sure I
>> chose advanced and still, I see no way of adding a guest network in
>> 4.18:
>>
>> 4.17 has a button to create a guest network.  Do I have to change a
>> parameter in the global config to enable this?
>>
>> Thanks
>> -jeremy
>>
>> On Thursday, Mar 09, 2023 at 11:54 PM, Wei ZHOU
>>  wrote:
>>
>> Hi Jeremy,
>>
>> There is a new type of network: L2. Please try with the L2 network.
>> refer to
>>
> https://docs.cloudstack.apache.org/en/latest/adminguide/networking_and_traffic.html#configure-guest-traffic-in-an-advanced-zone
>>
>>
>> Please note, L2 networks are only supported in the Advanced zone .
>> If you created a Basic zone, you cannot create any new networks.
>>
>> Kind regards,
>> Wei
>>
>> On Fri, 10 Mar 2023 at 06:22, Jeremy Hansen
>> 
>> wrote:
>>
>> Ran in to this while trying to setup QuickCloudNoServices:
>>
>> Configuring guest traffic
>> *Something went wrong; please correct the following:*
>> Service Dhcp is not supported by the network offering [Network
>> Offering
>> [20-Guest-QuickCloudNoServices]
>>
>> This is during the configuration wizard.
>>
>> Not really sure I understand. I’m trying to set up a L2 network
>> with an
>> external DHCP server. Is QuickCloudNoServices the wrong choice?
>>
>> -jeremy
>>
>> On Thursday, Mar 09, 2023 at 6:23 PM, Me  wrote:
>> Is there links to any kind of updated documentation? I seem to be
>> having
>> issues with libvirtd and setting up the agent on Rocky 9. I’m
>> trying to
>> follow the 4.17 docs, but some things seem to no longer apply.
>>
>> Error 530
>> Unable to add the host: Cannot find the server resources at
>> http://dell1.fr1.clx.corp
>>
>> Also noticed in the agent adding process, this being written to
>> qemu.conf:
>>
>> #deprecation_behavior = "none"vnc_tls=1
>> vnc_tls=1vnc_tls=1
>> vnc_tls=1vnc_tls=1
>>
>> which breaks libvirtd:
>>
>> Mar 09 18:14:21 dell1.fr1.clx.corp libvirtd[29917]: configuration
>> file
>> syntax error: /etc/libvirt/qemu.conf:955: expecting a separator
>> Mar 09 18:14:21 dell1.fr1.clx.corp libvirtd[29917]: Initialization
>> of QEMU
>> state driver failed: configuration file syntax error:
>> /etc/libvirt/qemu.conf:955: expecting a separator
>> Mar 09 18:14:21 dell1.fr1.clx.corp libvirtd[29917]: Driver state
>> initialization failed
>>
>> Fixing that config allowed libvirtd to start and I was able to add
>> hosts.
>>
>> Thanks
>> -jeremy
>>
>> On Thursday, Mar 09, 2023 at 10:22 AM, Wei ZHOU
>> 
>> wrote:
>> Hi Jeremy,
>>
>> You can find the packages for 4.18.0.0-RC2 at
>>
>>
> http://packages.shapeblue.com/cloudsta

Re: Cloudstack Billing Integration

[Rohit Yadav]

I think there are several options that you would need to evaluate.

CloudStack has an inbuilt simple credit or prepaid based system, that's the 
quota plugin you can try:
https://docs.cloudstack.apache.org/en/latest/plugins/quota.html

In addition to this, one can write their own billing logic on top of the usage 
records APIs - 
https://docs.cloudstack.apache.org/en/latest/adminguide/usage.html


Some of the commercial billing integrators that you may explore are - Apiculus, 
StackBill, HostBill, Amysta, Stack Console. I may be forgetting a couple more 
that the community might help suggest.


Regards.


From: Prasad Reddy 
Sent: Sunday, July 16, 2023 05:46
To: users@cloudstack.apache.org 
Subject: Re: Cloudstack Billing Integration

I think this is the weak link of this entire project. Having a simple user
management and billing system would make the project worthwhile.
Pretty much all major contributors to this project are working to make sure
their proprietary subscription based billing works.

ᐧ

On Sat, Jul 15, 2023 at 4:24 PM Ian Tobin  wrote:

> Hi,
>
> I'm sure this has been asked before but what are people using for billing,
> I've seen some such as Hostbill but they are all seem to be very costly in
> comparison to standard VPS integration.
>
> Thanks
>
> Ian
>
>
>

 

Re: Unable to ping System VM in Advanced Zone (without SG)

[Rohit Yadav]

Glad it helped Pratik.

Regards.

Regards.

From: Pratik Chandrakar 
Sent: Tuesday, July 4, 2023 12:42:14 PM
To: users@cloudstack.apache.org 
Subject: Re: Unable to ping System VM in Advanced Zone (without SG)

Hi all,
Finally, I am able to resolve the issue and especially thank Mr Rohit Yadav
for his blog https://rohityadav.cloud/blog/cloudstack-kvm/
I was running Ceph OSD and Cloudstack on the same host and docker was
causing the issue.

On Tue, Jun 20, 2023 at 10:35 AM Pratik Chandrakar <
chandrakarpra...@gmail.com> wrote:

> Yes
>
> On Fri, Jun 16, 2023 at 5:19 PM Wei ZHOU  wrote:
>
>> Have you configured the vlan tag of public ip range ?
>>
>> -Wei
>>
>> On Friday, 16 June 2023, Pratik Chandrakar 
>> wrote:
>>
>> > Hi,
>> > I am pinging the Public IP. I tried to ping the gateway from CPVM also
>> but
>> > was unable to connect to the gateway, whereas in the SG-enabled setup,
>> the
>> > same IP and configuration work. I have checked the switch as well and I
>> am
>> > getting the MAC of the System VMs.
>> > Unable to identify this strange issue.
>> >
>> >
>> > On Fri, Jun 16, 2023 at 11:48 AM Wei ZHOU 
>> wrote:
>> >
>> > > Hi,
>> > >
>> > > System vms have multiple IPs, which IP do you ping to?
>> > >
>> > > -Wei
>> > >
>> > > On Thursday, 15 June 2023, Pratik Chandrakar <
>> chandrakarpra...@gmail.com
>> > >
>> > > wrote:
>> > >
>> > > > Hi Wei,
>> > > > Switch ports are in trunk mode.
>> > > > VM on the same host is also not working even though its agent state
>> is
>> > > > showing up.
>> > > > I think the Configuration is also correct because the same
>> > configuration
>> > > is
>> > > > working for SG-enabled Zone.
>> > > >
>> > > > On Thu, Jun 15, 2023 at 3:30 PM Wei ZHOU 
>> > wrote:
>> > > >
>> > > > > Hi,
>> > > > >
>> > > > > If VMs on the same host work, but not on different hosts - this
>> is a
>> > > > > typical issue of network misconfiguration.
>> > > > > Please check if switch ports are trunk mode, hosts and cloudstack
>> > > network
>> > > > > configurations are correct.
>> > > > >
>> > > > > -Wei
>> > > > >
>> > > > > On Thu, 15 Jun 2023 at 11:46, Pratik Chandrakar <
>> > > > > chandrakarpra...@gmail.com>
>> > > > > wrote:
>> > > > >
>> > > > > > Hi all,
>> > > > > > In the Advanced Zone-SG Enabled deployment there is no issue
>> but on
>> > > the
>> > > > > > same setup when I deploy Advanced Zone-Without SG, I am not
>> able to
>> > > > ping
>> > > > > > System VMs from other client machines/CS hosts. Both Console
>> Proxy
>> > > and
>> > > > > > Secondary storage are UP and agent states are also UP in case
>> > > > Management
>> > > > > > Server and System VMs are deployed on the same host whereas when
>> > > System
>> > > > > VMs
>> > > > > > are deployed on other hosts then it does not show any state in
>> > > > Management
>> > > > > > Server. I checked the logs but couldn't find any error on both
>> > > > management
>> > > > > > and agent logs.
>> > > > > > Environment Details are
>> > > > > >   ACS - 4.18
>> > > > > >   Host - Ubuntu 22.04.2
>> > > > > >
>> > > > > > Please guide me as I am unable to find any solution to this
>> strange
>> > > > > issue.
>> > > > > >
>> > > > > > --
>> > > > > > *Regards,*
>> > > > > > *Pratik Chandrakar*
>> > > > > >
>> > > > >
>> > > >
>> > > >
>> > > > --
>> > > > *Regards,*
>> > > > *Pratik Chandrakar*
>> > > >
>> > >
>> >
>> >
>> > --
>> > *Regards,*
>> > *Pratik Chandrakar*
>> >
>>
>
>
> --
> *Regards,*
> *Pratik Chandrakar*
>


--
*Regards,*
*Pratik Chandrakar*

 

Re: guest.cpu.mode per guest/vm on the same KVM host

[Rohit Yadav]

Hi Lukáš,

It's not possible to do it on per VM basis, however, do explore the extra 
config feature if that allows for some customisation: 
https://www.shapeblue.com/cloudstack-feature-first-look-enable-sending-of-arbitrary-configuration-data-to-vms/

Not ideal - a workaround may also be to do it on one-time basis by setting 
guest.cpu.mode property in agent.properties for the VM you want to deploy and 
once it's deployed, revert the cpu mode setting and restart the agent on the 
KVM host.


Regards.


From: Daan Hoogland 
Sent: Tuesday, June 6, 2023 19:45
To: users@cloudstack.apache.org 
Subject: Re: guest.cpu.mode per guest/vm on the same KVM host

Lukáš
This is an agent property, which means per host at least. I don't know
of a way to make this per VM, but if you can do this on KVM, it seems
like a reasonable feature request.

On Tue, Jun 6, 2023 at 3:56 PM Lukáš Mrtvý  wrote:
>
> Hello,
> Is possible somehow to set guest.cpu.mode per guest ( VM ) ? I would like
> to create on the same KVM host VM with guest.cpu.mode=host-passthrough and
> a second VM without any passthrough. Is it possible or this setting is
> global / per KVM host? Thanks
> --
> BR,
> Lukáš Mrtvý



--
Daan

 

Re: [VOTE] Upgrade Log4j to Log4j2

[Rohit Yadav]

João,

Technically, for lazy consensus a vote thread needs three +1 (binding) votes 
which are only counted towards a decision or approval [1].

Since there are no objections but concerns shared so far, the PR can be 
reviewed, tested and merged as any other PR as long as it meets the community 
review and merge guidelines, in this case since the PR is a large one I would 
request additional manual QA and upgrade tests be done to ensure there is no 
stability/upgrade regression(s).

[1] 3.2.1: https://cloudstack.apache.org/bylaws.html


Regards.


From: João Jandre Paraquetti 
Sent: Tuesday, June 6, 2023 01:36
To: users@cloudstack.apache.org ; 
d...@cloudstack.apache.org 
Subject: Re: [VOTE] Upgrade Log4j to Log4j2

Hi all,

This voting has been going on for quite some time already. In the
meantime, more tests have been done and the PR has been verified as
working with both mbx and BO.

As we did not get any -1 votes, and achieved the minimum of three +1s, I
will therefore close this vote and propose we proceed in the PR. Any
remaining issues people might have with the PR can be addressed in the
PR's discussions in github, so that we can finally merge the PR.

Best regards,
João Jandre (JoaoJandre)

On 18/05/2023 17:29, Sidimar Carniel wrote:
> Important effort in this work!
>
> [ ] +1 approve
>
> Regards,
> Sidimar Carniel
>
>
>
> Em qua., 17 de mai. de 2023 às 10:27, Rodrigo D. Lopez <
> rodrigoduartelo...@gmail.com> escreveu:
>
>> Thanks for the great work!
>>
>> Based on discussions in PR and the discussion thread[1]. My vote is +1.
>>
>> Log4j v1 (deprecated) and its current alternative reload4j in use in ACS
>> are not ideal for the long run. Therefore, for the future of ACS, and to
>> enable us to keep evolving, the upgrade is most welcome.
>>
>> Regards,
>> Rodrigo Lopez
>>
>> [1]  https://lists.apache.org/thread/261j7m0p5mr4q7yclvo49mwhkxz4yov2
>>
>> Em qua., 17 de mai. de 2023 às 09:41, Daan Hoogland <
>> daan.hoogl...@gmail.com>
>> escreveu:
>>
>>> -0
>>>
>>> Joao, Daniel reacted negatively to my question to create a proxy with bad
>>> arguments and I had no time to respond yet. I think not adding a proxy at
>>> this time is a missed opportunity and I would full heartedly +1 if we
>> had.
>>> Not creating a proxy class (with or without configurability) is a waste
>> of
>>> your effort.
>>> All the standardisation of calls is very useful irrespective.
>>>
>>> On Tue, May 16, 2023 at 8:45 PM Daniel Salvador >>
>>> wrote:
>>>
 Hello, João

 Considering the discussion we had in the thread[1] and that the
>> conflicts
 will be mostly regarding loggers names (which is simple to fix), I am
>> +1
>>> on
 the proposal.

 Best regards,
 Daniel Salvador (gutoveronezi)

 [1] https://lists.apache.org/thread/261j7m0p5mr4q7yclvo49mwhkxz4yov2

 On Tue, May 16, 2023 at 1:28 PM João Jandre Paraquetti <
 j...@scclouds.com.br>
 wrote:

> Hello guys,
>
> I am opening this voting thread as result of the discussion in thread
> "ACS upgrade to Log4J2 version 2.19"[1].
>
> The voting aims to continue the efforts and conclude the upgrade of
>> the
> ACS logging library to Log4j2 through PR 7131[2]; merge the PR as
>> soon
> as possible and provide ways to contributors solve the conflicts
>>> easily,
> so all the contributors have time to fix their merge conflicts before
> 4.19; announce that change in the release notes and provide ways to
> users upgrade their customization made to the default log4j
> configuration files.
>
> 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)
>
> Best regards,
> João Jandre (JoaoJandre)
>
> [1] https://lists.apache.org/thread/261j7m0p5mr4q7yclvo49mwhkxz4yov2
> [2] https://github.com/apache/cloudstack/pull/7131
>
>
>>>
>>> --
>>> Daan
>>>

 

Re: ACS upgrade to Log4J2 version 2.19

[Rohit Yadav]

Hi João,

I'm using the latest mbx as from https://github.com/shapeblue/mbx there is no 
private fork/version that I'm using. I did a quick test against 4.19/main EL8 
packages from latest main branch from today and they're deploying okay for me. 
I'm using mbx on a NUC9 i7 based mini-pc server with Ubuntu 22.04 + KVM.


Regards.


From: João Jandre Paraquetti 
Sent: Friday, May 26, 2023 20:04
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: Re: ACS upgrade to Log4J2 version 2.19

Hi Rohit,

 > PR has issues with intermittent Github Actions failures (which
I'm not sure are due to the PR or generally - this needs to be
investigated and fixed). While simulator-based Github Actions
smoketests appear to pass, and perhaps the PR works in your
environment, it doesn't work with actual environments with both
BO/Trillian and mbx. In actual env, systemvms not starting and I
could reproduce Joao's volume issue, which doesn't happen with 4.18
pkgs using mbx or Trillian/BO (so I think the PR isn't stable yet).
I see Daan has also found and has reported other issues.

The issues reported by you happened to me even when using packages from
main. MBX has the same behavior with both packages (main and my PR).
Maybe you are using a different version of MBX that is not the one in
github?

 > Since this is a rather large PR change, it would also require
some manual testing of the logs and upgrade tests and for the
community to commit efforts towards that. It's possible more runtime
issues are found with different hypervisors/storages, so it's
important the PR tests exhaustively all the supported hypervisors,
and at least NFS and local storages (scaleio, ceph, storpool, linbit
etc. would be great too). Due to this, this can potentially take
more time and effort to stablise it, and maybe far away to consider
merging.

The manual testing has already been done by at least 3 people. With
multiple hypervisors and plugins. As always, further testing is welcome.

About upgrading and supporting the community, I am happy to help review
PRs and point people in the right direction, I also can try my best to
respond questions in the ML regarding log4j2. As for the log4j2
configuration upgrade, the new configs will have the same names and same
paths as the old ones, this upgrade has already been tested. All that
users must do when installing the new packages is answer 'yes' when
questioned about upgrading the log4j config.

Best regards,
João Jandre (JoaoJandre)

On 26/05/2023 06:19, Rohit Yadav wrote:
> João, Daniel, Daan, All,
>
> I've reviewed and tested the PRhttps://github.com/apache/cloudstack/pull/7131 
>  using packages Daan uploaded onhttps://download.cloudstack.org/testing/7131/ 
>  (thanks Daan!) and added my comment on the PR.
>
> PR has issues with intermittent Github Actions failures (which I'm not sure 
> are due to the PR or generally - this needs to be investigated and fixed). 
> While simulator-based Github Actions smoketests appear to pass, and perhaps 
> the PR works in your environment, it doesn't work with actual environments 
> with both BO/Trillian and mbx. In actual env, systemvms not starting and I 
> could reproduce Joao's volume issue, which doesn't happen with 4.18 pkgs 
> using mbx or Trillian/BO (so I think the PR isn't stable yet). I see Daan has 
> also found and has reported other issues.
>
> Since this is a rather large PR change, it would also require some manual 
> testing of the logs and upgrade tests and for the community to commit efforts 
> towards that. It's possible more runtime issues are found with different 
> hypervisors/storages, so it's important the PR tests exhaustively all the 
> supported hypervisors, and at least NFS and local storages (scaleio, ceph, 
> storpool, linbit etc. would be great too). Due to this, this can potentially 
> take more time and effort to stablise it, and maybe far away to consider 
> merging.
>
> We also need some plan on how we support users esp for upgrades and other 
> developers in the community. Reflecting on this, here's what I propose we 
> should do once the PR is ready for testing, passes testing and community 
> guidelines for merging:
>
>*   Figure out and document manual/semi/automated steps that users should 
> take while upgrading to future ACS version which has this PR. For example, 
> the packages post-install script could figure out a way wherein old log4j xml 
> config is renamed/backed-up and new only is installed in a way that it 
> continues to log in the same file/path so as not to disrupt a normal user's 
> expectation of CloudStack logging (the log file paths and logging format).
>*   We need an upgrade documentation PR as for admin users.
>*   Anybody with a private plugin/integr