Repository navigation
Replies: 1 comment
|
@holmanb @blackboxsw Can you help me look at this idea? I haven't figured out how to design a good configuration file that is compatible with the previous resize_rootfs configuration,Do you have any good ideas |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Cloud-init currently has two modules related to partition and filesystem expansion:
growpartexpands partitions and supports multiple entries throughgrowpart.devices.resizefsexpands the filesystem, but it is controlled only byresize_rootfs, so it can resize only the root filesystem.For example:
In this configuration,
growpartexpands the partitions backing both/and/data, butresizefsexpands only the filesystem mounted at/. The filesystem mounted at/dataremains unchanged, so users must resize it separately.I would like to propose adding support for multiple filesystems to the
resizefsmodule, aligned with thedevicesconfiguration supported bygrowpart.One possible configuration could be:
The entries could use the same format and resolution rules as
growpart.devices, such as mount points or device paths.For backward compatibility,
resize_rootfsshould continue to work as it does today. If the new configuration is not specified, the current behavior would remain unchanged. We would also need to define the behavior when bothresize_rootfsand the new configuration are present.All reactions