Re: [VOTE] Apache CloudStack Kubernetes Provider 1.1.0 RC1

[Kiran Chavala]

Hi Vishesh

+1

I tried the same steps as Wei did,  but deployed a cks cluster in a vpc network 
tier with acl rule of default_allow

1. Create a CKS cluster with k8s 1.28.4 and Select a vpc network

2. Delete cloudstack-kubernetes-provider 1.0.0

kubectl delete -f
https://raw.githubusercontent.com/apache/cloudstack-kubernetes-provider/main/deployment.yaml

3.  Install 1.1.0-rc1

kubectl apply -f
https://github.com/apache/cloudstack-kubernetes-provider/releases/download/v1.1.0-rc1/deployment.yaml

4. Create nginx deployment and expose the service with type=LoadBalancer.

kubectl  expose deploy/nginx-deployment3 --port=80 --type=LoadBalancer.

The public ip is qcuired

kubectl  get svc
NAMETYPE   CLUSTER-IP  EXTERNAL-IP   PORT(S)
AGE
kubernetes  ClusterIP  10.96.0.1   443/TCP
12m
nginx-deployment3   LoadBalancer   10.105.61.120   10.0.54.125   80:31053/TCP   
7m37s



5.  Delete the nginx service.
Public IP is released

Regards
Kiran

From: Rohit Yadav 
Date: Thursday, 20 June 2024 at 12:04 PM
To: dev@cloudstack.apache.org , 
us...@cloudstack.apache.org 
Subject: Re: [VOTE] Apache CloudStack Kubernetes Provider 1.1.0 RC1
Lucian,

The convenience binary in case of this sub-project is the docker/container 
image, users can test RC1 builds from: 
https://hub.docker.com/r/apache/cloudstack-kubernetes-provider/tags


Regards.




 



From: Nux 
Sent: Thursday, June 20, 2024 04:03
To: dev@cloudstack.apache.org 
Cc: us...@cloudstack.apache.org 
Subject: Re: [VOTE] Apache CloudStack Kubernetes Provider 1.1.0 RC1

In community's interest, do we have binary packages anywhere, ie
deb/rpms?

Cheers

On 2024-06-19 07:12, Vishesh Jindal wrote:
> Hi All,
>
> I made a mistake and didn't create the release on dist.apache.org.
> Please discard my previous email.
>
> I've created a new CloudStack Kubernetes Provider 1.1.0 release (RC1),
> with the following artifacts up for a vote:
>
> Git Branch and Commit SHA:
> https://github.com/apache/cloudstack-kubernetes-provider/tree/59c3e7b21c39eefb2306bb8504bcef901a9d
> Commit: 59c3e7b21c39eefb2306bb8504bcef901a9d
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/kubernetes-provider-1.1.0/
>
> PGP release keys (signed using
> 5ED1E1122DC5E8A4A45112C2484248210EE3D884):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> For users convenience:
> * docker hub -
> https://hub.docker.com/r/apache/cloudstack-kubernetes-provider/tags
>
> * Kubernetes manifest for the rc release:
> https://github.com/apache/cloudstack-kubernetes-provider/releases/download/v1.1.0-rc1/deployment.yaml
>
> 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)
>
> Regards
> Vishesh
>
> 
>
>
>
> From: Vishesh Jindal
> Sent: Tuesday, June 18, 2024 6:36 PM
> To: us...@cloudstack.apache.org ;
> dev@cloudstack.apache.org 
> Subject: [VOTE] Apache CloudStack Kubernetes Provider 1.1.0 RC1
>
> Hi All,
>
> I've created a 1.1.0 release (RC1) for Apache CloudStack Kubernetes
> Provider, with the following artifacts up for
> a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack-kubernetes-provider/tree/v1.1.0-rc1
>
> Commit: 774a144876d2c875c61becab00e0487692130302
>
> Deployment manifest:
> https://github.com/apache/cloudstack-kubernetes-provider/releases/download/v1.1.0-rc1/deployment.yaml
>
> Docker image:
> apache/cloudstack-kubernetes-provider:v1.1.0-rc1
>
> Docker image manifest digest:
> sha256:38dc0a4413657b9c88cdcb28ef330e49aee6fb972a4cbc4055a0608b9f8bf7b8
>
> You can check the changelog for the release
> here:https://github.com/apache/cloudstack-kubernetes-provider/releases/tag/v1.1.0-rc1
>
> 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)
>
> Regards
> Vishesh

[ANNOUNCE] Apache CloudStack Terraform Provider v0.5.0 Release

[Kiran Chavala]

Hi All

# Apache CloudStack Terraform Provider v0.5.0 Release

We are pleased to announce the release of Apache CloudStack Terraform
provider v0.5.0.

Terraform is an open-source infrastructure as code software tool that
provides a consistent CLI workflow to manage resources in many
public/private clouds.

Terraform v0.5.0 comes packed with several new features, enhancements,
and bug fixes to make it even more robust and reliable.

Some of the key highlights of this release include:


