Project

General

Profile

Feature #6821

BE: Dash: List of hostnames running mon and OSD services

Added by Neil Levine almost 8 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Backend (REST API)
Target version:
% Done:

0%

Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:

6821-example.txt View - Example output from /cluster/<id>/server resource (1.9 KB) John Spray, 11/25/2013 08:34 AM

History

#1 Updated by Neil Levine almost 8 years ago

For the host widget on the dashboard, we need to show the total number of unique hosts in the cluster. We currently get a list of unique OSD IPs but we don't have any data for MON IPs.

#2 Updated by Neil Levine almost 8 years ago

  • Status changed from New to 12

#3 Updated by John Spray almost 8 years ago

  • Subject changed from BE: Dash: Return number of unique hosts/IPs in cluster to BE: Dash: List of hostnames running mon and OSD services

So we discussed this yesterday, what I took away was:

- We actually want hostnames rather than IPs here
- Although counts may be used somewhere, the frontend will also need the actual list of servers so that it can indicate which specific ones may have a problem.

The data we give here will also be somewhat affected by #6082, wherein our hostname resolution for OSDs is not always reliable.

#4 Updated by John Spray almost 8 years ago

  • Category set to Backend (REST API)

#5 Updated by Neil Levine almost 8 years ago

For the initial widget, the goal is just to say "this many machines are in the cluster". We won't yet get the widget to indicate if a host (rather than an OSD) has a problem - that can be inferred from the workbench.

#6 Updated by Dan Mick almost 8 years ago

  • Target version set to v1.1rc2

#7 Updated by John Spray almost 8 years ago

  • Status changed from 12 to In Progress
  • Assignee set to John Spray

#8 Updated by John Spray almost 8 years ago

https://github.com/inktankstorage/calamari/tree/wip-6821

Borrowed the reverse dns path from Dan's wip-shortname branch

#9 Updated by Yan-Fa Li almost 8 years ago

I'm a little bit concerned with hostname not always being in the data structure, but other than that, I think this will work for the first pass. I don't need hostnames for the initial cut, but I can see them being useful for flipping a card.

I'm also not totally getting the difference between host and name, but as long as it's documented I can live with it.

#10 Updated by John Spray almost 8 years ago

The field you should be using is 'name' (which is equal to hostname if hostname is set, but may be something else if it's not).

In 2.0, hostname should always be known: the fuzzy part here is because we're just talking to one mon's ceph-rest-api, so sometimes the hostname is just unknowable.

#11 Updated by Ian Colle almost 8 years ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF