15:55:12 #startmeeting Ansible VMware Working Group Meeting 15:55:12 Meeting started Mon May 6 15:55:12 2019 UTC. 15:55:12 This meeting is logged and archived in a public location. 15:55:12 The chair is akasurde. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:55:12 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:55:12 The meeting name has been set to 'ansible_vmware_working_group_meeting' 15:55:55 Hello everyone 15:55:59 * alongchamps waves 15:56:20 #chair alongchamps 15:56:20 Current chairs: akasurde alongchamps 15:56:22 hi 15:56:27 alongchamps, hi 15:56:33 #chair dericcrago 15:56:33 Current chairs: akasurde alongchamps dericcrago 15:56:36 dericcrago, hi 15:57:49 I wanted to discuss VMware Ansible community roadmap 15:58:14 need more people though 15:58:48 so how much can we manage with the quantity of people we have actively contributing 15:59:27 2-3 features 16:02:07 I have couple of topics if you ok we can discuss them 16:02:31 sounds good to me 16:03:00 First, 16:03:33 guest customization is a major part of vmware_guest 16:04:14 just brought that up - it is a lot of properties 16:05:23 One of the roadmap point is - VMware Guest Customization 16:06:03 I have gathered some of the issues which seems important and can be tackled in 2.9 release cycles - https://github.com/ansible/community/wiki/VMware%3A-Guest-Customisation-related-issues 16:06:08 #info https://github.com/ansible/community/wiki/VMware%3A-Guest-Customisation-related-issues 16:06:38 I am also managing a VMware guest customization support matrix - https://github.com/ansible/community/wiki/VMware%3Acustomisation 16:11:33 looks like a lot of networking stuff 16:11:38 relating to config on the VMs 16:12:40 yup 16:12:57 basically lacks testing in this part of area 16:13:44 can some of the real environment testing that is being explored (I forget the issue number) help with this? 16:14:04 for being able to test on real VMs 16:15:11 alongchamps, yes, we are exploring this option but it is in nascent stage 16:15:16 ok 16:16:44 Second point 16:17:03 vmware dynamic inventory plugin in very new right now and lacks lot of features 16:17:35 I am planning to have the features to VMware dynamic inventory plugins in 2.9 release cycle 16:17:36 I saw recent discussions about having ESXi hosts in there and that gets a +1 from me 16:18:00 yup, you are correct 16:19:12 Third point, is related to VMC and SDDC which are newest features from VMware cloud offerings 16:19:41 Developing APIs and modules related to VMC and SDDC can be tackled in this release cycle 16:21:14 any links on the plans for that? 16:22:09 because I'm especially interested in that 16:25:41 alongchamps, no plan link as such but you can take a lead and create one in VMware wiki pages - https://github.com/ansible/community/wiki/VMware 16:25:59 so this would be VMware on AWS, right? 16:26:11 just making sure I'm not getting my acronyms all mixed up 16:26:31 one of the VMware team member also stated that he is interested in working on this, so I can patch you both 16:26:45 alongchamps, yes, VMware on AWS it is 16:27:12 ok 16:30:17 These are some of major areas I think we should target for 2.9 16:35:27 these sound good to me 16:36:23 I have a couple of things I've been working on lately, if now's a good time to talk about them 16:38:25 sure 16:38:39 alongchamps, go ahead 16:39:32 ok, first up is 51240, for vmware_host_firewall_manager, I'm going to get a PR going hopefully this afternoon 16:39:58 it works as expected on the ticket there, with adding/removing/modifying firewall configurations 16:40:28 secondly, I wrote a quick module for waiting for an ESXi host to connect or disconnect (e.g. when rebooting, this would be used to wait for it to disconnect and then wait for the host to reconnect) 16:40:58 I was thinking of using vmware_host_facts for this but it didn't track connection state and also that module doesn't work if the host is disconnected (which makes sense, vCenter can't read the info) 16:47:42 Ok 16:47:51 Cool thanks for the information. 16:48:04 so that module would be something like vmware_host_wait_connection_status 16:48:41 which seems to follow similar naming for 'wait' modules 16:49:59 we can drop status 16:50:08 or make 16:50:18 vmware_host_wait_conn_status or something 16:51:41 ok vmware_host_wait_connection works for me 16:52:07 it only exists on my local machine (I don't even have an issue made yet) so it's easy to rename 16:57:35 be sure to add test case as well 16:59:28 alongchamps, We are little over the time for this meeting. 16:59:38 oh yeah, good catch 16:59:41 Thanks for joining 16:59:46 #endmeeting