Introduction

[Abhishek Kumar]

Hello all!


This is Abhishek Kumar. I've recently joined ShapeBlue as Software Engineer to 
work on Cloudstack.
Looking forward to learn and contribute in the project and community in a 
meaningful manner.


Regards,


Abhishek Kumar

Software Engineer

ShapeBlue

abhishek.ku...@shapeblue.com

www.shapeblue.com<http://www.shapeblue.com>

abhishek.ku...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

Re: [ANNOUNCE] New Committer: Dennis Konrad

[Abhishek Kumar]

Congrats Dennis!

From: Tutkowski, Mike 
Sent: 18 March 2019 21:02
To: dev@cloudstack.apache.org
Subject: [ANNOUNCE] New Committer: Dennis Konrad

Hi everyone,

The Project Management Committee (PMC) for Apache CloudStack
has invited Dennis Konrad to become a committer and I am pleased
to announce that he has accepted.

Please join me in congratulating Dennis on this accomplishment.

Thanks!
Mike


abhishek.ku...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

Re: [ANNOUNCE] New Committer: Sven Vogel

[Abhishek Kumar]

Congratulations Sven!

From: Tutkowski, Mike 
Sent: 18 March 2019 21:01
To: dev@cloudstack.apache.org
Subject: [ANNOUNCE] New Committer: Sven Vogel

Hi everyone,

The Project Management Committee (PMC) for Apache CloudStack
has invited Sven Vogel to become a committer and I am pleased
to announce that he has accepted.

Please join me in congratulating Sven on this accomplishment.

Thanks!
Mike


abhishek.ku...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

Re: Hello

[Abhishek Kumar]

Welcome Darrin!


Regards,
Abhishek Kumar


From: Darrin Hüsselmann 
Sent: 13 June 2019 17:44
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Hello

Hi All,


I have joined Shapeblue as a software engineer and look forward to contributing 
to the cloudstack project and working with the community.


Cheers

Darrin


darrin.husselm...@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue




abhishek.ku...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

Re: [ANNOUNCE] Andrija Panic has joined the PMC

[Abhishek Kumar]

Congrats Andrija!

Regards,
Abhishek Kumar

From: Paul Angus 
Sent: 13 July 2019 20:32
To: us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Subject: [ANNOUNCE] Andrija Panic has joined the PMC

Fellow CloudStackers,



It gives me great pleasure to say that Adrija has been invited to join the
PMC and has gracefully accepted.


Please joining me in congratulating Andrija!




Kind regards,



Paul Angus

CloudStack PMC

abhishek.ku...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

Re: [ANNOUNCE] Gabriel Beims Bräscher has joined the PMC

[Abhishek Kumar]

Congratulations Gabriel!


Regards,
Abhishek Kumar

From: Paul Angus 
Sent: 13 July 2019 21:30
To: us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Subject: [ANNOUNCE] Gabriel Beims Bräscher has joined the PMC

Fellow CloudStackers,


Its non-stop today!



It gives me great pleasure to say that Gabriel has been invited to join the
PMC and has gracefully accepted.


Please joining me in congratulating Sven!




Kind regards,



Paul Angus

CloudStack PMC

abhishek.ku...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

Re: [ANNOUNCE] Sven Vogel has joined the PMC

[Abhishek Kumar]

Congratulations Sven!


Regards,
Abhishek Kumar

From: Paul Angus 
Sent: 13 July 2019 21:14
To: priv...@cloudstack.apache.org ; 
dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org 
Subject: [ANNOUNCE] Sven Vogel has joined the PMC

Fellow CloudStackers,



It gives me great pleasure to say that Sven has been invited to join the
PMC and has gracefully accepted.


Please joining me in congratulating Sven!




Kind regards,



Paul Angus

CloudStack PMC

abhishek.ku...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

Re: [ANNOUNCE] Bobby (Boris Stoyanov) has joined the PMC

[Abhishek Kumar]

Congratulations Bobby!

Regards,
Abhishek Kumar

From: Paul Angus 
Sent: 16 July 2019 14:42
To: priv...@cloudstack.apache.org ; 
dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org 
Subject: [ANNOUNCE] Bobby (Boris Stoyanov) has joined the PMC

Fellow CloudStackers,



It gives me great pleasure to say that Bobby has been invited to join the
PMC and has gracefully accepted.



Please join me in congratulating  Bobby!





Kind regards,





Paul Angus

CloudStack PMC

abhishek.ku...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

Re: Introduction: Radu Todirica

[Abhishek Kumar]

Welcome Radu!

Regards,

Abhishek Kumar


From: Simon Weller 
Sent: 21 August 2019 20:36
To: dev 
Cc: Radu Todirica 
Subject: Introduction: Radu Todirica

All,

I'd like to introduce Radu Todirica to the community.  Radu is a new(er) member 
of the ENA team and has been making lots of contributions to CloudStack and you 
can expect to see some PRs from him pretty soon.

Please join me in making him welcome!

-Si



abhishek.ku...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

CloudStack cwiki write/edit access

[Abhishek Kumar]

Hi devs,

Can someone please grant me write, edit access on CloudStack cwiki 
https://cwiki.apache.org/confluence/spaces/spacepermissions.action?key=CLOUDSTACK
My username there is shwstppr.
I need to add/update design document for a feature for CloudStack which I'll be 
sharing with community soon.

Regards,

Abhishek Kumar

abhishek.ku...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

[DISCUSS] CloudStack Kubernetes Service plugin

[Abhishek Kumar]

Hi all,

I would like to propose developing a plugin for Kubernetes integration in 
CloudStack, can be named CloudStack Kubernetes Service plugin.
I've written down an initial design document for it here, 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Kubernetes+Service
Please review and provide your thoughts and suggestions.

Regards,


Abhishek Kumar

Software Engineer

ShapeBlue

abhishek.ku...@shapeblue.com

www.shapeblue.com<http://www.shapeblue.com>

abhishek.ku...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

Re: [DISCUSS] CloudStack Kubernetes Service plugin

[Abhishek Kumar]

Hi Pierre-Luc,

As FS states and Paul mentioned, plugin can support scaling of worker nodes 
through an API(scaleK8sCluster), howerver, there is no automatic scaling in the 
proposal. Also, I'm not sure about shared worker nodes pool at this moment.
Also, as mentioned in FS createK8sCluster API takes parameters 
serviceofferingid and noderootdisksize so user can manage compute power of 
nodes as desired.

Regards,
Abhishek


From: Pierre-Luc Dion 
Sent: 25 September 2019 20:00
To: dev@cloudstack.apache.org 
Subject: Re: [DISCUSS] CloudStack Kubernetes Service plugin

Hi Paul,

Yeah, was bad timing for the CCCNA this year unfortunately :-(,  I'm not
sure I'm curious to see how cloudstack could become more
"other Apache products friendly" but I don't have particular use case
compared to k8s integration. Has you are suggesting,
would probably make sense to use Helm to deploy any other application stack.

btw, we are still working on the Canonical MaaS integration, a bit more
challenging than anticipated...


To get back to a *Kubernetes Service plugin*:
To me, as a user of cloudstack at the moment, If I deploy a k8s cluster, I
need to deploy monstrous instances for worker nodes.
which doesn't make sense if I'm a cloud consumer. So I think we need to
solve something challenging: a k8s service that would scale has needed
while keeping in mind redundancy of worker nodes without sacrifice on
security. Is the worker node is part of the ongoing work or it's more about
offering a k8s master and api infrastructure to a user ?

An easy path would be some kind of shared worker nodes pool but that
involve possible security risk unless you would trust users that consume
those workers.


On Wed, Sep 25, 2019 at 10:15 AM Paul Angus 
wrote:

> Hi Pierre-Luc,
>
> (we missed you at CCCNA!) How are you seeing CloudStack being more
> deployment friendly?  What you do think that we could do on top of creating
> the Kubenetes Cluster to begin with?
> [thinking out loud - we could pre-package Tiller to make it easier to
> deploy openWhisk via Helm charts ? ]
>
> Kind regards
>
>
> Paul.
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Pierre-Luc Dion 
> Sent: 25 September 2019 13:37
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] CloudStack Kubernetes Service plugin
>
> Hi Rohit, Nux,
>
> Thanks Rohit for cloudstack-provider, that's exactly it ! :-D Nux, I agree
> with your opinion, but there is a lot of interest for k8s and seams like a
> lot of organisations are moving to container based infrastructures to
> standardized their deployment.
>
> if we want to extent the discussion to function as a service, would you
> guys see a possibility for us to be more aligned or more deployment
> friendly for Openwhisk ?
>
> Cheers,
>
>
> On Wed, Sep 25, 2019 at 6:54 AM Will Stevens 
> wrote:
>
> > We see huge demand for K8s in our customer base. Just a note...
> >
> > On Wed, Sep 25, 2019, 4:03 AM Nux!  wrote:
> >
> > > Do you guys see high demand for K8s?
> > >  From where I'm looking it seems to be going the way of Openstack,
> > > loads of hype, overcomplicated, near-impossible to upgrade.
> > > Not sure if it's worth investing resources for this.
> > >
> > > Lucian
> > >
> > > ---
> > > Sent from the Delta quadrant using Borg technology!
> > >
> > > On 2019-09-24 07:41, Abhishek Kumar wrote:
> > > > Hi all,
> > > >
> > > > I would like to propose developing a plugin for Kubernetes
> > > > integration in CloudStack, can be named CloudStack Kubernetes
> Service plugin.
> > > > I've written down an initial design document for it here,
> > > >
> > >
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Kube
> > rnetes+Service
> > > > Please review and provide your thoughts and suggestions.
> > > >
> > > > Regards,
> > > >
> > > >
> > > > Abhishek Kumar
> > > >
> > > > Software Engineer
> > > >
> > > > ShapeBlue
> > > >
> > > > abhishek.ku...@shapeblue.com
> > > >
> > > > www.shapeblue.com<http://www.shapeblue.com>
> > > >
> > > > abhishek.ku...@shapeblue.com
> > > > www.shapeblue.com<http://www.shapeblue.com>
> > > > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
> > >
> >
>
>
> --
>
> *Pierre-Luc Dion*Lead Cloud Architect | Architecte infonuagique principal
> t 1.888.796.8364 ext. 1403
>
>
> <
> https://cloud.ca/?utm_source=email&utm_medium=signature&utm_content=cloud-ca-logo-1&utm_campaign=general_email
> >
>


--

abhishek.ku...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

Re: [DISCUSS] CloudStack Kubernetes Service plugin

[Abhishek Kumar]

I would be really interested in exploring multi-master k8s cluster but it is 
not in proposal at the moment. We can surely look into this.
FS mentions, for deployment, plugin will use kubeadm and kubectl tools.


From: Pierre-Luc Dion 
Sent: 25 September 2019 22:41
To: dev@cloudstack.apache.org 
Subject: Re: [DISCUSS] CloudStack Kubernetes Service plugin

Make sense for the proposed implementation, would it handle redundant
master?
How would the k8s cluster would be created, using Rancher tools, kubectl or
other?

so far, the small part I understand from MaaS, it could be very interesting
to integrate it to cloudstack in a way where it could be use to  scale
Hypervisor host, specially KVM nodes.


On Wed, Sep 25, 2019 at 10:47 AM Paul Angus 
wrote:

> The proposed implementation will create a master and n worker nodes.
> It will also support (graceful) cluster resizing, the next step would be
> to enable the CloudStack plugin for Kubernetes to allow Kubernetes to drive
> that scaling, so that you can scale with demand rather than needing to
> oversize you environment to begin with.
>
> I've been keeping MaaS in mind as way of doing baremetal Kubernetes along
> side VM based Kubernetes clusters.  Interestingly a few people that I have
> spoken to have said that they prefer the use of VMs, because whole servers
> as the unit of scale is often very wasteful, unless you 'share' them which
> has all sorts of security implications...
>
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Pierre-Luc Dion 
> Sent: 25 September 2019 15:31
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] CloudStack Kubernetes Service plugin
>
> Hi Paul,
>
> Yeah, was bad timing for the CCCNA this year unfortunately :-(,  I'm not
> sure I'm curious to see how cloudstack could become more "other Apache
> products friendly" but I don't have particular use case compared to k8s
> integration. Has you are suggesting, would probably make sense to use Helm
> to deploy any other application stack.
>
> btw, we are still working on the Canonical MaaS integration, a bit more
> challenging than anticipated...
>
>
> To get back to a *Kubernetes Service plugin*:
> To me, as a user of cloudstack at the moment, If I deploy a k8s cluster, I
> need to deploy monstrous instances for worker nodes.
> which doesn't make sense if I'm a cloud consumer. So I think we need to
> solve something challenging: a k8s service that would scale has needed
> while keeping in mind redundancy of worker nodes without sacrifice on
> security. Is the worker node is part of the ongoing work or it's more about
> offering a k8s master and api infrastructure to a user ?
>
> An easy path would be some kind of shared worker nodes pool but that
> involve possible security risk unless you would trust users that consume
> those workers.
>
>
> On Wed, Sep 25, 2019 at 10:15 AM Paul Angus 
> wrote:
>
> > Hi Pierre-Luc,
> >
> > (we missed you at CCCNA!) How are you seeing CloudStack being more
> > deployment friendly?  What you do think that we could do on top of
> > creating the Kubenetes Cluster to begin with?
> > [thinking out loud - we could pre-package Tiller to make it easier to
> > deploy openWhisk via Helm charts ? ]
> >
> > Kind regards
> >
> >
> > Paul.
> >
> >
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Pierre-Luc Dion 
> > Sent: 25 September 2019 13:37
> > To: dev@cloudstack.apache.org
> > Subject: Re: [DISCUSS] CloudStack Kubernetes Service plugin
> >
> > Hi Rohit, Nux,
> >
> > Thanks Rohit for cloudstack-provider, that's exactly it ! :-D Nux, I
> agree
> > with your opinion, but there is a lot of interest for k8s and seams like
> a
> > lot of organisations are moving to container based infrastructures to
> > standardized their deployment.
> >
> > if we want to extent the discussion to function as a service, would you
> > guys see a possibility for us to be more aligned or more deployment
> > friendly for Openwhisk ?
> >
> > Cheers,
> >
> >
> > On Wed, Sep 25, 2019 at 6:54 AM Will Stevens 
> > wrote:
> >
> > > We see huge demand for K8s in our customer base. Just a note...
> > >
> > > On Wed,

Re: [DISCUSS] CloudStack Kubernetes Service plugin

[Abhishek Kumar]

nking out loud - we could pre-package Tiller to make it easier to
> deploy openWhisk via Helm charts ? ]
>
> Kind regards
>
>
> Paul.
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>
>
>
>
> -Original Message-
> From: Pierre-Luc Dion 
> Sent: 25 September 2019 13:37
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] CloudStack Kubernetes Service plugin
>
> Hi Rohit, Nux,
>
> Thanks Rohit for cloudstack-provider, that's exactly it ! :-D Nux, I agree
> with your opinion, but there is a lot of interest for k8s and seams like a
> lot of organisations are moving to container based infrastructures to
> standardized their deployment.
>
> if we want to extent the discussion to function as a service, would you
> guys see a possibility for us to be more aligned or more deployment
> friendly for Openwhisk ?
>
> Cheers,
>
>
> On Wed, Sep 25, 2019 at 6:54 AM Will Stevens 
> wrote:
>
> > We see huge demand for K8s in our customer base. Just a note...
> >
> > On Wed, Sep 25, 2019, 4:03 AM Nux!  wrote:
> >
> > > Do you guys see high demand for K8s?
> > >  From where I'm looking it seems to be going the way of Openstack,
> > > loads of hype, overcomplicated, near-impossible to upgrade.
> > > Not sure if it's worth investing resources for this.
> > >
> > > Lucian
> > >
> > > ---
> > > Sent from the Delta quadrant using Borg technology!
> > >
> > > On 2019-09-24 07:41, Abhishek Kumar wrote:
> > > > Hi all,
> > > >
> > > > I would like to propose developing a plugin for Kubernetes
> > > > integration in CloudStack, can be named CloudStack Kubernetes
> Service plugin.
> > > > I've written down an initial design document for it here,
> > > >
> > >
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Kube
> > rnetes+Service
> > > > Please review and provide your thoughts and suggestions.
> > > >
> > > > Regards,
> > > >
> > > >
> > > > Abhishek Kumar
> > > >
> > > > Software Engineer
> > > >
> > > > ShapeBlue
> > > >
> > > > abhishek.ku...@shapeblue.com
> > > >
> > > > www.shapeblue.com<http://www.shapeblue.com>
> > > >
> > > > abhishek.ku...@shapeblue.com
> > > > www.shapeblue.com<http://www.shapeblue.com>
> > > > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
> > >
> >
>
>
> --
>
> *Pierre-Luc Dion*Lead Cloud Architect | Architecte infonuagique principal
> t 1.888.796.8364 ext. 1403
>
>
> <
> https://cloud.ca/?utm_source=email&utm_medium=signature&utm_content=cloud-ca-logo-1&utm_campaign=general_email
> >
>


--

Re: Introduction

[Abhishek Kumar]

Welcome Pearl!

From: Pearl d'Silva 
Sent: 06 November 2019 10:04
To: dev@cloudstack.apache.org 
Subject: Introduction

Hello Everyone,

I'm Pearl and have recently joined Shapeblue. Really excited about being part 
of Cloudstack community. Looking forward to learn and contribute to the 
community.


