: 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
LS,
Github are outfasing their old template mechs for new issues. Please have a
look as https://github.com/apache/cloudstack/pull/10186 .
I propose a new set of templates, in that PR. Please comment or suggest
changes.
regards,
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
Hello all,
Great initiative, for sure I'll attend.
Best regards,
Bernardo De Marco Gonçalves (bernardodemarco).
gt; >
> > >
> > > Hi all,
> > >
> > >
> > > Happy New Year everyone in the community with my best wishes for health
> > > and prosperity.
> > >
> > >
> > > During the last CloudStack Collaboration Conference in Madr
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
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
t; > Happy New Year everyone in the community with my best wishes for health
> > and prosperity.
> >
> >
> > During the last CloudStack Collaboration Conference in Madrid, an idea
> > came up that I’d like to discuss with you. Many community members
> > expressed the need for mor
Hello everyone,
I would like to open a discussion to change the default value of the agent
property `reboot.host.and.alert.management.on.heartbeat.timeout` to false.
The default behaviour of the kvm agent is to check the storage heartbeat
and, if it timeouts, to check the
`reboot.host.and.alert.m
trova" <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 CloudStack Collaboration Conference in Madrid, an idea
came up that I’d like to discuss with you. Many community members
expresse
of Ivet's
initiative.
Let's gather subjects to discuss in this thread and add them somewhere on
a wiki:
- next ccc (I bet Ivet wants this one)
- user management
- GPU orchestration design
- ...
just a bunch of ideas, I am sure you all can do better ;)
On Thu, Jan 9, 2025 at 9:07
During the last CloudStack Collaboration Conference in Madrid, an idea came up
that I’d like to discuss with you. Many community members expressed the need
for more opportunities to connect, collaborate, and exchange ideas beyond the
events and mails. It’s clear that we value the power of working tog
Hi all,
Happy New Year everyone in the community with my best wishes for health and
prosperity.
During the last CloudStack Collaboration Conference in Madrid, an idea came up
that I’d like to discuss with you. Many community members expressed the need
for more opportunities to connect
: dev@cloudstack.apache.org
Subject: Re: [PROPOSE][DISCUSS] CloudStack Installer
Thanks all, as no objections were raised I’ll proceed by creating a new
sub-project repository.
Once the initial installation script is pushed, everyone is welcome to submit
PRs and suggest changes through Github issues.
As pro
Same, +1
On 23 December 2024 09:19:57 CET, Daan Hoogland wrote:
>nothing to add. I'd +1 this if it comes to a vote.
>
>On Mon, Dec 23, 2024 at 6:20 AM Rohit Yadav wrote:
>
>> All,
>>
>> Following the CCC2024 hackathon idea of CloudStack script-based
>> installer [1], I want to propose a new repo
but
offer our users an alternative installation option that they're already
familiar with.
Regards.
Regards.
From: Rene Moser
Sent: Monday, December 23, 2024 6:22:33 PM
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSE][DISCUSS] CloudStack Installer
hi everyone
I don't have a strong opinion, VOTE 0
Nevertheless, a few comments:
1. pipe bash installers from a third party somewhere on the internet was
popular but not really a good practice. Should be "support" this kind of
insecure practice?
2. For testing, it would be fine. But the scop
Op 23/12/2024 om 06:19 schreef Rohit Yadav:
All,
Following the CCC2024 hackathon idea of CloudStack script-based
installer [1], I want to propose a new repository to host this as a
sub-project under the ASF/CloudStack PMC. The script-based installer
will make it easier for anybody to try Clou
Same here. Sounds great.
-Original Message-
From: Daan Hoogland
Sent: 23 December 2024 00:20
To: dev@cloudstack.apache.org
Cc:
Subject: Re: [PROPOSE][DISCUSS] CloudStack Installer
nothing to add. I'd +1 this if it comes to a vote.
On Mon, Dec 23, 2024 at 6:20 AM Rohit
nothing to add. I'd +1 this if it comes to a vote.
On Mon, Dec 23, 2024 at 6:20 AM Rohit Yadav wrote:
> All,
>
> Following the CCC2024 hackathon idea of CloudStack script-based
> installer [1], I want to propose a new repository to host this as a
> sub-project under the ASF/CloudStack PMC. The s
All,
Following the CCC2024 hackathon idea of CloudStack script-based
installer [1], I want to propose a new repository to host this as a
sub-project under the ASF/CloudStack PMC. The script-based installer
will make it easier for anybody to try CloudStack on one of the
supported Linux distros (suc
: Re: [DISCUSS] Deprecate/remove support for EOL distros and hypervisors
All,
Thank you for your comments and participation. I sense we're largely in
agreement and logistically it wouldn't be possible to support EL7 now (reached
vendor EOL yesterday), let's try and get the related PRs a
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
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
...@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
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
_
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
tion
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
hy
rg
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
. 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
dev ; users
Subject: [REVIVE][DISCUSS] Closing issues & PR after a certain time
People,
I want to revive this discussion and bring Vishesh' PR under your
attention again.
The discussion there is mostly about the length of the period before closing.
So here I am going to state 1year - fi
ed, we can always remove the
> action if it doesn't work out. And if a PR/issue gets closed, we can always
> reopen it.
>
>
>
>
> From: Daan Hoogland
> Sent: Wednesday, February 14, 2024 2:17 PM
> To: dev@cloudstack.apache.org
>
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
: [DISCUSS] New terraform git tag for registry workaround
All,
I got the following from TF support:
Hello there, provider versions are immutable in the registry. Therefore, when
you deleted and recreated the version in Github, the hash has changed, and the
registry will refuse to serve it. Your
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
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
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:
All,
The recent Terraform provider release v0.5.0 has a problem with the Terraform
registry website.
https://github.com/apache/cloudstack-terraform-provider/issues/109
The registry support isn't able to provide a resolution now, their manual
resync button on the provider isn't fixing the issue
t: Tuesday, January 30, 2024 15:06
To: dev@cloudstack.apache.org ;
us...@cloudstack.apache.org
Subject: [DISCUSS] Next cmk release
All,
Anybody have any feature/improvements requests and bugs to report for the next
cmk release? (RM/release timeline yet to be discussed/determined).
Please add
Hi all,
I had posted this message on another thread, but following Rohit's
advice I've decided to create a new one for it. That being said, I have
another proposal for the versioning scheme. Instead of dropping the "X"
on our X.Y.Z.N, we can set a fixed schedule (that can be further
discussed
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
ing 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 no
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
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
v
Cc: PMC
Subject: [DISCUSS][PROPOSAL] web site publishing procedure
devs (and PMC),
I created a procedure based on a staging->production promotion of PRs.
it is described in the readme file [1]
I went ahead and created it as we didn't have anything before. That
does not mean I get to
devs (and PMC),
I created a procedure based on a staging->production promotion of PRs.
it is described in the readme file [1]
I went ahead and created it as we didn't have anything before. That
does not mean I get to decide on my own, so please add your unsalted
comment or create/add change propo
All,
Anybody have any feature/improvements requests and bugs to report for the next
cmk release? (RM/release timeline yet to be discussed/determined).
Please add them here - https://github.com/apache/cloudstack-cloudmonkey/issues
Regards.
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
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
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
: 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
There have been some discussions on github PRs about the subject of
proper logging and I want to use this to start a discussion and come
to some guidelines that hopefully everybody can agree to.
My idea is the following
Fatal:
- include a reason why the system can not function anymore,
- be follo
fra seems to have enabled integration and allowing Discussions
integrated with mailing lists:
https://github.com/search?q=.asf.yaml+discussions&type=code
Following discussions with both technical and non-technical users from
the CCC, I believe we should try this out and use it for users to
nice idea!
Bobby.
From: Rohit Yadav
Date: Tuesday, 28 November 2023 at 11:28
To: dev@cloudstack.apache.org
Subject: [DISCUSS] Adopting Github Discusssions Users Forum
All,
It's been a while since I had last proposed adopting and trying the Github
Discussions feature for our users community.
Discussions integrated with mailing
> lists: https://github.com/search?q=.asf.yaml+discussions&type=code
>
> Following discussions with both technical and non-technical users from the
> CCC, I believe we should try this out and use it for users to discuss their
> ideas, questions
sions&type=code
Following discussions with both technical and non-technical users from the CCC,
I believe we should try this out and use it for users to discuss their ideas,
questions, and problems, all that traditionally has happened on the users@ ML;
while been integrating such discussions on
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
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
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
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 can be written in Go and can be useful for anybody to
benchmark CloudStack API
luxurious we can
implement a setting that creates a default NIC if one is missing.
€0,02
On Mon, Oct 2, 2023 at 8:30 AM Henrique Sato
wrote:
> Hello guys,
>
> As mentioned in PR #7859 [1], I'm opening this thread so we can discuss
> whether ACS should allow importin
Hello guys,
As mentioned in PR #7859 [1], I'm opening this thread so we can discuss
whether ACS should allow importing VMs without NIC.
Currently, ACS allows importing VMs without a NIC. However, when creating
new NICs for these VMs, it will not be possible to set them as default.
When us
Hi all,
I came across an interesting bug today which can result in high wait times on
System VMs & agents.
While processing a Command on system VM or an agent, even if the management
server is no longer waiting for an answer the Command still keeps on getting
processed. This can lead to high w
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:
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,
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.
>
>
>
> 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
: [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
..@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,
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
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
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
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
Sirett
>> CEO
>> giles.sir...@shapeblue.com<mailto:giles.sir...@shapeblue.com>
>> www.shapeblue.com<http://www.shapeblue.com/>
>>
>>
>>
>>
>> From: Ivet Petrova > ivet.petr...@shapeblue.com>>
>> Sent: Wednesday, August 30, 2023
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
lue.com<http://www.shapeblue.com/>
From: Ivet Petrova
mailto:ivet.petr...@shapeblue.com>>
Sent: Wednesday, August 30, 2023 10:14 AM
To: us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org>;
Marketing mailto:market...@shapeblue.com>>
Cc: dev mailto:dev@cloudstack
..@cloudstack.apache.org>;
> Marketing mailto:market...@shapeblue.com>>
> Cc: dev mailto:dev@cloudstack.apache.org>>
> Subject: [DISCUSS] New Design for the Apache CloudStack Website
>
> Hello,
>
> I would like to start a discussion on the design of the Apache CloudSt
...@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
;
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
sday, August 30, 2023 10:14 AM
To: us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org>; Marketing
mailto:market...@shapeblue.com>>
Cc: dev mailto:dev@cloudstack.apache.org>>
Subject: [DISCUSS] New Design for the Apache CloudStack Website
Hello,
I would like to star
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
Hello,
I would like to start a discussion on the design of the Apache CloudStack
Website and to propose a new design for it.
As we all know, the website has not been changed for years in terms of design
and information. The biggest issue we know we have is that the website is not
showing the f
ups 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: Fr
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
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. M
All,
Our UI building in packages/PRs uses npm v14, while the current LTS version is
v18. However, since we use npm for only development and building the UI
statically there are hopefully no concerns around security and support.
I've been using both v14 and v16 to build UI across different branc
+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
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
, 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
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
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 release was on Nov 2, 2020. The project seems to have been
abandoned. Powermock has compatibility issu
, 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
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
, 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
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
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
of the page.
- rearrange a bit some internal pages - the ones for features, so that it can
represent better the project capabilities.
- considering the new look, we would need to match the use cases pages to it.
Shall we do this together to discuss how to arrange them?
- can we align the logo of
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
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
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
1 - 100 of 3683 matches
Mail list logo
