[DISCUSS] Deprecate/remove support for EOL distros and hypervisors
All, Referencing https://docs.cloudstack.apache.org/en/4.19.0.0/releasenotes/compat.html, some of the distros and hypervisors we support have reached or reaching EOL by end of this month. Please review and advise how we should deprecating/remove the following for the next 4.20 release (i.e. compatibility matrix for the future 4.20 release notes): Distros: * EL7 (CentOS 7, RHEL7, https://endoflife.date/centos) * Ubuntu 18.04 (https://endoflife.date/ubuntu) Software requirements: * JRE 11 (Discuss - should we transition to support JRE/JDK 17 or 21, for 4.20? https://endoflife.date/oracle-jdk And are all supported distros have a JRE17/21 package/dependency availalble) * MySQL 5.6, 5.7 (https://endoflife.date/mysql) Hypervisors: * KVM: Ubuntu 18.04 (https://endoflife.date/ubuntu), EL7 (https://endoflife.date/centos) * XenServer All versions except 8.x (retain note that it's not tested, https://www.citrix.com/support/product-lifecycle/legacy-product-matrix.html) * XCP-ng: All versions except 8.2/LTS (https://endoflife.date/xcp-ng) * VMware: 6.5, 6.7 (https://endoflife.date/vcenter) Regards.
RE: [DISCUSS] Deprecate/remove support for EOL distros and hypervisors
I'd like if we keep EL7 for at least one more version, the transition path out of that is clear now but many cloud operators haven't replaced it yet. On the rest +1 -Original Message- From: Rohit Yadav Sent: Thursday, June 20, 2024 11:43 AM To: dev@cloudstack.apache.org Subject: [DISCUSS] Deprecate/remove support for EOL distros and hypervisors All, Referencing https://docs.cloudstack.apache.org/en/4.19.0.0/releasenotes/compat.html, some of the distros and hypervisors we support have reached or reaching EOL by end of this month. Please review and advise how we should deprecating/remove the following for the next 4.20 release (i.e. compatibility matrix for the future 4.20 release notes): Distros: * EL7 (CentOS 7, RHEL7, https://endoflife.date/centos) * Ubuntu 18.04 (https://endoflife.date/ubuntu) Software requirements: * JRE 11 (Discuss - should we transition to support JRE/JDK 17 or 21, for 4.20? https://endoflife.date/oracle-jdk And are all supported distros have a JRE17/21 package/dependency availalble) * MySQL 5.6, 5.7 (https://endoflife.date/mysql) Hypervisors: * KVM: Ubuntu 18.04 (https://endoflife.date/ubuntu), EL7 (https://endoflife.date/centos) * XenServer All versions except 8.x (retain note that it's not tested, https://www.citrix.com/support/product-lifecycle/legacy-product-matrix.html) * XCP-ng: All versions except 8.2/LTS (https://endoflife.date/xcp-ng) * VMware: 6.5, 6.7 (https://endoflife.date/vcenter) Regards.
Re: [DISCUSS] Deprecate/remove support for EOL distros and hypervisors
+1 what Alex said. It's kind of wrong, but CentOS7 has such a large install base (generally and for Cloudstack, too) that I feel deprecating it right away would be a mistake. On 2024-06-20 10:45, Alex Mattioli wrote: I'd like if we keep EL7 for at least one more version, the transition path out of that is clear now but many cloud operators haven't replaced it yet. On the rest +1 -Original Message- From: Rohit Yadav Sent: Thursday, June 20, 2024 11:43 AM To: dev@cloudstack.apache.org Subject: [DISCUSS] Deprecate/remove support for EOL distros and hypervisors All, Referencing https://docs.cloudstack.apache.org/en/4.19.0.0/releasenotes/compat.html, some of the distros and hypervisors we support have reached or reaching EOL by end of this month. Please review and advise how we should deprecating/remove the following for the next 4.20 release (i.e. compatibility matrix for the future 4.20 release notes): Distros: * EL7 (CentOS 7, RHEL7, https://endoflife.date/centos) * Ubuntu 18.04 (https://endoflife.date/ubuntu) Software requirements: * JRE 11 (Discuss - should we transition to support JRE/JDK 17 or 21, for 4.20? https://endoflife.date/oracle-jdk And are all supported distros have a JRE17/21 package/dependency availalble) * MySQL 5.6, 5.7 (https://endoflife.date/mysql) Hypervisors: * KVM: Ubuntu 18.04 (https://endoflife.date/ubuntu), EL7 (https://endoflife.date/centos) * XenServer All versions except 8.x (retain note that it's not tested, https://www.citrix.com/support/product-lifecycle/legacy-product-matrix.html) * XCP-ng: All versions except 8.2/LTS (https://endoflife.date/xcp-ng) * VMware: 6.5, 6.7 (https://endoflife.date/vcenter) Regards.
Re: [DISCUSS] Deprecate/remove support for EOL distros and hypervisors
+ Users Just to be clear, what this thread is about - Deprecating/removing documentation via the compatibility matrix for a component does not necessarily mean CloudStack will not work on it, in fact it might (with some additional pkg installation if required if we decide to transition to JRE17/21) and community's testing. The discussion is whether from a project point of view, what should users be advised that is considered supported via the compatibility matrix page in the release notes. The same applies for other distro/hosts, hypervisors, MySQL DB version. Just a note for the community to be aware: EL7/CentOS7 active support has already ended in 2020, and we've already supported it since the last 3-4 years. It's only the security update/support ending by end June 2024. So, if there's any future/potential security issue around EL7, we will not be able to support that 18months moving forward (18 months being typical ACS LTS release support period). That's risk, I think we logistically wouldn't be able to carry forward for the next major release (4.20) in Q3/Q4 '24. Refer: https://endoflife.date/centos Regards. From: Nux Sent: Thursday, June 20, 2024 15:21 To: dev@cloudstack.apache.org Cc: Alex Mattioli Subject: Re: [DISCUSS] Deprecate/remove support for EOL distros and hypervisors +1 what Alex said. It's kind of wrong, but CentOS7 has such a large install base (generally and for Cloudstack, too) that I feel deprecating it right away would be a mistake. On 2024-06-20 10:45, Alex Mattioli wrote: > I'd like if we keep EL7 for at least one more version, the transition > path out of that is clear now but many cloud operators haven't replaced > it yet. > > On the rest +1 > > > > > -Original Message- > From: Rohit Yadav > Sent: Thursday, June 20, 2024 11:43 AM > To: dev@cloudstack.apache.org > Subject: [DISCUSS] Deprecate/remove support for EOL distros and > hypervisors > > All, > > Referencing > https://docs.cloudstack.apache.org/en/4.19.0.0/releasenotes/compat.html, > some of the distros and hypervisors we support have reached or reaching > EOL by end of this month. > > Please review and advise how we should deprecating/remove the following > for the next 4.20 release (i.e. compatibility matrix for the future > 4.20 release notes): > > Distros: > > * > EL7 (CentOS 7, RHEL7, https://endoflife.date/centos) > * > Ubuntu 18.04 (https://endoflife.date/ubuntu) > > > Software requirements: > > * > JRE 11 (Discuss - should we transition to support JRE/JDK 17 or 21, for > 4.20? https://endoflife.date/oracle-jdk And are all supported distros > have a JRE17/21 package/dependency availalble) > * > MySQL 5.6, 5.7 (https://endoflife.date/mysql) > > Hypervisors: > > * > KVM: Ubuntu 18.04 (https://endoflife.date/ubuntu), EL7 > (https://endoflife.date/centos) > * > XenServer All versions except 8.x (retain note that it's not tested, > https://www.citrix.com/support/product-lifecycle/legacy-product-matrix.html) > * > XCP-ng: All versions except 8.2/LTS (https://endoflife.date/xcp-ng) > * > VMware: 6.5, 6.7 (https://endoflife.date/vcenter) > > > Regards.
Re: [VOTE] Apache CloudStack Kubernetes Provider 1.1.0 RC1
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
Re: [VOTE] Apache CloudStack Kubernetes Provider 1.1.0 RC1
+1 as well, based on similar test to Wei's. Good job, Vishesh. On 2024-06-20 12:34, Kiran Chavala wrote: 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/TCP12m 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
Re: [DISCUSS] Deprecate/remove support for EOL distros and hypervisors
By all means, remove CentOS7 and any EOL OS or component from the matrix and recommendations! Regards On 2024-06-20 11:45, Rohit Yadav wrote: + Users Just to be clear, what this thread is about - Deprecating/removing documentation via the compatibility matrix for a component does not necessarily mean CloudStack will not work on it, in fact it might (with some additional pkg installation if required if we decide to transition to JRE17/21) and community's testing. The discussion is whether from a project point of view, what should users be advised that is considered supported via the compatibility matrix page in the release notes. The same applies for other distro/hosts, hypervisors, MySQL DB version. Just a note for the community to be aware: EL7/CentOS7 active support has already ended in 2020, and we've already supported it since the last 3-4 years. It's only the security update/support ending by end June 2024. So, if there's any future/potential security issue around EL7, we will not be able to support that 18months moving forward (18 months being typical ACS LTS release support period). That's risk, I think we logistically wouldn't be able to carry forward for the next major release (4.20) in Q3/Q4 '24. Refer: https://endoflife.date/centos Regards. From: Nux Sent: Thursday, June 20, 2024 15:21 To: dev@cloudstack.apache.org Cc: Alex Mattioli Subject: Re: [DISCUSS] Deprecate/remove support for EOL distros and hypervisors +1 what Alex said. It's kind of wrong, but CentOS7 has such a large install base (generally and for Cloudstack, too) that I feel deprecating it right away would be a mistake. On 2024-06-20 10:45, Alex Mattioli wrote: I'd like if we keep EL7 for at least one more version, the transition path out of that is clear now but many cloud operators haven't replaced it yet. On the rest +1 -Original Message- From: Rohit Yadav Sent: Thursday, June 20, 2024 11:43 AM To: dev@cloudstack.apache.org Subject: [DISCUSS] Deprecate/remove support for EOL distros and hypervisors All, Referencing https://docs.cloudstack.apache.org/en/4.19.0.0/releasenotes/compat.html, some of the distros and hypervisors we support have reached or reaching EOL by end of this month. Please review and advise how we should deprecating/remove the following for the next 4.20 release (i.e. compatibility matrix for the future 4.20 release notes): Distros: * EL7 (CentOS 7, RHEL7, https://endoflife.date/centos) * Ubuntu 18.04 (https://endoflife.date/ubuntu) Software requirements: * JRE 11 (Discuss - should we transition to support JRE/JDK 17 or 21, for 4.20? https://endoflife.date/oracle-jdk And are all supported distros have a JRE17/21 package/dependency availalble) * MySQL 5.6, 5.7 (https://endoflife.date/mysql) Hypervisors: * KVM: Ubuntu 18.04 (https://endoflife.date/ubuntu), EL7 (https://endoflife.date/centos) * XenServer All versions except 8.x (retain note that it's not tested, https://www.citrix.com/support/product-lifecycle/legacy-product-matrix.html) * XCP-ng: All versions except 8.2/LTS (https://endoflife.date/xcp-ng) * VMware: 6.5, 6.7 (https://endoflife.date/vcenter) Regards.
