jberkus added a new comment to an issue you are following:
So, there's two questions here:
Aha, thanks. Seems like DOCKER_ROOT_VOLUME should default to "on" then if
we're going to do partitioning. That leaves us with two questions:
1) What do we feel is the best default settup for an overlay-based system?
2) Do we need to support switch-back to devicemapper on a running system?
For (1), what I'm concerned about with partition-by-default is that it tends to make a
no-options-simple install unusable; that is, it *requires* getting the user involved with
partitioning on the first Atomic Host they install. This is because we can't
dynamically size the rootfs volume based on available space, so we end up with the default
too-small 3GB we currently have. Personally, I can't imagine any automated
configuration of two partitions which wouldn't require the user to make decisions
about partitioning, even in simple cases.
So what I'm saying is that, while serious production users are going to want separate
partitions, we should consider leaving that up to those who are willing to feed cloud-init
(or Kickstart) parameters, and know their expected disk usage. And that the default
should be "one big shared volume", because that's the only "zero
information" decision we can make.
However, if we need to support (2), then this kind of decides it for us. I'm not sure
that we do, though. Arguments?
To reply, visit the link below or just reply to this email