Thanks & Regards,
Pearl Dsilva
pearl.dsi...@shapeblue.com




pearl.dsi...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue




abhishek.ku...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

Re: [DISCUSS]/[PROPOSAL] draft PRs

[Abhishek Kumar]

+1

From: Daan Hoogland 
Sent: 14 February 2020 17:33
To: dev 
Subject: [DISCUSS]/[PROPOSAL] draft PRs

devs, I thought I had already sent a mail about this but i cannot find it.
I'm sure i had mentioned it somewhere (probably on github).
this is a follow up on [1] and hopefully you'll agree, a slight improvement.

here it comes:

At the moment we are creating PRs with a [WIP] or [DO NOT MERGE] tag in the
title. This title stands the chance of being merged once we agree the PR is
ready for merge. It also clutters the title.

Github has introduced a nice feature a while ago; draft PR. When creating a
PR you can opt not to open it for merge but as draft. Choose a button left
of the "Create pull request" button, marked "Create draft PR". It will be a
full PR with all CI and discussion possibilities open. The only difference
is the merge button being disabled. One will than have to make/mark it
"ready for merge" before it *can* be merged.

[1]
https://lists.apache.org/thread.html/f3f0988907f85bfc2cfcb0fbcde831037f9b1cb017e94bc68932%40%3Cdev.cloudstack.apache.org%3E
please shoot any comments you may have back at me,
thanks

--
Daan

abhishek.ku...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 

[ANNOUNCE] Apache CloudStack CVE-2024-41107: SAML Signature Exclusion

[Abhishek Kumar]

Apache CloudStack project announces the release of LTS releases 4.19.1.0
and 4.18.2.2 that addresses CVE-2024-41107 that affects CloudStack SAML
users, of severity 'important' explained below.

# CVE-2024-41107: SAML Signature Exclusion

The CloudStack SAML authentication (disabled by default) does not enforce
signature check. In CloudStack environments where SAML authentication is
enabled, an attacker that initiates CloudStack SAML single sign-on
authentication can bypass SAML authentication by submitting a spoofed SAML
response with no signature and known or guessed username and other user
details of a SAML-enabled CloudStack user-account. In such environments,
this can result in a complete compromise of the resources owned and/or
accessible by a SAML enabled user-account.

# Credits

The original issue was reported by Christian Gross of Netcloud AG who filed
it as a bug report at https://github.com/apache/cloudstack/issues/4519.

More recently it was reported as a security issue by the following
reporters from the Apple Services Engineering Security team:

- Damon Smith
- Adam Pond
- Terry Thibault

# Affected Versions

- Apache CloudStack 4.5.0 through 4.18.2.1
- Apache CloudStack 4.19.0.0 through 4.19.0.2

# Resolution

Affected users are recommended to disable the SAML authentication plugin
by setting the "saml2.enabled" global setting to "false", or upgrade to
version 4.18.2.2, 4.19.1.0 or later, which addresses this issue.

# Downloads and Documentation

The official source code for the 4.18.2.2 and 4.19.1.0 releases can be
downloaded from the project downloads page:
https://cloudstack.apache.org/downloads

The 4.18.2.2 and 4.19.1.0 release notes can be found at:
https://docs.cloudstack.apache.org/en/4.18.2.2/releasenotes/about.html
https://docs.cloudstack.apache.org/en/4.19.1.0/releasenotes/about.html

In addition to the official source code release, individual contributors
have also made release packages available on the Apache CloudStack
download page, and available at:

https://download.cloudstack.org/el/7/
https://download.cloudstack.org/el/8/
https://download.cloudstack.org/el/9/
https://download.cloudstack.org/suse/15/
https://download.cloudstack.org/ubuntu/dists/
https://www.shapeblue.com/cloudstack-packages/

Re: [ANNOUNCE] New committer: Daniel Augusto Veronezi Salvador

[Abhishek Kumar]

Congratulations Daniel!

From: Gabriel Beims Bräscher 
Sent: 06 July 2021 22:51
To: dev 
Subject: [ANNOUNCE] New committer: Daniel Augusto Veronezi Salvador

The Project Management Committee (PMC) for Apache CloudStack
has invited Daniel to become a committer and we are pleased
to announce that the contributor has accepted.

Please join me in congratulating Daniel on this accomplishment.

Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.
Being a PMC member enables assistance with the management
and to guide the direction of the project.

--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair

 

Re: [ANNOUNCE] New committer: Pearl DSilva

[Abhishek Kumar]

Congratulations Pearl!

From: Gabriel Beims Bräscher 
Sent: 06 July 2021 22:51
To: dev 
Subject: [ANNOUNCE] New committer: Pearl DSilva

The Project Management Committee (PMC) for Apache CloudStack
has invited Pearl to become a committer and we are pleased
to announce that the contributor has accepted.

Please join me in congratulating Pearl on this accomplishment.

Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.
Being a PMC member enables assistance with the management
and to guide the direction of the project.

--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair

 

Re: [ANNOUNCE] New committer: David Jumani

[Abhishek Kumar]

Congrats David!

From: Gabriel Beims Bräscher 
Sent: 06 July 2021 22:51
To: dev 
Subject: [ANNOUNCE] New committer: David Jumani

The Project Management Committee (PMC) for Apache CloudStack
has invited David to become a committer and we are pleased
to announce that the contributor has accepted.

Please join me in congratulating David on this accomplishment.

Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.
Being a PMC member enables assistance with the management
and to guide the direction of the project.

--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair

 

[DISCUSS] VMware network rate for network and VMs

[Abhishek Kumar]

Hi all,

I've been working on fixing/refactoring VMware portgroup reconfigure on network 
offering change, https://github.com/apache/cloudstack/pull/5181
While working on it I found different portgroups on the same VLAN can be used 
based on the different network rates used in the network offering of the 
network and compute offering of the user VMs. Below are my findings:

  *   Network offerings will control network rate only for VR(s) and 
non-default NICs of the user VMs.
  *   Default network rate for VRs and non-default NICs of the user VMs can be 
controlled by global setting, "network.throttling.rate".

  *   For the default NIC of user VMs, the network rate is controlled by the 
compute offerings of the VM.

  *   For the default NIC of user VMs, the default network rate can be 
controlled using the global setting,"vm.network.throttling.rate".

So now my queries are:

  *   Is having VM-level (using compute offering and global setting for VMs) 
useful? Having a higher network rate for VMs and a lower network rate for 
VRs(network) will make it useless.
  *   Should there be a single portgroup in vCenter based on the network rate 
of VRs/network especially in the case when the network rate for VRs is lower?
  *   Even while using different network rates, should there be consistency 
across different NICs of user VMs? Currently, compute offering and global 
setting only affects the default NIC of the user VMs.

Please share your thoughts and ideas. It will be interesting to know how others 
configure network throttling for networks and VMs.

Regards,
Abhishek


 

Re: [DISCUSS] VMware network rate for network and VMs

[Abhishek Kumar]

Hi Vivek,

Thank you for your response.
I understand the scenarios you have explained but the issue I face right now is 
that portgroup for user VMs is not updated when network offering (with network 
rate difference) for that network is changed from ACS.
I tried to show that here, https://youtu.be/Kdaad9c1Fq4

I've also gone through the code and on network offering change, currently ACS 
just stops and destroys the running VR, creates a new portgroup (for new 
network rate) and starts new VR on that portgroup. And user VMs continue 
running on the existing portgroup.

Similarly, for different NICs of the VM, it can have different network rate 
depending on default and non-default NIC.
eg:
VM, v1 is created with a compute offering having network rate, 350Mbps
It has three networks:
n1 with network offering having network rate 400Mbps (default NIC)
n2 with network offering having network rate 500Mbps
n3 with network offering having no rate specified, defaulted to 
"network.throttling.rate" 200Mbps. "vm.network.throttling.rate" is set to 
375Mbps

Now, three nics of the VM will have portgroups with following network rates:
NIC1 (default) - 350Mbps (taken from compute offering)
NIC2 - 500Mbps (taken from n/w offering)
NIC3 - 200Mbps(taken from n/w offering)

Therefore, my point is both network rate from compute offering and value of 
vm.network.throttling.rate doesn't affect all the NICs of the VM and are 
honored just by the default NIC.

Regards,
Abhishek


From: Vivek Kumar 
Sent: 26 July 2021 15:32
To: CloudStack Users Mailing list 
Cc: dev@cloudstack.apache.org 
Subject: Re: [DISCUSS] VMware network rate for network and VMs

Hello Abhishek,

Everything is useful and it completely depends on your requirements..!

  *   Is having VM-level (using compute offering and global setting for
VMs) useful? Having a higher network rate for VMs and a lower network rate
for VRs(network) will make it useless.

Ans - Yes definitely it's useful, so consider a scenerio where you want to
provide a higher speed of data transfer between VMs in same network  (
Guest traffic ) but lower speed for public traffic or may be on the
different network.


  *   Should there be a single portgroup in vCenter based on the network
rate of VRs/network especially in the case when the network rate for VRs is
lower?

Ans -  ACS create separate port group for each config, single port groups
can't controller multiple QoS. So let's suppose if you create a VM with 500
Mbps network rate, ACS will create a port group and will put 500Mbps in
network rate, so if you create other VMs under the same network and same
compute offering it will out under the same, but the moment you change your
network offering i.e 200 Mbps then it will create a separate port group
with 200 Mbps network rate and will attach same to the VM.


  *   Even while using different network rates, should there be consistency
across different NICs of user VMs? Currently, compute offering and global
setting only affects the default NIC of the user VMs.

Ans- As I said, it create separate port group as per the network rate and
VLAN.

Regards
Vivek Kumar

On Mon, 26 Jul, 2021, 15:04 Abhishek Kumar, 
wrote:

> Hi all,
>
> I've been working on fixing/refactoring VMware portgroup reconfigure on
> network offering change, https://github.com/apache/cloudstack/pull/5181
> While working on it I found different portgroups on the same VLAN can be
> used based on the different network rates used in the network offering of
> the network and compute offering of the user VMs. Below are my findings:
>
>   *   Network offerings will control network rate only for VR(s) and
> non-default NICs of the user VMs.
>   *   Default network rate for VRs and non-default NICs of the user VMs
> can be controlled by global setting, "network.throttling.rate".
>
>   *   For the default NIC of user VMs, the network rate is controlled by
> the compute offerings of the VM.
>
>   *   For the default NIC of user VMs, the default network rate can be
> controlled using the global setting,"vm.network.throttling.rate".
>
> So now my queries are:
>
>   *   Is having VM-level (using compute offering and global setting for
> VMs) useful? Having a higher network rate for VMs and a lower network rate
> for VRs(network) will make it useless.
>   *   Should there be a single portgroup in vCenter based on the network
> rate of VRs/network especially in the case when the network rate for VRs is
> lower?
>   *   Even while using different network rates, should there be
> consistency across different NICs of user VMs? Currently, compute offering
> and global setting only affects the default NIC of the user VMs.
>
> Please share your thoughts and ideas. It will be interesting to know how
> others configure network throttling for networks and VMs.
>
> Regards,
> Abhishek
>
>
>
>
>

 

Re: [ANNOUNCE] Nicolas Vazquez has joined the PMC

[Abhishek Kumar]

Congrats Nicolas!

From: Gabriel Beims Bräscher 
Sent: 03 August 2021 00:58
To: dev 
Subject: [ANNOUNCE] Nicolas Vazquez has joined the PMC

Hello @dev,

I am pleased to announce that Nicolas Vazquez was invited to join the
Project Management Committee (PMC) for Apache CloudStack, and he has
gracefully accepted.

Nicolas has been working actively on the project since 2015 and has proven
a great contributor, committer and now will be part of the PMC.

Please join me in congratulating Nicolas and wish him wisdom in his new
role.

On behalve of the PMC,
--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair

 

Re: [VOTE] Apache CloudStack Kubernetes Provider v1.0.0 (RC1)

[Abhishek Kumar]

+1

Tested kubernetes-provider running on k8s cluster deployed using version 1.15.0 
with a KVM env built using ACS main branch.
Able to deploy test deployment from repo traefik-ingress-controller


From: David Jumani 
Sent: 04 August 2021 17:12
To: dev@cloudstack.apache.org ; users 

Subject: [VOTE] Apache CloudStack Kubernetes Provider v1.0.0 (RC1)

Hi All,

I've created the initial CloudStack Kubernetes Provider release v1.0.0, with 
the following artifacts up for a vote:

Git Branch and Commit SH:
https://github.com/apache/cloudstack-kubernetes-provider/tree/1.0
Commit: a8fccd9fe5c145bc3a12e3681bdf33e9f6ed382c

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

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

The docker image can be found at 
https://hub.docker.com/r/apache/cloudstack-kubernetes-provider

The documentation for the same can be found at
https://github.com/apache/cloudstack-documentation/blob/main/source/plugins/cloudstack-kubernetes-provider.rst
https://github.com/apache/cloudstack-kubernetes-provider/blob/main/README.md#deployment
(be sure to replace the image version 
`apache/cloudstack-kubernetes-provider:v1.0.0` with 
`apache/cloudstack-kubernetes-provider:v1.0.0-RC20210804T0500`)

The vote will be open until 08 August 2021.

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Thanks,
David




 

Re: GSoC 2021 Completes

[Abhishek Kumar]

Congratulations to both students and mentors, and the community in general!
Some great work started with these projects. Looking forward to seeing them in 
action in upcoming releases.
Students - hoping ACS community will continue to interest you and will look 
forward to seeing you around.


Regards,
Abhishek

From: Rohit Yadav 
Sent: 03 September 2021 16:10
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org ; Bikram Biswas 
; Sangwoo Bae ; Apurv 
Gupta ; atrocityth...@gmail.com 
Cc: Apache CloudStack Marketing 
Subject: GSoC 2021 Completes

All,

I'm happy to share with the community that our project participation at Google 
Summer of Code 2021 comes to an end with four successful projects [1][2] by our 
four students passing with flying colours. Results were available earlier this 
week on 31st Aug 2021 [3].

Let's use this opportunity to congratulate our students and mentors and ask 
them to share any feedback on the project - hope we'll participate next year 
too!

Let me start;

Congratulate Apurv, Junxuan, Bikram, and Sangwoo for your hard work and 
successful projects! We look forward to seeing you around in the community!

Thank you mentors for your hard work and mentoring the students - Pearl, David, 
Suresh, Bobby, Hari, and Nicolas!

Two of our students have blogged about their experiences, you may read them 
here:
Apurv's blog: 
https://apurv-gupta.medium.com/google-summer-of-code-apachecloudstack-final-report-bae911b0bd44
Bikram's blog: 
https://medium.com/@bickrombishsass/gsoc-2021-experience-at-apache-cloudstack-8946fe31ff5b

[1] GSoC 2021 at Apache CloudStack Project: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/GSoC+2021
[2] Student PR submissions: 
https://github.com/apache/cloudstack/pulls?q=is%3Aopen+is%3Apr+label%3Agsoc2021
[3] https://summerofcode.withgoogle.com/how-it-works/#timeline

Regards.




 

Re: [VOTE] Release Apache CloudStack CloudMonkey 6.2.0

[Abhishek Kumar]

+1

Tested build for different operations on a ACS 4.16-snapshot env. Everything 
worked as expected.

Regards,
Abhishek

From: Pearl Dsilva 
Sent: 24 September 2021 13:14
To: dev@cloudstack.apache.org 
Cc: us...@cloudstack.apache.org 
Subject: [VOTE] Release Apache CloudStack CloudMonkey 6.2.0

Hi All,

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

Git Branch and commit SHA:
https://github.com/apache/cloudstack-cloudmonkey/commits/8aae61e20c6789133c1d97d49e58f354ba7428c3

Commit:
8aae61e20c6789133c1d97d49e58f354ba7428c3

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

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

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

The vote will be open until October 1st, 2021.

For sanity in tallying the vote, can PMC members please be sure to
indicate "(binding)" with their vote?
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and the reason why)

Regards,
Pearl Dsilva

 

Re: [VOTE] Apache CloudStack 4.16.0.0 (RC2)

[Abhishek Kumar]

Hi all,

-1

I'm hitting an issue with deploying a CKS cluster in an upgraded env.

2021-10-29 12:27:30,544 ERROR [c.c.k.c.a.KubernetesClusterActionWorker] 
(API-Job-Executor-7:ctx-62c6bc28 job-79 ctx-f80558ff) (logid:7a78d08a) 
Provisioning the control VM failed in the Kubernetes cluster : c3
com.cloud.exception.InvalidParameterValueException: The template 203 is not 
available for use
at 
com.cloud.vm.UserVmManagerImpl.createVirtualMachine(UserVmManagerImpl.java:3935)
at 
com.cloud.vm.UserVmManagerImpl.createAdvancedVirtualMachine(UserVmManagerImpl.java:3634)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

Deployed a 4.14.1 env with 2 clusters (2 ESXi 6.7 hosts in 1st cluster and 1 
ESXi 6.7 host in 2nd cluster); centos7 MS; Advanced zone
Upgraded the env to 4.16RC2 using 
https://download.cloudstack.org/testing/41600-RC2/ (it didn't has centos7 
directory/symlink there)
I did not pre-register 4.16 system VM template.
After the upgrade, almost everything else worked fine except the error 
mentioned with CKS cluster deployment above.
I've created a Github ticket for the same here, 
https://github.com/apache/cloudstack/issues/5641

