tayzlor
commented
8 years ago Love the ideas in here some of them are touched on a couple of other issues (e.g https://github.com/Capgemini/mesos-ui/issues/22 / https://github.com/Capgemini/mesos-ui/issues/16) but like the idea around draining and the maintenance primitives too.
The customisable view thing sounds interesting as well, I think it would make sense to tackle each individual function to start with then when we have those in place we could layer on additional UI goodies on top.
There's quite a lot going on in your comment :) so it might make sense to split this out in to various tasks that we can attack individually (e.g. Add functionality to terminate a task) then we can discuss each individual change in those specific issues in more detail.
So before I go into details here on my idea, I want to say that I am not a UI developer, not a web developer, not a JS developer, and know little about node/gulp etc. Thus, this is just an idea/brain storm, and the eventual effort may be way more than is feasible.
I love this UI, it's much more representative than the default UI, but one thing I've noticed with Mesos in general is there is a lot of functionality under the hood. For example, if I want to terminate a framework, I can hit an API, and terminate it, but there is no way to do that in the default UI. So, what if we could create that here, every user/admin may want to play with different things, how hard would it be to add a tab on left that may include all tasks, and then let the user customize a view? That view could show the task, show sandbox logs, show a "terminate" button. This is true of nodes too, there are some maintenance primitives in Mesos now, how nice would it be to click a node and drain it for work? Dynamically assigning roles is another option. Perhaps some dev work needs to be done, so we want to pull from unassigned resources and tag three nodes as dev (there is an API for that). This would need to involve authentication, but perhaps we could do that by for an individual session, allow a user to supply credentials that all API requests would have added... I love all the things we can do with MEsos, it would be neat if as a user, and as I learn to adopt some of the features in our org, we could make "buttons" for them so to speak by customizing a UI like mesos-ui.... this seems complicated, and it probably is, but it would really make mesos-ui an amazing tool for Mesos in general.
Thoughts?