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

[ui] Job Deployment Status: History and Update Props #16518

Conversation

philrenaud
Copy link
Contributor

@philrenaud philrenaud commented Mar 16, 2023

Adds "Deployment History" and "Update Params" sections to the bottom of a Deployment window
image

@philrenaud philrenaud self-assigned this Mar 16, 2023
@philrenaud philrenaud changed the title Deployment history wooooooo [ui] Job Deployment Status: History and Update Props Mar 16, 2023
@github-actions
Copy link

github-actions bot commented Mar 16, 2023

Ember Asset Size action

As of 9102247

Files that got Bigger 🚨:

File raw gzip
nomad-ui.js +9.4 kB +1.44 kB
nomad-ui.css +17.4 kB +1.09 kB

Files that stayed the same size 🤷‍:

File raw gzip
vendor.js 0 B 0 B
vendor.css 0 B 0 B

@github-actions
Copy link

github-actions bot commented Mar 16, 2023

Ember Test Audit comparison

16350-service-job-deployment-status-panel 9102247 change
passes 1493 212 -1281
failures 0 1 +1
flaky 0 0 0
duration 13m 39s 279ms 000ms -13m 39s 279ms

Copy link
Contributor

@ChaiWithJai ChaiWithJai left a comment

Choose a reason for hiding this comment

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

Do you really need the watchers here? This doesn't seem intuitive. I'd be curious to see some tests that prove this out.

@philrenaud
Copy link
Contributor Author

Do you really need the watchers here? This doesn't seem intuitive. I'd be curious to see some tests that prove this out.

Hey @ChaiWithJai — this is what I wanted us to talk about earlier. There are a couple assumptions being made in the comments here that I think would be easier to correct in person, so let's sync up tomorrow.

@mikenomitch mikenomitch marked this pull request as ready for review March 21, 2023 03:35
@mikenomitch
Copy link
Contributor

Oh no, I accidentally clicked "Ready for Review" and don't know if I can revert it 🙃

@tgross tgross marked this pull request as draft March 21, 2023 13:04
Copy link
Contributor

@ChaiWithJai ChaiWithJai left a comment

Choose a reason for hiding this comment

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

There's a good deal of data fetching that could be reconsidered. Some requests may not be necessary given that we're already loading data in the view. I think both components should extract data loading logic out of the component using something like Trigger and then individually worry about derived state computation and presentational logic.

