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 configurations in order to connect.
On Thu, May 24, 2018 at 1:15 PM, Dan Smith <dsm...@pivotal.io> wrote: > 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 > admin REST endpoint. How do the clients and servers discover that endpoint > and how do they make sure they have the right security certificates to > connect, etc.? It seems like this will require additional configuration on > the clients and servers so they can connect to this endpoint? > > -Dan > > On Thu, May 24, 2018 at 11:57 AM, Sai Boorlagadda < > sai_boorlaga...@apache.org> wrote: > > > 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+Management+Service > > > > I would like to hear the feedback on the proposal. > > > > Sai > > > -- Cheers Jinmei
