Re: CentOS 7 is reaching EOL

[Nux]

Yes, I understood, that's what I was addressing. :)

On 2024-01-23 23:03, Wei ZHOU wrote:

Hi Lucian,

I think what Vishesh meant is removing the support of CentOS 7 as a
management server or kvm host.

-Wei

On Tue, 23 Jan 2024 at 22:07, Nux  wrote:

I would not be so hasty. I am sure there are still CentOS 5 instances 
in
existence somewhere, similarly I think CentOS 7 will not go down 
without

a fight.
I'm not saying to never kill support for it, but I'd leave it maybe 
1-2

more releases. Corporate users especially will take a lot of time to
move...

/imho

On 2024-01-23 16:27, Vishesh Jindal wrote:
> Hi all
>
> While working on a PR[1] to upgrade JRE, I noticed that CentOS 7 is
> reaching end of life on 30 June, 2024 [2].
>
> Should we remove support for CentOS 7 after 4.19 is released? Because
> by the time 4.20 is out, CentOS 7 would already have reached its EOL
> and IMO it doesn't make sense to maintain support for it.
>
> Regards,
> Vishesh
>
>
> Ref:
> [1] https://github.com/apache/cloudstack/pull/8438
> [2] https://www.redhat.com/en/topics/linux/centos-linux-eol

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

[Wei ZHOU]

Yes, the ubuntu version naming is the best in my opinion.
Other than the version naming, we need to decide the frequency of major
releases and minor releases, which version will be LTS, how long the
LTS/normal version will be supported, etc.

Maybe a vote in the dev/users/pmc mailing list?



在 2024年1月23日星期二，Nicolas Vazquez  写道：

> I like this idea as well, even if its .MM or YY.MM.
>
> Would we want to define delivery months for releases similar to Ubuntu .04
> and .10?
>
> Regards,
> Nicolas Vazquez
> 
> From: Nux 
> Sent: Tuesday, January 23, 2024 6:11 PM
> To: dev@cloudstack.apache.org 
> Cc: Wei ZHOU 
> Subject: Re: [PROPOSAL] version naming : drop the 4.
>
> An interesting proposition, I like it.
> It would also relieve us from having to come up with any over-the-top
> feature or change for a major version change.
>
> On 2024-01-23 14:49, Wido den Hollander wrote:
> > We could look at Ubuntu, and other projects, and call it 2025.01 if we
> > release it in Jan 2025.
> >
> > A great post on the website, mailinglists and social media could
> > explain the change in versioning, but that the code doesn't change that
> > much.
> >
> > Project has matured, etc, etc.
>
>
>
>

Re: CentOS 7 is reaching EOL

[Wei ZHOU]

Hi Lucian,

I think what Vishesh meant is removing the support of CentOS 7 as a
management server or kvm host.

-Wei

On Tue, 23 Jan 2024 at 22:07, Nux  wrote:

> I would not be so hasty. I am sure there are still CentOS 5 instances in
> existence somewhere, similarly I think CentOS 7 will not go down without
> a fight.
> I'm not saying to never kill support for it, but I'd leave it maybe 1-2
> more releases. Corporate users especially will take a lot of time to
> move...
>
> /imho
>
> On 2024-01-23 16:27, Vishesh Jindal wrote:
> > Hi all
> >
> > While working on a PR[1] to upgrade JRE, I noticed that CentOS 7 is
> > reaching end of life on 30 June, 2024 [2].
> >
> > Should we remove support for CentOS 7 after 4.19 is released? Because
> > by the time 4.20 is out, CentOS 7 would already have reached its EOL
> > and IMO it doesn't make sense to maintain support for it.
> >
> > Regards,
> > Vishesh
> >
> >
> > Ref:
> > [1] https://github.com/apache/cloudstack/pull/8438
> > [2] https://www.redhat.com/en/topics/linux/centos-linux-eol
>

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

[Nicolas Vazquez]

I like this idea as well, even if its .MM or YY.MM.

Would we want to define delivery months for releases similar to Ubuntu .04 and 
.10?

Regards,
Nicolas Vazquez

