On Oct 27, 2016 8:05 AM, "Stephen Gallagher" <sgallagh(a)redhat.com> wrote:
On 10/27/2016 06:04 AM, Subhendu Ghosh wrote:
> Another option is to leave the VARIANT same, but introduce a new var
like
> MANAGED= and then key of that for cockpit vs Ansible vs Puppet,
etc.
>
The issue here is entirely one of the default firewall, which is
delivered as a
single XML file at install-time. (Modifications can be made after the
fact,
which is the point of option 2 in my original message).
Right now, we have a policy[1] on how to get different defaults landed on
the
system for different install targets. This is all predicated on
having
different
VARIANT_ID values that triggers the installation of the correct
file.
In any case, adding MANAGED to os-release would be an incorrect use of
that
file. The purpose of it is to indicate vendor-provided data about a
system.
Having a Variant for every configuration flavor shipped by the vendor seems
wrong. It will cause variant sprawl.
The variant is the product, the different pre-defined configurations do
not make them different products. There should be a second marker for the
flavor of the product.