Gabriel, all,
I suppose it depends, there's no right answer just trade-offs. Here's my
lengthy brain dump;
0. our LTS definition is really to tag a set of releases and show intent that
they are "stable" and will be supported and get maintenance releases. We don't
really do LTS releases like la
I don't have any specific inclination, I would use whatever becomes a standard.
However, I prefer the readability of a utility method that is readable and easy
to understand such as isNullOrEmpty (which suggests it's doing a null check)
versus isEmpty.
I suppose a refactoring exercise can be do
Hi Benoit,
Yes, it's possible to write a backup and recovery plugin. The framework exposes
interfaces that your plugin or an external service managed by the plugin can
execute/implement. For example, taking backup, restoring backup to primary
storage etc. Depending on what/how you're integratin
+1
At work we're discussing a new RRD framework feature that would expand on the
metrics feature of various resources which would include (possibly in future)
metrics of VRs too. I suppose, just like VM stats you would want to capture VR
stats plus something extra (like active connection, VR fi
+1
That makes sense. In the go-sdk we've a generator that consumes the listApis
output of a ACS release and generates the library -
https://github.com/apache/cloudstack-go/tree/main/generate
I suppose for every ACS release, we can update go-sdk with release-specific API
list, test it, release
Hi Daniel,
I don't have a preference either, but the work you are proposing on your PR
makes sense to me.
Regards,
Nicolas Vazquez
From: Rohit Yadav
Sent: Wednesday, September 8, 2021 5:05 AM
To: dev@cloudstack.apache.org
Subject: Re: [Discussion] String lib
Thanks all for helping with the discussion.
Yes, Rohit. I need to answer a few pings, sorry for the delay :-)
I totally agree with you and Paul, the costs of releasing are high,
especially for the release manager(s) which dedicates a lot of energy and
time to it.
This is one of the reasons behind
Hi All,
We are upgrading a Vue 2 application to Vue 3 on CloudStack. As far as our
investigation goes, Vue 3 does support migration from Vue 2 to Vue 3 by using
`@vue/compat` (aka "the migration build"). However, it is worth mentioning that
there are some incompatible features (please refer to:
Hi
I am facing the same problem. Please suggest any solution group members.
Thanks in advance
On Tue, 7 Sep, 2021, 11:30 pm R R, wrote:
> I installed a cloudstack server on a bare metal server (all in one
> installation). The bandwidth usage was normal. After a couple days, the
> bandwidth usa
Hi,
That would be bandwidth between which hosts? Also, what exactly would you
call normal and excessive bandwidth usage?
Regards
Alex
-Original Message-
From: Saurabh Rapatwar
Sent: 08 September 2021 16:46
To: us...@cloudstack.apache.org
Cc: dev@cloudstack.apache.org
Subject: Re
Daniel et al,
I've no preference and don't mind multiple dependencies when they supply
overlapping features. I do want to keep 3rd party libraries in facade
projects at all times. It keeps maintenance surface small and it is easier
to see conflicts happening (a good reason to reduce dependencies bt
signing correct, archive contents sane (no further testing done)
+1 (binding)
On Tue, Sep 7, 2021 at 2:53 PM Rohit Yadav wrote:
> All,
>
> I've created a 4.15.2.0 release, with the following artifacts up for a
> vote:
>
> Git Branch and Commit SHA:
> https://github.com/apache/cloudstack/tree/4.1
Hello,
I asked networking team to comment on “How should the IPv6 block/allocation
work in VPCs?”
Option1: They haven’t seen lately devices with limits on how many static routes
can be created.
Option2: With /60 and /62 assignments and big quantity of routers IPv6
assignment from RIPE NNC can b
Hi Kristaps,
Thanks for sharing, I suppose that means individual tiers should be allocated
/64 instead of larger ipv6 blocks to the whole VPC which could cause wastage.
Any objection from anybody?
Regards.
From: Kristaps Cudars
Sent: Wednesday, September 8, 202
Hi Rohit, Kristaps,
I'd say option 1 as well, it does create a bit more overhead with static
routes but if that's automated for a VPC it can also be easily automated for
several tiers of a VPC. We also don't constrain the amount of tiers in a VPC.
It has the added advantage to be closer to th
This should not happen, Cloudstack Is just web application, it does not
consume any bandwidth . The one consume bandwidth is the VM inside .
On Wed, Sep 8, 2021 at 10:52 PM Alex Mattioli
wrote:
> Hi,
>
> That would be bandwidth between which hosts? Also, what exactly would
> you call normal
Hello Hoang, (or should I say Nguyen?)
I see no options to discuss in your request. We will have to move our vue
usage forward to version 3 eventually. Are there choices to make? If not,
go ahead.
regards,
On Tue, Sep 7, 2021 at 2:49 AM Nguyen Mai Hoang wrote:
> Hi All,
>
> We are upgrading a
shwstppr opened a new pull request #240:
URL: https://github.com/apache/cloudstack-documentation/pull/240
Note on hypervisor/host capabilities.
Addresses https://github.com/apache/cloudstack/issues/3015
--
This is an automated message from the Apache Git Service.
To respond to the mess
shwstppr commented on pull request #240:
URL:
https://github.com/apache/cloudstack-documentation/pull/240#issuecomment-915801536
@blueorangutan docbuild
--
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 t
blueorangutan commented on pull request #240:
URL:
https://github.com/apache/cloudstack-documentation/pull/240#issuecomment-915802141
@shwstppr a Jenkins job has been kicked to build the document. I'll keep you
posted as I make progress.
--
This is an automated message from the Apache G
blueorangutan commented on pull request #240:
URL:
https://github.com/apache/cloudstack-documentation/pull/240#issuecomment-915802588
Doc build preview: http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/240.
(SL-JID 140)
--
This is an automated message from the Apache Git Service.
To resp
21 matches
Mail list logo
