Hi folks,
Thanks for all the input. I'm trying to gather all the comments, and from what I
can gather it seems that most of the opinions are converging towards scoping
a Sidecar release. These are the items that were called out that we will need
for a release:
- Documentation
- Authorization / Aut
+1 on all the points raised by Mick. Please let me know if there is
anything I can help with.
- Yifan
On Wed, Oct 2, 2024 at 8:13 AM Josh McKenzie wrote:
> - Qbot notifications in #cassandra-dev and #cassandra-noise , as well as
> in any subproject channels
> - some cadence of dev@ ML updates,
> By vnode support, do you mean the analytics library? Or do other features
> in sidecar not work with vnodes?
Mostly Analytics, which should not be a blocker for Sidecar. However, I do
feel there should be more testing around vnodes in Sidecar.
> If we're talking about analytics, that gets a li
I think we just need to ask infra to create the jira instances, but I
guess we need to have some kind of consistent naming scheme to help
identify them?
Kind Regards,
Brandon
On Wed, Oct 2, 2024 at 1:02 PM Francisco Guerrero wrote:
>
> +1 too on the points brought by Mick, we need more visibilit
I don't think we should release sidecar 1.0 without any docs.
I took a look through the closed JIRAs to see what's there. Here's what I
found, please correct me if there's more:
- Lots of stuff related to analytics.
I would be pretty excited for this, but the analytics library only works
with s
When I developed some of the original sidecar code, it was based on REST
Easy, which would have allowed us to generate the spec automatically. I
did this in a similar project.
That was removed here:
https://issues.apache.org/jira/browse/CASSANDRASC-57
But unfortunately it looks like you can't ge
+1 too on the points brought by Mick, we need more visibility into
subprojects. For starters, we should look into integrating Qbot
notifications in #cassandra-dev and #cassandra-noise for
CASSANDRASC tickets. Let me know if I can help with that.
On 2024/10/02 17:39:28 Yifan Cai wrote:
> +1 on all
By vnode support, do you mean the analytics library? Or do other features
in sidecar not work with vnodes?
If we're talking about analytics, that gets a little complicated. Are we
also then talking about 1.0'ing analytics? If so, I think we need support
for 5.0 and BTI there.
In my opinion, if
> Mostly Analytics, which should not be a blocker for Sidecar.
Yes, agreed. I'm just trying to understand the context of the vnode
statement and how we're framing 1.0 sidecar.
> We definitely need to support 5.0 for the Analytics release, but that's
orthogonal to Sidecar.
It is, unless we're en
Totally agree with Jon here basically on all fronts. Apache Cassandra
Sidecar was always a hard nut to crack for me, that is probably why I have
not been involved with that a lot even that is a great tool to have and be
invested in as I was writing my own sidecar and I found a lot of
similarities a
> - Qbot notifications in #cassandra-dev and #cassandra-noise , as well as in
> any subproject channels
> - some cadence of dev@ ML updates, e.g. on activities, or dependency changes,
> etc
> - regular releases
Agree on all 3 points. Also - I've *definitely* fallen off on the project
updates for
Something like this:
https://instaclustr.github.io/instaclustr-icarus-go-client/
On Wed, Oct 2, 2024 at 4:54 PM Štefan Miklošovič
wrote:
> While documenting endpoints please use something like OpenAPI
> specification. The sidecar should expose this document itself so when I go
> to this and tha
Hi Abhijeet,
Contributing documentation would be greatly appreciated.
Feature wise - is there functionality in sidecar that I missed? What are
you finding to be quite useful? I think everyone would benefit to hear
from folks who use it and are getting something useful out of it as it will
help
While documenting endpoints please use something like OpenAPI
specification. The sidecar should expose this document itself so when I go
to this and that URL, I see all endpoints, I put the payloads / parameters
for them and I can just directly call that, no messing with curl / wget or
programmatic
Hi folks,
I have been using Sidecar recently and have found some of its
functionalities to be quite useful. Hari and I are also working on CEP-40
which aims to introduce live migration features in Sidecar in the
near future.
However, as others have mentioned, I agree that it currently lacks prope
15 matches
Mail list logo
