[caasp-beta] platform architecture and filesystem

[Flavio Castelli]

Starting from CaaSP v4 there's no special need to have a dedicated
subvolume for "/var/lib/kubelet". There's also no need to create a new
one for "/var/lib/crio"

We recommend to use the overlay graph driver both for docker, podman (on
standard SLE machines that are not part of CaaS Platform) and for CRI-O.
It's totally fine to use overlay over btrfs or other file systems; for
example our AutoYaST profile creates a /var partition that uses xfs.

We recommend to enable copy-on-write (COW) for the overall container
storage (/var/lib/containers), independently if it's btrfs or xfs.

To come back to what you wrote: it would be fine to keep /var on
subvolumes with no COW, and mount their device in /var/lib/containers,
which should enable COW.

I hope that helps.

Thanks
Flavio

On 9/9/19 4:30 PM, Le Bihan Stéphane (AMUNDI-ITS) wrote:
> Hi all,
> 
> In CAAS v3 we have dedicated devie for /var/lib/docker.
> 
> For Caas V4, we also want to use this device.
> But I see copy-and-write is disable for subvolume /var on base installation SLES15.
> 
> So, from your opinion, what is best solution :
> 
> ·         Keep /var on subvolumes with no copy-and-write, and mount device in /var/lib/container
> 
> ·         Mout device on /var (But I can see where in autoyast or other I can disble copy-and-write with no subvolume)
> 
> ·         Mount device on /var, create subvolume with no copy-ad-write for /var/lib/container, /var/lib/kubelet, /var/lib/crio etc ....
> 
> Regards,
> 
> 
> _______________________________________________
> caasp-beta mailing list
> caasp-beta at lists.suse.com
> Check the mailing list archives or Unsubscribe at http://lists.suse.com/mailman/listinfo/caasp-beta
>