-
Notifications
You must be signed in to change notification settings - Fork 15
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
Refactoring and fixing issues with job requests types #300
Refactoring and fixing issues with job requests types #300
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
new_obj._memory_size = memory | ||
new_obj._allocation_paradigm = paradigm | ||
new_obj._allocation_priority = priority | ||
#new_obj._cpu_count = cpus |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like these comments can be removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've cleaned those up now.
934adb4
to
524a89c
Compare
Modifying class supertype, then updating __init__ and adding necessary properties.
- Updating class __init__ to require params previously taken from (already present) job_request param to conform to standard pattern used in class hierarchies - Adding convenience class method to factory create an instance with just the originating message, which __init__ previously did - Updating deserialization to account for above changes
Updating interface definition and existing implementation of job manager create_job function to have a fixed, required 'request' parameter of a type extending DmodJobRequest.
Updating dmod.client to depend on dmod.communication>=0.11.0.
Fixing init to properly handle args passed to super init.
Make sure value from passed model_request is used if no explicit 'config_data_id' is passed, while also ensuring an explicit value matches if it is provided.
f7c7ee3
to
a4a7b50
Compare
create_job
in JobManager interface and implementations to expect a DmodJobRequestNote that this supersedes #277. It is essentially the same change set rebased onto the current master commit.