Other things that worked fine for me during testing:

  *   VM lifecycle - deploy, start, stop, migrate, etc
  *   Networks
  *   Templates
  *   Offerings
  *   Infrastructure operations

Regards,
Abhishek


From: Nicolas Vazquez 
Sent: 25 October 2021 19:25
To: dev@cloudstack.apache.org ; users 

Subject: [VOTE] Apache CloudStack 4.16.0.0 (RC2)

Hi All,

I have created a 4.16.0.0 release (RC2), with the following artifacts up for 
testing and a vote:

Git Branch and Commit SHA:
https://github.com/apache/cloudstack/tree/4.16.0.0-RC20211025T0851
Commit: 1e070be4c9a87650f48707a44efff2796dfa802a

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

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

The vote will be open until 28th October 2021, 16.00 CET (72h).

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

For users convenience, the packages from this release candidate (RC2) and
4.16.0 systemvmtemplates are available here:
https://download.cloudstack.org/testing/41600-RC2/
https://download.cloudstack.org/systemvm/4.16/

Regards,
Nicolas Vazquez





 

Re: [VOTE] Apache CloudStack 4.16.0.0 (RC3)

[Abhishek Kumar]

+1

Tested upgrade for a 4.14.1 env to 4.16.0.0 RC3 packages
Advanced zone; 1 VMware cluster with 2x ESXi 6.7 hosts.
Tested following:

  *   VM lifecycle tests
  *   Kubernetes cluster deployment
  *   Changing network rate for isolated networks
  *   Template, ISO registration
  *   Basic operations with accounts and domains
  *   Import-export VM functionality
  *   Group action in UI

Regards,
Abhishek

From: Nicolas Vazquez 
Sent: 05 November 2021 00:11
To: users ; dev@cloudstack.apache.org 

Subject: [VOTE] Apache CloudStack 4.16.0.0 (RC3)

Hi All,
I have created a 4.16.0.0 release (RC3), with the following artifacts up for 
testing and a vote:

Git Branch and Commit SHA:
https://github.com/apache/cloudstack/tree/4.16.0.0-RC20211104T1414
Commit: 44c08b5acc598972b4f0af576ffdea4e2447cb41

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

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

The vote will be open until 8th November 2021.

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

For users convenience, the packages from this release candidate (RC3) and
4.16.0 systemvmtemplates are available here:
https://download.cloudstack.org/testing/41600-RC3/
https://download.cloudstack.org/systemvm/4.16/

Regards,
Nicolas Vazquez




 

Re: import existing instance from vsphere to cloudstack failed

[Abhishek Kumar]

Hi Haven,

From the error, API is failing to find the local storage pool for the volume 
for disk ID: 2-2000. I'm not sure if importing VM with local storage is widely 
tested so there can be an issue there. There could be some difference in pool's 
path as returned by listUnmanagedInstances vs listStoragePools APIs.
Can you please share output of:

  *   listUnmanagedInstances API for the VM
  *   listStoragePools API for the storage pool that corresponds to datastore 
named - localsr1

Regards,
Abhishek

From: haven <382829...@qq.com.INVALID>
Sent: 10 December 2021 22:02
To: dev 
Subject: import existing instance from vsphere to cloudstack failed

Hi devs
    I tried to   import existing instance from vsphere to 
cloudstack failed， this instance use vsphere local storage datastore .already 
enabled localstorage vmware zone and found that localstorage in 
cloudstack,  get same error again。Is there any way to import it normally？


ENV:
Version: cloudstack 4.15.2 
vsphere:6.5


API:
http://x.x.x.x:8090/client/api/?clusterid=8f5efc66-17a9-4f80-925b-92722a04a501&name=localstorage&serviceofferingid=a9544da9-cc83-4ed0-9cf5-52e46f9e9361&command=importUnmanagedInstance&nicnetworklist[0].network=7b0b27c0-7827-4505-9c53-a7969406562b&nicnetworklist[0].nic=%E7%BD%91%E7%BB%9C%E9%80%82%E9%85%8D%E5%99%A8%201&response=json


