[Proposal] CMS - cluster management service

Hello, Updating configuration of Geode clusters involves a workflow and is currently only exposed through 'gfsh commands'. Proposing a new service/API to manage Geode clusters in which the underlying workflow is accessible through an API. https://cwiki.apache.org/confluence/display/GEODE/Cluster+

Fixed version as 1.8

Hi Geode Community, If you are committing any fix to the Apache Geode develop branch only, please mark the the fixed version as 1.8 in the respective JIRA ticket Regards Nabarun Nag

Re: [Proposal] CMS - cluster management service

Hi Sai, +1 for making the cluster configuration API public. This looks great! One question I have is about how the Java API is supposed to work. You are saying that the clients and servers will not send cluster configuration messages over their existing channels, but will instead connect to this

Re: [Proposal] CMS - cluster management service

We haven't pinned down the exact java api on how client/server will interact with this rest service available on the locator. I would image a java api that would wrap the rest service call will be in place. It would require the caller to provide the endpoint and the necessary credentials and ssl co

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #927 was SUCCESSFUL (with 2406 tests)

--- Spring Data GemFire > Nightly-ApacheGeode > #927 was successful. --- Scheduled 2408 tests in total. https://build.spring.io/browse/SGF-NAG-927/ -- This

PR: Configure Spotless not to join already-wrapped lines

Hi all, I've submitted a PR to configure Spotless to refrain from joining already-wrapped lines: https://github.com/apache/geode/pull/1994 My main motivation was to allow formatting method chains with one method per line (such as in long Stream pipel