16:02:37 #startmeeting Ansible VMware Working Group Meeting 16:02:37 Meeting started Mon Dec 3 16:02:37 2018 UTC. 16:02:37 This meeting is logged and archived in a public location. 16:02:37 The chair is akasurde. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:37 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:02:37 The meeting name has been set to 'ansible_vmware_working_group_meeting' 16:10:43 hi Akasurde 16:10:50 #chair ckotte 16:10:50 Current chairs: akasurde ckotte 16:10:55 Hi ckotte how are you 16:11:02 looks like no attendees today :) 16:11:14 I'm fine. thanks. how about you? 16:13:22 hi folks 16:13:43 hi 16:14:15 #chair acozine 16:14:15 Current chairs: acozine akasurde ckotte 16:14:54 I'm watching Shippable run on https://github.com/ansible/ansible/pull/45412 16:15:06 I think a watched CI run, like a watched pot, never boils 16:15:26 :) 16:16:16 ckotte: sorry about the docs failure on your PR 16:16:41 I introduced that problem, but for some reason Shippable didn't catch it on my PR 16:16:45 so it turned up on yours 16:17:22 it's fixed now . . . the remaining failures on https://github.com/ansible/ansible/pull/47937 reflect something different 16:17:30 acozine, don't be sorry, it happens 16:17:39 I do you mean "playbooks_strategies.rst"? 16:17:45 yeah 16:17:48 I had the same error in two PRs 16:18:42 yeah, it probably happened in every PR that ran between when I merged the change to the plugin docs and when gundalow fixed the problem (while I was still sleeping) 16:18:45 how can I start the checks manually without pushing a commit? 16:19:08 if you have full access to Shippable, you should see a "play" button on the run 16:19:18 if you don't, post a link here and either Abhijeet or I can kick ot off 16:19:23 s/ot/it 16:19:47 https://github.com/ansible/ansible/pull/47937 16:20:07 https://github.com/ansible/ansible/pull/48084 16:20:08 thx 16:21:38 ckotte, you can close and re-open PR 16:21:47 but that is additional effort 16:21:49 though 16:22:00 I've kicked them both off again 16:22:23 47937 is now passing the docs sanity tests, but failing for other reasons 16:22:30 48084 is running now 16:23:23 yeah, I need to check in 47937 if SNMP config is possible with vc simulator 16:24:20 ckotte: https://app.shippable.com/github/ansible/ansible/runs/96380/87/tests 16:24:54 and https://app.shippable.com/github/ansible/ansible/runs/96380/88/tests 16:26:31 (sorry to interrupt the meeting) here is my issue freshly created about my ovf_deploy of 'replication' problem 16:30:48 #chari xenlo 16:31:08 xenlo, yes, can you paste the link here ? 16:31:16 issue link 16:31:36 https://github.com/ansible/ansible/issues/49447 16:34:18 #chair pdellaert 16:34:18 Current chairs: acozine akasurde ckotte pdellaert 16:34:48 xenlo, Frankly speaking, never seen this error before 16:34:50 but can debug 16:35:03 ckotte: tests are green now on https://github.com/ansible/ansible/pull/48084 16:37:56 acozine: thx 16:42:29 Can anyone please take a look into this - https://github.com/ansible/ansible/pull/49421 ? 16:43:21 meeting already started? ok :p 16:43:33 it's wrong in my work calendar then ;) 16:44:08 pdellaert, Day light saving ? 16:44:26 yeah, i guess :) 16:54:50 pdellaert, Do you want unit test as a separate PR for 49421 16:54:51 ? 17:04:22 * gundalow waves 17:04:57 akasurde: I'd like to add PR review to the agenda, to go though at the end if that's OK? 17:07:55 #chair gundalow 17:07:55 Current chairs: acozine akasurde ckotte gundalow pdellaert 17:08:02 Thanks 17:08:06 gundalow, yes, we almost closing 17:15:08 gundalow, I think you can start we don't have any other topic to discuss 17:21:38 akasurde: https://github.com/orgs/ansible/projects/4 > Is this up to date? 17:23:18 #topic VMware Backlog review 17:23:35 So i was wondering how I can help you with the backlog of PRs and issues 17:24:09 Last Thursday we have a Community PR review day in #ansible-community which was very well attended and we went through a lot of PRs. 17:24:47 If their is a time that is convenient for all of you I'll happily arrange another one focused just on VMwaer 17:25:33 I'm happy to close older PRs if they aren't realistically going to get anywhere 17:26:11 akasurde: ckotte pdellaert Would welcome your thoughts 17:26:24 pdellaert, yes 17:26:52 pdellaert: Import by URL https://raw.githubusercontent.com/ansible/community/master/meetings/ical/vmware.ics into your calendar 17:30:19 some of the old PRs just need to be acceptes. I.e. https://github.com/ansible/ansible/pull/40520 17:30:26 accepted 17:30:58 Looks like their are outstanding review comments on that 17:31:03 I hope you won't close my PRs. I wait for feedback on the old ones 17:31:22 ckotte: nod 17:31:25 so, you mean the owner doesn't respond anymore? 17:32:14 Close will be done by human after review it. For example, we could close if waiting on PR author (and has been for ~year) 17:32:34 ok. makes sense 17:33:25 ckotte: Would you be interested in joining such an activity? 17:33:59 gundalow, I need to step away from keyboard 17:34:06 could you please take over this meeting chair ? 17:34:18 akasurde: Sure :) 17:34:18 gundalow: Unfortunately, I don't have time to review and fix VM-related modules. Maybe next year. 17:34:33 pdellaert: How's your diary looking? 17:34:40 I spent a lot of my time to improve host modules 17:34:51 I can help with them 17:34:57 Which modules? 17:35:03 oh, I need to drop out now as well 17:35:10 just look at my 20 PRs :) 17:35:42 I need to go as well. Bye 17:35:50 https://github.com/ansible/community/issues/417 <- Signup 17:35:55 Thanks everyone 17:36:10 #info Please sign up for the VMware PR review https://github.com/ansible/community/issues/417 17:36:12 #endmeeting