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

Improve monitoring page collapsed rows #1812

Merged
merged 1 commit into from
Jul 19, 2017

Conversation

spadgett
Copy link
Member

@spadgett spadgett commented Jul 10, 2017

  • Show how many containers are ready for individual pods
  • Use the mini pod donut for deployments and stateful sets

The mini donut lets you click through to get to the pods and shows when
pods are crashing and not ready.

screen shot 2017-07-10 at 9 41 57 am

Fixes #1489

- Show how many containers are ready for individual pods
- Use the mini pod donut for deployments and stateful sets

The mini donut lets you click through to get to the pods and shows when
pods are crashing and not ready.
@spadgett spadgett requested a review from jwforres July 10, 2017 13:48
ng-switch-when="New"></span><span
ng-switch-when="Pending"></span><span
ng-switch-default>, ran for {{build.status.startTimestamp | duration : build.status.completionTimestamp}}</span>
<span ng-if="!build.status.reason || build.status.phase === 'Cancelled'">{{build.status.phase}}</span>
Copy link
Member Author

Choose a reason for hiding this comment

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

@jwforres This is only used on the monitoring page. I wanted it to be consistent with container ready for pods (see screenshot in description), and I think it's easier to scan the page without the "ran for..." It also takes less space, and we're somewhat space constrained here.

$ rg -thtml build-status
app/views/builds.html
105:                        <!-- <build-status build="build"></build-status> -->

app/views/monitoring.html
386:                              <build-status build="build"></build-status>

@spadgett
Copy link
Member Author

@ncameronbritt FYI

ng-switch-when="Pending"></span><span
ng-switch-default>, ran for {{build.status.startTimestamp | duration : build.status.completionTimestamp}}</span>
<span ng-if="!build.status.reason || build.status.phase === 'Cancelled'">{{build.status.phase}}</span>
<span ng-if="build.status.reason && build.status.phase !== 'Cancelled'">{{build.status.reason | sentenceCase}}</span>
Copy link
Member

Choose a reason for hiding this comment

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

is a pending build showing up correctly? i don't think it has a reason, its phase is not cancelled and it wouldn't have a startTimestamp

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah. If it doesn't have a reason, the first ng-if is true.

screen shot 2017-07-11 at 1 07 15 pm

@jwforres
Copy link
Member

LGTM for 3.7

@spadgett
Copy link
Member Author

[merge]

1 similar comment
@spadgett
Copy link
Member Author

[merge]

@spadgett
Copy link
Member Author

cc @jwforres looks like this might be a flake

1) User adds a template to a project after creating a new project using the Import YAML tab should save the template in the project catalog
  - Error: URL hasn't changed to project/console-test-project-1500489744656/overview(is currently: undefined)
Wait timed out after 5089ms

@spadgett
Copy link
Member Author

[merge]

@openshift-bot
Copy link

Evaluated for origin web console merge up to 5484782

@openshift-bot
Copy link

openshift-bot commented Jul 19, 2017

Origin Web Console Merge Results: SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin_web_console/14/) (Base Commit: adf6034) (PR Branch Commit: 5484782)

@openshift-bot openshift-bot merged commit 4209f2a into openshift:master Jul 19, 2017
@spadgett spadgett deleted the monitoring-mini-donut branch July 19, 2017 19:44
@spadgett
Copy link
Member Author

Flake #1685

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants