On Mon, 2013-11-18 at 20:21 -0500, Stephen Gallagher wrote:
== FOS, FOSSP and Roles ==
One place where we very clearly had some confusing terminology is in
terms of the three layers that Jóhann is proposing in this thread.
Part of the confusion comes from the classic ambiguity between "core"
and "base" that we have in Fedora today. For the non-native English
speakers reading this, these two words are basically synonyms, but in
the context of Fedora, "core" has generally meant the "minimal"
install of Fedora and "base" something like the standard headless
Jóhann then added new terms, FOS (Fedora OS) and FOSSP (Fedora OS
Server Platform) and proceeded to use the terms interchangably with
"core" and "base", respectively. It had been unclear to me prior to
our conversation today that FOSSP == "base for the Fedora Server".
So to first clarify those three layers as Jóhann defines them:
FOS: Analagous to "core" from traditional Fedora. Should essentially
contain the absolute minimal set of functionality necessary to install
the bits, get a shell and install software on a running machine. This
is what he expects as output from the Base WG.
Is this what BaseWG had in mind ?
I suspect they called it BaseWG because they intend to create a base,
not a core image.
FOSSP: Analagous to "base" from traditional Fedora. This
should be the
platform delivered by the Fedora Server. It should provide all of the
foundational pieces necessary to support the deployment of the
Why do we need to have different bases per product ?
What do people expect to be different between the various 'bases' ?
I fear that building a per-product base would quickly make the 3
products not able to share other packages and diverge too much,
effectively forking the distribution in 3 incompatible sets.
FOSSP Roles: Individual services installable by API as described
above, ideally isolated on the target system.
I think I would say 'optionally' isolate, rather than 'ideally'.
Not that I do not want them to be able to run in isolation, but that
should be an informed decision of the Administrator and not forced on by
Simo Sorce * Red Hat, Inc * New York