16:01:43 #startmeeting Ansible VMware Working Group Meeting 16:01:43 Meeting started Mon Apr 9 16:01:43 2018 UTC. The chair is akasurde. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:43 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:01:43 The meeting name has been set to 'ansible_vmware_working_group_meeting' 16:01:45 I'll apologize for slow typing, someone decided nap time needed to be during the meeting 16:02:09 #chair warthog9 16:02:09 Current chairs: akasurde warthog9 16:02:20 Welcome warthog9 16:02:29 :-) 16:02:39 we will wait for others to join 16:03:35 I have two topics to discuss 16:03:56 1. vmware_guest documentation 16:04:23 #info https://github.com/ansible/ansible/pull/38377 16:04:40 2. Vmware dynamic invenetory plugin 16:04:59 #info https://github.com/ansible/ansible/pull/37456 16:06:50 I think rdwebster might have a topic if we have time at the end 16:06:59 and his client stays on 16:07:20 Sure 16:07:39 Bob's here now, finished messing with my client. 16:07:58 #chair rdbwebster 16:07:58 Current chairs: akasurde rdbwebster warthog9 16:08:08 Hi rdbwebster 16:08:40 Hello 16:11:07 warthog9, while wait for other, we can discuss about rdbwebster points 16:11:22 rdbwebster: have at 16:11:41 Shall I recap? 16:11:45 sure 16:12:09 The vCloud Director team within VMware is planning to create a new Ansible plugin for vCloud Director. 16:12:16 hello 16:12:32 #chair jtanner 16:12:32 Current chairs: akasurde jtanner rdbwebster warthog9 16:12:37 hi warthog9 16:12:39 It will support the latest versions of vCloud Director and leverage the pyvcloud python modules - https://github.com/vmware/ansible-module-vcloud-director 16:12:53 hey jtanner 16:13:10 rdbwebster: is that repo private or just not created yet? 16:13:21 This will enable both service providers and tenants to provision and maintain cloud infrastructure that uses vCD. 16:13:46 There are two repos, which are both private until we clear approvals with our Open Source program office. 16:13:57 Which will be in the next week or so hopefully. 16:14:06 what's your plan for distribution? 16:14:36 we're working on making galaxy work as a packaging framework for all plugin types instead of just roles 16:14:52 Open to suggestions. 16:15:02 galaxy would be my vote 16:15:10 galaxy has advantage 16:15:18 we just need to get our plan rolling and done 16:15:24 if galaxy is getting more generic, that's likely the best plan 16:15:35 as its fast and not tideup with ansible release 16:15:41 then you'd be able to keep your own repos and retain complete control instead of dealing with ansible/ansible PR process 16:15:58 at least that's how i'm selling it =) 16:16:12 :-) 16:16:28 ok that sounds good to me, Let me explore that idea. thank you 16:16:40 it's cool though that you guys are doing vcd stuff. i really don't have time or hardware to go mess with vcd again 16:16:43 jtanner: any timeline for that? anything we can do to help? 16:16:56 yes 16:16:59 everything is ASAP from my perspective 16:17:04 we have hardware crunch 16:17:19 we gave a rundown to another group within vmware last week 16:17:25 not sure if i should say in public chat who 16:17:49 you have 11 #1 priorities! 16:17:51 akasurde: lets take the hardware needs offline? 16:18:03 yes sure 16:19:00 #chair bcoca 16:19:00 Current chairs: akasurde bcoca jtanner rdbwebster warthog9 16:19:03 thaumos: do you have anything you can add about timeline for galaxy? 16:19:11 #chair thaumos 16:19:11 Current chairs: akasurde bcoca jtanner rdbwebster thaumos warthog9 16:20:03 galaxy aside, is there anything you folks need from us on the ansible side? 16:20:44 For the new vCD provider, not right now, thank you 16:20:51 galaxy is WIP, so some features might come out soon (server side) but client side we are probalby playing catchup, I would not make any firm decisions until after summer 16:21:40 you should still be able to publish as role for now, to get 'latest and greatest' out, independantly from submitting as PR or not 16:21:41 bcoca: ok so galaxy isn't, potentially, useful till fall? 16:21:57 (for this purpose) 16:22:03 ^ no, i would say ' dont commit to single strategy' till fall 16:22:10 got it 16:22:11 its useful NOW 16:22:45 we hope to make it more useful 16:22:57 and in the end 'the best way' 16:23:04 just not there yet 16:24:16 cool, anything else on that front rdbwebster for now? 16:24:46 nothing from my side 16:24:53 Thats all for now thx 16:25:13 you folks coming to pycon? 16:25:26 I'll sneak in in my typical fashion 16:25:36 no plans. 16:25:51 let's plan to have a sit down sometime during 16:26:14 that works 16:26:24 Wanna discuss something related open issues and open PRs 16:26:43 inv plugin maybe? 16:27:37 Sure 16:28:38 #link https://github.com/ansible/ansible/pull/37456 16:31:07 iirc you were curious about performance on large vcenters? 16:39:40 warthog9: is there a group inside vmware that can perf test our inventory scripts? 16:42:55 jtanner: like me go fishing 16:43:14 rdbwebster might have access to something big 16:43:39 if he doesn't, I know someone on the performance group who seems to like me, and I need to talk to him about some storage for a project anyway 16:43:52 k 16:44:17 we know our scripts do well on vcsim, but that's not really reflective of vcenter's api response times 16:45:22 warthog9: lets talk offline about this, I might have something. Need to understand the performance monitoring tools needed. 16:49:03 I would like to bring to everyone's notice that there are lot of PRs pending due to lack of review 16:56:47 anything else? 16:58:28 not from me 16:58:36 not for me 17:00:24 akasurde: anything else or should we call it for today, and pick up next week? 17:00:56 not for me as well 17:01:06 Thanks everyone for join-in 17:01:09 #endmeeting