-
Notifications
You must be signed in to change notification settings - Fork 76
Revert "ore: Introspect disk for size rather than hardcode 8GB" #948
Revert "ore: Introspect disk for size rather than hardcode 8GB" #948
Conversation
It breaks all cases that don't include an explicit --file argument, including --source-object, --source-snapshot, and using the latest build from the CL SDK. Revert for now. This reverts commit 8244c5d.
LGTM, will look at fixing this in a next attempt. |
😆 I see you noticed my branch name... OK so what was our thought on fixing this? We could only do it if |
I think it'd be cleanest for the size to be the larger of:
Unfortunately that requires a nontrivial amount of new code. |
One thing I don't quite understand is the use cases for the latter two. Are they used today in CL? The flow we have for RHCOS at least today is to upload via a file to a single region, get an AMI, then use AWS' builtin region-copy API (which is what plume is doing I believe). So at least we don't need object/snapshot bits (we always pass How about |
Remember, ore is a development tool, not a production tool. I don't think anyone actively uses them, but they might be useful for working with images in various stages of creation.
I'm not thrilled with lack of consistency across image sources, but I can live with it. We should still have the manual option though:
|
We want to expand the disk size of Red Hat CoreOS; previously there was a hardcoded 8GiB size for Container Linux which (I believe entirely coincidentally) matched RHCOS. See coreos#948 and coreos#944
We want to expand the disk size of Red Hat CoreOS; previously there was a hardcoded 8GiB size for Container Linux which (I believe entirely coincidentally) matched RHCOS. See coreos#948 and coreos#944
We want to expand the disk size of Red Hat CoreOS; previously there was a hardcoded 8GiB size for Container Linux which (I believe entirely coincidentally) matched RHCOS. See coreos#948 and coreos#944
We want to expand the disk size of Red Hat CoreOS; previously there was a hardcoded 8GiB size for Container Linux which (I believe entirely coincidentally) matched RHCOS. See coreos#948 and coreos#944
It breaks all cases that don't include an explicit
--file
argument, including--source-object
,--source-snapshot
, and using the latest build from the CL SDK. Revert for now.This reverts commit 8244c5d.
cc @cgwalters