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

 ansible/.gitignore                                 |   3 +
 ansible/Makefile                                   |  12 +
 ansible/README.markdown                            |  60 ++
 ansible/ansible.cfg                                |   9 +
 ansible/bootstrap.yml                              |  15 +
 ansible/group_vars/all/main.yml                    |  10 +
 ansible/host_vars/libvirt-centos-6/main.yml        |  10 +
 ansible/host_vars/libvirt-centos-6/vault.yml       |  10 +
 ansible/host_vars/libvirt-centos-7/main.yml        |  19 +
 ansible/host_vars/libvirt-centos-7/vault.yml       |  10 +
 ansible/host_vars/libvirt-debian-8/main.yml        |  17 +
 ansible/host_vars/libvirt-debian-8/vault.yml       |  10 +
 ansible/host_vars/libvirt-debian-9/main.yml        |  19 +
 ansible/host_vars/libvirt-debian-9/vault.yml       |  10 +
 ansible/host_vars/libvirt-fedora-25/main.yml       |  20 +
 ansible/host_vars/libvirt-fedora-25/vault.yml      |  10 +
 ansible/host_vars/libvirt-fedora-26/main.yml       |  20 +
 ansible/host_vars/libvirt-fedora-26/vault.yml      |  10 +
 ansible/host_vars/libvirt-fedora-rawhide/main.yml  |  20 +
 ansible/host_vars/libvirt-fedora-rawhide/vault.yml |  10 +
 ansible/host_vars/libvirt-freebsd-10/main.yml      |  25 +
 ansible/host_vars/libvirt-freebsd-10/vault.yml     |  10 +
 ansible/host_vars/libvirt-freebsd-11/main.yml      |  25 +
 ansible/host_vars/libvirt-freebsd-11/vault.yml     |  10 +
 ansible/host_vars/libvirt-ubuntu-12/main.yml       |   7 +
 ansible/host_vars/libvirt-ubuntu-12/vault.yml      |   8 +
 ansible/host_vars/libvirt-ubuntu-14/main.yml       |  14 +
 ansible/host_vars/libvirt-ubuntu-14/vault.yml      |   8 +
 ansible/host_vars/libvirt-ubuntu-16/main.yml       |  18 +
 ansible/host_vars/libvirt-ubuntu-16/vault.yml      |   8 +
 ansible/inventory                                  |   9 +
 ansible/site.yml                                   |  27 +
 ansible/tasks/base.yml                             | 108 ++++
 ansible/tasks/bootstrap.yml                        |  22 +
 ansible/tasks/compat.yml                           |  31 +
 ansible/tasks/jenkins.yml                          |  59 ++
 ansible/tasks/packages.yml                         |  66 ++
 ansible/templates/jenkins.service.j2               |  14 +
 ansible/vars/mappings.yml                          | 684 +++++++++++++++++++++
 ansible/vars/projects/base.yml                     |  17 +
 ansible/vars/projects/jenkins.yml                  |   3 +
 ansible/vars/projects/libosinfo.yml                |  15 +
 ansible/vars/projects/libvirt-cim.yml              |   8 +
 ansible/vars/projects/libvirt-glib.yml             |   8 +
 ansible/vars/projects/libvirt-go-xml.yml           |   3 +
 ansible/vars/projects/libvirt-go.yml               |   3 +
 ansible/vars/projects/libvirt-perl.yml             |   8 +
 ansible/vars/projects/libvirt-python.yml           |   8 +
 ansible/vars/projects/libvirt-sandbox.yml          |  14 +
 ansible/vars/projects/libvirt-tck.yml              |  21 +
 ansible/vars/projects/libvirt.yml                  |  78 +++
 ansible/vars/projects/osinfo-db-tools.yml          |   8 +
 ansible/vars/projects/osinfo-db.yml                |   4 +
 ansible/vars/projects/virt-manager.yml             |   7 +
 ansible/vars/projects/virt-viewer.yml              |  10 +
 55 files changed, 1672 insertions(+)
 create mode 100644 ansible/.gitignore
 create mode 100644 ansible/Makefile
 create mode 100644 ansible/README.markdown
 create mode 100644 ansible/ansible.cfg
 create mode 100644 ansible/bootstrap.yml
 create mode 100644 ansible/group_vars/all/main.yml
 create mode 100644 ansible/host_vars/libvirt-centos-6/main.yml
 create mode 100644 ansible/host_vars/libvirt-centos-6/vault.yml
 create mode 100644 ansible/host_vars/libvirt-centos-7/main.yml
 create mode 100644 ansible/host_vars/libvirt-centos-7/vault.yml
 create mode 100644 ansible/host_vars/libvirt-debian-8/main.yml
 create mode 100644 ansible/host_vars/libvirt-debian-8/vault.yml
 create mode 100644 ansible/host_vars/libvirt-debian-9/main.yml
 create mode 100644 ansible/host_vars/libvirt-debian-9/vault.yml
 create mode 100644 ansible/host_vars/libvirt-fedora-25/main.yml
 create mode 100644 ansible/host_vars/libvirt-fedora-25/vault.yml
 create mode 100644 ansible/host_vars/libvirt-fedora-26/main.yml
 create mode 100644 ansible/host_vars/libvirt-fedora-26/vault.yml
 create mode 100644 ansible/host_vars/libvirt-fedora-rawhide/main.yml
 create mode 100644 ansible/host_vars/libvirt-fedora-rawhide/vault.yml
 create mode 100644 ansible/host_vars/libvirt-freebsd-10/main.yml
 create mode 100644 ansible/host_vars/libvirt-freebsd-10/vault.yml
 create mode 100644 ansible/host_vars/libvirt-freebsd-11/main.yml
 create mode 100644 ansible/host_vars/libvirt-freebsd-11/vault.yml
 create mode 100644 ansible/host_vars/libvirt-ubuntu-12/main.yml
 create mode 100644 ansible/host_vars/libvirt-ubuntu-12/vault.yml
 create mode 100644 ansible/host_vars/libvirt-ubuntu-14/main.yml
 create mode 100644 ansible/host_vars/libvirt-ubuntu-14/vault.yml
 create mode 100644 ansible/host_vars/libvirt-ubuntu-16/main.yml
 create mode 100644 ansible/host_vars/libvirt-ubuntu-16/vault.yml
 create mode 100644 ansible/inventory
 create mode 100644 ansible/site.yml
 create mode 100644 ansible/tasks/base.yml
 create mode 100644 ansible/tasks/bootstrap.yml
 create mode 100644 ansible/tasks/compat.yml
 create mode 100644 ansible/tasks/jenkins.yml
 create mode 100644 ansible/tasks/packages.yml
 create mode 100644 ansible/templates/jenkins.service.j2
 create mode 100644 ansible/vars/mappings.yml
 create mode 100644 ansible/vars/projects/base.yml
 create mode 100644 ansible/vars/projects/jenkins.yml
 create mode 100644 ansible/vars/projects/libosinfo.yml
 create mode 100644 ansible/vars/projects/libvirt-cim.yml
 create mode 100644 ansible/vars/projects/libvirt-glib.yml
 create mode 100644 ansible/vars/projects/libvirt-go-xml.yml
 create mode 100644 ansible/vars/projects/libvirt-go.yml
 create mode 100644 ansible/vars/projects/libvirt-perl.yml
 create mode 100644 ansible/vars/projects/libvirt-python.yml
 create mode 100644 ansible/vars/projects/libvirt-sandbox.yml
 create mode 100644 ansible/vars/projects/libvirt-tck.yml
 create mode 100644 ansible/vars/projects/libvirt.yml
 create mode 100644 ansible/vars/projects/osinfo-db-tools.yml
 create mode 100644 ansible/vars/projects/osinfo-db.yml
 create mode 100644 ansible/vars/projects/virt-manager.yml
 create mode 100644 ansible/vars/projects/virt-viewer.yml

