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: set memory max for oversubscription. #10309

Closed
wants to merge 2 commits into from
Closed

Conversation

notnoop
Copy link
Contributor

@notnoop notnoop commented Apr 6, 2021

Display reserved vs max memory for allocations/tasks with memory oversubscription, introduced in #10247 .

Implements the alloc/task display memory info part of #10268 .

Needless to say, I very much lack javascript experience, and I'm unfamiliar with frontend patterns, so feel free to ignore the PR and do it the "proper" way and I can learn by watching it. Thanks!

For a task with memory_max set, here are the screen shots:
Screen Shot 2021-04-06 at 12 09 09 PM

After:

Screen Shot 2021-04-06 at 12 10 29 PM

Comment on lines 78 to 79
console.log(find('.annotation').innerText);
assert.ok(find('.annotation').innerText.includes('/ 256 MiB reserved, 512 MiB max'));
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've struggled with getting this test to pass - I always get 0 MiB / 0 MiB reserved. I get the same text in the above test as well. Would love pointers for how to set it up.

Copy link
Contributor

Choose a reason for hiding this comment

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

Since the template uses @allocation={{this.resource}} I think your property-setting call would need to be this.setProperties({ resource: alloc, metric: 'memory'}). But also I think alloc should be extracted from the job created with the resourceSpec vs created anew. I could pair with you on this if you like?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Apparently, the issue was a bit gnarlier than that - the tracker spy/mock didn't actually fill-in the annotation info, and there is something odd about the mirage creation if multiple jobs/annotations are in play. Anyways, I took out the test, and would love to have a frontend engineer take over if possible :( sorry!

@github-actions
Copy link

github-actions bot commented Apr 6, 2021

Ember Asset Size action

As of 1eee305

Files that got Bigger 🚨:

File raw gzip
nomad-ui.js +1.74 kB +349 B

Files that stayed the same size 🤷‍:

File raw gzip
vendor.js 0 B 0 B
nomad-ui.css 0 B 0 B
vendor.css 0 B 0 B

@github-actions
Copy link

github-actions bot commented Apr 6, 2021

Ember Test Audit comparison

main 1eee305 change
passes 1078 1079 +1
failures 0 0 0
flaky 0 0 0
duration 8m 20s 165ms 8m 44s 008ms +23s 843ms

@notnoop notnoop changed the title set memory max for oversubscription. UI: set memory max for oversubscription. Apr 8, 2021
@vercel vercel bot temporarily deployed to Preview – nomad April 13, 2021 19:13 Inactive
@notnoop
Copy link
Contributor Author

notnoop commented Apr 27, 2021

Closing, superseded by #10459 .

@notnoop notnoop closed this Apr 27, 2021
@backspace
Copy link
Contributor

#10459 isn’t quite the same as this, I just wanted to start with the bare minimum given the time constraints 😳

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 24, 2022
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.

2 participants