16:02:03 <akasurde> #startmeeting Ansible VMware Working Group Meeting
16:02:03 <zodbot> Meeting started Mon Oct  8 16:02:03 2018 UTC.
16:02:03 <zodbot> This meeting is logged and archived in a public location.
16:02:03 <zodbot> The chair is akasurde. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:02:03 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:02:03 <zodbot> The meeting name has been set to 'ansible_vmware_working_group_meeting'
16:02:10 <akasurde> stroobl, hi
16:02:15 <dericcrago> hi
16:02:24 <akasurde> #chair dericcrago
16:02:24 <zodbot> Current chairs: akasurde dericcrago
16:02:28 <akasurde> #chair stroobl
16:02:28 <zodbot> Current chairs: akasurde dericcrago stroobl
16:02:34 <akasurde> dericcrago, hi
16:03:48 <stroobl> not sure how the meeting process works, can I just throw my question in the group? :)
16:04:14 <akasurde> stroobl, yes, we discuss issues and PRs
16:04:15 <akasurde> here
16:04:33 <stroobl> akasurde: thanks
16:04:57 <stroobl> I was wondering there's a way to get the resource pool PR Pieter wrote merged in 2.7.x
16:04:58 <akasurde> stroobl, do you have anything specific question or issue
16:05:00 <stroobl> https://github.com/ansible/ansible/pull/39792
16:07:05 <akasurde> stroobl, I don't see any reason why we can't
16:07:28 <stroobl> I don't know how the process works, so this might be obvious for you :)
16:07:30 <dericcrago> it's merged so you can already use it if you install / run devel
16:08:28 <stroobl> I know, but that probably means another 6 months delay before we can use the official module with 2.7
16:08:39 <pdellaert> o/
16:08:43 <dericcrago> 2.8 will be out long before then ;)
16:08:53 <stroobl> we're working on a forked version now and we try to contribute our patches to get rid of that :)
16:09:13 <pdellaert> sorry for being late, seems like my irssi decided to roll over and die
16:09:27 <akasurde> #chair pdellaert
16:09:27 <zodbot> Current chairs: akasurde dericcrago pdellaert stroobl
16:11:44 <agowa338> Is there a possibility to get https://github.com/ansible/ansible/pull/46625 merged in 2.7.x, too?
16:13:01 <pdellaert> agowa338: as it is not a patch, my understanding is no... New parameters are a change in signature, which should only happen in the next release
16:13:11 <akasurde> #chair agowa338
16:13:11 <zodbot> Current chairs: agowa338 akasurde dericcrago pdellaert stroobl
16:13:30 <akasurde> agowa338, you are adding new parameter in 2.8 so we can not backport
16:14:03 <agowa338> ok, was just hoping.
16:14:32 <agowa338> It's solving a big problem for deploying windows vms, as otherwise there is no posibility for ansible to wait until the customization has completed.
16:15:19 <pdellaert> Think it is a good addition as a feature, but there's rules when it comes to software development :)
16:15:54 <agowa338> I know, but one can still hope, right ;-) ?
16:16:19 <pdellaert> :)
16:16:28 <akasurde> Yes, definitely this is good addition to vmware_guest customization
16:16:50 <akasurde> stroobl, https://github.com/ansible/ansible/pull/46630
16:17:21 <akasurde> dericcrago, did you have initial implementation of vmware connection plugin ?
16:17:58 <dericcrago> yep, I need help with what tests we want for it
16:18:27 <dericcrago> I struggled with that last week, haven't made any progress around testing
16:18:47 <akasurde> you can post first draft and we can start discussing on PR itself
16:18:50 <akasurde> what say ?
16:19:12 <stroobl> akasurde: thanks!
16:19:19 <dericcrago> https://github.com/ansible/ansible/compare/devel...dericcrago:v2.8_vmware_tools_connection_plugin
16:19:38 <stroobl> we're also trying to find a fix for this issue, but that's a more annoying one https://github.com/ansible/ansible/issues/26095
16:19:47 <dericcrago> I didn't create a PR yet since I didn't have any tests or really any error handling to speak of
16:20:05 <akasurde> #info https://github.com/ansible/ansible/compare/devel...dericcrago:v2.8_vmware_tools_connection_plugin
16:20:16 <dericcrago> if you want a PR without tests, I'll add some error handling and submit a PR
16:20:19 <akasurde> stroobl, it is already solved
16:21:17 <stroobl> right, ic
16:21:17 <akasurde> stroobl, https://github.com/ansible/ansible/pull/33230
16:21:24 <stroobl> I'll check that again
16:22:41 <stroobl> not sure I had the right bug, in our case the problem was that all disks end up on the same member of a clustered datastore
16:22:42 <akasurde> Please provide your feedback and reviews on PR so that we can expeite
16:22:59 <akasurde> yup
16:26:00 <dericcrago> akasurde - would you prefer I submit a PR before or after I figure out the testing situation for the connection plugin?
16:26:39 <akasurde> yes, i think we can decide on test while community is reviewing your implementation
16:26:47 <dericcrago> ok
16:27:12 <akasurde> I am not sure if we can test this using vcsim, because connection plugin will execute commands and put/get files from VM
16:27:20 <akasurde> which is not supported by vcsim
16:27:22 <dericcrago> right
16:29:20 <dericcrago> I had talked with mattclay some last week about it, doesn't seem like we'd be able to have cloud tests, but maybe some tests that could be configured / ran locally during development
16:29:58 <akasurde> ok
16:30:35 <dericcrago> so I'll give it another look and get a PR submitted in the next day or so
16:30:55 <akasurde> ok sure
16:32:11 <dericcrago> I'd also like to request a summary of ansible fest / contributor's summit from the perspective of the VMware working group if we've got time today (or just point me to a link if it's been written up somewhere)
16:33:13 <pdellaert> yeah, same... Sorry i couldn't join, just overlapped with an internal summit
16:33:38 <akasurde> yes sure
16:42:57 <akasurde> I have point to discuss
16:43:44 <akasurde> We need help in filling gaps in https://docs.ansible.com/ansible/devel/vmware/index.html
16:46:14 <pdellaert> ok, i guess the first thing is to update the existing topics?
16:48:19 <akasurde> like
17:11:07 <akasurde> Well, we are little over time for meeting. I will close this meeting now
17:11:11 <akasurde> #endmeeting