All - As we are in the final hours of the 0.13.0 VOTE on RC-2, I thought we might start a thread for planning on 0.14.0 (1.0.0).
We have made a good deal of progress on our existing KIP's over the last couple of releases. There may be a couple stray tasks from a few of them and I will go through and try to identify them and pull them in 0.14.0 or revisit whether they are actually needed. There is already a set of 0.14.0 issues that were pushed out of 0.13.0 which we can start with as well. I'd like to put up for consideration a feature that abstracts a service registry or discovery service that we could plug in various implementations to. We could potentially start with an implementation that leverages the Ambari API to determine the endpoints of services described in a topology. I'd also like to simplify the creation of topologies so that they can be much more easily authored in UIs like Ambari or our admin UI without it being a big blob of XML. Thinking about a simple, flat file with service names and the name of a separately configured set of providers. Then deployment machinery can discover changes to these files and generate topologies by leveraging the discovery service to find the service details such as: URL/s, HA or not, etc. I am also going to spend some time thinking about how to simplify the rewrite rules for UI proxying. I will start a separate DISCUSS on this if I come up with anything. If anyone would like to take a crack at writing up one or more of the above as a KIP, please feel free. Thanks! --larry
