Skip to content

Conversation

@irainia
Copy link
Member

@irainia irainia commented Dec 3, 2021

Context

There's a requirement to allow resource configuration in job for Optimus. It is mentioned in Optimus issue.

Changes

The change is only to add additional message, using it inside the job spec.

Comment on lines 258 to 266
message JobSpecResourceConfig {
string cpu = 1;
string memory = 2;
}

message JobSpecResource {
JobSpecResourceConfig request = 1;
JobSpecResourceConfig limit = 2;
}
Copy link
Member

Choose a reason for hiding this comment

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

Should we prefix them with Metadata? Resource is a term already used for something else in Optimus. It doesn't directly convey the message these are execution time resource limits/requests

Copy link
Member Author

Choose a reason for hiding this comment

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

Oh right. Then, are JobSpecMetadataResource and JobSpecMetadataResourceConfig good enough?

Copy link
Member

Choose a reason for hiding this comment

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

yeah sounds good.

Copy link
Member Author

Choose a reason for hiding this comment

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

it's updated as suggested

@kushsharma kushsharma merged commit b5ad9cf into main Dec 21, 2021
@kushsharma kushsharma deleted the optimus-job-resource branch December 21, 2021 05:15
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