Re: Adding an Administrator UI to Knox

[larry mccay <lm...@apache.org>]

Hi Zac -

This is a great idea and definitely something that is needed.
We definitely need to consider the issue of synchronization across multiple
instances.

Zookeeper may be a solution toward that end but we will have to carefully
consider the eventual consistency of ZK.
I have a paper somewhere about using it for such a purpose and will get it
into the wiki or something if it is still relevant.

In addition to the topology features you list we could also include the
ability to add/edit service definitions for API and UI proxying.

I think that we have JIRA for your previous thoughts on this already - so
we can continue discussion there or you can file another one.

thanks,

--larry

On Thu, Jun 30, 2016 at 4:35 PM, Zachary Blanco <zb...@hortonworks.com>
wrote:

> ?Hey there dev@,
>
>
> Currently we have an administrator API that has some basic functionality
> for uploading and downloading topologies from Knox. With the advent of
> KNOX-670<https://issues.apache.org/jira/browse/KNOX-670> (ability for
> Knox to host webapps) I think it would be useful if we added a  baked-in UI
> that users could use to control some of the configurations for Knox.
>
>
> Right now the admin API doesn't have a whole lot of functionality.
> However, it could be expanded to be able to add things like custom service
> definitions, provide metrics, or even views of the logs. These are things
> that we could add to the UI functionality as well.
>
>
> Before I went ahead with this I wanted to see what others thought about a
> set of features for a first-run of the UI.
>
>
> Currently I'm thinking that it should at least:
>
>   *   ?Upload topologies
>   *   Edit topologies
>   *   View/Get a topology
>
> It also wouldn't hurt to discuss any possible issues or limitations that
> we might have to hurdle as well with things like doing updates in
> environments with HA and such. It would be especially good to hear other's
> opinions on this.
>
>
>
>