16:02:24 #startmeeting Ansible VMware Working Group Meeting 16:02:24 Meeting started Mon Mar 25 16:02:24 2019 UTC. 16:02:24 This meeting is logged and archived in a public location. 16:02:24 The chair is akasurde. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:24 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:02:24 The meeting name has been set to 'ansible_vmware_working_group_meeting' 16:02:36 Hello Everyone 16:04:27 hey! 16:04:36 #chair Goneri 16:04:36 Current chairs: Goneri akasurde 16:04:42 Goneri, Hello 16:05:14 o/ 16:06:41 #chair jillr 16:06:41 Current chairs: Goneri akasurde jillr 16:08:25 Goneri, jillr We generally discuss issues and PRs in this meeting. 16:10:05 it appears we have no PRs to review then, if this is still accurate? https://github.com/ansible/community/issues/417 16:11:12 those are on demand from user/ authos 16:11:20 authors* 16:12:57 https://github.com/ansible/ansible/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+label%3Avmware 16:13:20 shall we just start at the top of the list then? 16:13:37 yes sure 16:14:37 #topic https://github.com/ansible/ansible/pull/54304 16:17:30 looks reasonable enough to me 16:18:15 jillr, this is related to -https://github.com/vmware/vsphere-automation-sdk-python/issues/136 16:18:20 yep, saw that 16:18:37 There is issue with VMware documentation which I referred 16:18:56 silly question for the newbie - what is the actual merge criteria. 2x +1? 1x +1? is there auto-merging? 16:19:02 and due to lack for integration test never got caught 16:19:19 Generally 2 x +1 16:19:30 cool, ta 16:20:13 jillr, Thanks for review 16:20:34 np 16:20:54 Goneri: any thoughts on that PR? 16:21:16 I dont want us to rush ahead if you've still reviewing 16:21:30 jillr, I merged it :) 16:21:35 ah well :) 16:21:45 #topic https://github.com/ansible/ansible/pull/54170 16:22:58 changes logically looks good to me. But I need to test before commenting 16:23:21 from a code perspective I agree but yeah, I'm not entirely sure the implications 16:23:48 jillr, Goneri this is kind of PRs we would like to go through CI environment testing 16:23:55 totally 16:24:19 akasurde: what are we doing now? would you just stand up a local instance and test manually? 16:24:33 this is related to VMware guest customization and we don't have way to do that in govcsim 16:24:42 yes 16:24:48 ack 16:25:07 next PR 16:25:22 #topic https://github.com/ansible/ansible/pull/54123 16:27:30 Another example of customization 16:27:56 I agree with kobayashi the proposed fix is overly complicated 16:28:55 akasurde: FAOD, do you mean like environment-specific customization, or something else? 16:29:39 oh, or like guest customizations that govcsim doesnt test? 16:29:56 yes guest customization 16:30:00 ic 16:30:15 add your comments in PR 16:32:25 * jillr tries not to grumble that gh doesnt work exactly like gerrit and flails at the ui ;) 16:32:39 #topic https://github.com/ansible/ansible/pull/53976 16:34:31 lgtn 16:34:36 *lgtm 16:35:07 akasurde: so with 2 reviews, will this automerge? 16:37:14 yes 16:37:35 #topic https://github.com/ansible/ansible/pull/53632 16:39:40 Code LGTM 16:39:54 I need to test this before we can merge/ 16:40:06 #action akasurde test #53632 16:40:24 thx, I'll let that to you then, I'm still wrapping my head around it 16:40:59 if you have vcenter 6.7 then you can reproduce the issue and check the fix as well 16:40:59 #topic https://github.com/ansible/ansible/pull/53523 16:41:05 ah cool 16:45:01 * akasurde looking 16:46:58 code seems reasonable, and the requestor reports it working, so I suppose that wfm 16:48:26 yes, I am waiting for jeking3 to comment again 16:48:49 do we want to put this on hold for them? 16:49:38 ah just saw your comment, ok 16:49:52 #topic https://github.com/ansible/ansible/pull/53321 16:52:09 jillr, for this PR, I would like to request PR author to create a new module 16:52:46 little background here, vmware_guest is heavily loaded with features and it is very difficult to manage this module now, 16:53:23 so we decided in (IRC meetings) to stabilize existing features and moving all new features to modules 16:53:33 that makes sense 16:54:01 for example, vmware_guest_vnc, vmware_guest_disk, and new vmware_guest_network 16:54:20 this way we can manage individual features efficiently 16:54:53 I will comment accordingly 16:55:33 ok thanks 16:57:28 jillr, I have another meeting so we will close this meeting for now. 16:57:50 akasurde: sounds good, thanks o/ 16:58:01 thanks jillr Goneri 16:58:04 #endmeeting