16:05:52 <akasurde> #startmeeting Ansible VMware Working Group Meeting
16:05:52 <zodbot> Meeting started Mon Feb 11 16:05:52 2019 UTC.
16:05:52 <zodbot> This meeting is logged and archived in a public location.
16:05:52 <zodbot> The chair is akasurde. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:05:52 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:05:52 <zodbot> The meeting name has been set to 'ansible_vmware_working_group_meeting'
16:06:47 <alongchamps> hi adasurde
16:08:03 <akasurde> #chair alongchamps
16:08:03 <zodbot> Current chairs: akasurde alongchamps
16:08:05 <akasurde> hi alongchamps
16:10:00 <alongchamps> looks like there's not much on the agenda today
16:10:36 <akasurde> alongchamps, yes, if you have anything to discuss we can do tht
16:11:37 <alongchamps> I am actually working on a module (mostly an exercise for myself) on vmware_host_kernel_module so I do need to get an issue open for that
16:11:45 <alongchamps> and once I've done enough testing on my side, a PR
16:12:09 <alongchamps> but that will be a topic for next week most likely
16:12:23 <akasurde> Yes sure
16:12:42 <akasurde> I happy to have new prs and features
16:13:05 <alongchamps> of course
16:13:32 <alongchamps> my next one will most likely be an update on the firewall configuration / allowed IP addresses because we have a real need for that on our side for config tracking
16:13:43 <akasurde> You can take a look at existing issues and prs as well
16:13:49 <alongchamps> I think we talked about that one previously over email
16:13:55 <alongchamps> and there is an issue for it
16:14:00 <akasurde> ah !
16:14:15 <akasurde> definitely
16:14:20 <alongchamps> yep that was me
16:14:21 <alongchamps> :)
16:14:52 <akasurde> currently i am occupied but sure once i find some free cycle i will work on it
16:15:04 <akasurde> pr welcome
16:15:20 <alongchamps> sounds good
16:16:45 <akasurde> any specific req for firewall config issue
16:17:19 <alongchamps> that was one to update the script so that it can set allowed_all to false and specify a range of IPs or subnets that the host can talk to for a particular service
16:17:30 <alongchamps> I know it's available in the API to configure that, but it's not worked into the script yet
16:18:53 <akasurde> ok
16:26:29 <alongchamps> I didn't have anything else at this point
16:26:43 <akasurde> same here
16:32:19 <akasurde> alongchamps, how often do you try latest patches in VMware space ?
16:33:13 <alongchamps> not too often actually, but is there something in particular you need to test?
16:33:34 <alongchamps> I'm also leaving for lunch now, because I have a 12:00 meeting
16:33:45 <akasurde> nothing specific
16:34:03 <alongchamps> ok; I'll be back in about half an hour and can get back to you then
17:02:29 <alongchamps> I'm back, what did you have going on
17:06:07 <akasurde> alongchamps, nothing much
17:07:13 <akasurde> alongchamps, Can you try any of these - https://github.com/ansible/ansible/pulls?q=is%3Aopen+is%3Apr+label%3Avmware and provide feedback
17:07:23 <akasurde> nothing specific as such
17:07:44 <akasurde> What ever you feel interesting and required will do
17:10:05 <alongchamps> ah ok
17:10:18 <alongchamps> I'll take a look at some of them and see what I can do if I get a chance
17:39:51 <akasurde> #endmeeting