[PATCH 3/3 rhel7-branch] atomic: set up atomic specific partitioning defaults

Colin Walters walters at verbum.org
Wed Oct 22 15:02:27 UTC 2014


On Wed, Oct 22, 2014, at 09:58 AM, Chris Lumens wrote:

> Well, the point of that first patch from me here (which references bug
> 1138820) was to provide a mechanism to allow them to set that default
> for just a single product.  There's been no further work along those
> lines, nor talk in the bug, so I imagine it's still not implemented.
> But it certainly ought to be easy to do so now.

Makes sense.  Maybe ping sgallagh to see if he can make F21 Server use
it now?

> --fstype is there to define the formatting used.  Think of it as the
> string you would add after "mkfs." to make a filesystem.  Perhaps --type
> is more what you're thinking of, given that it is used to define what
> kind of scheme you want?  

That sounds right.

> I'm not sure why a new autopart argument would
> be handy here, though.

There are two crosscutting things:

1) We want this partitioning layout to apply *by default* to install
media for [distribution] Atomic.

2) I would like to allow the many people who won't want the rpm-ostree
part of Atomic (yet), but *do* want a Docker-optimized system to be able
to easily set that up.  Right now, it's not *too* hard to do in a
kickstart, but the thing with kickstart is (afaik) it's hard to perform
dynamic computation based on the install media size or layout - you end
up needing to template kickstarts on the server side based on the
install host target, etc.  

If we can get an "autopart --type=docker" verb or so that has good
Docker defaults, I imagine it would have good uptake.


More information about the anaconda-patches mailing list