Is there a change to include to nmstate repos, like in
https://gerrit.ovirt.org/#/c/104143/23/common/yum-repos/ovirt-master-host-cq.repo.in
?

Even nmstate might be not enabled by default in the alpha, but if the repos
would be enabled, the user could comfortably
enable nmstate by
engine-config --set VdsmUseNmstate=true

On Thu, Nov 21, 2019 at 3:29 PM Sandro Bonazzola <[email protected]>
wrote:

> While waiting for CentOS Linux 8.1 to be released, we are now preparing an
> alpha compose that will be made available on top of CentOS Linux 8.0.
> I'm starting gathering the builds to be included in the alpha release with
> the first commit here: https://gerrit.ovirt.org/#/c/104880/
> If you want a specific version to be included in alpha please push a
> patch updating the release configuration file.
> For needed packages that won't be included in the release file, latest
> build passing CI tests will be included in the compose.
>
> Thanks,
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>
> Red Hat EMEA <https://www.redhat.com/>
>
> [email protected]
> <https://www.redhat.com/>*Red Hat respects your work life balance.
> Therefore there is no need to answer this email out of your office hours.*
> _______________________________________________
> Devel mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/[email protected]/message/ASUCLLCCSKUCUAY3LRNLBE55YQ3O3XG7/
>
_______________________________________________
Devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/XVLVRN2CYKLCPRDEYDW4V2C4GSBNBWVN/

Reply via email to