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

Display number of containers on the top right quad of container prov #4015

Merged
merged 1 commit into from
Jun 1, 2018

Conversation

skateman
Copy link
Member

The quadicon for container provider introduced some inconsistency compared with other provider quads. The top-right quad displays an icon based on the data collection is suspended for the given provider or not. As we're extending this suspend feature to other providers and planning to use the bottom-right quad for displaying this info on each one, this would cause some redundancy for the container provider quadicons.

So I'm proposing to use the top-right quad for container providers more consistently with the other provider quads and display in it the number of containers for the given provider. Analogously to the infra provider displays the number of VMs in the same quad.

Before:
screenshot from 2018-05-31 17-23-48

After:
screenshot from 2018-05-31 17-13-54

@miq-bot add_label gaprindashvili/no, GTLs, compute/containers
@miq-bot add_reviewer @epwinchell
@miq-bot add_reviewer @romanblanco

@miq-bot
Copy link
Member

miq-bot commented May 31, 2018

Checked commit skateman@9563c29 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0
1 file checked, 0 offenses detected
Everything looks fine. 👍

@mzazrivec mzazrivec self-assigned this Jun 1, 2018
@mzazrivec mzazrivec added this to the Sprint 87 Ending Jun 4, 2018 milestone Jun 1, 2018
@mzazrivec mzazrivec merged commit 9c01d66 into ManageIQ:master Jun 1, 2018
@skateman skateman deleted the container-size branch June 1, 2018 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants