On Mon, 2017-10-09 at 11:39 +0100, Daniel P. Berrange wrote:
On Fri, Oct 06, 2017 at 02:48:36PM +0200, Andrea Bolognani wrote:
> Changes from [v1]:
>
> * drop support for building projects;
> * reduce redundancy by using mappings;
> * add FreeBSD 10 support.
>
> [v1]
https://www.redhat.com/archives/libvir-list/2017-October/msg00035.html
>
> Andrea Bolognani (16):
> ansible: Initial support
> ansible: Add libosinfo project
> ansible: Add libvirt project
> ansible: Add libvirt-cim project
> ansible: Add libvirt-glib project
> ansible: Add libvirt-go project
> ansible: Add libvirt-go-xml project
> ansible: Add libvirt-perl project
> ansible: Add libvirt-python project
> ansible: Add libvirt-sandbox project
> ansible: Add libvirt-tck project
> ansible: Add osinfo-db project
> ansible: Add osinfo-db-tools project
> ansible: Add virt-manager project
> ansible: Add virt-viewer project
> ansible: Install and configure Jenkins agent
ACK to all patches on the basis that I don't know ansible but nothing
looks bad from a naive POV.
That's good enough for me. Pushed :)
One thing the current builders have setup is a cron job to do a
nightly
yum update (or equiv). I'm not sure whether this belongs in Ansible or
in prior kickstart file ?
Oh, I was not aware of that.
There are two ways we can approach this:
a) have Ansible set up the necessary cron jobs;
b) run the Ansible playbook from the host instead.
I'd rather go with b) since the playbook already upgrades all
installed packages as part of setting up the base system.
--
Andrea Bolognani / Red Hat / Virtualization