On Thu, 2019-10-17 at 14:44 -0600, Orion Poplawski wrote: > On 10/17/19 2:35 PM, Adam Williamson wrote: > > On Thu, 2019-10-17 at 09:32 -0700, John M. Harris Jr wrote: > > > On Thursday, October 17, 2019 1:59:19 AM MST Alexander Bokovoy wrote: > > > > The one thing we are using default modular stream in RHEL 8 for is to be > > > > able to provide access to packages in kickstart that were moved to > > > > modules in RHEL 8. An example is idm:client stream which is a default > > > > module stream in RHEL 8 exactly for this reason, to be able to install > > > > ipa-client package and enroll a system into IPA from a kickstart file. > > > > > > > > We don't package FreeIPA in modules in Fedora yet but this is one of > > > > real examples how default module streams are helpful to maintain > > > > coherent user experience for existing users of kickstart files. > > > > > > > > -- > > > > / Alexander Bokovoy > > > > Sr. Principal Software Engineer > > > > Security / Identity Management Engineering > > > > Red Hat Limited, Finland > > > > > > You could install the ipa-client package and enroll a system into IPA from a > > > kickstart in RHEL 7 too.. Without modules. That's what I've deployed for the > > > environments I support, for example. Using a module is not required there. > > > > That wasn't the point, though - the point was the answer the question > > "why do we need *default* module streams?" > > > > The logic is this: FreeIPA maintainers wanted FreeIPA to be a module in > > RHEL, to take advantage of the added flexibility around lifecycles and > > version bumps (basically so each RHEL release isn't tied to one version > > of FreeIPA forever). But if it's modularized and there's no concept of > > 'default stream modules', this is a thing that breaks: you can't > > install it from a kickstart. So, *given that* we wanted to modularize > > FreeIPA in RHEL *and* we also want to still make it deployable via > > kickstart, that creates a requirement for default stream modules or > > something a lot like it. > > This doesn't seem quite true. You couldn't install it with the same kickstart > you used for EL7, but you could use the new module command or syntax in kickstart: Indeed, you can install modules via kickstart. For details, see: https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#chapter-9-package-selection https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#module > > module --name=NAME [--stream=STREAM] This just enables a module stream (or can explicitely disable it with the --disable option). No packages will be installed from such module unless specified in the %packages section. > > and/or > > %packages > @module:stream/profile This enables the module stream and installs a profile - the one specified or the default profile otherwise. The syntax is pretty much the same as for DNF CLI - if you call "dnf install @module:stream/profile" you should get the same result. > > > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
