Skip to content
This repository has been archived by the owner on Oct 7, 2021. It is now read-only.

Update documentation for namespace overview #21

Merged
merged 3 commits into from
Aug 25, 2018

Conversation

cshinn
Copy link
Contributor

@cshinn cshinn commented Aug 2, 2018

Updates designs and documentation for the namespace overview based on feedback and requirements

  • Removes list view
  • Removes alternate representations
  • Updates card view to better reflect user needs

Closes #22

@abonas
Copy link
Contributor

abonas commented Aug 2, 2018

@cshinn I just added a summary issue https://github.com/kiali/kiali-design/issues/22 at the same time!

Copy link
Contributor

@abonas abonas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 questions/comments in addition to inline comments:

  1. in both popover and in click the cursor in the mockup is hand palm. In case of popover - should it also be a handpalm to indicate it's clickable? (just making sure for implementation purposes)
  2. the tooltip for 15 greens services says "service in error, service 2 in error" , for clarity it would be nicer to have non error service names for the "green" services example :)

### Namespace Cards
- **Title:** Displays the name of the namespace. May wrap to a second line if necessary.
- **Status Counts:** Shows the number of services with each status. Icons should only be shown for a given status if there are services in the namespace that have that status.
- **Service Count:** The total number of services in the namespace.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

count should come before status counts

### Card interactions
- Clicking on a card links to a view of the services list filtered by the relevant namespace
- Clicking on a status count links to a view of the services with that status in the selected namespace
- Hovering over a status count displays a popover with a list of the services with that status.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

with a list of service names (not all service information)

- Clicking on a card links to a view of the services list filtered by the relevant namespace
- Clicking on a status count links to a view of the services with that status in the selected namespace
- Hovering over a status count displays a popover with a list of the services with that status.
- If more than 6 services with a given status exist, the popover should show the names of the first 5 followed by the message "and # more..." to describe the total number
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good point

### Namespace Cards
- **Title:** Displays the name of the namespace. May wrap to a second line if necessary.
- **Service Count:** The total number of services in the namespace.
- **Status Counts:** Shows the number of services with each status. Icons should only be shown for a given status if there are services in the namespace that have that status.
Copy link
Contributor

@abonas abonas Aug 2, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Except green, right? Or if all are green then indicate X services green



### Card interactions
- Clicking on a card links to a view of the services list filtered by the relevant namespace
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cshinn this is a bit confusing to me. The view is called namespaces, the name on the card is namespace, so I think clicking on the card would imply that the user would navigate to the namespace.

Could we instead provide a link on the #Services and allow that to provide the navigation?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please define "navigate to the namespace" - for me this would be the graph of that namespace (in what mode?)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a plan to include namespaces as objects in Kiali? AFAIK right now they're really only represented as attributes on services

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cshinn no, namespaces are not "direct" objects in Kiali. Those are k8s/openshift objects that are used for filtering in Kiali. I don't expect this to change.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My point is just that if the view is called namespaces, and we are navigating to services, it should be done so by clicking the "services" link, rather than the card.

### Card interactions
- Clicking on a card links to a view of the services list filtered by the relevant namespace
- Clicking on a status count links to a view of the services with that status in the selected namespace
- Hovering over a status count displays a popover with a list of the names of services with that status.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it's a hover, should it be a tooltip rather than an Infotip? I don't remember if there is relevant PF guidance.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, tooltip would be a better word to use here. I'll update

@@ -1,21 +1,18 @@
# Namespace Overview
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The view shows Filter and Sort components.

What are available sorting fields ? Name and Status?
Are we allowing them to filter by anything else?

Copy link
Contributor Author

@cshinn cshinn Aug 3, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could sort by number of services as well. Might be useful

@pilhuhn
Copy link
Contributor

pilhuhn commented Aug 3, 2018

Can we make that that cards that show warnings / errors automatically bubble up to the top (on refresh)? Those with errors should go before the ones that have warnings only.

@serenamarie125
Copy link
Contributor

@pilhuhn that's the plan for the sorting. Who will create that formula?
Should it be highest percentage of errors would be first, then highest percentage of warnings?
Or would we want those things weighted?

@pilhuhn
Copy link
Contributor

pilhuhn commented Aug 7, 2018

@serenamarie125 Great.
My thought is that anything with red (e) goes before everything that is not red.
Same for yellow (w) before anything green (g).
So 1e3w would go before 5w1g before 3g
Within the the 'categories' I'd go for sorting by number of the state. So 2eX will go before 1e5w before 1e3w

@cshinn
Copy link
Contributor Author

cshinn commented Aug 17, 2018

@abonas now that the graph has switched to showing applications instead of services, are there changes that need to be made to this design? Should we show applications/workloads instead, or should both services and workloads be included?

@abonas
Copy link
Contributor

abonas commented Aug 22, 2018

@mwringe @lucasponce can you please address @cshinn question above?

@lucasponce
Copy link

I should say that the graph represents applications, workloads and also services.
If I am not wrong, this is an example of three ones:
image
As a preliminar step (version 0) we are introducing a new navigation entry called Application; but overall yes, I should say it should be taken into consideration for high level goals on the design.

@serenamarie125
Copy link
Contributor

@abonas @cshinn FYI I'm going to merge this PR. If you need workspaces included as well, we can iterate on the design.

@serenamarie125 serenamarie125 merged commit 4be132a into kiali:master Aug 25, 2018
@cshinn cshinn deleted the namespace-overview branch August 28, 2018 16:33
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants