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

Configure build CPU capacity #758

Closed
jithine opened this issue Oct 6, 2017 · 3 comments
Closed

Configure build CPU capacity #758

jithine opened this issue Oct 6, 2017 · 3 comments
Assignees

Comments

@jithine
Copy link
Member

jithine commented Oct 6, 2017

Context

As a pipeline owner, I want the ability to configure my build to be run on a machine with higher CPU capacity than what is allocated by default.

Objective

User builds running CPU intensive tasks should be allowed to configure higher CPU capacity.

Requirements

  1. User specifies in screwdriver.yaml user's CPU requirement
  2. Requirement can be specified at a job level or at a pipeline level
  3. If executor cannot honor user requirement then it should be communicated to user. (en entry is log should be okay)
  4. We could provide presets to user eg: HIGH_CPU/HIGH which could potentially be combined with other resource requirements (eg: memory/disk). Eg: HIGH could mean high capacity for cpu, disk & memory. HIGH_CPU could mean high capacity for CPU and default for everything else.
@tkyi
Copy link
Member

tkyi commented Nov 14, 2017

Daily summary 11/13:

Changes have been implemented and merged. Just needed to change hyperctl-image to take in CPU and memory arguments and to pass in that data in the executor-k8s-vm.

Currently working on verifying the changes.

@tkyi
Copy link
Member

tkyi commented Nov 15, 2017

Daily summary 11/14:

Tested out the new hyperctl image changes by running a build using the executor k8s-vm with job-level annotations:

annotations: 
            beta.screwdriver.cd/resource: HIGH

The CPU and memory were set to the "HIGH" settings, 6 vcpu and 12288 MB, respectively.

The initial work is considered done. Changes might be made in the future to tweak those values so they better suit our users' needs.

@tkyi
Copy link
Member

tkyi commented May 22, 2018

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

No branches or pull requests

3 participants