arm: create COS_PERSISTENT instead of COS_OEM

[mudler]

Add a cloud-init also to automatically expand the COS_PERSISTENT
partition on first boot.

Tied to #930

Still testing it

Signed-off-by: Ettore Di Giacinto edigiacinto@suse.com

[davidcassany]

Cool, with this you are not loosing OEM functionality, you can still plug a USB having the OEM label with some custom cloud init data and it would be executed.

Note you are forgetting to update examples/odroid-c2/files/system/oem/01_layout.yaml

[mudler]

Cool, with this you are not loosing OEM functionality, you can still plug a USB having the OEM label with some custom cloud init data and it would be executed.

Note you are forgetting to update examples/odroid-c2/files/system/oem/01_layout.yaml

Good catch, I actually forgot to commit its deletion 😓

[mudler]

Oh wait, I did commit it, I've deleted both layout files as now cOS defaults should be good

[mudler]

This might need rancher-sandbox/cos-toolkit-docs#67

[mudler]

seems adding rd.cos.oemlabel=COS_OEM to bootargs doesn't help. Still dropping to emergency shell from dracut

[mudler]

ok, seems to boot when creating an COS_OEM (even from an .img file). So looks like entries listed in VOLUMES in layout.env, once specified are mandatory. I'll create a layout file to disable oem entirely

[mudler]

@davidcassany needs a re-review please as things changed slightly. It looks like the OEM partition is required if specified in VOLUMES in the layout.env file. I have still to test the recent commit, although would make sense to offer a way to mount certain paths 'optionally' like COS_OEM, in that case we can still support the scenarios of plugging an USB stick and load cloud config files from there.

Is there a way to override the default ? by looking at the code at a quick glance I didn't noticed, but not sure if I might have missed something

[mudler]

ok so after discussing with @davidcassany OEM gets tried to be mounted by default even if not specified inside VOLUMES. Adding it in volumes makes it a required mount. That means we can't rely on cOS defaults for ARM here, hence why the specific cloud-config file which overrides the layout

[mudler]

ok now booting works. However automatic resizing of COS_PERSISTENT it doesn't. Fails silently here with an exit 2. I'd say to merge this and create a follow-up for the partition resizing as it is out of purpose (and can be workarounded easily after image creation too).