Project

General

Profile

Actions
Copy link

Feature #14311

closed

ovh jobs needs to run with larger disks if radosbench is found in the final yaml

Added by Samuel Just over 8 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
-
Category:
-
% Done:

0%

Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:

Description

I'm not sure what the cleanest way to do this would be. One way would be to add some kind of override we could add to radosbench.yaml which would be picked up by the openstack provisioning process. Another more hacky option might be to just scan the yaml during suite scheduling and change the ovh provisioning setting. Not sure. I don't think we want to increase the size globally, but we also don't want to make all jobs small enough to run in 30G (smithi has 100G -- that should be our max). There also may be future yamls that need more space, so I'd lean towards the override in radosbench.yaml approach.

Actions
Copy link
 #1

Updated by Samuel Just over 8 years ago

some kind of

override:
  provisioning:
    min_osd_space: 100G

we can put in yamls that need it.

Actions
Copy link
 #2

Updated by Samuel Just over 8 years ago

  • Status changed from New to Resolved

some kind of

override:
provisioning:
min_osd_space: 100G

we can put in yamls that need it.

Actions
Copy link
 #3

Updated by Nathan Cutler over 8 years ago

Sam, what PR/commit resolved this?

Actions
Copy link

Also available in: Atom PDF