Mick, I think there is someone who’s maintaining CTOP now.. I added it to my admin/monitoring list on https://github.com/Anant/awesome-cassandra
Rahul On Sep 29, 2018, 3:20 PM -0400, Dinesh Joshi <dinesh.jo...@yahoo.com.invalid>, wrote: > > On Sep 27, 2018, at 7:35 PM, Mick Semb Wever <m...@apache.org> wrote: > > > > Reaper, > > I have looked at this already. > > > Priam, > > I have looked at this already. > > > Marcus Olsson's offering, > > This isn't OSS. > > > CStar, > > I have looked at this already. > > > OpsCenter. > > Latest release is only compatible with DSE and not Apache Cassandra[1] > > > Then there's a host of command line tools like: > > ic-tools, > > ctop (was awesome, but is it maintained anymore?), > > tablesnap. > > These are interesting tools and I don't think they do what we're interested > in doing. > > > And maybe it's worth including the diy approach people take… > > pssh/dsh/clusterssh/mussh/fabric, etc > > What's the point? You can definitely add this to the website as helpful > documentation. > > The proposal in the original thread was to create something that is supported > by the Apache Cassandra project learning from the tooling we've all built > over the years. The fact that everyone has a sidecar or their own internal > tooling is an indicator that the project has room to grow. It will certainly > help this project be more user friendly (at least for operators). > > I, as a user and a developer, do not want to use a patchwork of disparate > tools. Does anybody oppose this on technical grounds? If you do, please help > me understand why would you prefer using a patchwork of tools vs something > that is part of the Cassandra project? > > Thanks, > > Dinesh > > [1] https://docs.datastax.com/en/opscenter/6.0/opsc/opscPolicyChanges.html > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org >