From: Nux 
Sent: Tuesday, January 23, 2024 6:11 PM
To: dev@cloudstack.apache.org 
Cc: Wei ZHOU 
Subject: Re: [PROPOSAL] version naming : drop the 4.

An interesting proposition, I like it.
It would also relieve us from having to come up with any over-the-top
feature or change for a major version change.

On 2024-01-23 14:49, Wido den Hollander wrote:
> We could look at Ubuntu, and other projects, and call it 2025.01 if we
> release it in Jan 2025.
>
> A great post on the website, mailinglists and social media could
> explain the change in versioning, but that the code doesn't change that
> much.
>
> Project has matured, etc, etc.

 

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

[Nux]

An interesting proposition, I like it.
It would also relieve us from having to come up with any over-the-top 
feature or change for a major version change.


On 2024-01-23 14:49, Wido den Hollander wrote:
We could look at Ubuntu, and other projects, and call it 2025.01 if we 
release it in Jan 2025.


A great post on the website, mailinglists and social media could 
explain the change in versioning, but that the code doesn't change that 
much.


Project has matured, etc, etc.

Re: CentOS 7 is reaching EOL

[Nux]

I would not be so hasty. I am sure there are still CentOS 5 instances in 
existence somewhere, similarly I think CentOS 7 will not go down without 
a fight.
I'm not saying to never kill support for it, but I'd leave it maybe 1-2 
more releases. Corporate users especially will take a lot of time to 
move...


/imho

On 2024-01-23 16:27, Vishesh Jindal wrote:

Hi all

While working on a PR[1] to upgrade JRE, I noticed that CentOS 7 is 
reaching end of life on 30 June, 2024 [2].


Should we remove support for CentOS 7 after 4.19 is released? Because 
by the time 4.20 is out, CentOS 7 would already have reached its EOL 
and IMO it doesn't make sense to maintain support for it.


Regards,
Vishesh


Ref:
[1] https://github.com/apache/cloudstack/pull/8438
[2] https://www.redhat.com/en/topics/linux/centos-linux-eol

[PR] Fixup drs docs [cloudstack-documentation]

[via GitHub]

vishesh92 opened a new pull request, #376:
URL: https://github.com/apache/cloudstack-documentation/pull/376

   cc: @andrijapanicsb 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

CentOS 7 is reaching EOL

[Vishesh Jindal]

Hi all

While working on a PR[1] to upgrade JRE, I noticed that CentOS 7 is reaching 
end of life on 30 June, 2024 [2].

Should we remove support for CentOS 7 after 4.19 is released? Because by the 
time 4.20 is out, CentOS 7 would already have reached its EOL and IMO it 
doesn't make sense to maintain support for it.

Regards,
Vishesh


Ref:
[1] https://github.com/apache/cloudstack/pull/8438
[2] https://www.redhat.com/en/topics/linux/centos-linux-eol

 

Re: Apache CloudStack and Ceph Day - February 22, Amsterdam

[Ruben Bosch]

Looking forward to it! See you there.

On Fri, Jan 19, 2024 at 3:03 PM Daan Hoogland 
wrote:

> I live in his backyard, will there as well.
>
> On Tue, Jan 9, 2024 at 3:58 PM Wido den Hollander
>  wrote:
> >
> >
> >
> > Op 09/01/2024 om 13:45 schreef Ivet Petrova:
> > > Dear community members,
> > >
> > > We managed to finalised the date for our joint event with the Ceph
> community.
> > > I am happy to share that we are doing it on February 22nd, in
> Amsterdam, Netherlands.
> > > The event will be hosted by Adyen, the address is: Rokin 49, 1012 KK
> Amsterdam, The Netherlands
> > >
> > > Two things at this stage:
> > >
> > > 1. We still have a few speaking slots free (actually 2 slots only). If
> you are interested to present at the event, please submit your talk
> proposal now.
> > > https://forms.gle/TnBfxS2cKWfe28CS6
> > >
> > > 2. We would be happy if we can see more people from the community, so
> register as an attendee here:
> > >
> https://www.eventbrite.nl/e/cloudstack-and-ceph-day-netherlands-2024-tickets-700177167757
> > >
> > > Look forward to meeting you in Amsterdam!
> >
> > Yes! That's like my backyard. I'll be there!
> >
> > Wido
> >
> > >
> > > Best regards,
> > >
> > >
> > >
> > >
> > >
>
>
>
> --
> Daan
>

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

[Wido den Hollander]

Op 22/01/2024 om 12:17 schreef Wei ZHOU:

+1 with 20.0

5.0 sounds like a leap with lots of significant changes. Unfortunately it
has not been discussed what needs to be done.
20.0 (or 24.0) looks better.



We could look at Ubuntu, and other projects, and call it 2025.01 if we 
release it in Jan 2025.


A great post on the website, mailinglists and social media could explain 
the change in versioning, but that the code doesn't change that much.


Project has matured, etc, etc.

Wido


Wei

On Mon, 22 Jan 2024 at 12:01, Daan Hoogland  wrote:


João,
I think we should not consider 5.0, but go to 20,0 that is more in
line with what we've actually been doing (semantic versioning from the
second digit)

On Mon, Jan 22, 2024 at 11:53 AM Nux  wrote:


LGTM!

On 2024-01-19 19:19, João Jandre Paraquetti wrote:

Hi all,

I agree that our current versioning schema doesn't make much sense, as
"minors" introduce pretty big features; even backward incompatibilities
are introduced in minor versions sometimes.

As the current plan is to have 4.20 by June, I think we should stick to
it and still have the next "minor", and make it the last minor version
of the major 4. After so much time in the same major version, we should
plan something relevant before changing it, and June 2024 is a bit of a
tight schedule for that.

I think that we should plan to move to version 5.0.0, we could set the
release date to the end of 2024 or the start (January) of 2025; by
doing that, we have plenty of time for planning and developing amazing
features for version 5, while also preparing a cleanup of our current
APIs. For instance, we are working on the following major developments:
KVM differential snapshots/backups without needing extra software;
theme management system (white label portal for ACS); native
snapshot/backup for VMware (without needing Veeam) to make it similar
to what ACS does with XenServer and KVM; Operators backup (which are
different from end-user backups); and many other items.

What do you guys think?

Best regards,
João Jandre.

On 1/19/24 10:39, Daan Hoogland wrote:

devs, PMC,

as we are closing in on 4.19 I want to propose that we drop the 4. in
our versioning scheme. We've been discussing 5 but no real initiatives
have been taken. Nowadays big features go into our "minor"
dot-releases. In my opinion this warrants promoting those version to
the status of major and dropping the 4..

technically this won't be an issue as 20 > 4 and out upgrade scheme
supports a step like that.

any thoughts?





--
Daan

Re: [VOTE] Apache CloudStack 4.19.0.0 RC3

[Rohit Yadav]

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


Regards.


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

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

Hi all,

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

Regards,
Abhishek


 

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

> Hi All,
>
> I've created a 4.19.0.0 release (RC3), with the following artifacts up for
> a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/tree/4.19.0.0-RC20240122T1028
> Commit: 43066e4020cf48108e6d0bb125be7d24fc2d609f
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.19.0.0/
>
> PGP release keys (signed using 65518106473A09D7AF26B384A70BD2EAA74E2866):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> For testing purposes, I have uploaded the different distro packages to:
> http://download.cloudstack.org/testing/4.19.0.0-RC3/
>
> Since 4.16 the system VM template registration is no longer mandatory
> before upgrading, however, it can be downloaded from here if needed:
> https://download.cloudstack.org/systemvm/4.19/
>
> The vote will be open for 72 hours.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Regards,
> Abhishek
>

Re: [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
>

Re: new website design

[Rohit Yadav]

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

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

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

versus

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

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

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

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

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



Regards.


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

+1 looks nice

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



+1 - do it.

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

 

Re: Setup Linstor Plugin for ACS

[Rohit Yadav]

Hi,

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

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


Regards.


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

Hello community!

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

Also please share any technical details for setup it.

--

*Thanks & Regards.*

*Support Admin*



*Facebook  | Twitter
 | YouTube
 | LinkedIn
*

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

Dhaka-1217, Bangladesh

*Mob :* +88 01716915504

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

*Web :* www.technologyrss.com