On Fri, Sep 20, 2019 at 12:01 PM Merlin Mathesius <mmathesi@redhat.com> wrote:


On Fri, Sep 20, 2019 at 11:28 AM Stephen Gallagher <sgallagh@redhat.com> wrote:
On Wed, Sep 11, 2019 at 1:38 PM Kevin Fenzi <kevin@scrye.com> wrote:
>
> On 9/10/19 1:57 PM, Merlin Mathesius wrote:
> > Please review the attached patch to add a new file to
> > https://infrastructure.fedoraproject.org/cgit/ansible.git/.
> >
> > This patch provides a new platform:el8 default module definition so
> > fm-orchestrator knows about EPEL8. Some review and discussion has already
> > taken place at https://pagure.io/Fedora-Infra/ansible/pull-request/40.
> >
> > The contents are based on the current Fedora platform module definitions
> > plus the rpm profiles from the package groups found in
> > https://kojipkgs.fedoraproject.org/repos/epel8-infra-build/latest/groups/comps.xml
> > .
> >
> > Note: I'm starting with just this platform:el8 module definition for
> > staging MBS. Once we're happy with it, it can be replicated for
> > platform:el8-playground. Then, when ready, they can be copied to production.
>
> Looks ok to me. +1
>

Same here. +1

Since this seems to be well received so far, here's a patch with platform:el8-playground...

Merlin

Hi, all,

Since folks seem to be happy with the el8 platform virtual module definitions, can they be merged and deployed to staging--or does something else need to happen first? (Of course, any module builds based on platform:el8* won't be usable until there are corresponding pungi configs.)

Thanks.

Merlin