-  Added support for Kubernetes Cluster creation
-  Added support for Kubernetes iso registration
-  Added support for new data sources in Cloudstack
-  Added UEFI Support to the Cloudstack instance resource
-  Added vApp properties support to the Cloudstack Instance resource
-  Added parameters (host_id , cluster_id support to the
Cloudstack instance resource
-  Added source_nat_ip_address support to the Cloudstack network
-  Added  new resource attach_volume
-  Improved service offering creation by adding more parameters
-  Added documentation for new resources
-  Various Bug fixes
-  Validated and fixed all existing resource creations to work as expected


Apache CloudStack Terraform provider v0.5.0.  is available for
download now from the Apache CloudStack website.

## Downloads and Documentation

The official source code for Apache CloudStack Terraform provider can
be downloaded from:

https://cloudstack.apache.org/downloads


The installation and usage documentation for Apache CloudStack
Terraform provider is available at:

https://github.com/apache/cloudstack-terraform-provider/wiki
https://github.com/apache/cloudstack-terraform-provider/wiki#installing-from-github-release


Users can also get the provider from the Terraform registry published at:

https://registry.terraform.io/providers/cloudstack/cloudstack/0.5.0


The documentation for the usage of resources to create and interact
with CloudStack is available at

https://registry.terraform.io/providers/cloudstack/cloudstack/0.5.0/docs


Regards
Kiran Chavala

Re: New PMC member: Slavka Peleva

[Kiran Chavala]

Congratulations Slavka!

Regards
Kiran

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

Regards,
Nicolas Vazquez


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

Cheers,
Rene

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

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



 

Re: New Committer: Kiran Chavala

[Kiran Chavala]

Thanks all!!

Regards
Kiran Chavala

From: Nicolas Vazquez 
Date: Tuesday, 9 April 2024 at 6:04 PM
To: dev@cloudstack.apache.org 
Subject: Re: New Committer: Kiran Chavala
Congratulations Kiran!

Regards,
Nicolas Vazquez


From: Vishesh Jindal 
Date: Tuesday, 9 April 2024 at 09:27
To: dev@cloudstack.apache.org 
Subject: Re: New Committer: Kiran Chavala
Congratulations Kiran!






 



From: Slavka Peleva 
Sent: Tuesday, April 9, 2024 5:12 PM
To: dev@cloudstack.apache.org 
Subject: Re: New Committer: Kiran Chavala

Congratulations Kiran!

On Tue, Apr 9, 2024 at 2:17 PM João Jandre Paraquetti 
wrote:

> Congratunations Kiran!!
>
> On 4/9/24 02:45, Rohit Yadav wrote:
> > 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.
>

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

[Kiran Chavala]

Hi All

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

5 PMC + 2 non-PMC votes.

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

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

0
none

-1
none

Thanks to everyone participating.

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

Regards,
Kiran Chavala

 

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

[Kiran Chavala]

Hi All,

Reminder – terraform 0.5.0  is up for testing and voting.

Regards.
Kiran

From: Rohit Yadav 
Date: Wednesday, 3 April 2024 at 9:43 AM
To: dev@cloudstack.apache.org , 
us...@cloudstack.apache.org 
Subject: Re: [VOTE] Release Apache CloudStack Terraform Provider v0.5.0
+1 (binding)

Tested vm deployment using 0.5.0-pre.

Regards.



 



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

Hi ALL

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

Git Branch and Commit SH:

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

Commit: 7c682bf17bebf40837a30ebcca811fc7b8785a15

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

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

Vote will be open for 72 hours.

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

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

For users convenience, they can use this 0.5.0-pre build 
https://registry.terraform.io/providers/cloudstack/cloudstack/0.5.0-pre for 
testing purposes.
The binaries are here: 
https://github.com/apache/cloudstack-terraform-provider/releases/tag/v0.5.0-pre


Regards
Kiran Chavala

[VOTE] Release Apache CloudStack Terraform Provider v0.5.0

[Kiran Chavala]

Hi ALL

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

Git Branch and Commit SH:

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

Commit: 7c682bf17bebf40837a30ebcca811fc7b8785a15

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

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

Vote will be open for 72 hours.

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

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

For users convenience, they can use this 0.5.0-pre build 
https://registry.terraform.io/providers/cloudstack/cloudstack/0.5.0-pre for 
testing purposes.
The binaries are here: 
https://github.com/apache/cloudstack-terraform-provider/releases/tag/v0.5.0-pre


Regards
Kiran Chavala

 

Re: [PROPOSE] RM for Cloudstack Terraform Provider

[Kiran Chavala]

Hi All

Update- I am planning to cut 0.5 RC 1 and start the voting process on  April 1st

Please continue testing the 0.5 pre 
(https://registry.terraform.io/providers/cloudstack/cloudstack/0.5.0-pre)  and 
help report any issues/regressions at 
https://github.com/apache/cloudstack-terraform-provider/issues

Regards
Kiran

From: Rohit Yadav 
Date: Monday, 18 March 2024 at 9:44 PM
To: dev@cloudstack.apache.org , 
us...@cloudstack.apache.org 
Subject: Re: [PROPOSE] RM for Cloudstack Terraform Provider
All,

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

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


Regards.




 



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

All,

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

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

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

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

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


Thanks and regards,

Rohit & Kiran




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

Hi All,

Greetings

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


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


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


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

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


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


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

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



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

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

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





Regards
Kiran

[PROPOSE] RM for Cloudstack Terraform Provider

[Kiran Chavala]

Hi All,

Greetings

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


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


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


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

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


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


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

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



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

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

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





Regards
Kiran

 

Re: new committer: Vishesh Jindal (vishesh)

[Kiran Chavala]

Congratulations Vishesh

Regards
Kiran

From: Daan Hoogland 
Date: Monday, 26 February 2024 at 7:35 PM
To: users , dev 
Subject: new committer: Vishesh Jindal (vishesh)
users and devs,

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

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.

Please join me in congratulating Vishesh.

--
on behalf of the PMC, Daan

 

Re: [DISCUSS] Closing issues & PR after a certain time

[Kiran Chavala]

Good idea Vishesh

+1 for using Githubactions

Regards
Kiran

From: Vishesh Jindal 
Date: Tuesday, 13 February 2024 at 6:33 PM
To: dev@cloudstack.apache.org 
Subject: [DISCUSS] Closing issues & PR after a certain time
Hi everyone,

I was going through the issues and PRs, and I noticed that a lot of them are 
really old and some of them are waiting for the original author to reply.

I wanted to discuss if we should add a github action 
(https://github.com/marketplace/actions/close-stale-issues) for auto closing 
the issues and PRs after a certain time.

From the github actions' documentation, this is how it works:

  *   Add a label "Stale" on issues and pull requests after 60 days of 
inactivity and comment on them
  *   Close the stale issues and pull requests after 7 days of inactivity
  *   If an update/comment occur on stale issues or pull requests, the stale 
label will be removed and the timer will restart

Instead of using the defaults, I would like to:

  *
mark the issue/PR stale after 90 days
  *
 close the stale issue/PR after 30 days

Let me know if this sounds good. I will create the PR to set this up.

Regards,
Vishesh






 

Re: new website is life

[Kiran Chavala]

Congratulations to all involved!,  Breath of fresh air to the website, Looks 
Neat and clean

Regards
Kiran

From: Daan Hoogland 
Date: Wednesday, 7 February 2024 at 1:53 PM
To: dev , users 
Subject: new website is life
People,
we brought the new website. Please all have a look at
https://cloudstack.apache.org

thanks for any feedback

--
Daan

 

Re: [ANNOUNCEMENT] Apache CloudStack 4.19.0.0 LTS Release

[Kiran Chavala]

Congratulations  everyone on the 4.19 release it has amazing features.

Great work Abhishek

Regards
Kiran

From: Abhishek Kumar 
Date: Tuesday, 6 February 2024 at 5:07 PM
To: dev@cloudstack.apache.org 
Subject: [ANNOUNCEMENT] Apache CloudStack 4.19.0.0 LTS Release
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: new PMC member Harikrishna Patnala

[Kiran Chavala]

Congrats Hari!

Regards
Kiran

From: Abhishek Kumar 
Date: Monday, 15 January 2024 at 5:14 PM
To: dev , users 
Subject: Re: new PMC member Harikrishna Patnala
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



 

Re: New committer: Alexandre Mattioli

[Kiran Chavala]

Congratulations Alex!

Regards
Kiran

From: Jithin Raju 
Date: Thursday, 11 January 2024 at 10:16 AM
To: us...@cloudstack.apache.org , Dev 

Subject: Re: New committer: Alexandre Mattioli
Congratulations Alex.

-Jithin

From: Nux 
Date: Thursday, 11 January 2024 at 3:58 AM
To: Dev , Users 
Subject: New committer: Alexandre Mattioli
All,

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

Alex has been instrumental in many features present today in Cloudstack,
with a focus on networking and VMWare:
- IPv6 static routing
- Edge Zones
- Autoscaling with VR
- VNF appliances
- VMWare NSX support
- Tungsten Fabric / OpenSDN
- Backup & recovery framework
- VLAN trunking and security policies in ESX
and so on.


Please join me in congratulating Alex!



 

Re: new committer Vladimir Petrov

[Kiran Chavala]

Congratulations Vladi

Regards
Kiran

From: Ruben Bosch 
Date: Tuesday, 12 December 2023 at 11:03 AM
To: dev@cloudstack.apache.org 
Cc: users 
Subject: Re: new committer Vladimir Petrov
Congrats!

Met vriendelijke groet / Kind regards,

Ruben Bosch
CLDIN


 

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

Re: [ANNOUNCEMENT] Apache CloudStack LTS Maintenance Release 4.18.1.0

[Kiran Chavala]

Congratulations everyone on the new release

Regards
Kiran



From: Rohit Yadav 
Date: Friday, 15 September 2023 at 10:12 PM
To: us...@cloudstack.apache.org , 
dev@cloudstack.apache.org 
Cc: Wei ZHOU 
Subject: Re: [ANNOUNCEMENT] Apache CloudStack LTS Maintenance Release 4.18.1.0
Congratulations everyone on the new release, and thanks Wei and everyone 
involved in the release and voting process.


Regards.


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

Great, thanks Wei!

Regards,
Nicolas Vazquez


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

Congrats! Well done Wei!



--






 

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


>

>

> That's amazing! Thanks, Wei!
>

>

>

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

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

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

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

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

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

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

> > # Documentation
> >

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

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

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

> > # Downloads
> >

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

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

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

Re: [DISCUSS] Simplifying constructs and UX

[Kiran Chavala]

Hi Rohit

Good  Ideas !, Please find my feedback inline


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

Kiran> I prefer to keep the Default view as there should be some differentiation

Projects is a feature (like grouping) through which a user can organize his 
resources in Cloudstack.

Other public cloud providers uses the concept of resource groups to organize a 
account resources

May be it could be useful is future as more integrations are added to Cloudstack

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

Kiran> +1 for this

All other public cloud providers  by default deploy a vpc network along with 
the vm deployment

Do you mean by default Cloudstack, should create a vpc  network , instead of 
isolated network ?

Currently isolated network is created by default during vm creation


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

Kiran> +1 for this

Also I believe the community and shared filter can be merged into one as it 
simplifies

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

Kiran> I believe the data disk should be present in the vm deploy form, as the 
user should have the option to select large disk for his use case

Also when deploying a vm from ISO, a data disk offering is a mandatory feild


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

Kiran> +1, as user-data(cloud-init) is widely used in automation as it helps in 
bringing up the vm with the required configuration

+1 also for shifting the affinity groups from advanced menu

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

Kiran> +1, for this

Regards
Kiran

From: Rohit Yadav 
Date: Friday, 11 August 2023 at 9:44 PM
To: dev@cloudstack.apache.org 
Cc: us...@cloudstack.apache.org 
Subject: [DISCUSS] Simplifying constructs and UX
All,

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

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

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

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

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

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

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


Regards.



 

Re: Guest OS Rhel 9 and centos 9 going to kernel panic mode.

[Kiran Chavala]

Hi Sanjay

This look like limitation from the el9 side

https://www.phoronix.com/news/RHEL-9-x86-64-v2-Plans
https://developers.redhat.com/blog/2021/01/05/building-red-hat-enterprise-linux-9-for-the-x86-64-v2-microarchitecture-level#recommendations_for_rhel_9

https://forums.rockylinux.org/t/rocky-linux-9-virtualbox-kernel-panic/6692/5


As a workaround, Please perform the following changes

1. Edit the file present on the kvm hosts  
“/etc/cloudstack/agent/agent.properties “

guest.cpu.mode=host-passthrough

2. Restart the agent service

service cloudstack-agent restart

---
Now to try to launch a  new centos 9 stream vm from the ISO

Regards
Kiran


From: Sanjay Kumar 
Date: Wednesday, 2 August 2023 at 12:58 PM
To: us...@cloudstack.apache.org , 
dev@cloudstack.apache.org 
Subject: Guest OS Rhel 9 and centos 9 going to kernel panic mode.
Hello,

We are facing strange issue with guest Os rhel 9 and centos 9 going to
kernel panic mode while deploying the vm.

ACS_Version: 4.18
KVM_Host: Rocky_Linux 8.8

Any help would be much appreciated

Thanks,
Sanjay Kumar

 

Re: CentOS9 going to kernel panic mode

[Kiran Chavala]

Hi Stanley

This look like limitation from the el9 side

https://www.phoronix.com/news/RHEL-9-x86-64-v2-Plans
https://developers.redhat.com/blog/2021/01/05/building-red-hat-enterprise-linux-9-for-the-x86-64-v2-microarchitecture-level#recommendations_for_rhel_9

https://forums.rockylinux.org/t/rocky-linux-9-virtualbox-kernel-panic/6692/5


As a workaround, Please perform the following changes

1. Edit the file present on the kvm hosts  
“/etc/cloudstack/agent/agent.properties “

guest.cpu.mode=host-passthrough

2. Restart the agent service

service cloudstack-agent restart

---
Now to try to launch a  new centos 9 stream vm from the ISO

Regards
Kiran

From: Kiran Chavala 
Date: Wednesday, 2 August 2023 at 1:27 PM
To: dev@cloudstack.apache.org 
Subject: Re: CentOS9 going to kernel panic mode
Hi Rohit

Able to reproduce the issue, Booting Centos 9 stream iso goes into a kernel 
panic mode

Able to boot Centos 9 stream iso on virtuabox and natively on kvm  without any 
issues


Not observing the issue  with Centos 8 stream iso

Attaching the virsh dumpxml  of centos 8 and centos 9  streams

Regards
Kiran





From: Stanley Burkee 
Date: Wednesday, 2 August 2023 at 10:15 AM
To: dev@cloudstack.apache.org 
Subject: Re: CentOS9 going to kernel panic mode
Hi Rohit

Thanks for your support.
I have tried with RHEL9, Oracle Linux9, RockyLinux 9 as well. I am
experiencing same issue with all of them. And all of them are working in
VMware on my machine. The issue is only with Linux 9 flavours,the restall
the other linux OS are working fine.

Best Regards

Stanley


On Tue, Aug 1, 2023 at 9:38 PM Rohit Yadav 
wrote:

> Perhaps try with a different ISO build again, it could be an issue with
> the ISO - have you tested if it works say on VirtualBox, or VMware
> fusion/workstation?
>
>
> Regards.
>
> 
> From: Stanley Burkee 
> Sent: Tuesday, August 1, 2023 19:12
> To: dev@cloudstack.apache.org 
> Subject: Re: CentOS9 going to kernel panic mode
>
> Screenshot link given below
>
>
> https://drive.google.com/file/d/1ijpRW1ojwDyVYoErN5dWfa6C229zjNN3/view?usp=drive_link
>
> On Tue, Aug 1, 2023 at 6:54 PM Stanley Burkee 
> wrote:
>
> > Hi Rohit,
> >
> > Thanks for your support
> > The issue is consistent with multiple CPU offerings. I have used 4C4R,
> > 4C8R, 8C8R & 8C16R CPU & RAM offerings.
> >
> > Best Regards
> >
> > Stanley
> >
> >
> > On Tue, Aug 1, 2023 at 6:52 PM Rohit Yadav 
> > wrote:
> >
> >> Hi Stanley, is it consistent even if you use a service offering with
> >> large enough CPU and memory? Are you booting the VM in uefi or normal
> mode?
> >>
> >>
> >> Regards.
> >>
> >> 
> >> From: Stanley Burkee 
> >> Sent: Tuesday, August 1, 2023 18:50
> >> To: us...@cloudstack.apache.org ;
> >> dev@cloudstack.apache.org 
> >> Subject: CentOS9 going to kernel panic mode
> >>
> >> Hi Guys,
> >>
> >> Greetings
> >> I am using Cloudstack 4.18 in my testing environment. I am using Rocky
> 8.7
> >> as compute host with KVM.
> >>
> >> Whenever I create centOs9 from iso, it goes into kernel panic mode—and
> >> facing the same issue with other Linux 9 kernel flavours also.
> >>
> >> Thanks a lot in advance.
> >>
> >>
> >> Beast regards
> >>
> >> Stanley
> >>
> >>
> >>
> >>
>
>
>
>

 

Re: CentOS9 going to kernel panic mode

[Kiran Chavala]

Hi Rohit

Able to reproduce the issue, Booting Centos 9 stream iso goes into a kernel 
panic mode

Able to boot Centos 9 stream iso on virtuabox and natively on kvm  without any 
issues


Not observing the issue  with Centos 8 stream iso

Attaching the virsh dumpxml  of centos 8 and centos 9  streams

Regards
Kiran

From: Stanley Burkee 
Date: Wednesday, 2 August 2023 at 10:15 AM
To: dev@cloudstack.apache.org 
Subject: Re: CentOS9 going to kernel panic mode
Hi Rohit

Thanks for your support.
I have tried with RHEL9, Oracle Linux9, RockyLinux 9 as well. I am
experiencing same issue with all of them. And all of them are working in
VMware on my machine. The issue is only with Linux 9 flavours,the restall
the other linux OS are working fine.

Best Regards

Stanley


On Tue, Aug 1, 2023 at 9:38 PM Rohit Yadav 
wrote:

> Perhaps try with a different ISO build again, it could be an issue with
> the ISO - have you tested if it works say on VirtualBox, or VMware
> fusion/workstation?
>
>
> Regards.
>
> 
> From: Stanley Burkee 
> Sent: Tuesday, August 1, 2023 19:12
> To: dev@cloudstack.apache.org 
> Subject: Re: CentOS9 going to kernel panic mode
>
> Screenshot link given below
>
>
> https://drive.google.com/file/d/1ijpRW1ojwDyVYoErN5dWfa6C229zjNN3/view?usp=drive_link
>
> On Tue, Aug 1, 2023 at 6:54 PM Stanley Burkee 
> wrote:
>
> > Hi Rohit,
> >
> > Thanks for your support
> > The issue is consistent with multiple CPU offerings. I have used 4C4R,
> > 4C8R, 8C8R & 8C16R CPU & RAM offerings.
> >
> > Best Regards
> >
> > Stanley
> >
> >
> > On Tue, Aug 1, 2023 at 6:52 PM Rohit Yadav 
> > wrote:
> >
> >> Hi Stanley, is it consistent even if you use a service offering with
> >> large enough CPU and memory? Are you booting the VM in uefi or normal
> mode?
> >>
> >>
> >> Regards.
> >>
> >> 
> >> From: Stanley Burkee 
> >> Sent: Tuesday, August 1, 2023 18:50
> >> To: us...@cloudstack.apache.org ;
> >> dev@cloudstack.apache.org 
> >> Subject: CentOS9 going to kernel panic mode
> >>
> >> Hi Guys,
> >>
> >> Greetings
> >> I am using Cloudstack 4.18 in my testing environment. I am using Rocky
> 8.7
> >> as compute host with KVM.
> >>
> >> Whenever I create centOs9 from iso, it goes into kernel panic mode—and
> >> facing the same issue with other Linux 9 kernel flavours also.
> >>
> >> Thanks a lot in advance.
> >>
> >>
> >> Beast regards
> >>
> >> Stanley
> >>
> >>
> >>
> >>
>
>
>
>

 



centos8.xml
Description: centos8.xml


centos9.xml
Description: centos9.xml

Re: [proposal] Consistency of naming in Cloudstack

[Kiran Chavala]

+1 for instances

As other public cloud (AWS, Azure, GCP) also use the term Instances or vm 
instances

Regards
Kiran



From: Ayush Pandey 
Date: Monday, 12 June 2023 at 8:41 AM
To: dev@cloudstack.apache.org 
Subject: Re: [proposal] Consistency of naming in Cloudstack
Hi All,

I've recently started working as a GSoC Contributor (Adding unmanaged
instances for kvm hypervisor) and as a new cloudstack user I got really
confused between the term instances and virtual Machine used
interchangeably in UI/APIs, and it took me sometime to figure out both are
the same thing.

So +1 to Giles' proposal. Coming from the AWS ecosystem I think instances
make more sense but I do understand from Daan's perspective why it is not a
good choice.

Best Regards,
Ayush Pandey

On Fri, Jun 9, 2023 at 12:34 PM Nicolas Vazquez <
nicolas.vazq...@shapeblue.com> wrote:

> +1 thanks Giles.
>
> For the API we could also update the API docs descriptions for methods,
> parameters, and response fields (even though we can end up with: parameter:
> virtualmachineid and description: ‘Instance ID’ for example)
>
> Regards,
> Nicolas Vazquez
>
>
> From: Marco Sinhoreli 
> Date: Friday, 9 June 2023 at 12:58
> To: dev@cloudstack.apache.org 
> Subject: Re: [proposal] Consistency of naming in Cloudstack
> +1 to use “Instance” in the UI and docs. Everyone knows what " Instance "
> is, in my view, just a label to refer to an object in ACS. As Rohit said,
> it is under Compute, then it refers to a Compute Instance.
>
> From: Giles Sirett 
> Date: Thursday, 8 June 2023 at 16:46
> To: dev@cloudstack.apache.org 
> Subject: [proposal] Consistency of naming in Cloudstack
> Background
> Recently, I have been looking at a  number of issues relating to the
> "first use" / "first impression" use of cloudstack.  What to people think
> of Cloudstack as a new user? What is peoples perception of Cloudstack as a
> new user ? How easy is it for people to understand cloudstack & its
> concepts and to get help
>
>
> One thing I have seen is that CloudStack is inconsistent with what we call
> VM's/Instances:
>
>
>   *   In the UI main menu, we say Instances. We then have a very large
> "Create instance" button. All lifecycle operations are then  "Foo Instance"
>   *   In various other places in the UI (many text messages, error
> messages,  column headers,  for example) we say "VM"
>   *   The API uses Instance, VM and Virtual Machine
>   *   The documentation, again, uses all 3 terms
>
> Now - I know everybody on this list (myself included for the last 10
> years) has always used these terms interchangeably  - we all KNOW that
> these are the same things. However, I think it could cause confusion to
> people seeing Cloudstack for the first time and create negative
> impressions. Also, there is no consistency when searching documentation -
> one page uses one term, one the other (and some even use both on the same
> page) .  I don't know of many other pieces of software that use 2/3
> different names for their  primary functional object
>
>
> My proposal is to move towards having consistency of this naming  and
> would look something like this:
>
>
>   1.  Choose the name to use going forwards (more on that later)
>   2.  Undertake a remedial exercise:
>  *   Update UI elements to [new name]
>  *   Update documentation to [New Name]
>  *   Leave Global Settings names  alone, but change their description
> to reflect [New Name]
>  *   Leave the API alone - theres no way of getting consistency there
> without breaking compatibility
>   3.  Encourage contributors to use [new name] in all work going forwards
>
>
> The remedial exercise (hopefully) could be a find/replace (with some
> manual checking)  - I'd be happy to take that on with some help from work
> colleagues
> As/when/if  we do do Cloudstack 5.0, then look at the API, but IMO this is
> lower priority as people that's not usdually "first impression"
>
>
> So - first proposal  point: any objections to me undertaking this work ?
>
>
> Second point: what to call these things ?
> It is my view that we should call them Instances.  These are my reasons:
>
>   *   Nearly all Cloud computing platforms refer to them as instances
> (i.e. industry standard) . Yes, it is a VM "behind the scenes", but
> Instance is an accepted term that is slightly abstracted from VM
>   *   Our primary UI already uses Instance ns most prominent places,
> renaming  top level nav and functionality is a step backwards IMO
>   *   Today, Cloudstack provides these through VMs , but that could change
> in the future (please don't read anything into that comment) - instance
> doesn't tie us to VMs (which is probably why most cloud providers use it)
>
> So, my proposal is to bring consistency and use the term Instance
>
> From brief discussions, I know other people favour other terms and may
> have objections to the term Instance (despite it having been in use in ACS
> for many years)  - but happy to take all inputs if people feel t

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

[Kiran Chavala]

Congratulations Rohit 🎉😀

Regards
Kiran

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

 

Re: We are facing strange issue with acs 4.18 with Rocky Linux9

[Kiran Chavala]

Hi sanjay

Could you please give access to the logs

Regards
Kiran

From: Sanjay Kumar 
Sent: 27 March 2023 23:40
To: us...@cloudstack.apache.org 
Cc: dev@cloudstack.apache.org 
Subject: Re: We are facing strange issue with acs 4.18 with Rocky Linux9

  logs.zip



On Mon, Mar 27, 2023, 11:07 PM Wei ZHOU  wrote:

> Can you share the full log while added the host ?
>
> -Wei
>
>
>
> On Monday, 27 March 2023, Sanjay Kumar  wrote:
>
> > Hi All,
> >
> > We have setup the lab acs 4.18 with Rocky linux 9 and it was running but
> > after a day we faced the issue. is there any OS dependencies with 4.18?
> >
> >
> >
> > Could not add host at [http://10.40.40.71] with zone [1], pod [1] and
> > cluster [1] due to: [ can't setup agent, due to
> > com.cloud.utils.exception.CloudRuntimeException: Failed to setup keystore
> > on the KVM host: 10.40.40.71 - Failed to setup keystore on the KVM host:
> > 10.40.40.71].
> >
> >
> > 2023-03-27 10:09:11,382 DEBUG [c.c.c.ClusterManagerImpl]
> > (Cluster-Heartbeat-1:ctx-3383eeb3) (logid:c03fe0a7) Detected management
> > node left, id:2, nodeIP:10.40.40.23
> > 2023-03-27 10:09:11,382 INFO  [c.c.c.ClusterManagerImpl]
> > (Cluster-Heartbeat-1:ctx-3383eeb3) (logid:c03fe0a7) Trying to connect to
> > 10.40.40.23
> > 2023-03-27 10:09:11,383 INFO  [c.c.c.ClusterManagerImpl]
> > (Cluster-Heartbeat-1:ctx-3383eeb3) (logid:c03fe0a7) Management node 2 is
> > detected inactive by timestamp but is pingable
> > 2023-03-27 10:09:12,882 DEBUG [c.c.c.ClusterManagerImpl]
> > (Cluster-Heartbeat-1:ctx-ee783d0b) (logid:87ac62d2) Detected management
> > node left, id:2, nodeIP:10.40.40.23
> > 2023-03-27 10:09:12,882 INFO  [c.c.c.ClusterManagerImpl]
> > (Cluster-Heartbeat-1:ctx-ee783d0b) (logid:87ac62d2) Trying to connect to
> > 10.40.40.23
> > 2023-03-27 10:09:12,882 INFO  [c.c.c.ClusterManagerImpl]
> > (Cluster-Heartbeat-1:ctx-ee783d0b) (logid:87ac62d2) Management node 2 is
> > detected inactive by timestamp but is pingable
> > 2023-03-27 10:09:14,382 DEBUG [c.c.c.ClusterManagerImpl]
> > (Cluster-Heartbeat-1:ctx-1f50e525) (logid:a4ef06ad) Detected management
> > node left, id:2, nodeIP:10.40.40.23
> > 2023-03-27 10:09:14,383 INFO  [c.c.c.ClusterManagerImpl]
> > (Cluster-Heartbeat-1:ctx-1f50e525) (logid:a4ef06ad) Trying to connect to
> > 10.40.40.23
> > 2023-03-27 10:09:14,383 INFO  [c.c.c.ClusterManagerImpl]
> > (Cluster-Heartbeat-1:ctx-1f50e525) (logid:a4ef06ad) Management node 2 is
> > detected inactive by timestamp but is pingable
> > 2023-03-27 10:09:15,122 DEBUG [o.a.c.h.HAManagerImpl]
> > (BackgroundTaskPollManager-6:ctx-b26dd505) (logid:66b6c0db) HA health
> > check
> > task is running...
> > [root@ASCLDACS01 ~]# tail
> > /var/log/cloudstack/management/management-server.log
> > 2023-03-27 10:09:14,382 DEBUG [c.c.c.ClusterManagerImpl]
> > (Cluster-Heartbeat-1:ctx-1f50e525) (logid:a4ef06ad) Detected management
> > node left, id:2, nodeIP:10.40.40.23
> > 2023-03-27 10:09:14,383 INFO  [c.c.c.ClusterManagerImpl]
> > (Cluster-Heartbeat-1:ctx-1f50e525) (logid:a4ef06ad) Trying to connect to
> > 10.40.40.23
> > 2023-03-27 10:09:14,383 INFO  [c.c.c.ClusterManagerImpl]
> > (Cluster-Heartbeat-1:ctx-1f50e525) (logid:a4ef06ad) Management node 2 is
> > detected inactive by timestamp but is pingable
> > 2023-03-27 10:09:15,122 DEBUG [o.a.c.h.HAManagerImpl]
> > (BackgroundTaskPollManager-6:ctx-b26dd505) (logid:66b6c0db) HA health
> > check
> > task is running...
> > 2023-03-27 10:09:15,881 DEBUG [c.c.c.ClusterManagerImpl]
> > (Cluster-Heartbeat-1:ctx-b3ca8d68) (logid:50c9cf85) Detected management
> > node left, id:2, nodeIP:10.40.40.23
> > 2023-03-27 10:09:15,881 INFO  [c.c.c.ClusterManagerImpl]
> > (Cluster-Heartbeat-1:ctx-b3ca8d68) (logid:50c9cf85) Trying to connect to
> > 10.40.40.23
> > 2023-03-27 10:09:15,882 INFO  [c.c.c.ClusterManagerImpl]
> > (Cluster-Heartbeat-1:ctx-b3ca8d68) (logid:50c9cf85) Management node 2 is
> > detected inactive by timestamp but is pingable
> > 2023-03-27 10:09:17,382 DEBUG [c.c.c.ClusterManagerImpl]
> > (Cluster-Heartbeat-1:ctx-2dbaab99) (logid:7f3a46b4) Detected management
> > node left, id:2, nodeIP:10.40.40.23
> > 2023-03-27 10:09:17,382 INFO  [c.c.c.ClusterManagerImpl]
> > (Cluster-Heartbeat-1:ctx-2dbaab99) (logid:7f3a46b4) Trying to connect to
> > 10.40.40.23
> > 2023-03-27 10:09:17,383 INFO  [c.c.c.ClusterManagerImpl]
> > (Cluster-Heartbeat-1:ctx-2dbaab99) (logid:7f3a46b4) Management node 2 is
> > detected inactive by timestamp but is pingable
> >
> >
> > Any help you can give would be greatly appreciated
> >
> >
> >
> > With Regards,
> >
> > Sanjay
> >
>

 

Re: Daan Hoogland - New ASF Member

[Kiran Chavala]

Congratulations Daan

Regards
Kiran

From: Paul Angus 
Sent: 24 March 2023 14:58
To: us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org 
Subject: Daan Hoogland - New ASF Member



It is my pleasure to announce that Daan Hoogland as been elected to become a
member of the ASF.

The ASF would like to recognize both his practical involvement and the way
in which he has interacted with others in and around the ASF.



Congratulations  Daan.









Kind regards



Paul Angus




 

Re: Hello Again!

[Kiran Chavala]

Welcome back Kishan

Regards
Kiran

From: Nux 
Sent: 13 March 2023 21:49
To: dev@cloudstack.apache.org 
Cc: Kishan Kavala 
Subject: Re: Hello Again!

Welcome! :)

On 2023-03-09 10:41, Kishan Kavala wrote:
> Hi,
>  I've joined ShapeBlue and very happy to back with CloudStack
> community. Looking forward to working with you all.
>
> regards,
> Kishan

 

Re: Hello Community!!

[Kiran Chavala]

Welcome Jithin😀

Regards
Kiran

From: Vishesh Jindal 
Sent: 14 March 2023 15:52
To: us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org 
Subject: Re: Hello Community!!

Welcome Jithin!

Regards
Vishesh

From: Nicolas Vazquez 
Sent: Tuesday, March 14, 2023 3:44 PM
To: us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org 
Subject: Re: Hello Community!!

Welcome Jithin!

Regards,
Nicolas Vazquez


From: Jithin Raju 
Date: Tuesday, 14 March 2023 at 04:57
To: us...@cloudstack.apache.org , 
dev@cloudstack.apache.org 
Subject: Hello Community!!
Hi All,

I have joined ShapeBlue and looking forward to getting actively involved in the 
community. Previously I worked on the commercial fork of the ACS, mostly 
involved in technical support.

-Jithin









 

Re: [ANNOUNCE] Ivet Petrova has joined the PMC

[Kiran Chavala]

Congratulations Ivet!

From: David Jumani 
Sent: 15 February 2023 11:36
To: us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org 
Cc: priv...@cloudstack.apache.org 
Subject: Re: [ANNOUNCE] Ivet Petrova has joined the PMC

Congratulations Ivet!


From: Vishesh Jindal 
Sent: Wednesday, February 15, 2023 10:24 AM
To: us...@cloudstack.apache.org 
Cc: dev@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Subject: Re: [ANNOUNCE] Ivet Petrova has joined the PMC

Congratulations Ivet!

From: Rohit Yadav 
Sent: Wednesday, February 15, 2023 7:14 AM
To: us...@cloudstack.apache.org 
Cc: dev@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Subject: Re: [ANNOUNCE] Ivet Petrova has joined the PMC

Congratulations Ivet, well deserved!

Regards.

From: Martijn Struijk 
Sent: Wednesday, February 15, 2023 3:06:18 AM
To: us...@cloudstack.apache.org 
Cc: dev@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Subject: Re: [ANNOUNCE] Ivet Petrova has joined the PMC

Congratulations Ivet!

On Tue, Feb 14, 2023 at 7:24 PM Nicolas Vazquez <
nicolas.vazq...@shapeblue.com> wrote:

> Congratulations Ivet!
>
> Regards,
> Nicolas Vazquez
> 
> From: Simon Weller 
> Sent: Tuesday, February 14, 2023 1:01 PM
> 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)
>
>
>
>










 

Introduction

[Kiran Chavala]

Hi all,


This is Kiran, Just wanted to say hi to everyone in the community.

I've recently Shape blue as QA test engineer.

Previously I used to work with Citrix/Persistent for about 10 years in 
providing technical support to Cloudstack ( Citrix CloudPlatform and Rovius 
CloudPlatform) products

Looking forward to working with the community

Regards,
Kiran

kiran.chav...@shapeblue.com