Support per-breed definitions and inheritance in distro_signatures.json

[alanoe]

Currently, several OS versions under a breed replicate the same fields (eg default_autoinstall). This change will minimize information duplication and decrease the signature file size.

[jmaas]

What would be great if it would be possible to override breed values down from the distro level. There are some outstanding bugs in buildiso because of differences in kopts in a single breed (opensuse/sles).

On the other hand i dont really like the json format at all, i'd rather see a more human friendly format like YAML being used; i once started prototyping this.. in this prototype i even got rid of the breed concept altogether. i should finish it and see if it would actually improve matters..

[alanoe]

JM> What would be great if it would be possible to override breed values down from the distro level.

I do not understand exactly what you mean, Jörgen. distro level = distro OS version (eg sles12) level ? If so, my proposal will do what you suggest.

Currently all attributes in distro_signatures.json are already associated with an os_version. My proposal is to allow distro signatures file to also have attributes in the breed level and combine breed and os versions attributes during distro signatures file parsing. An attribute in os_version would override an attribute in breed, as Cobbler already does for distro-profile-system.

[SchoolGuy]

The specification and import of this won't be mainted here but instead in the library created for it. I will thus transfer this issue there.

[SchoolGuy]

I believe that this can be solved if we have a special version which is called default in each breed which collects the default of each breed.