Re: [DISCUSS] feedback on new experimental Cluster Management Service

2019-07-26 Thread Jens Deppe
Thanks for starting this thread Owen! I would, however, request that we keep the thread to one topic, namely feedback about the Cluster Management Service. Some background and motivation for this work: - The intention of this work came about as a need to provide a 'proper' API with functionality

Re: [DISCUSS] Time to cut Geode 1.10.0?

2019-07-26 Thread Owen Nichols
> I was expecting more discussion around this. I have some objections to the > current approach/design. I encourage you to start a [DISCUSS] thread! Also, thank you for the reminder that not everyone has been closely following the recent Cluster Management Service PRs, and since the original

[DISCUSS] feedback on new experimental Cluster Management Service

2019-07-26 Thread Owen Nichols
Starting with discussions over a year ago, the Geode community recognized the need for a new API for cluster management and cluster configuration management. Currently this requires a mix of properties, xml files, and gfsh commands. The envisioned “v2” API would expose identical REST and Java

Re: [DISCUSS] Time to cut Geode 1.10.0?

2019-07-26 Thread Alexander Murmann
*Cutting the release* Do we have any volunteers to take over the release manager role? *Re: Udo's concerns* While I believe that iterations of this particular work have been discussed on the mailing list as far back as March 2018, I do think that we should take Udo's response as an indicator that

Re: [DISCUSS] Time to cut Geode 1.10.0?

2019-07-26 Thread Dan Smith
+1 for cutting a 1.10.0 release branch. On Fri, Jul 26, 2019 at 3:55 PM Nabarun Nag wrote: > Hi, > I believe the original authors of the feature has done their due diligence > and followed all steps, we can get this feature in under the Experimental > flag and let the community improve on it,

Re: [DISCUSS] Time to cut Geode 1.10.0?

2019-07-26 Thread Nabarun Nag
Hi, I believe the original authors of the feature has done their due diligence and followed all steps, we can get this feature in under the Experimental flag and let the community improve on it, if there is anything else that needs to be done. We have done this before for Lucene re-index feature,

Re: [DISCUSS] Time to cut Geode 1.10.0?

2019-07-26 Thread Udo Kohlmeyer
@Alexander + @Jared, So maybe that was my misunderstanding on the RFC (not being optional on new feature work). Given that this is a new feature, there is significant risk to getting it "wrong". I was expecting more discussion around this. I have some objections to the current approach/desig