diff options
| author | Chris Evich <cevich@redhat.com> | 2022-06-13 12:12:13 -0400 |
|---|---|---|
| committer | Chris Evich <cevich@redhat.com> | 2022-07-01 11:25:47 -0400 |
| commit | f58d7dbdab7076d1ff83375fdbc010445261c0cd (patch) | |
| tree | fd9ca0b4542e31a9927006c27732f5338adc1642 /cmd/podman | |
| parent | b00e65aa9c071428579a55f91a92f3702765ed85 (diff) | |
| download | podman-f58d7dbdab7076d1ff83375fdbc010445261c0cd.tar.gz podman-f58d7dbdab7076d1ff83375fdbc010445261c0cd.tar.bz2 podman-f58d7dbdab7076d1ff83375fdbc010445261c0cd.zip | |
Cirrus: Fix elevator workaround multi-cloud support
In order to support execution on various non-GCP cloud environments, the
BFQ scheduler workaround needs updating. Previously it assumed the root
disk was always `/dev/sda`. With the addition of new clouds (AWS) and
different environment types, the assumption is not always valid. Update
the workaround to take care in looking up the block device where '/'
comes from.
Also update the scheduler to 'none', as all modern clouds already have
highly optimized underlying storage configurations. There's no reason
to complicate I/O paths further by hard-coding specific scheduler(s) for
all environment types.
Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to 'cmd/podman')
0 files changed, 0 insertions, 0 deletions