Error:
{"queryasyncjobresultresponse":{"accountid":"623017de-4b49-11ec-b1af-52540044e80f","userid":"6232957f-4b49-11ec-b1af-52540044e80f","cmd":"org.apache.cloudstack.api.command.admin.vm.ImportUnmanagedInstanceCmd","jobstatus":2,"jobprocstatus":0,"jobresultcode":530,"jobresulttype":"object","jobresult":{"errorcode":530,"errortext":"Storage
 pool for disk 硬盘 1(2-2000) with datastore: localsr1 not found in zone ID: 
db959f5f-2b65-435f-8cd7-2efb7d87c3c7"},"created":"2021-12-10T13:10:29+0800","completed":"2021-12-10T13:10:30+0800","jobid":"2ce8de02-8abc-41ef-acd5-2c205b206598"}}

 

Re: 回复： import existing instance from vsphere to cloudstack failed

[Abhishek Kumar]

Hi,

Thank you for sharing the out of APIs.
I checked it with the code and unfortunately the current code cannot import VMs 
with local storages considering the output that listUnmanagedInstances API 
returns. Code 
(https://github.com/shapeblue/cloudstack/blob/main/server/src/main/java/org/apache/cloudstack/vm/UnmanagedVMsManagerImpl.java#L485-L505)
 tries to compare datastorename with the path of storage pool and this case 
there are different.
[https://opengraph.githubassets.com/93c5f82065ba2a8daa2926dd261b1d20d28d781966a42bdd7133772f4080ca42/shapeblue/cloudstack]
cloudstack/UnmanagedVMsManagerImpl.java at main · 
shapeblue/cloudstack
The upstream repository is at http://github.com/apache/cloudstack. This is 
ShapeBlue's support/patch branches and Apache CloudStack™ backup - 
cloudstack/UnmanagedVMsManagerImpl.java at main · s...
github.com

You may raise a bug on GitHub for this.

Regards,
Abhishek

From: haven <382829...@qq.com.INVALID>
Sent: 14 December 2021 12:35
To: dev@cloudstack.apache.org 
Subject: 回复： import existing instance from vsphere to cloudstack failed

Hi Abhishek
     Thanks for your reply , info below:



 listUnmanagedInstances API for the VM

{"listunmanagedinstancesresponse":{"count":2,"unmanagedinstance":[{"name":"vc01","clusterid":"8f5efc66-17a9-4f80-925b-92722a04a501","hostid":"a75916bf-eb08-45cd-9101-7a2cabf06d6e","powerstate":"PowerOn","cpunumber":4,"cpucorepersocket":1,"cpuspeed":0,"memory":8192,"osid":"windows8Server64Guest","osdisplayname":"Microsoft
 Windows Server 2012 (64 位)","disk":[{"id":"1-2000","label":"硬盘 
1","capacity":53687091200,"imagepath":"[localsr1] 
acs/acs.vmdk","controller":"lsisas1068","controllerunit":0,"position":0,"datastorename":"localsr1"}],"nic":[{"id":"网络适配器
 1","networkname":"VM 
Network","macaddress":"00:0c:29:62:31:ad","vlanid":0,"adaptertype":"E1000"}]},{"name":"localstorage","clusterid":"8f5efc66-17a9-4f80-925b-92722a04a501","hostid":"a75916bf-eb08-45cd-9101-7a2cabf06d6e","powerstate":"PowerOn","cpunumber":1,"cpucorepersocket":1,"cpuspeed":0,"memory":2048,"osid":"centos7_64Guest","osdisplayname":"CentOS
 7 (64 位)","disk":[{"id":"2-2000","label":"硬盘 
1","capacity":17179869184,"imagepath":"[localsr1] 
localstorage/localstorage.vmdk","controller":"pvscsi","controllerunit":0,"position":0,"datastorename":"localsr1"}],"nic":[{"id":"网络适配器
 1","macaddress":"00:50:56:b4:fa:53","adaptertype":"Vmxnet3"}]}]}}



listStoragePools

{"liststoragepoolsresponse":{"count":5,"storagepool":[{"id":"a8eab88e-b302--92d1-04e3b83d47b7","zoneid":"db959f5f-2b65-435f-8cd7-2efb7d87c3c7","zonename":"vmware01","podid":"dd8a1ce9-f16b-4de2-9441-7baa3e26ecd8","podname":"vmwarepod","name":"datastore1","ipaddress":"VMFS
 datastore: 
datastore-10","path":"datastore-10","created":"2021-12-09T10:28:07+0800","type":"VMFS","clusterid":"8f5efc66-17a9-4f80-925b-92722a04a501","clustername":"10.226.18.132/Datacenter1/cl01","disksizetotal":118648471552,"disksizeallocated":0,"disksizeused":7552892928,"state":"Up","scope":"HOST","overprovisionfactor":"2.0","provider":"DefaultPrimary","storagecapabilities":{"VOLUME_SNAPSHOT_QUIESCEVM":"false"}},{"id":"a34f25c3-3452-3441-828c-302a2c6f7f03","zoneid":"db959f5f-2b65-435f-8cd7-2efb7d87c3c7","zonename":"vmware01","podid":"dd8a1ce9-f16b-4de2-9441-7baa3e26ecd8","podname":"vmwarepod","name":"nfs1","ipaddress":"10.226.18.132","path":"/Datacenter1/nfs1","created":"2021-12-08T15:05:34+0800","type":"NFS","clusterid":"8f5efc66-17a9-4f80-925b-92722a04a501","clustername":"10.226.18.132/Datacenter1/cl01","disksizetotal":11005929193472,"disksizeallocated":34365323222,"disksizeused":195802693632,"state":"Up","scope":"CLUSTER","overprovisionfactor":"2.0","provider":"DefaultPrimary","storagecapabilities":{"VOLUME_SNAPSHOT_QUIESCEVM":"false"}},{"id":"f42dea39-fa23-3e27-9062-45381b9cc1c7","zoneid":"db959f5f-2b65-435f-8cd7-2efb7d87c3c7","zonename":"vmware01","podid":"dd8a1ce9-f16b-4de2-9441-7baa3e26ecd8","podname":"vmwarepod","name":"nfs2","ipaddress":"10.226.18.132","path":"/Datacenter1/nfs2","created":"2021-12-08T13:55:49+0800","type":"NFS","clusterid":"8f5efc66-17a9-4f80-925b-92722a04a501","clustername":"10.226.18.132/Datacenter1/cl01","disksizetotal":11005933387776,"disksizeallocated":4194304000,"disksizeused":195802693632,"state":"Up","scope":"CLUSTER","overprovisionfactor":"2.0","provider":"DefaultPrimary","storagecapabilities":{"VOLUME_SNAPSHOT_QUIESCEVM":"false"}},{"id":"44069041-572d-32b0-abc4-745b97eae508","zoneid":"690eaa87-5228-4192-a388-ea250b58d963","zonename":"uat","podid":"f0a0d079-2944-45bd-8c77-b60b09330eff","podname":"SP01","name":"Ceph
 
RBD","ipaddress":"10.100.250.11,10.100.250.12,10.100.250.13","path":"rbd","created":"2021-11-22T12:22:40+080

Re: [ANNOUNCE] New committer: Ivet Petrova

[Abhishek Kumar]

Congrats Ivet!

Regards,
Abhishek




From: Suresh Anaparti 
Sent: 21 December 2021 18:42
To: dev@cloudstack.apache.org 
Subject: Re: [ANNOUNCE] New committer: Ivet Petrova

Congratulations Ivet!

Regards,
Suresh

On 21/12/21, 6:18 PM, "Gabriel Beims Bräscher"  wrote:

The Project Management Committee (PMC) for Apache CloudStack
has invited Ivet Petrova to become a committer and we are pleased
to announce that she has accepted.

Ivet has shown commitment to the Apache CloudStack community. Ivet has been
contributing to discussions related to marketing and community development,
organizing events, social media posts, interviews, videos, etc.

Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.
A PMC member helps manage and guide the direction of the project.

Let´s congratulate and welcome Ivet, Apache CloudStack’s newest committer.

--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair





 

Re: [ANNOUNCE] New committer: Slavka Peleva

[Abhishek Kumar]

Congrats Slavka!

Regards,
Abhishek




From: Gabriel Beims Bräscher 
Sent: 21 December 2021 18:18
To: dev 
Subject: [ANNOUNCE] New committer: Slavka Peleva

The Project Management Committee (PMC) for Apache CloudStack
has invited Slavka Peleva to become a committer and we are pleased
to announce that she has accepted.

Slavka has shown commitment to the Apache CloudStack community,
contributing with technical discussions in mailing lists, proposing
features, reviewing & testing PRs, creating PRs, resulting in relevant
contributions merged in the upstream.

Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.
A PMC member helps manage and guide the direction of the project.

Let´s congratulate and welcome Slavka, Apache CloudStack’s newest committer.

--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair

 

Re: IPV6 in Isolated/VPC networks

[Abhishek Kumar]

Hi all,

IPv6 Support in Isolated Network and VPC with Static Routing based on the 
design doc [1] has been implemented and is available in 4.17.0 RC2. I hope 
while testing 4.17.0 RC2 you will also try to test it ?
Documentation for it is available at 
http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/262/plugins/ipv6.html#isolated-network-and-vpc-tier
 (will be available in the official docs once 4.17.0 version of docs is built).

[1] 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+Support+in+Isolated+Network+and+VPC+with+Static+Routing

Regards,
Abhishek


From: Rohit Yadav 
Sent: 13 September 2021 14:30
To: dev@cloudstack.apache.org 
Subject: Re: IPV6 in Isolated/VPC networks

Thanks Alex, Wei. I've updated the docs here: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+Support+in+Isolated+Network+and+VPC+with+Static+Routing

I'll leave the thread open for futher discussion/ideas/feedback. I think we've 
completed the phase1 design doc including all feedback comments for adding IPv6 
support in CloudStack and some initial poc/work can be started. My colleagues 
and I will keep everyone posted on this thread and/or on a Github PR as and 
when we're able to start our work on the same (after 4.16, potentially towards 
4.17).


Regards.


From: Wei ZHOU 
Sent: Friday, September 10, 2021 20:22
To: dev@cloudstack.apache.org 
Subject: Re: IPV6 in Isolated/VPC networks

Agree with Alex.
We only need to know how many /64 are allocated. We do not care how many
ipv6 addresses are used by VMs.

-Wei

On Fri, 10 Sept 2021 at 16:36, Alex Mattioli 
wrote:

> Hi Rohit,
>
> I'd go for option 2, don't see a point tracking anything smaller than a
> /64 tbh.
>
> Cheers
> Alex
>
>
>
>
> -Original Message-
> From: Rohit Yadav 
> Sent: 09 September 2021 12:44
> To: dev@cloudstack.apache.org
> Subject: Re: IPV6 in Isolated/VPC networks
>
> Thanks Alex, Kristaps. I've updated the design doc to reflect two
> agreements:
>
>   *   Allocate /64 for both isolated network and VPC tiers, no large
> allocation of prefixes to VPC (cons: more static routing rules for upstream
> router/admins)
>   *   All systemvms (incl. ssvm, cpvm, VRs) get IPv6 address if zone has a
> dedicated /64 prefix/block for systemvms
>
> The only outstanding question now is:
>
>   *   How do we manage IPv6 usage? Can anyone advise how we do IPv6 usage
> for shared network (design, implementation and use-cases?)
> Option1: We don't do it, all user VMs nics have ipv4 address which whose
> usage we don't track. For public VR/nics/networks, we can simply add the
> IPv6 details for a related IPv4 address.
> Option2: Implement a separate, first-class IPv6 address or /64 prefix
> tracking/management and usage for all VMs and systemvms nic (this means
> account/domain level limits and new billing/records)
> Option3: other thoughts?
>
>
> Regards.
>
> 
> From: Alex Mattioli 
> Sent: Wednesday, September 8, 2021 23:24
> To: dev@cloudstack.apache.org 
> Subject: RE: IPV6 in Isolated/VPC networks
>
> Hi Rohit, Kristaps,
>
> I'd say option 1 as well,  it does create a bit more overhead with static
> routes but if that's automated for a VPC it can also be easily automated
> for several tiers of a VPC.  We also don't constrain the amount of tiers in
> a  VPC.
> It has the added advantage to be closer to the desired behaviour with
> dynamic routing in the future, where a VPC VR can announce several subnets
> upstream.
>
> Cheers
> Alex
>
>
>
>
>
>
>
>
>
>
> -Original Message-
> From: Rohit Yadav 
> Sent: 08 September 2021 19:04
> To: dev@cloudstack.apache.org
> Subject: Re: IPV6 in Isolated/VPC networks
>
> Hi Kristaps,
>
> Thanks for sharing, I suppose that means individual tiers should be
> allocated /64 instead of larger ipv6 blocks to the whole VPC which could
> cause wastage.
>
> Any objection from anybody?
>
> Regards.
> 
> From: Kristaps Cudars 
> Sent: Wednesday, September 8, 2021 9:24:01 PM
> To: dev@cloudstack.apache.org 
> Subject: Re: IPV6 in Isolated/VPC networks
>
> Hello,
>
> I asked networking team to comment on "How should the IPv6
> block/allocation work in VPCs?"
> Option1: They haven't seen lately devices with limits on how many static
> routes can be created.
> Option2: With /60 and /62 assignments and big quantity of routers IPv6
> assignment from RIPE NNC can be drained fast.
>
> /48 contains 64000 /64
> /60 contains 16 /64
> 64000 / 16 = 4000 routers
>
>
> On 2021/09/07 11:59:09, Rohit Yadav  wrote:
> > All,
> >
> > After another iteration with Alex, I've updated the design doc. Kindly
> review:
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+Support+in
> > +Isolated+Network+and+VPC+with+Static+Routing
> >
> >
> > ... and advise on some outstanding questions:
> >
> >   *   How should the IPv6 block/allocation work in VPCs?
> > Option1: Should this be simply /64 allocation

Re: IPV6 in Isolated/VPC networks

[Abhishek Kumar]

Yes. When a public IPv6 is assigned or released, CloudStack will publish event 
with type NET.IP6ASSIGN, NET.IP6RELEASE.
These event notifications can be tracked. And with improvements in events 
framework, these event messages will have network uuid as entityuuid and 
Network as entitytype. Using this network can be queried using to list IPv6 
routes that need to be added.

Sample event message,

{"eventDateTime":"2022-05-10 09:32:12 
+","entityuuid":"14658b39-9d20-4783-a1bc-12fb58bcbd98","Network":"14658b39-9d20-4783-a1bc-12fb58bcbd98","description":"Assigned
 public IPv6 address: fd23:313a:2f53:3000:1c00:baff:fe00:4 for network ID: 
14658b39-9d20-4783-a1bc-12fb58bcbd98","event":"NET.IP6ASSIGN","user":"bde866ba-c600-11ec-af19-1e00320001f3","account":"bde712c9-c600-11ec-af19-1e00320001f3","entity":"Network","status":"Completed"}


?Sample API call,
> list networks id=14658b39-9d20-4783-a1bc-12fb58bcbd98 filter=id,name,ip6routes
{
  "count": 1,
  "network": [
{
  "id": "14658b39-9d20-4783-a1bc-12fb58bcbd98",
  "ip6routes": [
{
  "gateway": "fd23:313a:2f53:3000:1c00:baff:fe00:4",
  "subnet": "fd23:313a:2f53:3cbf::/64"
    }
  ],
  "name": "routing_test"
}
  ]
}





From: Wido den Hollander 
Sent: 10 May 2022 13:59
To: dev@cloudstack.apache.org ; Abhishek Kumar 

Subject: Re: IPV6 in Isolated/VPC networks

Op 10-05-2022 om 10:19 schreef Abhishek Kumar:
> Hi all,
>
> IPv6 Support in Isolated Network and VPC with Static Routing based on the 
> design doc [1] has been implemented and is available in 4.17.0 RC2. I hope 
> while testing 4.17.0 RC2 you will also try to test it ?
> Documentation for it is available at 
> http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/262/plugins/ipv6.html#isolated-network-and-vpc-tier
>  (will be available in the official docs once 4.17.0 version of docs is 
> built).
>

Great work!

I see only static routing is supported. But do we publish something on
the message bus once a new VR/VPC is created?

This way you could pick up these messages and have the network create a
(static) route based on those.

ExaBGP for example could be used to inject such routes.

Wido

> [1] 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+Support+in+Isolated+Network+and+VPC+with+Static+Routing
>
> Regards,
> Abhishek
>
> 
> From: Rohit Yadav 
> Sent: 13 September 2021 14:30
> To: dev@cloudstack.apache.org 
> Subject: Re: IPV6 in Isolated/VPC networks
>
> Thanks Alex, Wei. I've updated the docs here: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+Support+in+Isolated+Network+and+VPC+with+Static+Routing
>
> I'll leave the thread open for futher discussion/ideas/feedback. I think 
> we've completed the phase1 design doc including all feedback comments for 
> adding IPv6 support in CloudStack and some initial poc/work can be started. 
> My colleagues and I will keep everyone posted on this thread and/or on a 
> Github PR as and when we're able to start our work on the same (after 4.16, 
> potentially towards 4.17).
>
>
> Regards.
>
> 
> From: Wei ZHOU 
> Sent: Friday, September 10, 2021 20:22
> To: dev@cloudstack.apache.org 
> Subject: Re: IPV6 in Isolated/VPC networks
>
> Agree with Alex.
> We only need to know how many /64 are allocated. We do not care how many
> ipv6 addresses are used by VMs.
>
> -Wei
>
> On Fri, 10 Sept 2021 at 16:36, Alex Mattioli 
> wrote:
>
>> Hi Rohit,
>>
>> I'd go for option 2, don't see a point tracking anything smaller than a
>> /64 tbh.
>>
>> Cheers
>> Alex
>>
>>
>>
>>
>> -Original Message-
>> From: Rohit Yadav 
>> Sent: 09 September 2021 12:44
>> To: dev@cloudstack.apache.org
>> Subject: Re: IPV6 in Isolated/VPC networks
>>
>> Thanks Alex, Kristaps. I've updated the design doc to reflect two
>> agreements:
>>
>>*   Allocate /64 for both isolated network and VPC tiers, no large
>> allocation of prefixes to VPC (cons: more static routing rules for upstream
>> router/admins)
>>*   All systemvms (incl. ssvm, cpvm, VRs) get IPv6 address if zone has a
>> dedicated /64 prefix/block for systemvms
>>
>> The only outstanding question now is:
>>
>>*   How do we manage IPv6 usage? Can anyone advise how we do IPv6 usage
>> for shared network (

Re: IPV6 in Isolated/VPC networks

[Abhishek Kumar]

Hi Wido,

I do not understand what you mean by WAB address but 
fd23:313a:2f53:3000:1c00:baff:fe00:4 is the public IP of the network (IPv6 of 
the public NIC of the network VR) in the sample.
Yes, route for fd23:313a:2f53:3cbf::/64 need to be added to this IP. 
fd23:313a:2f53:3cbf::/64 is guest IPv6 CIDR of the network here.

Currently, the message on event bus does not include subnet. Should that be 
included?
In case of VPCs, there could be multiple tiers which will need multiple routes 
to be added. Will that be an issue if we include current network/tier subnet in 
the event message?

Regards,
Abhishek

From: Wido den Hollander 
Sent: 10 May 2022 19:01
To: dev@cloudstack.apache.org ; Abhishek Kumar 

Subject: Re: IPV6 in Isolated/VPC networks

Hi,

Op 10-05-2022 om 11:42 schreef Abhishek Kumar:
> Yes. When a public IPv6 is assigned or released, CloudStack will publish 
> event with type NET.IP6ASSIGN, NET.IP6RELEASE.
> These event notifications can be tracked. And with improvements in events 
> framework, these event messages will have network uuid as entityuuid and 
> Network as entitytype. Using this network can be queried using to list IPv6 
> routes that need to be added.
>
> Sample event message,
>
> {"eventDateTime":"2022-05-10 09:32:12 
> +","entityuuid":"14658b39-9d20-4783-a1bc-12fb58bcbd98","Network":"14658b39-9d20-4783-a1bc-12fb58bcbd98","description":"Assigned
>  public IPv6 address: fd23:313a:2f53:3000:1c00:baff:fe00:4 for network ID: 
> 14658b39-9d20-4783-a1bc-12fb58bcbd98","event":"NET.IP6ASSIGN","user":"bde866ba-c600-11ec-af19-1e00320001f3","account":"bde712c9-c600-11ec-af19-1e00320001f3","entity":"Network","status":"Completed"}
>
>
> ?Sample API call,
>> list networks id=14658b39-9d20-4783-a1bc-12fb58bcbd98 
>> filter=id,name,ip6routes
> {
>"count": 1,
>"network": [
>  {
>"id": "14658b39-9d20-4783-a1bc-12fb58bcbd98",
>"ip6routes": [
>  {
>"gateway": "fd23:313a:2f53:3000:1c00:baff:fe00:4",
>"subnet": "fd23:313a:2f53:3cbf::/64"
>  }

Looking at this JSON, does this mean that
fd23:313a:2f53:3000:1c00:baff:fe00:4 is the WAB address of the VR?

And that I would need to (statically) route fd23:313a:2f53:3cbf::/64 to
that IP?

The event message does not include the subnet, that makes it a bit more
difficult as you would then also need to do a API-call to gather that
information.

Wido

P.S.: Who controls the DNS of qa.cloudstack.cloud? It lacks an
-record for IPv6!

>],
>"name": "routing_test"
>  }
>]
> }
>
>
>
>
> 
> From: Wido den Hollander 
> Sent: 10 May 2022 13:59
> To: dev@cloudstack.apache.org ; Abhishek Kumar 
> 
> Subject: Re: IPV6 in Isolated/VPC networks
>
> Op 10-05-2022 om 10:19 schreef Abhishek Kumar:
>> Hi all,
>>
>> IPv6 Support in Isolated Network and VPC with Static Routing based on the 
>> design doc [1] has been implemented and is available in 4.17.0 RC2. I hope 
>> while testing 4.17.0 RC2 you will also try to test it ?
>> Documentation for it is available at 
>> http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/262/plugins/ipv6.html#isolated-network-and-vpc-tier
>>  (will be available in the official docs once 4.17.0 version of docs is 
>> built).
>>
>
> Great work!
>
> I see only static routing is supported. But do we publish something on
> the message bus once a new VR/VPC is created?
>
> This way you could pick up these messages and have the network create a
> (static) route based on those.
>
> ExaBGP for example could be used to inject such routes.
>
> Wido
>
>> [1] 
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+Support+in+Isolated+Network+and+VPC+with+Static+Routing
>>
>> Regards,
>> Abhishek
>>
>> 
>> From: Rohit Yadav 
>> Sent: 13 September 2021 14:30
>> To: dev@cloudstack.apache.org 
>> Subject: Re: IPV6 in Isolated/VPC networks
>>
>> Thanks Alex, Wei. I've updated the docs here: 
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+Support+in+Isolated+Network+and+VPC+with+Static+Routing
>>
>> I'll leave the thread open for futher discussion/ideas/feedback. I think 
>> we've completed the phase1 design doc including all feedback comments for 
>> adding IPv6 support in CloudStack and some initial poc/work 

Re: Introduction

[Abhishek Kumar]

Welcome Jamie!

Regards,
Abhishek

From: Jamie Pell 
Sent: 12 May 2022 19:53
To: dev@cloudstack.apache.org 
Subject: Introduction

Hi all,

I've recently started working with Ivet and helping her out with some of the 
community marketing for the CloudStack community - so just wanted to say hi to 
everybody.

Ivet has recently gone on maternity leave so I'm going to be interacting on the 
mailing lists regularly now. I'm very much looking forward to getting to know 
some of the great members of the community and am open to any guidance anybody 
may have for me. I'm going to be picking up organising of CCC this year amongst 
other tasks.

Kind regards,




 

Re: IPV6 in Isolated/VPC networks

[Abhishek Kumar]

Hi Wido, Wei,

I've created a PR to have static route in the event description, 
https://github.com/apache/cloudstack/pull/6389
Can you please check.

Regards,
Abhishek

From: Wido den Hollander 
Sent: 13 May 2022 15:30
To: dev@cloudstack.apache.org ; Wei ZHOU 

Subject: Re: IPV6 in Isolated/VPC networks



Op 13-05-2022 om 11:39 schreef Wei ZHOU:
> Hi Wido,
>
> We do not allocate an ipv6 subnet to a VPC. Instead, we allocate an ipv6
> subnet for each vpc tier.
> These subnets have the same gateway (ipv6 addr in VR).
>
> for example
>
> ipv6 route fd23:313a:2f53:3111::/64 fd23:313a:2f53:3000:1c00:baff:fe00:4
> ipv6 route fd23:313a:2f53:3112::/64 fd23:313a:2f53:3000:1c00:baff:fe00:4
> ipv6 route fd23:313a:2f53:3113::/64 fd23:313a:2f53:3000:1c00:baff:fe00:4
>

Thanks Wei and Alex, that explains! So you can have multiple /64 subnets
being routed to the same VR.

It's up to the organization to only allocate /64s coming from a specific
/56 or /48 to make things logical, but underneath it's all /64s which we
need to route.

Wido

> -Wei
>

 

> On Fri, 13 May 2022 at 11:30, Wido den Hollander  wrote:
>
>>
>>
>> Op 12-05-2022 om 16:10 schreef Alex Mattioli:
 ipv6 route fd23:313a:2f53:3cbf::/64 fd23:313a:2f53:3000:1c00:baff:fe00:4
>>>
>>> That's correct
>>
>> Ok. So in that case the subnet would be very welcome to be present in
>> the message on the bus.
>>
>>>
 Or a larger subnet:
 ipv6 route fd23:313a:2f53:3c00::/56 fd23:313a:2f53:3000:1c00:baff:fe00:4
>>>
>>> Not really, the subnets for isolated/VPC networks are always /64.  Which
>> means also no real need to include subnets as well.
>>>
>>
>> But there can be multiple networks behind the VPC router or not? If
>> there are multiple networks you need >/64 as you can then allocate /64s
>> from that larger subnet.
>>
>> Wido
>>
>>> Cheers
>>> Alex
>>>
>>>
>>>
>>>
>>
>

Re: [VOTE] Apache Cloudstack 4.17.0.0 RC4

[Abhishek Kumar]

+1

Did basic lifecyle tasks on resource - vm, volume, networks, accounts, 
templates and k8s cluster with following env:
MS host: centos7
2x KVM centos 7 hosts
Advanced zone with 1 pod, 1 cluster.

Everything worked fine.

Regards,
Abhishek

From: Nicolas Vazquez 
Sent: 31 May 2022 23:09
To: dev@cloudstack.apache.org ; users 

Subject: [VOTE] Apache Cloudstack 4.17.0.0 RC4

Hi all,

I have created a 4.17.0.0 release (RCR) with the following artefacts up for 
testing and a vote:

Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.17.0.0-RC20220531T1433
Commit: c56220fcf2348c7809331dcc266775f3d7130fe6

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

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

The vote will be open until 6th June 2022.

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,
Nicolas Vazquez





 

[PROPOSE] CloudStack 4.17.1.0 release and RM

[Abhishek Kumar]

Hi all,

I would like to propose and put myself forward as the release manager for the 
4.17.1.0 release. My colleague Nicolas Vazquez will support me as the co-RM for 
the PR reviews/tests/merges, and others are welcome to support as well.
We can keep the scope limited to include only bugs, critical issues and fixes 
for a stable release. I see about 89 closed issues/PRs already on the 4.17.1.0 
milestone[1] and some 24 items are remaining.

I propose the following timeline, aiming to cut the first RC around the end of 
August.
 - ~3 weeks from now till late August 2022 (Ongoing): Accept all bugs, 
issues and minor improvements allowed in LTS [2]
 - 1 week: Accept only critical/blocker fixes, stabilize 4.17 branch
 - end-August 2022 and onwards: Cut 4.17.1.0 RC1 and further RCs if 
necessary, start/conclude vote, and finish release work

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

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

Regards,
Abhishek

 

4.17.1.0 release

[Abhishek Kumar]

All,

We've 5 items remaining on the 4.17.1.0 milestone now: 
https://github.com/apache/cloudstack/milestone/25

Considering these and the previously proposed rough timeline, I would like to 
propose 4.17 branch soft freeze from tomorrow 31 Aug 2022, after which only 
blocker and critical fixes will be allowed with the RC1 cut during next week 
depending on the branch stability.

Thoughts, objections?

Regards,
Abhishek

 

[VOTE] Apache CloudStack 4.17.1.0 (RC1)

[Abhishek Kumar]

Hi All,

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

Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.17.1.0-RC20220907T1706
Commit: cf815b051d2cd0e88fda40ab1690d7b173f68fdf

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

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

Vote will be open for 120 hours, until 12 Sep 2022.

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

For users convenience, the packages from this release candidate (RC1) and 
4.17.0 systemvmtemplates (there is no change in system vm template since 
4.17.0.0 release and the same 4.17.0 system vm templates can be used) are 
available here:
https://download.cloudstack.org/testing/4.17.1.0-RC1/
https://download.cloudstack.org/systemvm/4.17/

Documentation is not published yet, but the following may be referenced for
upgrade related tests:

https://github.com/apache/cloudstack-documentation/tree/4.17/source/upgrading/upgrade

Regards,
Abhishek




 

Re: [VOTE] Apache CloudStack 4.17.1.0 (RC1)

[Abhishek Kumar]

All,

We've found a couple of issues which are of critical and blocker nature, 
https://github.com/apache/cloudstack/milestone/25
I'll cut another RC shortly as soon as we have a working fix.
Due to this, I'm closing this voting thread.

Regards.
Abhishek

From: Nux 
Sent: 07 September 2022 18:32
To: us...@cloudstack.apache.org 
Cc: dev@cloudstack.apache.org 
Subject: Re: [VOTE] Apache CloudStack 4.17.1.0 (RC1)

+1 (binding) from me based on the testing I've done.

---
Nux
www.nux.ro

On 2022-09-07 13:50, Abhishek Kumar wrote:
> Hi All,
>
> I've created a 4.17.1.0 release, with the following artifacts up for a
> vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/tree/4.17.1.0-RC20220907T1706
> Commit: cf815b051d2cd0e88fda40ab1690d7b173f68fdf
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.17.1.0/
>
> PGP release keys (signed using
> 65518106473A09D7AF26B384A70BD2EAA74E2866):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> Vote will be open for 120 hours, until 12 Sep 2022.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> For users convenience, the packages from this release candidate (RC1)
> and 4.17.0 systemvmtemplates (there is no change in system vm template
> since 4.17.0.0 release and the same 4.17.0 system vm templates can be
> used) are available here:
> https://download.cloudstack.org/testing/4.17.1.0-RC1/
> https://download.cloudstack.org/systemvm/4.17/
>
> Documentation is not published yet, but the following may be referenced
> for
> upgrade related tests:
>
> https://github.com/apache/cloudstack-documentation/tree/4.17/source/upgrading/upgrade
>
> Regards,
> Abhishek
> <https://github.com/apache/cloudstack-documentation/tree/4.17/source/upgrading/upgrade>

 

[VOTE] Apache CloudStack 4.17.1.0 (RC2)

[Abhishek Kumar]

Hi All,

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

Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.17.1.0-RC20220914T1258
Commit: 350ef38e1cbd001c77e6b919b8f1fedcf1bcce64

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

PGP release keys (signed using 65518106473A09D7AF26B384A70BD2EAA74E2866):
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, the packages from this release candidate (RC2) and 
4.17.0 systemvmtemplates (there is no change in system VM template since 
4.17.0.0 release and the same 4.17.0 system VM templates can be used) are 
available here:
https://download.cloudstack.org/testing/4.17.1.0-RC2/
https://download.cloudstack.org/systemvm/4.17/

Documentation is not published yet, but the following may be referenced for
upgrade related tests:
https://github.com/apache/cloudstack-documentation/tree/4.17/source/upgrading/upgrade

Regards,
Abhishek


 

[RESULT][VOTE] Apache CloudStack 4.17.1.0

[Abhishek Kumar]

Hi all,

After 72 hours, the vote for CloudStack 4.17.1.0 *passes* with
4 PMC + 1 non-PMC votes.

+1 (PMC / binding)
Nux
Daan
Nicolas
Rohit

+1 (non binding)
Vladimir

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: [RESULT][VOTE] Apache CloudStack 4.17.1.0

[Abhishek Kumar]

Hi all,

Unfortunately, there is a blocker issue found for the release which will create 
problems in upgrading from the 4.17.0.1 release to 4.17.1.0, 
https://github.com/apache/cloudstack/pull/6759.

Considering this, I'm recalling the release vote/result. A new RC will be cut 
soon and a vote thread will be started.

Thanks in advance for your understanding.

Regards,
Abhishek



From: Rohit Yadav 
Sent: 19 September 2022 16:16
To: dev@cloudstack.apache.org 
Cc: us...@cloudstack.apache.org 
Subject: Re: [RESULT][VOTE] Apache CloudStack 4.17.1.0

Excellent work, thanks for your efforts Abhishek and the wider community!
Congratulations everyone on a new release.


Regards.


From: Katie F. 
Sent: Monday, September 19, 2022 16:12
To: dev@cloudstack.apache.org 
Cc: us...@cloudstack.apache.org 
Subject: Re: [RESULT][VOTE] Apache CloudStack 4.17.1.0

Thank you

On Mon, Sep 19, 2022 at 6:40 AM Abhishek Kumar 
wrote:

> Hi all,
>
> After 72 hours, the vote for CloudStack 4.17.1.0 *passes* with
> 4 PMC + 1 non-PMC votes.
>
> +1 (PMC / binding)
> Nux
> Daan
> Nicolas
> Rohit
>
> +1 (non binding)
> Vladimir
>
> 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
>
>
>
>
> --
Kathleen Foos




 

[VOTE] Apache CloudStack 4.17.1.0 (RC3)

[Abhishek Kumar]

Hi All,

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

Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.17.1.0-RC20220923T1732
Commit: 974369e3d4cacb99790f21fadbd4daca19765910

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

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

Vote will be open until lazy consensus (3 +1 binding) votes are reached.

For sanity in tallying the vote, can PMC members please be sure to
indicate "(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

For users convenience, the packages from this release candidate (RC3)
and 4.17.0 systemvmtemplates (there is no change in system vm template
since 4.17.0.0 release and the same 4.17.0 system vm templates can be
used) are available here:
https://download.cloudstack.org/testing/4.17.1.0-RC3/
https://download.cloudstack.org/systemvm/4.17/

The following documentation may be referenced for upgrade related tests:
http://docs.cloudstack.apache.org/en/4.17.1.0/

Regards,
Abhishek

Re: [VOTE] Apache CloudStack 4.17.1.0 (RC3)

[Abhishek Kumar]

Hi Wei,

I just tested 4.17.0.1 to 4.17.1.0 upgrade with an Ubuntu 20.04 based
management server and I was able to see schema changes being applied
in the logs,

2022-09-24 09:27:56,817 INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle]
(main:null) (logid:) Running system integrity checker
com.cloud.upgrade.DatabaseUpgradeChecker@5e180aaf
2022-09-24 09:27:56,819 INFO  [c.c.u.DatabaseUpgradeChecker]
(main:null) (logid:) Grabbing lock to check for database upgrade.
2022-09-24 09:27:56,909 DEBUG [c.c.u.d.VersionDaoImpl] (main:null)
(logid:) Checking to see if the database is at a version before it was
the version table is created
2022-09-24 09:27:56,984 DEBUG [c.c.u.SystemVmTemplateRegistration]
(main:null) (logid:) Looking for file [
./engine/schema/dist/systemvm-templates/metadata.ini ] in the
classpath.
2022-09-24 09:27:56,985 DEBUG [c.c.u.SystemVmTemplateRegistration]
(main:null) (logid:) Looking for file [
/usr/share/cloudstack-management/templates/systemvm/metadata.ini ] in
the classpath.
2022-09-24 09:27:57,034 INFO  [c.c.u.DatabaseUpgradeChecker]
(main:null) (logid:) DB version = 4.17.0.1 Code Version = 4.17.1.0
2022-09-24 09:27:57,036 INFO  [c.c.u.DatabaseUpgradeChecker]
(main:null) (logid:) Database upgrade must be performed from 4.17.0.1
to 4.17.1.0
2022-09-24 09:27:57,058 DEBUG [c.c.u.DatabaseUpgradeChecker]
(main:null) (logid:) Running upgrade Upgrade41700to41710 to upgrade
from 4.17.0.0-4.17.1.0 to 4.17.1.0

Full logs and upgrade steps used can be seen here,
https://gist.github.com/shwstppr/03ec3669cb329cf7b69f1f1794d70130

Can you please re-check if the correct packages were used for 4.17.1.0 RC3?

Regards,
Abhishek

On Sat, 24 Sept 2022 at 01:49, Wei ZHOU  wrote:
>
> Hi Abhishek,
>
> I have tested the upgrade from 4.17.0.1 to 4.17.1.0. However, it doesn't
> seem good.
>
> 2022-09-23 20:09:53,498 INFO  [c.c.u.DatabaseUpgradeChecker] (main:null)
> (logid:) DB version = 4.17.0.1 Code Version = 4.17.1.0
> 2022-09-23 20:09:53,499 INFO  [c.c.u.DatabaseUpgradeChecker] (main:null)
> (logid:) Database upgrade must be performed from 4.17.0.1 to 4.17.1.0
> 2022-09-23 20:09:53,521 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null)
> (logid:) Running upgrade NoopDbUpgrade to upgrade from 4.17.0.1-4.17.1.0 to
> 4.17.1.0
> 2022-09-23 20:09:53,549 INFO  [c.c.u.DatabaseUpgradeChecker] (main:null)
> (logid:) Cleanup upgrade NoopDbUpgrade to upgrade from 4.17.0.1-4.17.1.0 to
> 4.17.1.0
> 2022-09-23 20:09:53,575 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null)
> (logid:) Upgrade completed for version 4.17.1.0
>
> The packages are downloaded from
> https://download.cloudstack.org/testing/4.17.1.0-RC3/debian/4.17/
>
> No idea what's wrong.
>
> -Wei
>
> On Fri, 23 Sept 2022 at 15:33, Abhishek Kumar  wrote:
>
> > Hi All,
> >
> > I've created a 4.17.1.0 release, with the following artifacts up for a
> > vote:
> >
> > Git Branch and Commit SH:
> > https://github.com/apache/cloudstack/tree/4.17.1.0-RC20220923T1732
> > Commit: 974369e3d4cacb99790f21fadbd4daca19765910
> >
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.17.1.0/
> >
> > PGP release keys (signed using 65518106473A09D7AF26B384A70BD2EAA74E2866):
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> > Vote will be open until lazy consensus (3 +1 binding) votes are reached.
> >
> > For sanity in tallying the vote, can PMC members please be sure to
> > indicate "(binding)" with their vote?
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > For users convenience, the packages from this release candidate (RC3)
> > and 4.17.0 systemvmtemplates (there is no change in system vm template
> > since 4.17.0.0 release and the same 4.17.0 system vm templates can be
> > used) are available here:
> > https://download.cloudstack.org/testing/4.17.1.0-RC3/
> > https://download.cloudstack.org/systemvm/4.17/
> >
> > The following documentation may be referenced for upgrade related tests:
> > http://docs.cloudstack.apache.org/en/4.17.1.0/
> >
> > Regards,
> > Abhishek
> >

[RESULT][VOTE] Apache CloudStack 4.17.1.0

[Abhishek Kumar]

Hi all,

The vote for CloudStack 4.17.1.0 *passes* with
3 PMC votes.

+1 (PMC / binding)
Boris
Rohit
Wei

+1 (non binding)
none

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

[ANNOUCE] Apache CloudStack 4.17.1.0 LTS Release

[Abhishek Kumar]

# Apache CloudStack LTS Maintenance Release 4.17.1.0

The Apache CloudStack project is pleased to announce the release of
CloudStack 4.17.1.0.
The CloudStack 4.17.1.0 release is a maintenance release as part of its
4.17.x LTS branch and contains more than 150 fixes and improvements since
the CloudStack 4.17.0.0 release.

Highlights include:

* Support for Ubuntu 22.04 LTS as management server and KVM host
* Improvements for System VM storage migration on KVM
* CKS cluster upgrade enhancements
* Several network and VPC related fixes especially related IPv6 and permissions
* KVM libvirt Java library upgrade
* KVM Shared Mount Point fix
* VMware local storage volume migration improvements

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.17.1.0:
https://docs.cloudstack.apache.org/en/4.17.1.0/releasenotes/about.html

The 4.17.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.17.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.17.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/suse/15
https://download.cloudstack.org/ubuntu/dists/
https://www.shapeblue.com/packages/

Re: [VOTE] Apache Cloudstack 4.17.2.0 (RC3)

[Abhishek Kumar]

+1

Tested basic lifecycles using a mbx deployed KVM env.

From: Rohit Yadav 
Sent: 14 December 2022 10:56
To: dev ; users 
Subject: [VOTE] Apache Cloudstack 4.17.2.0 (RC3)

All,

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

Git Branch and Commit SHA:
https://github.com/apache/cloudstack/tree/4.17.2.0-RC20221214T0522
Commit: 5b9a989ab0dd6b8f482f4d6c6ce24e1a6108002e

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

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

The vote will be open for 72 hours, until the end of 16 Dec 2022.

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)

For users' convenience, the packages from this release candidate (RC3) and
4.17.2 systemvmtemplates are available here:
https://download.cloudstack.org/testing/4.17.2.0-RC3/ (building/uploading)
https://download.cloudstack.org/systemvm/4.17/

Documentation is not officially published yet, you may refer to the
following doc PR:
https://github.com/apache/cloudstack-documentation/pull/295

The list of changes included in this minor release over 4.17.1.0 can be
referenced here:
https://github.com/apache/cloudstack/milestone/26?closed=1

Regards.

 

Re: [ANNOUNCE] Ivet Petrova has joined the PMC

[Abhishek Kumar]

Congrats Ivet!

From: Simon Weller 
Sent: 14 February 2023 21:30
To: priv...@cloudstack.apache.org ; 
dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org 
Subject: [ANNOUNCE] Ivet Petrova has joined the PMC

Hi everyone,

It gives me great pleasure to announce that Ivet has been invited to join
the
CloudStack PMC and she has accepted.

Please join me in congratulating Ivet!

-Simon (on behalf of the CloudStack PMC)

 

Re: [ANNOUNCE] New VP of Apache CloudStack - Rohit Yadav

[Abhishek Kumar]

Congratulations Rohit!

From: Simon Weller 
Sent: 30 March 2023 09:05
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org 
Cc: priv...@cloudstack.apache.org 
Subject: [ANNOUNCE] New VP of Apache CloudStack - Rohit Yadav

All,

I'm very pleased to announce that the ASF board has accepted the nomination
of Rohit Yadav to be the new VP of the Apache CloudStack project.

It has been my pleasure to serve as the VP over the past year, and I'd like
to thank the community for all of the support.

Rohit, congratulations and I wish you the best as you take on this new role.

-Simon

 

[PROPOSE] RM for 4.19.0

[Abhishek Kumar]

Dear All,

I would like to propose and put myself forward as the release manager for 
4.19.0 release. In the past, I've RM'd 4.17.1.0 release and co-RM'd a couple of 
releases before that. I would like to take experiences from those to work on a 
successful release.

I propose we start early, sometime in Q3 2023, with the planning, triaging, 
bug-fixing, etc to get back on the traditional two-release per year cycle. With 
this we can aim to cut the RC sometime in October. I will propose a detailed 
timeline soon.

I hope to have your support. Please let me know if you have any 
thoughts/comments.

Regards,
Abhishek

 

Re: ACS upgrade to Log4J2 version 2.19

[Abhishek Kumar]

Great work.
Though I feel this is a 5.0 change. I agree with Wei that this would create
too much overhead for upcoming releases. 4.18 was pushed ahead a few months
and we may end up on a similar path.
Also, reload4j is still actively maintained so I don't think this is urgent.

Regards,
Abhishek

On Fri, 28 Apr 2023 at 18:28, João Jandre Paraquetti 
wrote:

> In PR #7131 (https://github.com/apache/cloudstack/pull/7131) I have
> proposed to normalize ACS's loggers, and more importantly, upgrade the
> library log4j to log4j2 version 2.19.
>
> Log4j2 has a lot of features that could offer benefits to ACS:
>
>   * Async Loggers - performance similar to logging switched off
>   * Custom log levels
>   * Automatically reload its configuration upon modification without
> loosing log events during reconfigurations.
>   * Java 8-style lambda support for lazy logging (which enables methods
> to be executed only when necessary, i.e.: the right log level)
>   * Log4j 2 is garbage-free (or at least low-garbage) since version 2.6
>   * Plugin Architecture - easy to extend by building custom components
>   * Log4j 2 API is separated from the Log4j 2 implementation.
>   * Log4j 2 API supports more than just logging Strings: CharSequences,
> Objects and custom Messages. Messages allow support for interesting
> and complex constructs to be passed through the logging system and
> be efficiently manipulated. Users are free to create their own
> Message types and write custom Layouts, Filters and Lookups to
> manipulate them.
>   * Concurrency improvements: log4j2 uses java.util.concurrent libraries
> to perform locking at the lowest level possible. Log4j-1.x has known
> deadlock issues.
>   * Configuration via XML, JSON, YAML, properties configuration files or
> programmatically.
>
> In my personal experience using it in some other projects, log4j2 is
> easier to work with in general, has better performance, and is an active
> project with constant development, innovation, and security patches.
> Moreover, it is under a well known and trusted open source organization.
>
> The change proposed in PR #7131
> (https://github.com/apache/cloudstack/pull/7131) has been tested and
> validated in a lot of different scenarios by different people. We have
> already tested the logging in the management server, usage, agents, and
> system VMs; all of that using KVM and Vmware + Veeam. Most feature sets
> were tested, create/delete/update VMs, disks, cresate snapshots, user
> management and so on.
>
> The proposal has been discussed since January, 2023 in the PR
> (https://github.com/apache/cloudstack/pull/7131), but I have been
> requested to bring it to the mailing list. I would love to hear your
> opinions on it, also, any reviews to the PR would be welcome.

Re: ACS upgrade to Log4J2 version 2.19

[Abhishek Kumar]

Hi Daniel,

It was just my opinion it is based on the reasons that it is something that
we haven't seen any request in the community before and it will create some
challenges for the releases, forward-merging bug-fixes and also for any
existing integrations that users might be having.
To be specific, I'm neutral (0) on this.
Great that you want to take up the RM work to address part of those
challenges. You have my support.
The only thing that I would hope for is to get this tested/merged early to
avoid issues at the later stages nearer to the release.

Regards,
Abhishek

On Mon, 1 May 2023 at 18:58, Daniel Salvador 
wrote:

> Abhishek,
>
> I do not see why it would be a 5.0 change. Also, ACS 5.0 is a discussion
> the community has been having for a long time from now and is something we
> are too far away to achieve consensus.
>
> The patch is important to enable further development for the log management
> on ACS and facilitate everyone's life while coding and troubleshooting. If
> you think it is too much work for the RM, I reiterate that I am willing to
> be the 4.19 RM and conduct/execute all of the work.
>
> Best regards,
> Daniel Salvador (gutoveronezi)
>
> On Mon, May 1, 2023 at 4:10 AM Abhishek Kumar  wrote:
>
> > Great work.
> > Though I feel this is a 5.0 change. I agree with Wei that this would
> create
> > too much overhead for upcoming releases. 4.18 was pushed ahead a few
> months
> > and we may end up on a similar path.
> > Also, reload4j is still actively maintained so I don't think this is
> > urgent.
> >
> > Regards,
> > Abhishek
> >
> > On Fri, 28 Apr 2023 at 18:28, João Jandre Paraquetti <
> j...@scclouds.com.br
> > >
> > wrote:
> >
> > > In PR #7131 (https://github.com/apache/cloudstack/pull/7131) I have
> > > proposed to normalize ACS's loggers, and more importantly, upgrade the
> > > library log4j to log4j2 version 2.19.
> > >
> > > Log4j2 has a lot of features that could offer benefits to ACS:
> > >
> > >   * Async Loggers - performance similar to logging switched off
> > >   * Custom log levels
> > >   * Automatically reload its configuration upon modification without
> > > loosing log events during reconfigurations.
> > >   * Java 8-style lambda support for lazy logging (which enables methods
> > > to be executed only when necessary, i.e.: the right log level)
> > >   * Log4j 2 is garbage-free (or at least low-garbage) since version 2.6
> > >   * Plugin Architecture - easy to extend by building custom components
> > >   * Log4j 2 API is separated from the Log4j 2 implementation.
> > >   * Log4j 2 API supports more than just logging Strings: CharSequences,
> > > Objects and custom Messages. Messages allow support for interesting
> > > and complex constructs to be passed through the logging system and
> > > be efficiently manipulated. Users are free to create their own
> > > Message types and write custom Layouts, Filters and Lookups to
> > > manipulate them.
> > >   * Concurrency improvements: log4j2 uses java.util.concurrent
> libraries
> > > to perform locking at the lowest level possible. Log4j-1.x has
> known
> > > deadlock issues.
> > >   * Configuration via XML, JSON, YAML, properties configuration files
> or
> > > programmatically.
> > >
> > > In my personal experience using it in some other projects, log4j2 is
> > > easier to work with in general, has better performance, and is an
> active
> > > project with constant development, innovation, and security patches.
> > > Moreover, it is under a well known and trusted open source
> organization.
> > >
> > > The change proposed in PR #7131
> > > (https://github.com/apache/cloudstack/pull/7131) has been tested and
> > > validated in a lot of different scenarios by different people. We have
> > > already tested the logging in the management server, usage, agents, and
> > > system VMs; all of that using KVM and Vmware + Veeam. Most feature sets
> > > were tested, create/delete/update VMs, disks, cresate snapshots, user
> > > management and so on.
> > >
> > > The proposal has been discussed since January, 2023 in the PR
> > > (https://github.com/apache/cloudstack/pull/7131), but I have been
> > > requested to bring it to the mailing list. I would love to hear your
> > > opinions on it, also, any reviews to the PR would be welcome.
> >
>

Re: [PROPOSE] RM for 4.19.0

[Abhishek Kumar]

Daan, Rohit and others,

Personally, I don't see log4j2 PR alone or one particular feature/PR that
can be the reason for managing the release. Though I certainly understand
it may create some additional work for the RM.
Since Daniel also has an interest in being the RM for the 4.19 release, is
happy to do that additional work and RM work is not the most exciting work
for me :-P, I'm happy to support Daniel for the role. I, like others, can
help him where I can.

Regards,
Abhishek


On Wed, 3 May 2023 at 14:49, Rohit Yadav  wrote:

> +1
>
> Thanks for volunteering Abhishek. As you've worked already as a RM for
> CloudStack LTS maintenance releases that you've shared and I think you have
> all the necessary experience to work as the 4.19 RM.
>
> Daan, I don't see any mention of log4j on this thread or feel that
> Abhishek has disregarded the log4j issue. As an individual contributor,
> he's well within his rights to volunteer as a release manager and share his
> opinion and thoughts in the community in this or any other threads.
>
> We shouldn't force or expect anybody to conclude a discussion in a way we
> would want. We must all conduct and treat one another professionally and
> politely on the mailing lists [1].
>
> [1] https://cloudstack.apache.org/mailing-lists.html
>
>
> Regards.
>
> 
> From: Daan Hoogland 
> Sent: Tuesday, May 2, 2023 13:19
> To: dev@cloudstack.apache.org 
> Cc: us...@cloudstack.apache.org 
> Subject: Re: [PROPOSE] RM for 4.19.0
>
> Abhishek, I think the discussion about log4j2 needs to be concluded in
> coercion with this. I am fine if you and/or Daniel co-RM this release for
> instance, but the log4j issue may not be disregarded on these grounds and
> must be fully discussed and agreed upon.
>
> On Tue, May 2, 2023 at 9:43 AM Suresh Kumar Anaparti <
> sureshkumar.anapa...@gmail.com> wrote:
>
> > +1, Good luck Abhishek!
> >
> > Regards,
> > Suresh
> >
> > On Mon, May 1, 2023 at 7:49 PM Boris Stoyanov
> >  wrote:
> > >
> > > +1, thanks Abhishek. I know we’re in safe hands with you!
> > >
> > > Bobby.
> > >
> > > From: Harikrishna Patnala 
> > > Date: Monday, 1 May 2023, 9:21
> > > To: us...@cloudstack.apache.org ,
> > dev@cloudstack.apache.org 
> > > Subject: Re: [PROPOSE] RM for 4.19.0
> > > +1, thanks for volunteering and good luck Abhishek.
> > >
> > > Regards,
> > > Harikrishna
> > >
> > > From: Abhishek Kumar 
> > > Date: Sunday, 30 April 2023 at 10:23 PM
> > > To: dev@cloudstack.apache.org ,
> > us...@cloudstack.apache.org 
> > > Subject: [PROPOSE] RM for 4.19.0
> > > Dear All,
> > >
> > > I would like to propose and put myself forward as the release manager
> > for 4.19.0 release. In the past, I've RM'd 4.17.1.0 release and co-RM'd a
> > couple of releases before that. I would like to take experiences from
> those
> > to work on a successful release.
> > >
> > > I propose we start early, sometime in Q3 2023, with the planning,
> > triaging, bug-fixing, etc to get back on the traditional two-release per
> > year cycle. With this we can aim to cut the RC sometime in October. I
> will
> > propose a detailed timeline soon.
> > >
> > > I hope to have your support. Please let me know if you have any
> > thoughts/comments.
> > >
> > > Regards,
> > > Abhishek
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
>
>
> --
> Daan
>
>
>
>

Re: [VOTE] CloudStack Project Blog Migration

[Abhishek Kumar]

+1 Looks good!

From: Rohit Yadav 
Sent: 17 May 2023 14:27
To: dev 
Cc: users 
Subject: [VOTE] CloudStack Project Blog Migration

All,

The ASF-infra had announced a hard deadline [0][1] to decommission our
project’s Roller based blog [3] on the 31st May 2023.

For the blog migration, ASF-infra has exported CloudStack blog posts
from the current Roller’s database-backed infra to markdown files.
These were put together in cloudstack-www repository’s
docusauras-staging branch [2] with Docusauras used as a
static-site-generator and a GitHub Actions workflow to automate
publishing a staging site for your testing and review [4].

The staging site that migrates both the website and blog isn’t
completely ready to meet the hard deadline, so this vote is proposed
for only migrating the blog before the deadline and continue efforts
to migrate to a new website [2][4] when we're ready in the near
future.

The following is put for voting:

1. By the end of 31st May ’23, ASF-infra will decommission the project
blog at https://blogs.apache.org/cloudstack and for now we proceed
with only the blog migration before this deadline.

2. The old blog URL/pages from
https://blogs.apache.org/cloudstack/ will be
redirected to https://cloudstack.apache.org/blog/.
This will be done by the ASF-infra.

3. The blog content is copied to the "content/blog" directory of the
asf-site branch in the https://github.com/apache/cloudstack-www
repository [6], published at https://cloudstack.apache.org/blog/.

The vote will be open until we reach a lazy consensus.

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)

[0] https://markmail.org/message/o5pse33cgriebsrg
[1] https://lists.apache.org/thread/hfhzochhmqhd32tclgc47d5nk90jxmb2
[2] https://github.com/apache/cloudstack-www/tree/docusaurus-staging/blog
[3] https://blogs.apache.org/cloudstack/
[4] https://cloudstack.staged.apache.org/
[5] https://cloudstack.apache.org/bylaws.html
[6] 
https://github.com/apache/cloudstack-www/commit/651ec3ad9a3f524a5ce1bb9d6943856f57e638e3

Regards.

 

Re: Introductions

[Abhishek Kumar]

Welcome Ayush!
All the best for your project.

Regards,
Abhishek

From: Ayush Pandey 
Sent: 26 May 2023 10:22
To: dev@cloudstack.apache.org 
Subject: Introductions

Hi Everyone,

I am Ayush Pandey, joining the community for a project as part of Google
Summer of code 2023. I will be working with my mentor Nicolas Vazquez on
"Extend Import-Export Instances to the KVM Hypervisor"
https://github.com/apache/cloudstack/issues/7127

I am really looking forward to collaborating with and learning from this
amazing community.

Thank you,
Regards,
Ayush Pandey

 

[PROPOSE] ACS 4.19.0.0 release

[Abhishek Kumar]

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: [DISCUSS] New Design for the Apache CloudStack Website

[Abhishek Kumar]

Hi,

Thanks Ivet for all the work. The new design looks great and very professional. 
Looking forward to seeing it go live.

Regards,
Abhishek

From: Ivet Petrova 
Sent: 30 August 2023 19:04
To: Giles Sirett 
Cc: dev@cloudstack.apache.org ; 
us...@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: us...@cloudstack.apache.org; Marketing 
mailto:market...@shapeblue.com>>
Cc: dev mailto:dev@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: new committer: Sina Kashipazha

[Abhishek Kumar]

Congrats Sina 👏


From: Daan Hoogland 
Sent: 25 August 2023 16:23
To: dev 
Subject: new committer: Sina Kashipazha

The Project Management Committee (PMC) for Apache [PROJECT]

has invited Sina Kashipazha to become a committer and we are pleased
to announce that they have accepted.

Sina has been active as a contributor in several ways; code, testing,
talks, documentation

Please join me in welcoming Sina

 

Re: new committer: John Bampton

[Abhishek Kumar]

Congrats John!

From: Daan Hoogland 
Sent: 25 August 2023 16:21
To: dev 
Subject: new committer: John Bampton

The Project Management Committee (PMC) for Apache CloudStack
has invited Jown Bampton to become a committer and we are pleased
to announce that they have accepted.

John is mostly active on CI and build specific issues.


please join me in welcoming John to the project

--
Daan

 

Re: [PROPOSE] ACS 4.19.0.0 release

[Abhishek Kumar]

Hi all,

Update on the current state of the 4.19.0.0 milestone. Currently, there are 203 
open items in the 4.19.0.0 milestone with 72 open PRs and 131 open issues.
Considering the earlier suggested timeline, from next week, we will have to 
triage the open items more diligently to move the inactive items out of the 
milestone.
The release timeline remains the same:

  *   Code freeze, and stabilization to accept only critical/blocker issues in 
the second half of October 2023. We should be in a better position to have a 
specific date in a week or so.
  *   Cut 4.19.0.0 RC1 towards the end of October 2023.

Looking forward to your support.

Regards,
Abhishek


From: Abhishek Kumar 
Sent: 17 August 2023 22:47
To: dev@cloudstack.apache.org ; 
us...@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.19.0.0 release

[Abhishek Kumar]

Hi all,

Update on the current state of the 4.19.0.0 milestone. Currently, there are 
around 189 open items in the 4.19.0.0 milestone with 73 open PRs and 116 open 
issues.
Also, there are some issues and PRs in 4.18.2.0 milestone which are marked 
major in severity.
Considering these and the fact that there are some interesting new features in 
the milestone that still need some changes, review, or testing we may see some 
deviation in the earlier suggested timeline.

  *   Code freeze can be expected towards the end of the month, October 2023
  *   RC1 can be expected thereafter in the month of November 2023

Also, if you have got an active PR with a new feature or fix that you would 
like to see in 4.19.0.0 release please comment with your interest on the Github 
item.

Regards,
Abhishek



From: Daan Hoogland 
Sent: 29 September 2023 15:22
To: dev@cloudstack.apache.org 
Cc: us...@cloudstack.apache.org 
Subject: Re: [PROPOSE] ACS 4.19.0.0 release

Please note that these figures are not including any issues or PRs marked
for 4.18.2. We have a lot to filter out.

On Fri, Sep 29, 2023 at 11:33 AM Abhishek Kumar <
abhishek.ku...@shapeblue.com> wrote:

> Hi all,
>
> Update on the current state of the 4.19.0.0 milestone. Currently, there
> are 203 open items in the 4.19.0.0 milestone with 72 open PRs and 131 open
> issues.
> Considering the earlier suggested timeline, from next week, we will have
> to triage the open items more diligently to move the inactive items out of
> the milestone.
> The release timeline remains the same:
>
>   *   Code freeze, and stabilization to accept only critical/blocker
> issues in the second half of October 2023. We should be in a better
> position to have a specific date in a week or so.
>   *   Cut 4.19.0.0 RC1 towards the end of October 2023.
>
> Looking forward to your support.
>
> Regards,
> Abhishek
>
> 
> From: Abhishek Kumar 
> Sent: 17 August 2023 22:47
> To: dev@cloudstack.apache.org ;
> us...@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
>
>
>
>
>
>
>
>

--
Daan

 

Gentle reminder for getting your PRs/issues in 4.19.0.0

[Abhishek Kumar]

Hi devs,

I'm sending this to remind you that we are approaching code freeze as per our 
4.19.0.0 release timeline that is shared in the other email [1] to dev@ and 
user@, can you please mark your interest in the PRs and major/critical/blocker 
issues that you feel should be considered for the release.
Though we aspire to get as many fixes and interesting new features from the 
milestone [2], all of the current items may not be able to make it into the 
release with limited time, review and testing.
Looking forward to your support.


Regards,
Abhishek

[1] https://lists.apache.org/thread/ymqtk7y7623fvnm7bxntk36rdjn1q03k
[2] https://github.com/apache/cloudstack/milestone/24

 

Re: [PROPOSE] ACS 4.19.0.0 release

[Abhishek Kumar]

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 with a new feature or fix that you would like to 
see in 4.19.0.0 release please comment with your interest on the Github item.

Regards,
Abhishek

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

From: Abhishek Kumar 
Sent: 11 October 2023 12:49
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org 
Subject: Re: [PROPOSE] ACS 4.19.0.0 release

Hi all,

Update on the current state of the 4.19.0.0 milestone. Currently, there are 
around 189 open items in the 4.19.0.0 milestone with 73 open PRs and 116 open 
issues.
Also, there are some issues and PRs in 4.18.2.0 milestone which are marked 
major in severity.
Considering these and the fact that there are some interesting new features in 
the milestone that still need some changes, review, or testing we may see some 
deviation in the earlier suggested timeline.

  *   Code freeze can be expected towards the end of the month, October 2023
  *   RC1 can be expected thereafter in the month of November 2023

Also, if you have got an active PR with a new feature or fix that you would 
like to see in 4.19.0.0 release please comment with your interest on the Github 
item.

Regards,
Abhishek



From: Daan Hoogland 
Sent: 29 September 2023 15:22
To: dev@cloudstack.apache.org 
Cc: us...@cloudstack.apache.org 
Subject: Re: [PROPOSE] ACS 4.19.0.0 release

Please note that these figures are not including any issues or PRs marked
for 4.18.2. We have a lot to filter out.

On Fri, Sep 29, 2023 at 11:33 AM Abhishek Kumar <
abhishek.ku...@shapeblue.com> wrote:

> Hi all,
>
> Update on the current state of the 4.19.0.0 milestone. Currently, there
> are 203 open items in the 4.19.0.0 milestone with 72 open PRs and 131 open
> issues.
> Considering the earlier suggested timeline, from next week, we will have
> to triage the open items more diligently to move the inactive items out of
> the milestone.
> The release timeline remains the same:
>
>   *   Code freeze, and stabilization to accept only critical/blocker
> issues in the second half of October 2023. We should be in a better
> position to have a specific date in a week or so.
>   *   Cut 4.19.0.0 RC1 towards the end of October 2023.
>
> Looking forward to your support.
>
> Regards,
> Abhishek
>
> 
> From: Abhishek Kumar 
> Sent: 17 August 2023 22:47
> To: dev@cloudstack.apache.org ;
> us...@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
>
>
>
>
>
>
>
>

--
Daan

 

Re: [PROPOSE] ACS 4.19.0.0 release

[Abhishek Kumar]

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: dev@cloudstack.apache.org 
Cc: us...@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 with a new feature or fix that you would like
> to see in 4.19.0.0 release please comment with your interest on the Github
> item.
>
> Regards,
> Abhishek
>
> [1] https://github.com/apache/cloudstack/milestone/24
> [2] https://github.com/apache/cloudstack/milestone/29
> 
> From: Abhishek Kumar 
> Sent: 11 October 2023 12:49
> To: dev@cloudstack.apache.org ;
> us...@cloudstack.apache.org 
> Subject: Re: [PROPOSE] ACS 4.19.0.0 release
>
> Hi all,
>
> Update on the current state of the 4.19.0.0 milestone. Currently, there
> are around 189 open items in the 4.19.0.0 milestone with 73 open PRs and
> 116 open issues.
> Also, there are some issues and PRs in 4.18.2.0 milestone which are marked
> major in severity.
> Considering these and the fact that there are some interesting new
> features in the milestone that still need some changes, review, or testing
> we may see some deviation in the earlier suggested timeline.
>
>   *   Code freeze can be expected towards the end of the month, October
> 2023
>   *   RC1 can be expected thereafter in the month of November 2023
>
> Also, if you have got an active PR with a new feature or fix that you
> would like to see in 4.19.0.0 release please comment with your interest on
> the Github item.
>
> Regards,
> Abhishek
>
>
> 
> From: Daan Hoogland 
> Sent: 29 September 2023 15:22
> To: dev@cloudstack.apache.org 
> Cc: us...@cloudstack.apache.org 
> Subject: Re: [PROPOSE] ACS 4.19.0.0 release
>
> Please note that these figures are not including any issues or PRs marked
> for 4.18.2. We have a lot to filter out.
>
> On Fri, Sep 29, 2023 at 11:33 AM Abhishek Kumar <
> abhishek.ku...@shapeblue.com> wrote:
>
> > Hi all,
> >
> > Update on the current state of the 4.19.0.0 milestone. Currently, there
> > are 203 open items in the 4.19.0.0 milestone with 72 open PRs and 131
> open
> > issues.
> > Considering the earlier suggested timeline, from next week, we will have
> > to triage the open items more diligently to move the inactive items out
> of
> > the milestone.
> > The release timeline remains the same:
> >
> >   *   Code freeze, and stabilization to accept only critical/blocker
> > issues in the second half of October 2023. We should be in a better
> > position to have a specific date in a week or so.
> >   *   Cut 4.19.0.0 RC1 towards the end of October 2023.
> >
> > Looking forward to your support.
> >
> > Regards,
> > Abhishek
> >
> > 
> > From: Abhi

Re: new PMC member: Abhishek Kumar

[Abhishek Kumar]

Thank you all!

On Fri, 24 Nov, 2023, 06:38 Sina Kashipazha,
 wrote:

> Congrats, Abhishek! Well-deserved.
>
>
>
> On Thursday, 23 November 2023 at 23:01, Rohit Yadav <
> rohit.ya...@shapeblue.com> wrote:
>
>
> >
>
> >
>
> > Congratulations Abhishek, well deserved!
> >
>
> >
>
> > Regards.
> >
>
> > 
> > From: Daman Arora damans...@gmail.com
> >
>
> > Sent: Thursday, November 23, 2023 17:46
> > To: dev@cloudstack.apache.org dev@cloudstack.apache.org
> >
>
> > Cc: users us...@cloudstack.apache.org
> >
>
> > Subject: Re: new PMC member: Abhishek Kumar
> >
>
> > Many congrats Abhishek!
> >
>
> > On Thu, Nov 23, 2023, 9:25 p.m. Wei ZHOU ustcweiz...@gmail.com wrote:
> >
>
> > > Congratulations Abhishek!
> > >
>
> > > 在 2023年11月23日星期四，Daan Hoogland daan.hoogl...@gmail.com 写道：
> > >
>
> > > > 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: [PROPOSE] ACS 4.19.0.0 release

[Abhishek Kumar]

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: dev@cloudstack.apache.org ; 
us...@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: dev@cloudstack.apache.org 
Cc: us...@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 with a new feature or fix that you would like
> to see in 4.19.0.0 release please comment with your interest on the Github
> item.
>
> Regards,
> Abhishek
>
> [1] https://github.com/apache/cloudstack/milestone/24
> [2] https://github.com/apache/cloudstack/milestone/29
> 
> From: Abhishek Kumar 
> Sent: 11 October 2023 12:49
> To: dev@cloudstack.apache.org ;
> us...@cloudstack.apache.org 
> Subject: Re: [PROPOSE] ACS 4.19.0.0 release
>
> Hi all,
>
> Update on the current state of the 4.19.0.0 milestone. Currently, there
> are around 189 open items in the 4.19.0.0 milestone with 73 open PRs and
> 116 open issues.
> Also, there are some issues and PRs in 4.18.2.0 milestone which are marked
> major in severity.
> Considering these and the fact that there are some interesting new
> features in the milestone that still need some changes, review, or testing
> we may see some deviation in the earlier suggested timeline.
>
>   *   Code freeze can be expected towards the end of the month, October
> 2023
>   *   RC1 can be expected thereafter in the month of November 2023
>
> Also, if you have got an active PR with a new feature or fix that you
> would like to see in 4.19.0.0 release please comment with your interest on
> the Github item.
>
> Regards,
> Abhishek
>
>
> 
> From: Daan Hoogland 
> Sent: 29 September 2023 15:22
> To: dev@cloudstack.apache.org 
> Cc: us...@cloudstack.apache.org 
> Subject: Re: [PROPOSE] ACS 4.19.0.0 release
>
> Please note that these figures are not including any issues or PRs marked
>

Re: [PROPOSE] ACS 4.18.2.0

[Abhishek Kumar]

+1

João - your proposal sound good to me

From: João Jandre Paraquetti 
Sent: 08 December 2023 23:32
To: dev@cloudstack.apache.org 
Subject: [PROPOSE] ACS 4.18.2.0

Hi all,

As suggested on the 4.20.0.0 discussion thread (see
https://lists.apache.org/thread/nyoddmwydz2t59hsfs7gf0vozlf7n434), I'd
like to propose the release of version 4.18.2.0 with myself as the RM,
here's a rough timeline:

  - From now till the second week of February (2 months): accept bug
fixes and minor improvements
  - Third week of February: accept only blocker and critical bug fixes,
aiming to stabilize the branch.
  - End of February: start cutting RCs, vote and finish release work.

We currently have 7 open PRs [1] and 51 open issues [2] with 4.18.2.0 as
milestone, I believe the above timeline should give enough time to solve
all concerns. In case anyone wants to include a bug fix or a pull
request in 4.18.2.0 milestone, please mention me (JoaoJandre) on github.

If anyone has any suggestions, please voice them.

[1]:
https://github.com/apache/cloudstack/pulls?q=is%3Apr+milestone%3A4.18.2.0+is%3Aopen
[2]:
https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.18.2.0

Best regards,
João Jandre


 

Re: new committer Vladimir Petrov

[Abhishek Kumar]

Congrats Vladi!

On Tue, 12 Dec 2023 at 15:22, 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
>
> --
> Daan
>

Re: [PROPOSE] ACS 4.19.0.0 release

[Abhishek Kumar]

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: dev@cloudstack.apache.org ; 
us...@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: dev@cloudstack.apache.org ; 
us...@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: dev@cloudstack.apache.org 
Cc: us...@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 with a new feature or fix that you would like
> to see in 4.19.0.0 release please comment with your interest on the Github
> item.
>
> Regards,
> Abhishek
>
> [1] https://github.com/apache/cloudstack/milestone/24
> [2] https://github.com/apache/cloudstack/milestone/29
> 
> From: Abhishek Kumar 
> Sent: 11 October 2023 12:49
> To: dev@cloudstack.apache.org ;
> us...@cloudstack.apache.org 
> Subject: Re: [PROPOSE] ACS 4.19.0.0 release
>
> Hi all,
>
> Update on the current state of the 4.19.0.0 milestone. Currently, there
> are around 189 open items in the 4.19.0.0 milestone with 73 open PRs and
> 116 open issues.
> Also, there are some issues and PRs in 4.18.2.0 milestone which are marked
> major in severity.
> Considering these and the fact that there are some interesting new
> features in the milestone that still need some changes, review, or testing
> we may see some deviation in the earlier suggested timeline.
>
>   *  

Re: [PROPOSE] ACS 4.19.0.0 release

[Abhishek Kumar]

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: dev@cloudstack.apache.org ; 
us...@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: dev@cloudstack.apache.org ; 
us...@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: dev@cloudstack.apache.org ; 
us...@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: dev@cloudstack.apache.org 
Cc: us...@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 with a new feature or fix that you would like
> to see in 4.19.0.0 release please comment with your interest on the Github
> item.
>
> Regards,
> Abhishek
>
> [1] https://github.

[VOTE] Apache CloudStack 4.19.0.0 RC1

[Abhishek Kumar]

Hi All,

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

Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.19.0.0-RC20231222T1711
Commit: 92c0fc8fc25c916a7f3c7875d924b2d14d437501

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-RC1/

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/

Vote will be open for 120 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)

Happy Christmas everyone!

Regards,
Abhishek

[VOTE] Apache CloudStack 4.19.0.0 RC1

[Abhishek Kumar]

Hi All,

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

Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.19.0.0-RC20231222T1711
Commit: 92c0fc8fc25c916a7f3c7875d924b2d14d437501

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-RC1/

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/

Vote will be open for 120 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)

Happy Christmas everyone!

@Devs - sorry the previous email wasn't copied to the user mailing list
correctly.

Regards,
Abhishek

>

Re: [VOTE] Apache CloudStack 4.19.0.0 RC1

[Abhishek Kumar]

Thanks Daniel and Bobby for bringing this.
Yes, it makes sense to conclude the vote after next week.

Therefore, all, please continue testing RC1. Vote will remain open til 07
Jan 2024.

Regards,
Abhishek

On Thu, 28 Dec, 2023, 15:07 Boris Stoyanov, 
wrote:

> +1 to extend the vote to 1st week of Jan, most people are out on holiday
>
> Bobby.
>
> From: Daniel Salvador 
> Date: Wednesday, 27 December 2023 at 15:23
> To: us...@cloudstack.apache.org ,
> dev@cloudstack.apache.org 
> Subject: Re: [VOTE] Apache CloudStack 4.19.0.0 RC1
> Thanks, Abhishek!
>
> As a good part of the community is in holiday mood, I think we can
> postpone the vote tailing to the first week of January 2024. What do you
> think?
>
> Best regards,
> Daniel Salvador (gutoveronezi)
>
> On 12/22/23 10:58, Nux wrote:
> > That's a nice Christmas gift, Abhishek, thanks!
> >
> > I'll be testing after the new year.
> >
> >
> >
> > On 2023-12-22 13:48, Abhishek Kumar wrote:
> >> Hi All,
> >>
> >> I've created a 4.19.0.0 release (RC1), with the following artifacts
> >> up for
> >> a vote:
> >>
> >> Git Branch and Commit SH:
> >> https://github.com/apache/cloudstack/tree/4.19.0.0-RC20231222T1711
> >> Commit: 92c0fc8fc25c916a7f3c7875d924b2d14d437501
> >>
> >> 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-RC1/
> >>
> >> 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/
> >>
> >> Vote will be open for 120 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)
> >>
> >> Happy Christmas everyone!
> >>
> >> @Devs - sorry the previous email wasn't copied to the user mailing list
> >> correctly.
> >>
> >> Regards,
> >> Abhishek
> >>
> >>>
>
>
>
>

Re: [VOTE] Apache CloudStack 4.19.0.0 RC1

[Abhishek Kumar]

Hi all,

We have a blocker reported here,
https://github.com/apache/cloudstack/issues/8412 along with some other
regressions and minor issues.
https://github.com/apache/cloudstack/milestone/24

I'll work with contributors and cut a new RC once these are fixed.

Regards,
Abhishek

On Thu, 28 Dec 2023 at 21:09, Abhishek Kumar  wrote:

> Thanks Daniel and Bobby for bringing this.
> Yes, it makes sense to conclude the vote after next week.
>
> Therefore, all, please continue testing RC1. Vote will remain open til 07
> Jan 2024.
>
> Regards,
> Abhishek
>
> On Thu, 28 Dec, 2023, 15:07 Boris Stoyanov, 
> wrote:
>
>> +1 to extend the vote to 1st week of Jan, most people are out on holiday
>>
>> Bobby.
>>
>> From: Daniel Salvador 
>> Date: Wednesday, 27 December 2023 at 15:23
>> To: us...@cloudstack.apache.org ,
>> dev@cloudstack.apache.org 
>> Subject: Re: [VOTE] Apache CloudStack 4.19.0.0 RC1
>> Thanks, Abhishek!
>>
>> As a good part of the community is in holiday mood, I think we can
>> postpone the vote tailing to the first week of January 2024. What do you
>> think?
>>
>> Best regards,
>> Daniel Salvador (gutoveronezi)
>>
>> On 12/22/23 10:58, Nux wrote:
>> > That's a nice Christmas gift, Abhishek, thanks!
>> >
>> > I'll be testing after the new year.
>> >
>> >
>> >
>> > On 2023-12-22 13:48, Abhishek Kumar wrote:
>> >> Hi All,
>> >>
>> >> I've created a 4.19.0.0 release (RC1), with the following artifacts
>> >> up for
>> >> a vote:
>> >>
>> >> Git Branch and Commit SH:
>> >> https://github.com/apache/cloudstack/tree/4.19.0.0-RC20231222T1711
>> >> Commit: 92c0fc8fc25c916a7f3c7875d924b2d14d437501
>> >>
>> >> 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-RC1/
>> >>
>> >> 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/
>> >>
>> >> Vote will be open for 120 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)
>> >>
>> >> Happy Christmas everyone!
>> >>
>> >> @Devs - sorry the previous email wasn't copied to the user mailing list
>> >> correctly.
>> >>
>> >> Regards,
>> >> Abhishek
>> >>
>> >>>
>>
>>
>>
>>

Re: New committer: Alexandre Mattioli

[Abhishek Kumar]

Congrats Alex!

On Thu, 11 Jan 2024 at 03:58, 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!
>
>

-- 

Abhishek Kumar

Re: new PMC member Harikrishna Patnala

[Abhishek Kumar]

Congrats Hari!

From: Daan Hoogland 
Sent: 15 January 2024 14:55
To: dev ; users 
Subject: new PMC member Harikrishna Patnala

users and dev,

The PMC have invited Harikrishna to join their ranks and he has
gracefully accepted. Please join me in congratulating Hari.

--
Daan

 

[VOTE] Apache CloudStack 4.19.0.0 RC2

[Abhishek Kumar]

Hi All,

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

Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.19.0.0-RC20240115T1418
Commit: 38bd4fd72bdae354c4b0f615a4861fc84d67b29a

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-RC2/

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: [VOTE] Apache CloudStack 4.19.0.0 RC2

[Abhishek Kumar]

Hi all,

Thanks you for your vote Nicolas and Daan.
Thank you Wei for the tests. The reported issue will be a blocker for
people installing and upgrading on Ubuntu hosts.
We already have a fix and test results on the PR
https://github.com/apache/cloudstack/pull/8524 look good.

I'll work with contributors and cut a new RC with this fix.

Regards,
Abhishek

On Wed, 17 Jan 2024 at 20:59, Wei ZHOU  wrote:

> Hi Daan,
>
> multipath is not used in our environments at all.
> The tests for PR https://github.com/apache/cloudstack/pull/8524 look ok
> until now. Let's wait for the test results.
>
> -Wei
>
> On Wed, 17 Jan 2024 at 15:16, Daan Hoogland 
> wrote:
>
> > Wei, is this with a VM/Volume not using multipath itself? If it is it
> > is definitely a reason to create a new RC, if it isn't I think we can
> > manage a known issue for a new feature.
> >
> > On Wed, Jan 17, 2024 at 2:50 PM Wei ZHOU  wrote:
> > >
> > > Thanks Ahbishek, and everyone tested or is testing RC2.
> > >
> > > I ran some tests on a ubuntu22 environment , and got the following
> > > exception when stopping VMs.
> > >
> > > 2024-01-17 12:56:26,053 DEBUG [c.c.a.t.Request]
> > > (AgentManager-Handler-17:null) (logid:) Seq 2-8295911988593164342:
> > > Processing:  { Ans: , MgmtId: 32989056598488, via: 2, Ver: v1, Flags:
> 10,
> > >
> >
> [{"com.cloud.agent.api.Answer":{"result":"false","details":"java.lang.NullPointerException
> > > at com.cloud.utils.script.Script.getExitValue(Script.java:74)
> > > at
> > >
> >
> com.cloud.hypervisor.kvm.storage.MultipathSCSIAdapterBase.runScript(MultipathSCSIAdapterBase.java:476)
> > > at
> > >
> >
> com.cloud.hypervisor.kvm.storage.MultipathSCSIAdapterBase.disconnectPhysicalDiskByPath(MultipathSCSIAdapterBase.java:226)
> > > at
> > >
> >
> com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.disconnectPhysicalDiskByPath(KVMStoragePoolManager.java:205)
> > > at
> > >
> >
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.cleanupDisk(LibvirtComputingResource.java:3335)
> > > at
> > >
> >
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStopCommandWrapper.execute(LibvirtStopCommandWrapper.java:101)
> > > at
> > >
> >
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStopCommandWrapper.execute(LibvirtStopCommandWrapper.java:49)
> > > at
> > >
> >
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtRequestWrapper.execute(LibvirtRequestWrapper.java:78)
> > > at
> > >
> >
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1903)
> > >
> > > The workaround is
> > > chmod +x /usr/share/cloudstack-common/scripts/storage/multipath/*.sh
> > > The PR to fix it : https://github.com/apache/cloudstack/pull/8524
> > >
> > >
> > > Please note, this is not a -1 on the RC2. If we think this is not a
> > > critical issue, we need to update the upgrade instruction for it.
> > >
> > >
> > > -Wei
> > >
> > > On Mon, 15 Jan 2024 at 13:04, Abhishek Kumar 
> > wrote:
> > >
> > > > Hi All,
> > > >
> > > > I've created a 4.19.0.0 release (RC2), with the following artifacts
> up
> > for
> > > > a vote:
> > > >
> > > > Git Branch and Commit SH:
> > > > https://github.com/apache/cloudstack/tree/4.19.0.0-RC20240115T1418
> > > > Commit: 38bd4fd72bdae354c4b0f615a4861fc84d67b29a
> > > >
> > > > 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-RC2/
> > > >
> > > > 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
> > > >
> >
> >
> >
> > --
> > Daan
> >
>

[VOTE] Apache CloudStack 4.19.0.0 RC3

[Abhishek Kumar]

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: [VOTE] Apache CloudStack 4.19.0.0 RC3

[Abhishek Kumar]

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
>

[VOTE] Apache CloudStack 4.19.0.0 RC4

[Abhishek Kumar]

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

Re: Introduction and Greetings

[Abhishek Kumar]

Welcome Abhisar!

On Wed, 31 Jan 2024, 18:12 Abhisar Sinha, 
wrote:

> Hi All,
>
> I have background in Storage as a developer at NetApp India, and I have
> recently joined Shapeblue as a Software Engineer.
> I am excited to be joining the CloudStack community and looking forward to
> interacting with the community and contributing to the project.
>
> Thanks and Regards,
> Abhisar
>
>
>
>

Re: [VOTE] go life with new website(design)

[Abhishek Kumar]

+1 (binding)

Some minor layout issues in mobile view but that can be fixed later.

On Thu, 1 Feb 2024, 18:02 Daan Hoogland,  wrote:

> LS,
>
> I am not sure this is still needed after all the discussions
> before,but I would like to start a lazy consent vote threat anyway
> there are some non-blocking rest points mentioned and we can
> administer those in the repo for the site [1]
>
> so without further ado;
> Do we want to go life with the website as staged in
> cloudstack.staged.apache.org
>
> +1 yes
> 0 no opinion (no reaction suffices as well)
> -1 no (please state reasons
>
>
> [1] https://github.com/apache/cloudstack-www/issues/new/choose
>

[RESULT][VOTE] Apache CloudStack 4.19.0.0

[Abhishek Kumar]

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

[ANNOUNCEMENT] Apache CloudStack 4.19.0.0 LTS Release

[Abhishek Kumar]

The Apache Software Foundation and the Apache CloudStack Project Announces
Apache® CloudStack® v4.19.

Apache CloudStack 4.19 is the most recent release of the cloud management
platform. It comes as a product of extensive contributions from the
development community and is a LTS release, guaranteeing ongoing
maintenance and support for a period of 18 months

The 4.19 release contains 314 new features, improvements and bug fixes
since 4.18, 26 of these being major features.

Some of the highlighted features include:

- VMware to KVM Migration

- KVM Import

- CloudStack Object Storage

- CloudStack DRS

- VNF Appliances Support

- Scheduled Instance Lifecycle Operations

- OAuth 2 Authentication

- CloudStack Snapshot Copy

The full list of new features can be found in the project release notes at:
https://docs.cloudstack.apache.org/en/4.19.0.0/releasenotes


The CloudStack documentation includes upgrade instructions from previous
versions of Apache CloudStack, and can be found at:
https://docs.cloudstack.apache.org/en/4.19.0.0/upgrading

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

Downloads

The official source code for the 4.19.0.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/el/9/

- https://download.cloudstack.org/ubuntu/dists/

- https://www.shapeblue.com/cloudstack-packages/


Regards,

Abhishek

Re: [VOTE] next version 20 instead of 4.20

[Abhishek Kumar]

+1

On Mon, 19 Feb 2024 at 18:20, Daan Hoogland  wrote:

> LS,
>
> This is a vote on dev@c.a.o with cc to users@c.a.o. If you want to be
> counted please reply to dev@.
>
> As discussed in [1] we are deciding to drop the 4 from our versioning
> scheme. The result would be that the next major version will be 20
> instead of 4.20, as it would be in a traditional upgrade. As 20 > 4
> and the versions are processed numerically there are no technical
> impediments.
>
> +1 agree (next major version as 20
> 0 (no opinion)
> -1 disagree (keep 4.20 as the next version, give a reason)
>
> As this is a lazy consensus vote any -1 should be accompanied with a
> reason.
>
> [1] https://lists.apache.org/thread/lh45w55c3jmhm7w2w0xgdvlw78pd4p87
>
> --
> Daan
>

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

[Abhishek Kumar]

Thanks a lot Rohit for your work
Congratulations Daniel!
 



From: Rohit Yadav 
Sent: 21 March 2024 19:11
To: dev ; users ; 
 
Subject: [ANNOUNCE] New PMC Chair & VP Apache CloudStack Project - Daniel 
Salvador

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

Re: [ANNOUNCE] Rene Peinthor as committer

[Abhishek Kumar]

Congratulations Rene!

On Fri, 29 Mar 2024, 13:42 Daan Hoogland,  wrote:

> devs and users,
>
> The PMC have asked Rene Peinthor to become a committer to the Apache
> CloudStack project and they  have accepted.
>
> Please join me in congratulating Rene.
>
> --
> Daan
>

Re: New Committer: Kiran Chavala

[Abhishek Kumar]

Congratulations Kiran!
 



From: Rohit Yadav 
Sent: 09 April 2024 11:15
To: dev 
Subject: New Committer: Kiran Chavala

The Project Management Committee (PMC) for Apache CloudStack
has invited Kiran Chavala (kiranchavala) to become a committer and
we are pleased to announce that they have accepted.

Kiran has been a long time CloudStack contributor and has created
over a hundred issues on Github. Being a committer enables easier
contribution to the project and enable better productivity.

Please join me in congratulating Kiran!

Regards.

Re: New PMC member: Slavka Peleva

[Abhishek Kumar]

Congratulations Slavka!
 



From: Ivet Petrova 
Sent: 10 April 2024 16:41
To: us...@cloudstack.apache.org ; dev 

Subject: Fwd: New PMC member: Slavka Peleva

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,

[ANNOUNCE] Apache CloudStack LTS Security Releases 4.18.2.1 and 4.19.0.2

[Abhishek Kumar]

Apache CloudStack project announces the release of LTS security releases
4.18.2.1 and 4.19.0.2 that addresses CVE-2024-38346 and CVE-2024-39864,
both of severity rating 'important', explained below.

# CVE-2024-38346: Unauthenticated cluster service port leads to remote execution

The CloudStack cluster service runs on unauthenticated port (default 9090) that
can be misused to run arbitrary commands on targeted hypervisors and CloudStack
management server hosts. Some of these commands were found to have command
injection vulnerabilities that can result in arbitrary code execution via agents
on the hosts that may run as a privileged user. An attacker that can reach the
cluster service on the unauthenticated port (default 9090), can exploit this to
perform remote code execution on CloudStack managed hosts and result in complete
compromise of the confidentiality, integrity, and availability of CloudStack
managed infrastructure.

# CVE-2024-39864: Integration API service uses dynamic port when disabled

The CloudStack integration API service allows running its unauthenticated API
server (usually on port 8096 when configured and enabled via
integration.api.port global setting) for internal portal integrations and for
testing purposes. By default, the integration API service port is disabled and
is considered disabled when integration.api.port is set to 0 or negative. Due to
an improper initialisation logic, the integration API service would listen on a
random port when its port value is set to 0 (default value). An attacker that
can access the CloudStack management network could scan and find the randomised
integration API service port and exploit it to perform unauthorised
administrative actions and perform remote code execution on CloudStack managed
hosts and result in complete compromise of the confidentiality, integrity, and
availability of CloudStack managed infrastructure.

# Credits

Both the CVEs are credited to the following reporters from the Apple Services
Engineering Security team:

- Adam Pond (finder)
- Terry Thibault (finder)
- Damon Smith (finder)

# Affected Versions

- Apache CloudStack 4.0.0 through 4.18.2.0
- Apache CloudStack 4.19.0.0 through 4.19.0.1

# Resolution

Users are recommended to upgrade to version 4.18.2.1, 4.19.0.2 or later, which
addresses these issues.

Additionally, users are recommended the following actions:

- Restrict the network access to the cluster service
port (default 9090) on a CloudStack management server host to only its peer
CloudStack management server hosts.
- Restrict the network access on the CloudStack management server hosts
to only essential ports.

# Downloads and Documentation

The official source code for the 4.18.2.1 and 4.19.0.2 releases can be
downloaded from the project downloads page:
https://cloudstack.apache.org/downloads

The 4.18.2.1 and 4.19.0.2 release notes can be found at:
https://docs.cloudstack.apache.org/en/4.18.2.1/releasenotes/about.html
https://docs.cloudstack.apache.org/en/4.19.0.2/releasenotes/about.html

In addition to the official source code release, individual contributors
have also made release packages available on the Apache CloudStack
download page, and available at:

https://download.cloudstack.org/el/7/
https://download.cloudstack.org/el/8/
https://download.cloudstack.org/el/9/
https://download.cloudstack.org/suse/15/
https://download.cloudstack.org/ubuntu/dists/
https://www.shapeblue.com/cloudstack-packages/

Re: [ANNOUNCE] Next PMC Chair & VP Apache CloudStack Project - Sven Vogel

[Abhishek Kumar]

Thank you Paul for the great work over the last year.
Congratulations Sven!

Regards,
Abhishek

From: Paul Angus 
Sent: 19 March 2020 14:04
To: priv...@cloudstack.apache.org ; 
us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org ; Apache CloudStack 
Marketing 
Subject: [ANNOUNCE] Next PMC Chair & VP Apache CloudStack Project - Sven Vogel

Hi Everyone,

It gives me great pleasure to announce that ASF board last night
accepted our PMC's nomination of Sven Vogel as the next VP of the
project.

As I hand over the reins, I would like to thank everyone for the
support I've received over the past year. It looks like being a very
difficult year ahead for the world in general, and I wish everyone
good luck in navigating it and urge everyone to try to show patience
and compassion in these trying times.

I'd like to thank Sven for volunteering for the post and wish him the
best of luck, I'm sure that he'll do a great job.

So please join me in welcoming Sven Vogel as the new Apache CloudStack
VP and PMC Chair !

abhishek.ku...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 

[DISCUSS] New default template

[Abhishek Kumar]

Hi all,

I would like to hear everyone's opinion on a new default template in CloudStack.
Currently, we are using CentOS 5.x for different hypervisors but it is quite 
old(already completed its support life) and either the support for it has been 
removed (https://github.com/xcp-ng/xcp/wiki/Guest-System-Support) or in legacy 
(https://www.vmware.com/resources/compatibility/search.php?deviceCategory=software&details=1&partner=272&releases=448&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc&testConfig=16)
 in different hypervisors.
Therefore, I think it is time now to move to a newer OS template. In my 
understanding CentOS7 is the minimum viable choice if we are continuing with 
CentOS. This can be the preferred choice as we already have tested templates 
for it on different hypervisors and it has 4 years left in its cycle.

We can also explore Ubuntu’s cloud-images of 20.04. And if we want to go with 
something very light-weight we can think about something like Alpine Linux.

Please have your say. Also, do you think this can be included in 4.15 itself so 
we can have a proper default template for something like XCP-ng 8.x which 
doesn't support CentOS 5 (and PV VMs)?

Regards,
Abhishek


abhishek.ku...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 

[DISCUSS] Management server default port conflict

[Abhishek Kumar]

Hi all,

I would like to know everyone's opinion regarding an issue seen with CloudStack 
on CentOS8 (https://github.com/apache/cloudstack/pull/4068). CentOS8 comes with 
cockpit (https://cockpit-project.org/) installed which uses port 9090, although 
it is not active by default. CloudStack management server also needs port 9090. 
And when CloudStack management server is started with systemd it triggers the 
start of cockpit first and management server fails to start,


2020-06-25 07:20:51,707 ERROR [c.c.c.ClusterManagerImpl] (main:null) (logid:) 
Detected that another management node with the same IP 10.10.2.167 is already 
running, please check your cluster configuration
2020-06-25 07:20:51,708 ERROR [o.a.c.s.l.CloudStackExtendedLifeCycle] 
(main:null) (logid:) Failed to configure ClusterManagerImpl
javax.naming.ConfigurationException: Detected that another management node with 
the same IP 10.10.2.167 is already running, please check your cluster 
configuration
at 
com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1192)
at 
com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1065)
at 
org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114)
at 
org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153)
at 
org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110)
at 
org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55)
at 
org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:182)
at 
org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:53)
at 
org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:360)
at 
org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:158)
at 
org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:122)
at 
org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:894)
at 
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:144)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:121)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:244)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:249)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:249)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:232)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:116)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(DefaultModuleDefinitionSet.java:78)
at 
org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules(ModuleBasedContextFactory.java:37)
at 
org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init(CloudStackSpringContext.java:70)
at 
org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContext.java:57)
at 
org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContext.java:61)
at 
org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener.contextInitialized(CloudStackContextLoaderListener.java:51)
at 
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:930)
at 
org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:553)
at 
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:889)
at 
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:356)
at 
org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1445)
at 
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1409)
at 
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:822)
at 
org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:275)
   

Re: [DISCUSS] Management server default port conflict

[Abhishek Kumar]

+1 with adding documentation.

And maybe we should also refactor the port check logic and error message. 
Currently, code just tries to connect the socket for the port and if it fails 
that with the message,
Detected that another management node with the same IP XX.XX.XX.XX is already 
running, please check your cluster configuration
Instead of the cockpit, it can be any other service/process. Should we try to 
get details of that service in the logs, exception message so the user can make 
changes?

Regards,
Abhishek

From: Rohit Yadav 
Sent: 01 July 2020 13:04
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org 
Subject: Re: [DISCUSS] Management server default port conflict

I think we can document in our CloudStack qig/release/install notes to say 
users must disable cockpit on CentOS8. Here are my 2paisas;

  *   Most users using CentOS (7/8) won't use a single-host specific management 
tool/UI such as cockpit; they would probably use some fleet management software 
or automate using ansible/puppet/ceph etc.
  *   Last time I checked the minimal CentOS-8 ISO does not install cockpit or 
that it is enabled by default (service does not run by default until you active 
the port 9090 target)
  *   Some users may have monitoring scripts/tools or security rules that 
expect port 9090 to be used by CloudStack, so it's probably safer to ask users 
to change port for cockpit than CloudStack by default

Regards.

____
From: Abhishek Kumar 
Sent: Wednesday, July 1, 2020 11:14
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org 
Subject: [DISCUSS] Management server default port conflict

Hi all,

I would like to know everyone's opinion regarding an issue seen with CloudStack 
on CentOS8 (https://github.com/apache/cloudstack/pull/4068). CentOS8 comes with 
cockpit (https://cockpit-project.org/) installed which uses port 9090, although 
it is not active by default. CloudStack management server also needs port 9090. 
And when CloudStack management server is started with systemd it triggers the 
start of cockpit first and management server fails to start,


2020-06-25 07:20:51,707 ERROR [c.c.c.ClusterManagerImpl] (main:null) (logid:) 
Detected that another management node with the same IP 10.10.2.167 is already 
running, please check your cluster configuration
2020-06-25 07:20:51,708 ERROR [o.a.c.s.l.CloudStackExtendedLifeCycle] 
(main:null) (logid:) Failed to configure ClusterManagerImpl
javax.naming.ConfigurationException: Detected that another management node with 
the same IP 10.10.2.167 is already running, please check your cluster 
configuration
at 
com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1192)
at 
com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1065)
at 
org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114)
at 
org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153)
at 
org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110)
at 
org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55)
at 
org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:182)
at 
org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:53)
at 
org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:360)
at 
org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:158)
at 
org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:122)
at 
org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:894)
at 
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:144)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:121)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:244)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:249)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:249)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinit

Re: New Joiner

[Abhishek Kumar]

Hi,

Welcome Hoang!

Regards,
Abhishek

From: Unitech Mai Nguyen 
Sent: 04 November 2020 08:01
To: us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org 
Cc: sven.vo...@qform.de 
Subject: New Joiner

Hello Everyone,

My name is Hoang and I'm currently working for Ewerk.
It is my great pleasure to have a chance to join the Cloudstack Primate project.
It has been a wonderful time for me since last December when I started my first 
task.

I would look forward to being a part of this team for a long time to go. And I 
hope to have your kind help.
Thank you so much.
__
Hoang Nguyen
Frontend Developer

EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
www.ewerk.xn--com-zq0a

Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Frank Richter
Registergericht: Leipzig HRB 9065

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 2-1:2011

__

Unitech Mai Nguyen
Frontend Developer

EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P
F +49 341 42649 - 98
hoang.ngu...@ewerk.com
www.ewerk.com

Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
Registergericht: Leipzig HRB 9065

Support:
+49 341 42649 555

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 2-1:2011

ISAE 3402 Typ II Assessed

EWERK-Blog | 
LinkedIn | 
Xing | 
Twitter | 
Facebook


Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.

Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist 
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der 
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, 
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte 
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die 
E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen 
Dank.

The contents of this e-mail (including any attachments) are confidential and 
may be legally privileged. If you are not the intended recipient of this 
e-mail, any disclosure, copying, distribution or use of its contents is 
strictly prohibited, and you should please notify the sender immediately and 
then delete it (including any attachments) from your system. Thank you.

abhishek.ku...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 

Re: [ANNOUNCE] new committer: Rakesh Venkatesh

[Abhishek Kumar]

Congrats Rakesh!

From: Sven Vogel 
Sent: 18 November 2020 04:18
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org 
Cc: r.venkat...@global.leaseweb.com 
Subject: [ANNOUNCE] new committer: Rakesh Venkatesh

Hi everyone,



 The Project Management Committee (PMC) for Apache CloudStack
has invited Rakesh Venkatesh to become a committer and we are pleased

to announce that he has accepted.

Please join me in congratulating Rakesh on this accomplishment.


Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.


Thanks and Cheers,



Sven Vogel
Apache CloudStack PMC member

abhishek.ku...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue