Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial implementation of Cluster Dashboard #1687

Closed
stefwalter opened this issue Jan 20, 2015 · 19 comments

Comments

Projects
None yet
3 participants
@stefwalter
Copy link
Contributor

commented Jan 20, 2015

As mentioned on the wiki page one of the use cases is a cluster dashboard.

The use case:

https://github.com/cockpit-project/cockpit/wiki/Atomic:-Kubernetes-dashboard#d-browse-the-cluster

@stefwalter stefwalter changed the title Initial implementation of cluster Browse Initial implementation of Cluster Browse Jan 20, 2015

@stefwalter stefwalter self-assigned this Jan 20, 2015

@stefwalter stefwalter changed the title Initial implementation of Cluster Browse Initial implementation of Cluster Overview Jan 20, 2015

@jeffvance

This comment has been minimized.

Copy link
Contributor

commented Jan 20, 2015

Newbie question: why is a goal to "share styling and design with openshift"? Why not ManageIQ, for example?

@stefwalter

This comment has been minimized.

Copy link
Contributor Author

commented Jan 20, 2015

Because ManageIQ is not working on styling yet. Openshift designers are the ones working on this.

@stefwalter

This comment has been minimized.

Copy link
Contributor Author

commented Feb 11, 2015

service-listing

A rough design for the overview.

We got feedback, while at devconf in Brno, that the "browse" objects style view, wouldn't be good enough for an overview. The goal of us implementing this stuff is to help people learn about Kubernetes. Hence we need to separate the 'cluster dashboard' from the 'kubernetes browse objects'

Some notes:

  • Use of "containers" vs. "pods". Containers are readily understandable, and help people grasp this immediately. "Pods" are an unfamiliar concept, and could be left to the 'Browse objects' view.
    • Obviously the two are not words for the same thing. Here we're just showing containers each service/minion is running, instead of the pods.
    • However this may be a point of some discussion, and I'm not completely stuck on this.
  • Incomplete: There should also be a [+] button to add Nodes
  • Incomplete: Probably a big button to deploy an application.
  • Perhaps there would be a high level action to rescale a service (eg: update the replication controller)

The browse view designs should come from Openshift.

@stefwalter

This comment has been minimized.

Copy link
Contributor Author

commented Feb 11, 2015

I believe that 'delete service' and 'delete node' actions happen on the details pages for those (not yet designed).

@stefwalter

This comment has been minimized.

Copy link
Contributor Author

commented Feb 11, 2015

We should say "Kubernetes Services" and "Kubernetes Nodes" in the headings, to clarify these rather overloaded terms.

@stefwalter

This comment has been minimized.

Copy link
Contributor Author

commented Feb 12, 2015

service-listing

  • Icons at the end of row
  • Add buttons to the headers
  • More clarifications of where clicking on things goes

And yes, graph hovering will highlight rows as they do in other parts of Cockpit. Haven't designed the graph parts yet here.

@stefwalter stefwalter changed the title Initial implementation of Cluster Overview Initial implementation of Cluster Dashboard Feb 12, 2015

@stefwalter

This comment has been minimized.

@sub-mod

This comment has been minimized.

Copy link
Contributor

commented Feb 16, 2015

Just my opinion, but i feel having a tabular display of available Nodes can be slightly inconvenient to get a grasp of all the containers across the cluster.
Instead if we display below the "graphs" a visualization similar to github commit.
screen shot 2015-02-16 at 1 39 18 pm
We can get the entire cluster view and also by hovering on each box we can figure out how many containers exits per node
We can also color code each nodes with different colors if it makes sense to highlight nodes which contain containers of a particular service.

@stefwalter

This comment has been minimized.

Copy link
Contributor Author

commented Feb 16, 2015

I think initially for the proof of concept we are targetting small clusters of 1 - 10 nodes. But yes, perhaps in the future we could "auto-scale" to visualization like that when many nodes exist.

@jeffvance

This comment has been minimized.

Copy link
Contributor

commented Feb 16, 2015

For the color impaired we should use an additional clue besides color to indicate the service. Eg. font, texture. border, size, etc.

@stefwalter

This comment has been minimized.

Copy link
Contributor Author

commented Feb 16, 2015

For the color impaired we should use an additional clue besides color to indicate the service. Eg. font, texture. border, size, etc.

The 'blue' highlight that you see here is a standard patternfly row hover highlight, when the mouse is over the row.

If this is indeed a problem with Cockpit in general, we should work with @andreasn and patternfly team members like @rhamilto to identify a way to make this accessible, and perhaps have a high constrast mode or something like that?

@jeffvance

This comment has been minimized.

Copy link
Contributor

commented Feb 17, 2015

In an earlier comment Stef wrote: "Incomplete: Probably a big button to deploy an application."
Is this in scope for cockpit? I see this being required in openshift console but I didn't consider that cockpit would deploy an app.

@stefwalter

This comment has been minimized.

Copy link
Contributor Author

commented Feb 17, 2015

In an earlier comment Stef wrote: "Incomplete: Probably a big button to deploy an application." Is this in scope for cockpit? I see this being required in openshift console but I didn't consider that cockpit would deploy an app.

Yes, please see the use cases described on the design page: https://github.com/cockpit-project/cockpit/wiki/Atomic:-Kubernetes-dashboard

@sub-mod

This comment has been minimized.

Copy link
Contributor

commented Feb 17, 2015

@stefwalter The more i play with v3 api the more i realize the namespaces will be integral to k8 , I think we need to design namespaces in UI sooner than we planned .Lets have some discussions around how namespaces are going to be part of the dashboard and avoid rework on the dashboard i dont anticpate much effort if we do it now.

@stefwalter

This comment has been minimized.

Copy link
Contributor Author

commented Feb 19, 2015

I've split removed designs related to the browse view. That's a separate work item.

@stefwalter

This comment has been minimized.

Copy link
Contributor Author

commented Feb 19, 2015

Added the 'namespace' as a first order concept on the dashboard. Suggested by @sub-mod. Good idea.

dashboard

@sub-mod

This comment has been minimized.

Copy link
Contributor

commented Feb 24, 2015

@stefwalter The tabular display for Nodes may have a look and feel issue when there are many nodes ans where if the node is in bottom of the list then the nodes wont be visible to the user.
Scrollbar can solve it , not sure if it is a good UX design.

@stefwalter

This comment has been minimized.

Copy link
Contributor Author

commented Feb 24, 2015

Scrollbar can solve it , not sure if it is a good UX design.

Good point. This needs some thought. A scrollbar might work, with some tweaks. Are you okay with us splitting this out into a separate bug for work after the initial implementation of the dashboard?

@stefwalter

This comment has been minimized.

Copy link
Contributor Author

commented Mar 3, 2015

I'm implementing this on my kubernetes-dashboard branch.

stefwalter added a commit to stefwalter/cockpit that referenced this issue Mar 12, 2015

kubernetes: Bring in the rough design of the dashboard
The basis for the angular application.

We don't correctly yet fill in all the data, but this is a start.
Watch for changes and rerender when things happen.

Closes cockpit-project#1895
Fixes cockpit-project#1687

stefwalter added a commit to stefwalter/cockpit that referenced this issue Mar 13, 2015

kubernetes: Bring in the rough design of the dashboard
The basis for the angular application.

We don't correctly yet fill in all the data, but this is a start.
Watch for changes and rerender when things happen.

Closes cockpit-project#1895
Fixes cockpit-project#1687
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.