ui/app/components/job-status/update-params.js Outdated Show resolved Hide resolved
ui/app/components/job-status/update-params.hbs Outdated Show resolved Hide resolved
* @type { import('../../models/allocation').default[] }
*/
get jobAllocations() {
return this.job.get('allocations');
Copy link
Contributor

Choose a reason for hiding this comment

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

This is an asynchronous request. We already have a watchRelationship request set-up to populate the Ember Data with the correct records. Do we need another asynchronous request here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This does not cause an external data request but just looks against the existing model unless a reload: true flag is passed in.

Having this set up in this way allows us to reference this.history and know that it will update with the watched allocations as they roll in.

.sort((a, b) => a.get('time') - b.get('time'))
.reverse();
} catch (e) {
this.triggerError(e);
Copy link
Contributor

Choose a reason for hiding this comment

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

There is no asynchronous request being made in this getter. So I think we're handling the error in the incorrect place with the incorrect title.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You're right that this is not async, but this catch will still fire if the map/flat/map chain has errors. For example, if the returned values for task events deviates then this error would catch it.

/**
* @type { import('../../models/job').default }
*/
@alias('args.deployment.job') job;
Copy link
Contributor

Choose a reason for hiding this comment

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

Looks like an asynchronous request. Do we need this here? We already have access to the job in JobStatus.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Just a convenience method; could change jobAllocations to be a little longer and eschew this.

@philrenaud
Copy link
Contributor Author

There's a good deal of data fetching that could be reconsidered. Some requests may not be necessary given that we're already loading data in the view.

Hey @ChaiWithJai , the requests in question are .gets on existing ember data relationships. This does not cause an external data request but just looks against the existing model unless a reload: true flag is passed in. Are you still concerned about using .get() to find the data otherwise applied via parent route watchers with this in mind?

@philrenaud
Copy link
Contributor Author

@ChaiWithJai refactored updateParams to use the trigger component you recommended. As for deployment-history, it's not doing its own fetching, but it is doing its own formatting in get history.

This seems like not the correct place to use the <Trigger> component to me; a reactively generated array that doesn't have any "kickoff" action.

* Functioning searchbox

* Some nice animations for history items

* History search test

* Fixing up some old mirage conventions

* some a11y rule override to account for scss keyframes
@philrenaud philrenaud merged commit 734c560 into 16350-service-job-deployment-status-panel Mar 27, 2023
@philrenaud philrenaud deleted the 16512-service-job-deployment-panel-history-and-update-params branch March 27, 2023 20:22
philrenaud added a commit that referenced this pull request Apr 19, 2023
* A very fast and loose deployment panel

* Removing Unknown status from the panel

* Set up oldAllocs list in constructor, rather than as a getter/tracked var

* Small amount of template cleanup

* Refactored latest-deployment new logic back into panel.js

* Revert now-unused latest-deployment component

* margin bottom when ungrouped also

* Basic integration tests for job deployment status panel

* Updates complete alloc colour to green for new visualizations only (#16618)

* Updates complete alloc colour to green for new visualizations only

* Pale green instead of dark green for viz in general

* [ui] Job Deployment Status: History and Update Props (#16518)

* Deployment history wooooooo

* Styled deployment history

* Update Params

* lintfix

* Types and groups for updateParams

* Live-updating history

* Harden with types, error states, and pending states

* Refactor updateParams to use trigger component

* [ui] Deployment History search (#16608)

* Functioning searchbox

* Some nice animations for history items

* History search test

* Fixing up some old mirage conventions

* some a11y rule override to account for scss keyframes

* Split panel into deploying and steady components

* HandleError passed from job index

* gridified panel elements

* TotalAllocs added to deploying.js

* Width perc to px

* [ui] Splitting deployment allocs by status, health, and canary status (#16766)

* Initial attempt with lots of scratchpad work

* Style mods per UI discussion

* Fix canary overflow bug

* Dont show canary or health for steady/prev-alloc blocks

* Steady state

* Thanks Julie

* Fixes steady-state versions

* Legen, wait for it...

* Test fixes now that we have a minimum block size

* PR prep

* Shimmer effect on pending and unplaced allocs (#16801)

* Shimmer effect on pending and unplaced

* Dont show animation in the legend

* [ui, deployments] Linking allocblocks and legends to allocation / allocations index routes (#16821)

* Conditional link-to component and basic linking to allocations and allocation routes

* Job versions filter added to allocations index page

* Steady state legends link

* Legend links

* Badge count links for versions

* Fix: faded class on steady-state legend items

* version link now wont show completed ones

* Fix a11y violations with link labels

* Combining some template conditional logic

* [ui, deployments] Conversions on long nanosecond update params (#16882)

* Conversions on long nanosecond nums

* Early return in updateParamGroups comp prop

* [ui, deployments] Mirage Actively Deploying Job and Deployment Integration Tests (#16888)

* Start of deployment alloc test scaffolding

* Bit of test cleanup and canary for ungrouped allocs

* Flakey but more robust integrations for deployment panel

* De-flake acceptance tests and add an actively deploying job to mirage

* Jitter-less alloc status distribution removes my bad math

* bugfix caused by summary.desiredTotal non-null

* More interesting mirage active deployment alloc breakdown

* Further tests for previous-allocs row

* Previous alloc legend tests

* Percy snapshots added to integration test
philrenaud added a commit that referenced this pull request Apr 25, 2023
* [ui] Service job status panel (#16134)

* it begins

* Hacky demo enabled

* Still very hacky but seems deece

* Floor of at least 3 must be shown

* Width from on-high

* Other statuses considered

* More sensible allocTypes listing

* Beginnings of a legend

* Total number of allocs running now maps over job.groups

* Lintfix

* base the number of slots to hold open on actual tallies, which should never exceed totalAllocs

* Versions get yer versions here

* Versions lookin like versions

* Mirage fixup

* Adds Remaining as an alloc chart status and adds historical status option

* Get tests passing again by making job status static for a sec

* Historical status panel click actions moved into their own component class

* job detail tests plz chill

* Testing if percy is fickle

* Hyper-specfic on summary distribution bar identifier

* Perhaps the 2nd allocSummary item no longer exists with the more accurate afterCreate data

* UI Test eschewing the page pattern

* Bones of a new acceptance test

* Track width changes explicitly with window-resize

* testlintfix

* Alloc counting tests

* Alloc grouping test

* Alloc grouping with complex resizing

* Refined the list of showable statuses

* PR feedback addressed

* renamed allocation-row to allocation-status-row

* [ui, job status] Make panel status mode a queryParam (#16345)

* queryParam changing

* Test for QP in panel

* Adding @Tracked to legacy controller

* Move the job of switching to Historical out to larger context

* integration test mock passed func

* [ui] Service job deployment status panel (#16383)

* A very fast and loose deployment panel

* Removing Unknown status from the panel

* Set up oldAllocs list in constructor, rather than as a getter/tracked var

* Small amount of template cleanup

* Refactored latest-deployment new logic back into panel.js

* Revert now-unused latest-deployment component

* margin bottom when ungrouped also

* Basic integration tests for job deployment status panel

* Updates complete alloc colour to green for new visualizations only (#16618)

* Updates complete alloc colour to green for new visualizations only

* Pale green instead of dark green for viz in general

* [ui] Job Deployment Status: History and Update Props (#16518)

* Deployment history wooooooo

* Styled deployment history

* Update Params

* lintfix

* Types and groups for updateParams

* Live-updating history

* Harden with types, error states, and pending states

* Refactor updateParams to use trigger component

* [ui] Deployment History search (#16608)

* Functioning searchbox

* Some nice animations for history items

* History search test

* Fixing up some old mirage conventions

* some a11y rule override to account for scss keyframes

* Split panel into deploying and steady components

* HandleError passed from job index

* gridified panel elements

* TotalAllocs added to deploying.js

* Width perc to px

* [ui] Splitting deployment allocs by status, health, and canary status (#16766)

* Initial attempt with lots of scratchpad work

* Style mods per UI discussion

* Fix canary overflow bug

* Dont show canary or health for steady/prev-alloc blocks

* Steady state

* Thanks Julie

* Fixes steady-state versions

* Legen, wait for it...

* Test fixes now that we have a minimum block size

* PR prep

* Shimmer effect on pending and unplaced allocs (#16801)

* Shimmer effect on pending and unplaced

* Dont show animation in the legend

* [ui, deployments] Linking allocblocks and legends to allocation / allocations index routes (#16821)

* Conditional link-to component and basic linking to allocations and allocation routes

* Job versions filter added to allocations index page

* Steady state legends link

* Legend links

* Badge count links for versions

* Fix: faded class on steady-state legend items

* version link now wont show completed ones

* Fix a11y violations with link labels

* Combining some template conditional logic

* [ui, deployments] Conversions on long nanosecond update params (#16882)

* Conversions on long nanosecond nums

* Early return in updateParamGroups comp prop

* [ui, deployments] Mirage Actively Deploying Job and Deployment Integration Tests (#16888)

* Start of deployment alloc test scaffolding

* Bit of test cleanup and canary for ungrouped allocs

* Flakey but more robust integrations for deployment panel

* De-flake acceptance tests and add an actively deploying job to mirage

* Jitter-less alloc status distribution removes my bad math

* bugfix caused by summary.desiredTotal non-null

* More interesting mirage active deployment alloc breakdown

* Further tests for previous-allocs row

* Previous alloc legend tests

* Percy snapshots added to integration test

* changelog
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