Re: [DISCUSS] Apache CloudStack Quarterly Community Meeting (Virtual)

: dev@cloudstack.apache.org Subject: Re: [DISCUSS] Apache CloudStack Quarterly Community Meeting (Virtual) Great that there is such excitement and interest. I am proposing the following schedule: February May September December I will take the initiative to announce it officially, ensure a place

Re: [DISCUSS] Apache CloudStack Quarterly Community Meeting (Virtual)

Great that there is such excitement and interest. I am proposing the following schedule: February May September December I will take the initiative to announce it officially, ensure a place where we can write the agenda and provide a Zoom link to join. Best regards, On 11 Jan 2025, at 21:5

Re: [DISCUSS] Apache CloudStack Quarterly Community Meeting (Virtual)

Hello all, Great initiative, for sure I'll attend. Best regards, Bernardo De Marco Gonçalves (bernardodemarco).

Re: [DISCUSS] Apache CloudStack Quarterly Community Meeting (Virtual)

Hi Guys, Id also be interested to join the online meet. Its a good alternative for me as im based in southeast asia. Travelling to europe for cloudstack events is difficult and costly. Regards, Bryan Sent with Spark On 10 Jan 2025 at 3:07 PM +0800, pavan aravapalli , wrote: > Hi, > > I am also

Re: [DISCUSS]to disable the agent property setting `reboot.host.and.alert.management.on.heartbeat.timeout` by default

Thanks Slavka, your proposal LGTM. I think the scenario you described deserves a Github issue for fixing when this setting is enabled. Regards, Nicolas Vazquez From: Daan Hoogland Date: Friday, 10 January 2025 at 05:30 To: dev@cloudstack.apache.org Cc: users Subject: Re: [DISCUSS]to

Re: [DISCUSS]to disable the agent property setting `reboot.host.and.alert.management.on.heartbeat.timeout` by default

your proposal seems sensible for the most part Slavka, There is just one concern I have with this Such behaviour can create several problems. If the primary storage is > temporarily not accessible, all hosts could reboot. VMs become dysfunctional if their storage has been inaccessible and become

Re: [DISCUSS] Apache CloudStack Quarterly Community Meeting (Virtual)

Hi, I am also interested and will attend. Thanks & Regards, Pavan. On Fri, 10 Jan 2025 at 05:48, Nux wrote: > Not official anymore, but a few old timers have bouncers parked in > irc.libera.chat/#cloudstack :) > > On 2025-01-09 08:07, Jürgen Gotteswinter wrote: > > Great Idea, will attend for

Re: [DISCUSS] Apache CloudStack Quarterly Community Meeting (Virtual)

Not official anymore, but a few old timers have bouncers parked in irc.libera.chat/#cloudstack :) On 2025-01-09 08:07, Jürgen Gotteswinter wrote: Great Idea, will attend for sure. i would also love to see an IRC channel. But I am old. Am 08.01.25, 13:08 schrieb "Ivet Petrova"

Re: [DISCUSS] Apache CloudStack Quarterly Community Meeting (Virtual)

hey fellow old fellow, There used to be an IRC channel or two. but they were not very busy, as slack is now. I think having more DM channels will water down interaction, so I am not in favor of re-instating or adding channels. Not that I am against this. I am in favour as I am very much in favour

Re: [DISCUSS] Apache CloudStack Quarterly Community Meeting (Virtual)

Great Idea, will attend for sure. i would also love to see an IRC channel. But I am old. Am 08.01.25, 13:08 schrieb "Ivet Petrova" mailto:ivet.petr...@shapeblue.com>>: Hi all, Happy New Year everyone in the community with my best wishes for health and prosperity. During the last CloudStac

Re: [DISCUSS] Deprecate/remove support for EOL distros and hypervisors

ddress this esp. in the release notes for the next major release (4.20 and onwards). Regards. From: João Jandre Paraquetti Sent: Friday, June 21, 2024 21:43 To: us...@cloudstack.apache.org Cc: dev@cloudstack.apache.org Subject: Re: [DISCUSS] Deprecate/rem

Re: [DISCUSS] Deprecate/remove support for EOL distros and hypervisors

lease (4.20 and onwards). Regards. From: João Jandre Paraquetti Sent: Friday, June 21, 2024 21:43 To: us...@cloudstack.apache.org Cc: dev@cloudstack.apache.org Subject: Re: [DISCUSS] Deprecate/remove support for EOL distros and hypervisors I agree with Rohit, EL7 i

Re: [DISCUSS] Deprecate/remove support for EOL distros and hypervisors

Sent: Thursday, June 20, 2024 17:24 To: dev@cloudstack.apache.org Cc: us...@cloudstack.apache.org ; Rohit Yadav Subject: 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

Re: [DISCUSS] Deprecate/remove support for EOL distros and hypervisors

...@cloudstack.apache.org ; Rohit Yadav Subject: 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

Re: [DISCUSS] Deprecate/remove support for EOL distros and hypervisors

x27;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] Depre

Re: [DISCUSS] Deprecate/remove support for EOL distros and hypervisors

_ 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 (genera

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

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

Re: [DISCUSS] Define a release schedule for the project

nice to see this discussion being had again and sorry to be late in replying João, I see no replies have come forward yet. Let's add a new https://github.com/apache/cloudstack/discussions/new/choose for this as well. I still feel my proposal is good and should have been applied. but we can gather

Re: [DISCUSS] New terraform git tag for registry workaround

To: dev Subject: Re: [DISCUSS] New terraform git tag for registry workaround okay, given the situation your proposal seems right Rohit. Like Daan asked, if we can prevent this situation in future we need to document it also. Regards, Harikrishna From: Daan

Re: [DISCUSS] New terraform git tag for registry workaround

cloudstack/cloudstack provider namespace (as the plugin has history/registry even before being donated to the cloudstack project). Regards. From: Harikrishna Patnala Sent: Tuesday, April 16, 2024 11:54 To: dev Subject: Re: [DISCUSS] New terraform git tag

Re: [DISCUSS] New terraform git tag for registry workaround

okay, given the situation your proposal seems right Rohit. Like Daan asked, if we can prevent this situation in future we need to document it also. Regards, Harikrishna From: Daan Hoogland Sent: Monday, April 15, 2024 4:50 PM To: dev Subject: Re: [DISCUSS

Re: [DISCUSS] New terraform git tag for registry workaround

I think your proposals are ok as an ad-hoc solution to the current situation @Rohit Yadav . I wonder how we should deal with this in the future though. 1. As for the numbering, do we have a procedure to prevent this issue in the future? 2. The provider is part of apache and I think the link https:

Re: [DISCUSS] Next cmk release

All, Since we haven't heard of any issue/feature requests and the ones in the current milestone are all done. I'll start a vote on this today. https://github.com/apache/cloudstack-cloudmonkey/milestone/5 Thanks and regards. From: Rohit Yadav Sent: Tuesday,

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

From: Daan Hoogland Sent: Wednesday, February 14, 2024 2:17 PM To: dev@cloudstack.apache.org Subject: Re: [DISCUSS] Closing issues & PR after a certain time i'm a bit -0 on this. I agree that a lot of stale issues deserve closing, but others are really long term goals. I do not want to bl

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

i'm a bit -0 on this. I agree that a lot of stale issues deserve closing, but others are really long term goals. I do not want to block this great idea but am just a bit worried about other great ideas getting lost. So I would propose to tag anything we close or not remove the stale tag, so these c

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

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

Re: [DISCUSS][PROPOSAL] web site publishing procedure

Thanks Daan, LGTM - though, if website isn't going to get too many activity and updates (except for couple of blogs a month), we may simplify publishing from main in future. Regards. From: Daan Hoogland Sent: Thursday, February 8, 2024 17:39 To: dev Cc:

Re: [DISCUSS] log guidelines

Thanks João, On Tue, Dec 5, 2023 at 8:21 PM João Jandre Paraquetti wrote: ... > However, when the error happens because of system degradation, there are > times when having a stacktrace can save hours of debugging, as the error > might be hard to reproduce. Also, if the error is occurring in a

Re: [DISCUSS] Adopting Github Discusssions Users Forum

etermined by >the ASF infra (such as to Gitlab etc). > > >Regards. > > >From: Nux >Sent: Tuesday, November 28, 2023 15:40 >To: dev@cloudstack.apache.org >Cc: Rohit Yadav >Subject: Re: [DISCUSS] Adopting Github Discusssions Users For

Re: [DISCUSS] log guidelines

Hello all, As someone who has worked a lot on logging in this project, I feel like a set of log guidelines are a good addition. I generally agree with Daan's ideas; however, I think that the error level was oversimplified. As Daan already said, there are two main reasons for error logs: "the

Re: [DISCUSS] Adopting Github Discusssions Users Forum

: Rohit Yadav Subject: Re: [DISCUSS] Adopting Github Discusssions Users Forum Personally I'm against that, as it will dilute the community and once the mailing lists will get inactive they'll stay that way. Also github/discussions is a proprietary platform at Microsoft's whim, I think th

Re: [DISCUSS] Adopting Github Discusssions Users Forum

Personally I'm against that, as it will dilute the community and once the mailing lists will get inactive they'll stay that way. Also github/discussions is a proprietary platform at Microsoft's whim, I think this goes against the spirit of the project as free software. That said, I'll be "vot

Re: [DISCUSS] Adopting Github Discusssions Users Forum

Looks pretty good, well organized, and visible, rather email lists! I hope we start seeing more and more there. There might be some users not having a github account, which might not benefit and abstain one day if we decide to fully migrate, but let’s think about that then! Great work and nice

Re: [DISCUSS] Adopting Github Discusssions Users Forum

great On Tue, Nov 28, 2023 at 10:30 AM Rohit Yadav wrote: > > All, > > It's been a while since I had last proposed adopting and trying the Github > Discussions feature for our users community. Since then, the ASF infra seems > to have enabled integration and allowing Discussions integrated with

Re: [DISCUSS] New benchmarking tool

bject: Re: [DISCUSS] New benchmarking tool thanks Rohit, It is a great idea. I have some questions concerning "measuring is influencing" and "prerequisites", but those should not stop us from creating a repo for this in the project great idea, On Thu, Nov 2, 2023 at 9:58 AM

Re: [DISCUSS] New benchmarking tool

thanks Rohit, It is a great idea. I have some questions concerning "measuring is influencing" and "prerequisites", but those should not stop us from creating a repo for this in the project great idea, On Thu, Nov 2, 2023 at 9:58 AM Nux wrote: > Great idea, looking forward to it. > > > On 2023-11

Re: [DISCUSS] New benchmarking tool

Great idea, looking forward to it. On 2023-11-01 16:34, Rohit Yadav wrote: All, I want to kickstart a discussion of developing a new tool - csbench, that can help with generating resource load and measuring the performance and efficiency of Apache CloudStack APIs. Much like cmk, this tool

Re: [DISCUSS] Block importing VMs without NIC

Henrique, Thanks for bringing this up/ I think both disallowing and creating a default nic on importing are acceptable behaviours. One could argue for either and operators will complain either way (I know I probably would ;). I think we can make disallowing the default and if we want to make this l

Re: [DISCUSS] Upgrading Mockito & phasing out powermock

Good work Vishesh! Regards. From: Nicolas Vazquez Sent: Tuesday, September 26, 2023 20:23 To: dev@cloudstack.apache.org Subject: Re: [DISCUSS] Upgrading Mockito & phasing out powermock Great work Vishesh, thanks! Regards, Nicolas Vazquez From:

Re: [DISCUSS] Upgrading Mockito & phasing out powermock

Great work Vishesh, thanks! Regards, Nicolas Vazquez From: Daan Hoogland Date: Tuesday, 26 September 2023 at 11:15 To: dev@cloudstack.apache.org Subject: Re: [DISCUSS] Upgrading Mockito & phasing out powermock great, thanks you for your persistence and effort in general. On Tue, Sep 26,

Re: [DISCUSS] Upgrading Mockito & phasing out powermock

Regards, > Vishesh > > > From: Kishan Kavala > Sent: Friday, June 9, 2023 1:30 PM > To: dev@cloudstack.apache.org > Subject: RE: [DISCUSS] Upgrading Mockito & phasing out powermock > > +1 > Agree with the approach, Vishesh. > > >

Re: [DISCUSS] Upgrading Mockito & phasing out powermock

> From: Kishan Kavala > Sent: Friday, June 9, 2023 1:30 PM > To: dev@cloudstack.apache.org > Subject: RE: [DISCUSS] Upgrading Mockito & phasing out powermock > > +1 > Agree with the approach, Vishesh. > > > > > > > > -Origin

Re: [DISCUSS] Upgrading Mockito & phasing out powermock

: [DISCUSS] Upgrading Mockito & phasing out powermock +1 Agree with the approach, Vishesh. -Original Message- From: Wei ZHOU Sent: Tuesday, June 6, 2023 8:11 PM To: dev@cloudstack.apache.org Subject: Re: [DISCUSS] Upgrading Mockito & phasing out powermock lgtm. go ahead Vishes

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

..@cloudstack.apache.org>>; Marketing mailto:market...@shapeblue.com>> 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,

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

m>> > Sent: Wednesday, August 30, 2023 19:04 > To: Giles Sirett > mailto:giles.sir...@shapeblue.com>> > Cc: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org> > mailto:dev@cloudstack.apache.org>>; > us...@cloudstack.apache.org<mailto:us...@cloudstack.apa

Re: [DISCUSS] Fixing npm version for building UI

Hello guys, I think Rohit meant to upgrade the Node version to v18, as NPM is only the package manager and its latest release is 10.0. Currently, we do not enforce either Node or NPM version in the building; therefore, one can use newer Node versions rather than v14. The problem faced by Roh

Re: [DISCUSS] Fixing npm version for building UI

Hey Rohit, guess this is not a hot topic, but i'm +1 on this. with 4.18 out I think now is a good time. On Thu, Aug 10, 2023 at 10:53 AM Rohit Yadav wrote: > All, > > Our UI building in packages/PRs uses npm v14, while the current LTS > version is v18. However, since we use npm for only developm

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

to do. It's a great improvement over what we currently have. Wido Regards. From: Ivet Petrova Sent: Wednesday, August 30, 2023 19:04 To: Giles Sirett Cc: dev@cloudstack.apache.org ; us...@cloudstack.apache.org ; Marketing Subject: Re: [DISCUSS] New

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

Hi Ivet, +1 for the design. Looks very good. From my side please step forward. Looks Good work! Cheers > On 1. Sep 2023, at 15:14, Simon Weller wrote: > > It looks great, Ivet. Nice work! > >> On Wed, Aug 30, 2023 at 8:35 AM Ivet Petrova >> wrote: >> >> Hi All, >> >> I uploaded the

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

Looks great Ivet! Looking forward to seeing it in action! Regards, Nicolas Vazquez From: Nux Date: Friday, 1 September 2023 at 11:01 To: us...@cloudstack.apache.org Cc: Giles Sirett , dev@cloudstack.apache.org , Marketing Subject: Re: [DISCUSS] New Design for the Apache CloudStack Website

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

Hi Ivet, Looks nice and trendy, thanks for the effort! Regards On 2023-08-30 14:34, Ivet Petrova wrote: 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:g

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

It looks great, Ivet. Nice work! On Wed, Aug 30, 2023 at 8:35 AM Ivet Petrova wrote: > 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 giles.sir...@s

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

...@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

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

; 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:gile

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

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

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 From: Ivet Petrova Sent: Wednesday, August 30, 2023 10:14 AM To: us...@cloudstack.apache.org; Marketing Cc: dev Subject: [DISCUSS] New Design for

Re: [DISCUSS] Simplifying constructs and UX

Rohit, I either agree or have no strong opinion on points 2 through 6, but I do not think point 1 is a good idea. Users in some cases rely heavily on projects and/or sharing domains and accounts. The two constructs both have earned their right to existence in production environments. €0,02 On Mon

Re: [DISCUSS] Simplifying constructs and UX

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

RE: [DISCUSS] Upgrading Mockito & phasing out powermock

+1 Agree with the approach, Vishesh. -Original Message- From: Wei ZHOU Sent: Tuesday, June 6, 2023 8:11 PM To: dev@cloudstack.apache.org Subject: Re: [DISCUSS] Upgrading Mockito & phasing out powermock lgtm. go ahead Vishesh. -Wei On Tue, 6 Jun 2023 at 14:17, Vishesh Ji

Re: [DISCUSS] Upgrading Mockito & phasing out powermock

lgtm. go ahead Vishesh. -Wei On Tue, 6 Jun 2023 at 14:17, Vishesh Jindal wrote: > Hi all, > > I am working on upgrading Mockito's version & phasing out powermock. For > new maven modules, I would request all to use Mockito's mockStatic instead > of Powermock. > > Why? > Powermock's last releas

Re: [DISCUSS] Upgrading Mockito & phasing out powermock

, June 6, 2023 18:18 To: dev@cloudstack.apache.org Subject: Re: [DISCUSS] Upgrading Mockito & phasing out powermock I like your approach Vishesh +1 from me On Tue, Jun 6, 2023 at 2:18 PM Vishesh Jindal wrote: > > Hi all, > > I am working on upgrading Mockito's version & p

Re: [DISCUSS] Upgrading Mockito & phasing out powermock

I like your approach Vishesh +1 from me On Tue, Jun 6, 2023 at 2:18 PM Vishesh Jindal wrote: > > Hi all, > > I am working on upgrading Mockito's version & phasing out powermock. For new > maven modules, I would request all to use Mockito's mockStatic instead of > Powermock. > > Why? > Powermock

Re: [DISCUSS] CloudStack Website build and modernisation

, May 3, 2023 21:34 To: us...@cloudstack.apache.org ; dev@cloudstack.apache.org Cc: priv...@cloudstack.apache.org Subject: Re: [DISCUSS] CloudStack Website build and modernisation Ivet, All, Thanks for reporting and suggesting. The mailing list strips off attachments/images, may I ask to report

Re: [DISCUSS] CloudStack Website build and modernisation

ted deadline is 31st May '23. Regards. From: Ivet Petrova Sent: Wednesday, May 3, 2023 18:09 To: us...@cloudstack.apache.org Cc: dev@cloudstack.apache.org ; priv...@cloudstack.apache.org Subject: Re: [DISCUSS] CloudStack Website build and modernisation

Re: [DISCUSS] CloudStack Website build and modernisation

, May 3, 2023 15:53 To: us...@cloudstack.apache.org Cc: dev@cloudstack.apache.org ; priv...@cloudstack.apache.org Subject: Re: [DISCUSS] CloudStack Website build and modernisation Hi, Wouldn’t it be better to have a nice header banner as a background image on the home page instead of just the logo? We have the l

Re: [DISCUSS] CloudStack Website build and modernisation

dev@cloudstack.apache.org Subject: Re: [DISCUSS] CloudStack Website build and modernisation Thanks for the feedback Ivet but I don’t see the images in your mail. Could you forward your mail to me or open an issue on the apache/cloudstack repo. The system we’re using and the design/theme that you

Re: [DISCUSS] CloudStack Website build and modernisation

2023 10:11:45 PM To: priv...@cloudstack.apache.org Cc: dev@cloudstack.apache.org Subject: Re: [DISCUSS] CloudStack Website build and modernisation Hi Rohit, Thanks for doing the heavy lifting. Great that we have the most important things migrated. Now it is time for some polishing on top according to me. I w

Re: [DISCUSS] CloudStack Website build and modernisation

k.apache.org> mailto:priv...@cloudstack.apache.org>> Subject: Re: [DISCUSS] CloudStack Website build and modernisation All, The ASF infra has advised recently that they're deprecating and removing Roller support, our project blog is based on Roller. Given this hasn't receive

Re: [DISCUSS] CloudStack Website build and modernisation

gt; > > > Regards. > > > From: Suresh Kumar Anaparti > Sent: Tuesday, May 2, 2023 13:12 > To: dev@cloudstack.apache.org > Cc: priv...@cloudstack.apache.org ; > us...@cloudstack.apache.org > Subject: Re: [DISCUSS] CloudStack Website build and modernisation &g

Re: [DISCUSS] CloudStack Website build and modernisation

priv...@cloudstack.apache.org ; us...@cloudstack.apache.org Subject: Re: [DISCUSS] CloudStack Website build and modernisation Nice to see new website Rohit! My first look feedback => - May be, keeping the CloudStack description centered without logo would look better. - Logo on the top-left corner seems smaller

Re: [DISCUSS] CloudStack Website build and modernisation

27;ve ported most of the content from > the old website and blog to this PoC. Thanks. > > > Regards. > > > From: Rohit Yadav > Sent: Monday, May 1, 2023 11:24 > To: dev@cloudstack.apache.org > Cc: priv...@cloudstack.apache.org

Re: [DISCUSS] CloudStack Website build and modernisation

gards. From: Rohit Yadav Sent: Monday, May 1, 2023 11:24 To: dev@cloudstack.apache.org Cc: priv...@cloudstack.apache.org Subject: Re: [DISCUSS] CloudStack Website build and modernisation All, The ASF infra has advised deprecating and removing Roller support by 31st May 2023

Re: [DISCUSS] CloudStack Website build and modernisation

ack.apache.org Cc: priv...@cloudstack.apache.org Subject: Re: [DISCUSS] CloudStack Website build and modernisation All, The ASF infra has advised recently that they're deprecating and removing Roller support, our project blog is based on Roller. Given this hasn't received any objections on this thread, I&#

Re: [DISCUSS] CloudStack Website build and modernisation

All, The ASF infra has advised recently that they're deprecating and removing Roller support, our project blog is based on Roller. Given this hasn't received any objections on this thread, I've spent some time in the last two months exploring options that solve most of our website and blog req

Re: [DISCUSS][PROPOSAL][4.19] remove juniper plugins F5 and SRX

lugin is already removed from the build > system. Nevertheless, if there are no objections then you may execute your > proposal as the RM. > > > Regards. > > > From: Daan Hoogland > Sent: Thursday, December 29, 2022 22:03 > To: dev@clo

Re: [DISCUSS][PROPOSAL][4.19] remove juniper plugins F5 and SRX

From: Daan Hoogland Sent: Thursday, December 29, 2022 22:03 To: dev@cloudstack.apache.org Cc: users Subject: Re: [DISCUSS][PROPOSAL][4.19] remove juniper plugins F5 and SRX the plugin is already removed in the latest release, so I think this is a special case Rohit. It makes no sense to start d

Re: [DISCUSS][PROPOSAL][4.19] remove juniper plugins F5 and SRX

the plugin is already removed in the latest release, so I think this is a special case Rohit. It makes no sense to start deprecating now, it has been dysfunctional for more than half a year already. My proposal is to remove the code in 4.18, as the plugin is effectively already removed. On Thu, De

Re: [DISCUSS][PROPOSAL][4.19] remove juniper plugins F5 and SRX

We've done this in the past which usually would be to deprecate the component in a release and then remove that in subsequent releases, to not surprise our users to give enough time for the community to object or respond. I think we can start by deprecating them in 4.18, i.e. put in the release

RE: [DISCUSS] Github Discussions for CloudStack?

ly so that we can ensure that we support users as best we can. Kind Regards Paul Angus -Original Message- From: Rohit Yadav Sent: Monday, December 19, 2022 4:16 PM To: dev@cloudstack.apache.org; us...@cloudstack.apache.org Subject: Re: [DISCUSS] Github Discussions for CloudStack? U

Re: [DISCUSS] Github Discussions for CloudStack?

ps://www.apache.org/foundation/mailinglists.html Regards. From: Paul Angus Sent: Sunday, December 18, 2022 18:45 To: dev@cloudstack.apache.org ; us...@cloudstack.apache.org Subject: RE: [DISCUSS] Github Discussions for CloudStack? If this makes discussions more access

RE: [DISCUSS] Github Discussions for CloudStack?

ember 15, 2022 3:21 AM To: dev@cloudstack.apache.org; us...@cloudstack.apache.org Subject: Re: [DISCUSS] Github Discussions for CloudStack? Sounds like a good idea +1 for giving it a try! From: Rohit Yadav Sent: Wednesday, December 14, 2022 2:37 PM To: dev@cl

Re: [DISCUSS] Github Discussions for CloudStack?

Sounds like a good idea +1 for giving it a try! From: Rohit Yadav Sent: Wednesday, December 14, 2022 2:37 PM To: dev@cloudstack.apache.org ; us...@cloudstack.apache.org Subject: [DISCUSS] Github Discussions for CloudStack? All, In the past, we had moved away fr

Re: [DISCUSS] Github Discussions for CloudStack?

x27;m not suggesting we stop using mailing lists). Regards. From: Nux Sent: Wednesday, December 14, 2022 19:26 To: dev@cloudstack.apache.org Cc: Daniel Augusto Veronezi Salvador Subject: Re: [DISCUSS] Github Discussions for CloudStack? That's a good point,

Re: [DISCUSS] Github Discussions for CloudStack?

That's a good point, it'd be nice if there was a possibility to use the "discussions" integrated in the mailing lists. --- Nux www.nux.ro On 2022-12-14 12:22, Daniel Augusto Veronezi Salvador wrote: Hello all, The feature GitHub Discussions seems very interesting; I think it worth enabling it

Re: [DISCUSS] Github Discussions for CloudStack?

Hi Rohit, Will this be instead the mailing lists? Or an addition to them? Kind regards, On 14 Dec 2022, at 11:07, Rohit Yadav mailto:rohit.ya...@shapeblue.com>> wrote: All, In the past, we had moved away from JIRA and ReviewBoard to Github as it provided a single platform for both the u

Re: [DISCUSS] Github Discussions for CloudStack?

+1 Regards, Nicolas Vazquez From: Rohit Yadav Date: Wednesday, 14 December 2022 at 06:08 To: dev@cloudstack.apache.org , us...@cloudstack.apache.org Subject: [DISCUSS] Github Discussions for CloudStack? All, In the past, we had moved away from JIRA and ReviewBoard to Github as it provided a

Re: [DISCUSS] Github Discussions for CloudStack?

Hello all, The feature GitHub Discussions seems very interesting; I think it worth enabling it and trying it (+1). I just have one doubt: would we forward Discussions' updates to the mailing lists? Best regards, Daniel Salvador (gutoveronezi) On 14/12/2022 06:07, Rohit Yadav wrote: All,

Re: [DISCUSS] Github Discussions for CloudStack?

+1 good idea. -Wei On Wed, 14 Dec 2022 at 10:08, Rohit Yadav wrote: > All, > > In the past, we had moved away from JIRA and ReviewBoard to Github as it > provided a single platform for both the user and the dev community to > collaborate on issues/requests and code changes (pull requests). We

Re: [DISCUSS] ACS 4.17.2.0 release

Regards. From: Rohit Yadav Sent: Monday, November 28, 2022 20:40 To: us...@cloudstack.apache.org Cc: dev@cloudstack.apache.org Subject: Re: [DISCUSS] ACS 4.17.2.0 release Thanks Nicolas, Daan. Currently, the list is just three issues in this milestone: https://github.

Re: [DISCUSS] ACS 4.17.2.0 release

e.org Subject: Re: [DISCUSS] ACS 4.17.2.0 release Rohit, sorry for the late answer. I would agree to do that. Is the list already established or do we need to do more work for that? On Mon, Nov 28, 2022 at 11:41 AM Nicolas Vazquez < nicolas.vazq...@shapeblue.com> wrote: > Thanks Rohit, +

Re: [DISCUSS] ACS 4.17.2.0 release

Rohit, sorry for the late answer. I would agree to do that. Is the list already established or do we need to do more work for that? On Mon, Nov 28, 2022 at 11:41 AM Nicolas Vazquez < nicolas.vazq...@shapeblue.com> wrote: > Thanks Rohit, +1 on the short 4.17.2.0 release approach > > Regards, > Nic

Re: [DISCUSS] ACS 4.17.2.0 release

Thanks Rohit, +1 on the short 4.17.2.0 release approach Regards, Nicolas Vazquez From: Rohit Yadav Date: Thursday, 24 November 2022 at 11:24 To: dev@cloudstack.apache.org Cc: us...@cloudstack.apache.org Subject: [DISCUSS] ACS 4.17.2.0 release All, Based on our 4.18 RM's proposed release sche

Re: [DISCUSS] release and release manager 4.18

requirements to cut multiple RCs) > > [1] https://cloudstack.apache.org/who.html > > > Regards. > > > > > > From: Sina Kashipazha > Sent: Wednesday, September 21, 2022 03:11 > To: us...@cloudstack.apache.org; daan.hoogl...@gmail.com > Cc: dev > Subject: Re: [DISCUSS] re

Re: [DISCUSS] release and release manager 4.18

To: us...@cloudstack.apache.org; daan.hoogl...@gmail.com Cc: dev Subject: Re: [DISCUSS] release and release manager 4.18 Sorry to interrupt. I'm curious to know how is the release procedure. Is it possible for me to help or should I be a PMC member? --- Original Message --- On Tuesday, Sep

Re: [DISCUSS] release and release manager 4.18

t; wrote: > > > > > > > > +1 to Daan :-) > > > > From: Rohit Yadav rohit.ya...@shapeblue.com > > > > Sent: Tuesday, September 20, 2022 9:43 AM > > To: us...@cloudstack.apache.org us...@cloudstack.apache.org; dev

Re: [DISCUSS] release and release manager 4.18

__ > From: Rohit Yadav rohit.ya...@shapeblue.com > > Sent: Tuesday, September 20, 2022 9:43 AM > To: us...@cloudstack.apache.org us...@cloudstack.apache.org; dev > dev@cloudstack.apache.org > > Subject: Re: [DISCUSS] release and release manager 4.18 > > EXTERNAL E

Re: [DISCUSS] release and release manager 4.18

+1 to Daan :-) From: Rohit Yadav Sent: Tuesday, September 20, 2022 9:43 AM To: us...@cloudstack.apache.org ; dev Subject: Re: [DISCUSS] release and release manager 4.18 EXTERNAL EMAIL: This message originated outside of ENA. Use caution when clicking links

Re: [DISCUSS] release and release manager 4.18

+1 thanks for volunteering as 4.18 RM Daan. Regards. Regards. From: Daan Hoogland Sent: Tuesday, September 20, 2022 7:53:53 PM To: dev ; users Subject: [DISCUSS] release and release manager 4.18 Hello everybody, As Abhishek is wrapping up the 4.17.1 release. I´

Re: [DISCUSS] Community CI/CD/Triage Bot

* Explore triaging of Github issues (labels, milestone, assignees etc) [1] https://github.com/apache/cloudstack/tree/main/.github/workflows Regards. From: Rohit Yadav Sent: Monday, April 18, 2022 16:12 To: dev@cloudstack.apache.org Subject: Re: [DISCUSS] Community

  1   2   3   4   5   6   7   8   9   10   >