-- 
2.13.6

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

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

BTW, what's your thoughts on what we should do with this once committed ?

Do you have plans to rebuild all our current CI VMs from scratch
using these recipes ? It would probably nice todo this so we get
them into a known good state, as well as helping us move the
Fedora vms onto current versions.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

On Fri, 2017-10-06 at 14:29 +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
> 
> BTW, what's your thoughts on what we should do with this once committed ?
> 
> Do you have plans to rebuild all our current CI VMs from scratch
> using these recipes ? It would probably nice todo this so we get
> them into a known good state, as well as helping us move the
> Fedora vms onto current versions.

Definitely.

The idea would be to build a Fedora 26 worker, set it up using the
Ansible automation and add it to the Jenkins setup; there might be
some minor kinks to iron out before all jobs can run successfully.

Once that's done, we can start replacing existing workers one by
one, and finally expand the test matrix to its fullest potential.

-- 
Andrea Bolognani / Red Hat / Virtualization

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

On Fri, Oct 06, 2017 at 02:29:44PM +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
> 
> BTW, what's your thoughts on what we should do with this once committed ?
> 
> Do you have plans to rebuild all our current CI VMs from scratch
> using these recipes ? It would probably nice todo this so we get
> them into a known good state, as well as helping us move the
> Fedora vms onto current versions.

Yes, we are planning to do that, actually I'll be the one who will
rebuild all the VMs.  I'm also planning to prepare template kickstart
for Fedora to automate it even more.

Pavel
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

On Fri, Oct 06, 2017 at 04:53:34PM +0200, Pavel Hrdina wrote:
>On Fri, Oct 06, 2017 at 02:29:44PM +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
>>
>> BTW, what's your thoughts on what we should do with this once committed ?
>>
>> Do you have plans to rebuild all our current CI VMs from scratch
>> using these recipes ? It would probably nice todo this so we get
>> them into a known good state, as well as helping us move the
>> Fedora vms onto current versions.
>
>Yes, we are planning to do that, actually I'll be the one who will
>rebuild all the VMs.  I'm also planning to prepare template kickstart
>for Fedora to automate it even more.
>
>Pavel

Actually, we've been also thinking to add a Vagrantfile into our libvirt
repository that would be able to create build VMs with various development
environments (FreeBSD, fedora, debian, etc.) and we could utilize these Ansible
scripts to provision those machines.  Newbies could easily try out libvirt
without changing their system and anyone who wants to test the hell out of their
changes would just do with circa 3 commands.

>--
>libvir-list mailing list
>libvir-list@redhat.com
>https://www.redhat.com/mailman/listinfo/libvir-list

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

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.

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 ?

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

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

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

On Mon, Oct 09, 2017 at 01:58:45PM +0200, Andrea Bolognani wrote:
> 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.

I dont mind as long as the packages get updated daily.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list