summaryrefslogtreecommitdiff
path: root/content/cockpit/multi-server-dashboard.md
blob: ae67401b5ec1fbd8323846a421aa09457a76f6c7 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
Title: Cockpit Multi-Server Dashboard
Date: 2014-11-04
Category: Cockpit
Tags: cockpit, kubernetes

Andreas and Marius have been working on implementing a new multi-server dash
board for Cockpit. It's really looking great.

The goal here is that the dash board should work with either one server or several,
and give you an overview of what's going on. Problems that require attention should
be highlighted clearly. You should be able to click in spots to jump either to a
server, a sub-system, a service/container/pod or to the source of a problem.

The graphs will be correlated across multiple machines, and draggable. Hopefully down
road we'll be using a source of data like [PCP](http://www.performancecopilot.org/) to
gather the data more consistently. Problems will show up on the graphs as clickable.
You can add and remove servers, and we want to show the state of important services/server
applications/pods on those servers.

Once the basic code has landed, it would be good to tie this into Kubernetes as well.
If running a [Kubernetes](https://github.com/GoogleCloudPlatform/kubernetes) cluster,
and Cockpit is loaded on the master, we should use information from Kubernetes to
populate the dashboard.

Here are some wireframes, click to expand:

![Multi server dashboard wireframes](images/navigation-horizontal-2.png)

[Pull request is here ](https://github.com/cockpit-project/cockpit/pull/1455)