Howdy, Since I didn't find anything searching around, I decided to start implementing a dynamic inventory script for Lago for my local environment while trying to keep it as generic as possible. If you'd be interested I'd like to share it and get feedback but I am not sure where is the best place for me to place it or offer it to Lago via a PR.

On Wed, Jun 15, 2016 at 7:56 AM, Barak Korren <bkorren(a)redhat.com&gt; wrote: > On 15 June 2016 at 14:50, Eric Helms <ehelms(a)redhat.com&gt; wrote: > > Howdy, > > > > Since I didn't find anything searching around, I decided to start > > implementing a dynamic inventory script for Lago for my local environment > > while trying to keep it as generic as possible. If you'd be interested > I'd > > like to share it and get feedback but I am not sure where is the best > place > > for me to place it or offer it to Lago via a PR. > > > > Not sure what you mean by, "dynamic inventory". > See [1] for official reference. Instead of writing a static inventory script of hostnames, IPs and groupings Ansible allows writing a script to be run that produces that information dynamically. [1] http://docs.ansible.com/ansible/intro_dynamic_inventory.html

> > -- > Barak Korren > bkorren(a)redhat.com > RHEV-CI Team >

_______________________________________________ lago-devel mailing list lago-devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/lago-devel

>> >> See [1] for official reference. Instead of writing a static inventory >> script of hostnames, IPs and groupings Ansible allows writing a script to >> be run that produces that information dynamically. >> Ah ok. I failed to realise that was in the Ansible context. +1 from me as well. Could we also assign server roles/Ansible variable from the Lago YAML? Would we want to?

-- Barak Korren bkorren(a)redhat.com RHEV-CI Team

On 15 June 2016 at 15:41, Eric Helms <ehelms(a)redhat.com&gt; wrote: > > > On Wed, Jun 15, 2016 at 8:20 AM, Barak Korren <bkorren(a)redhat.com&gt; wrote: >> >> >> >> >> See [1] for official reference. Instead of writing a static inventory >> >> script of hostnames, IPs and groupings Ansible allows writing a script >> >> to >> >> be run that produces that information dynamically. >> >> >> >> Ah ok. I failed to realise that was in the Ansible context. >> >> +1 from me as well. >> Could we also assign server roles/Ansible variable from the Lago YAML? >> Would we want to? > > > You could/can and that would depend on how we write the inventory script. > Currently my script will parse out group assignments from the metadata. This > would probably be clearer seeing the source code and an example. Would > opening an issue with be best? Or a pull request with an example output to > then decide where the script should live? > I'd say start with an issue. WRT to where will that live, would an output format plugin for 'Lago status' be a reasonable place for this?

-- Barak Korren bkorren(a)redhat.com RHEV-CI Team

+1 from me as well. We are also thinking on moving existing bash deploy scripts we're using with ovirt-system-tests (running on Lago) with existing Ansible playbooks to install ovirt instead, though not sure its the same purpose as yours.

On Wed, Jun 15, 2016 at 4:10 PM, Eric Helms <ehelms(a)redhat.com&gt; wrote: > > > On Wed, Jun 15, 2016 at 8:53 AM, Barak Korren <bkorren(a)redhat.com&gt; wrote: > >> On 15 June 2016 at 15:41, Eric Helms <ehelms(a)redhat.com&gt; wrote: >> > >> > >> > On Wed, Jun 15, 2016 at 8:20 AM, Barak Korren <bkorren(a)redhat.com&gt; >> wrote: >> >> >> >> >> >> >> >> See [1] for official reference. Instead of writing a static >> inventory >> >> >> script of hostnames, IPs and groupings Ansible allows writing a >> script >> >> >> to >> >> >> be run that produces that information dynamically. >> >> >> >> >> >> >> Ah ok. I failed to realise that was in the Ansible context. >> >> >> >> +1 from me as well. >> >> Could we also assign server roles/Ansible variable from the Lago YAML? >> >> Would we want to? >> > >> > >> > You could/can and that would depend on how we write the inventory >> script. >> > Currently my script will parse out group assignments from the >> metadata. This >> > would probably be clearer seeing the source code and an example. Would >> > opening an issue with be best? Or a pull request with an example >> output to >> > then decide where the script should live? >> > >> >> I'd say start with an issue. >> WRT to where will that live, would an output format plugin for 'Lago >> status' be a reasonable place for this? >> >> > Created https://github.com/lago-project/lago/issues/281 with some sample > output, template info and the source code at the bottom for perusal. > > Eric > > >> -- >> Barak Korren >> bkorren(a)redhat.com >> RHEV-CI Team >> > > > _______________________________________________ > lago-devel mailing list > lago-devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/lago-devel > > -- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) _______________________________________________ lago-devel mailing list lago-devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/lago-devel