16:14:41 <tiffanie> #startmeeting openstack_ansible_meeting
16:14:42 <openstack> Meeting started Tue Aug 20 16:14:41 2019 UTC and is due to finish in 60 minutes.  The chair is tiffanie. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:14:43 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:14:45 <openstack> The meeting name has been set to 'openstack_ansible_meeting'
16:15:03 <tiffanie> #topic office hours
16:15:45 <guilhermesp> o/
16:15:58 <arxcruz> o/
16:17:11 <mnaser> hi
16:17:58 <mnaser> arxcruz: had something? ;)
16:17:59 <mnaser> :)
16:18:09 <arxcruz> mnaser: yes :)
16:18:37 <arxcruz> not sire if should i wait for next session
16:19:00 <mnaser> no sure whats up?
16:19:15 <arxcruz> mnaser: so, our collaboration with os_tempest was awesome, and we want to continue, this time, using our collect-logs role to be used by osa jobs
16:19:38 <mnaser> arxcruz: yeah! i thought about that the other day.. but im not sure how is the best way to move onwards cause its such a pita to test it
16:19:57 <arxcruz> mnaser: maybe an experimental job ?
16:20:15 <mnaser> arxcruz: its mainly how hard the it will be to test, cause every run will take 1h+ to see
16:21:04 <arxcruz> i see
16:21:25 <arxcruz> well, if you permit, an experiment job on collect-logs repo might be the right way
16:21:37 <arxcruz> there isn't so much trafic there
16:23:08 <arxcruz> mnaser: all I need is a green light to start work on these issues, because it won't worth work and then get a no, because collect-logs already work for us pretty well :)
16:23:29 <mnaser> arxcruz: i am 100% sure collect-logs will work for us well, its just that testing the implmenetation will take a while because each iteration takes an hour
16:23:40 <mnaser> i wonder if there's a way to invoke only collect logs so we can test it aon an already deployed aio
16:25:01 <arxcruz> mnaser: i don't think it's possible, at least not in zuul
16:25:32 <arxcruz> mnaser: but don't worry, i'm used to wait more than 1 hour, tripleo jobs takes 2 hours ;)
16:25:39 <mnaser> haha :)
16:26:22 <mnaser> so lets do that then.. i'd be up for it
16:26:25 <arxcruz> so, i'll work on the integration, and once I have something working properly i'll present here :)
16:26:30 <arxcruz> cool :)
16:26:59 <mnaser> im happy to be pinged about this stuff
16:27:05 <arxcruz> sure
16:28:28 <guilhermesp> annd for the momento I have two things on hold: https://review.opendev.org/#/c/672948/ I'm trying to dig into this locally to figure out why bionic dristro jobs are failing
16:28:38 <guilhermesp> and today I'm gonna start developing a new role for osa
16:28:40 <guilhermesp> will be murano
16:33:19 <ThiagoCMC> Hey guys, the doc: https://docs.openstack.org/project-deploy-guide/openstack-ansible/stein/deploymenthost.html points to a tag (19.0.2) that doesn't exists.
16:34:26 <ThiagoCMC> I'm wondering here, could I use the `git checkout stable/stein` instead of creating a new branch `git ... -b 19.0.1` from a tag?
16:35:21 <logan-> o/
16:49:23 <openstackgerrit> Merged openstack/openstack-ansible-os_glance master: Updated from OpenStack Ansible Tests  https://review.opendev.org/677309
16:50:28 <mnaser> ThiagoCMC: thats weird
16:51:33 <mnaser> ThiagoCMC: https://opendev.org/openstack/openstack-ansible/src/tag/19.0.1 the tag exists
16:51:46 <mnaser> oh but 19.0.2 doesnt exist
16:52:13 <mnaser> anyone has any ideas?
16:57:52 <jrosser> i wonder if the docs are generated of stable/stein which will be the *next* release
16:58:19 <jrosser> 19.0.1 was very recent https://review.opendev.org/#/c/673248/
16:58:41 <mgariepy> rocky is ok.
17:00:25 <tiffanie> #endmeeting