20:00:35 <jborean93> #startmeeting Ansible Windows Working Group
20:00:35 <zodbot> Meeting started Tue Jan 29 20:00:35 2019 UTC.
20:00:35 <zodbot> This meeting is logged and archived in a public location.
20:00:35 <zodbot> The chair is jborean93. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:35 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
20:00:35 <zodbot> The meeting name has been set to 'ansible_windows_working_group'
20:01:13 <jborean93> Hey all
20:01:37 <it-praktyk> Hey
20:01:50 <jborean93> #chair it-praktyk
20:01:50 <zodbot> Current chairs: it-praktyk jborean93
20:01:54 <ksubileau> Hello :)
20:02:00 <jborean93> #chair nitzmahone ksubileau
20:02:00 <zodbot> Current chairs: it-praktyk jborean93 ksubileau nitzmahone
20:02:06 <jborean93> Hey
20:02:36 <jborean93> dag ping
20:03:54 <jborean93> give it a few more minutes to see if anyone else turns up
20:04:06 * nitzmahone heats up sad lunch
20:04:37 <dag> o/
20:04:44 <jborean93> #chair dag
20:04:44 <zodbot> Current chairs: dag it-praktyk jborean93 ksubileau nitzmahone
20:04:46 <chopraaa> hey
20:04:52 <jborean93> #chair chopraaa
20:04:52 <zodbot> Current chairs: chopraaa dag it-praktyk jborean93 ksubileau nitzmahone
20:05:03 <jborean93> Ok I think we have enough to get started
20:05:16 <jborean93> Before we begin the module review is there anything someone wants to talk about?
20:06:15 <jhawkesworth_> hey sorry i'm late
20:06:23 <jborean93> #chair jhawkesworth_
20:06:23 <zodbot> Current chairs: chopraaa dag it-praktyk jborean93 jhawkesworth_ ksubileau nitzmahone
20:06:30 <jborean93> No worries
20:06:39 <jborean93> Sounds like a no to other topics let's get started on the module review
20:07:08 <jborean93> Before we start, we can do this over Blue Jeans (video chat) or we can just stick to text here.
20:07:31 <chopraaa> I'm at work ;(
20:07:34 <nitzmahone> +1 to Bluejeans for screen sharing and making sure we're all looking at the same thing
20:08:12 <jhawkesworth_> bluejeans can run off browser I think chopraaa
20:08:13 <jborean93> chopraaa: you don't have to share the video, probably just important you can access it and listen to the audio
20:08:38 <chopraaa> Can't access bluejeans regardless
20:08:51 <chopraaa> You guys can go on without me though
20:08:55 <chopraaa> Not an issue
20:09:25 <jborean93> Will see if dag, ksubileau, and it-praktyk are ok with it first
20:09:37 <it-praktyk> I'm OK
20:09:48 <dag> I will have to use a headset, and only listen (livingroom)
20:10:01 <ksubileau> Only listen for me too
20:10:11 <jborean93> cool
20:10:17 <jborean93> https://bluejeans.com/u/jborean/
20:10:19 <jhawkesworth_> iirc there's a chat window in bluejeans too
20:10:38 <nitzmahone> we should use one or the other, not both
20:10:58 <jborean93> I think IRC is best, it keeps the history in the logs
20:11:17 * chopraaa agrees
20:11:19 <jhawkesworth_> sure, irc makes most sense
20:12:02 <chopraaa> I think @gundalow does his community reviews on irc as well
20:13:21 <chopraaa> @jhawkesworth_, let me check
20:14:54 <jhawkesworth_> any  more joining the bluejeans meeting?
20:15:59 <jborean93> #topic https://github.com/ansible/ansible/pull/50798
20:16:57 <it-praktyk> I connect to the BlueJeans meeting (Fedora 28, Chrome) and that doesn't work like expected :(
20:18:07 <jborean93> are you able to hear us?
20:18:35 <it-praktyk> nope
20:18:47 <ksubileau> Ok for me
20:20:49 <it-praktyk> I'm OK now
20:21:47 <mhunsber> I just joined. Is there another conversation going on?
20:22:10 <jborean93> mhunsber: https://bluejeans.com/u/jborean/
20:22:32 <jborean93> we are using that to char to each other
20:23:23 <dag> that's a good point, what do similar modules do
20:24:00 <mhunsber> thanks
20:24:23 <dag> I didn't understand anything
20:24:32 <dag> he's possessed
20:25:10 <chopraaa> its good now @jborean93
20:26:20 <jborean93> thanks
20:27:17 <jborean93> #topic https://github.com/ansible/ansible/pull/50621 win_psmodule
20:28:14 <dag> jborean93: is possessed again
20:28:26 <dag> must be the underwater cables :-)
20:28:38 <jborean93> it's Australia
20:28:42 <dag> :-)
20:29:56 <dag> If you meet on bluejeans, half of the meeting is about bluejeans ;-)
20:30:10 <jborean93> #topic https://github.com/ansible/ansible/pull/49524 win_git
20:32:13 <it-praktyk> Youuuuu souuuunndddd weeeeeiiiiirdlyyyy .... ;)
20:32:41 <dag> It depends, if the maintainer is committed for the long run, I'd say go for it, but if the commitment is not there, this is probably a dead end
20:32:52 <nitzmahone> His next door neighbor is swinging the didgeridoo
20:33:11 <nitzmahone> s/swinging/playing/
20:33:18 <dag> nitzmahone: :-)
20:33:36 <jhawkesworth_> I feel bad for the contributor, lots of work done on this one.
20:34:02 <jhawkesworth_> it is another 'exe wrapper' module though
20:34:07 <dag> jhawkesworth_: true
20:34:17 <dag> jhawkesworth_: that's the same as the git module
20:34:32 <dag> to be discussed with the contributor
20:34:38 <jhawkesworth_> is there any more detail about collections (is this managed galaxy content)?
20:34:54 <dag> yeah, I don't know what these collections is
20:35:04 <chopraaa> not sure how to unmute lol, but i agree with matt on this
20:36:26 <jborean93> #topic https://github.com/ansible/ansible/pull/46450 win_hostscccccchuctutunlnnhturnbglkbvtlfuckbfnfrldugn
20:36:34 * jborean93 sigh
20:36:41 <jborean93> #topic https://github.com/ansible/ansible/pull/46450 win_hosts
20:37:54 * dag refrains from being critical :)
20:38:06 <jhawkesworth_> thanks for elaborating about collections
20:39:13 <dag> so during discussing the implementation it appeared the hosts file is in fact a lot versatile
20:39:35 <dag> supporting A records and CNAME records, while also supporting multiple IP's for the same host
20:39:45 <dag> so all this was supported here
20:40:34 <dag> yeah, we need to add tests
20:40:51 <dag> I'd like to help in that regard, but that's difficult if it's not merged
20:41:03 <dag> so if the contributor is not coming through, we can still do it
20:41:34 <dag> I'm putting myself forward to finish it for v2.8 if needed
20:41:48 <dag> TBH we need this for Unix as well :)
20:41:50 <jborean93> sounds good
20:41:54 <jborean93> #topic https://github.com/ansible/ansible/pull/45998 win_iis_webhandler
20:42:53 * dag never liked the IIS stuff, and this probably is better using DSC resources ?
20:43:49 <dag> but we already have IIS modules too, so to me it's confusing if we offer half of a solution
20:43:57 <dag> and point to DSC for the other half
20:44:19 <dag> jborean93: agreed, it's just a sorry state at this point :-/
20:44:22 <dag> in hindsight
20:45:02 <jborean93> #topic https://github.com/ansible/ansible/pull/45521 win_iis_logs
20:45:32 <dag> I don't know what the complexity is of these IIS modules
20:46:03 <dag> ok, because if those would be quite simple to maintain, I wouldn't mind that much
20:46:14 <dag> (also complexity of maintenance)
20:46:23 <dag> yeah, I expected a DSC resource
20:46:39 <dag> maybe we should clarify the IIS DSC resources from the remaining IIS modules
20:46:53 <jborean93> #topic https://github.com/ansible/ansible/pull/44766 win_chocolatey_pin
20:46:54 <dag> and add alternative DSC examples for the existing modules
20:47:10 <jhawkesworth_> yeah wondering if we should just make a plan to move all the IIS stuff to the dsc resources.
20:47:15 <dag> Can we add this as an action-item for the IIS modules ?
20:47:38 <dag> jhawkesworth_: starting with adding notes, seealso, and examples in the existing ones seems best
20:47:52 <jhawkesworth_> yes that sounds like a good plan
20:48:20 <dag> I'll add it to the wiki as an item for v2.8
20:53:33 <dag> nitzmahone: agreed
20:54:11 <dag> Thanks jborean93 !
20:54:27 <dag> You keep it :p
20:54:38 <jborean93> #topic https://github.com/ansible/ansible/pull/43943 win_mssql_login_server_role
20:55:09 <dag> But is there a DSC module ?
20:56:20 <dag> IMO if we don't plan to offer the most important functionality, we shouldn't start adding pieces IMO
20:57:14 <jhawkesworth_> if we are saying no to any new IIS modules in favour of dsc and there's DSC stuff for this as well, it sounds like a no to include in core to me
20:57:58 <jborean93> #topic https://github.com/ansible/ansible/pull/43406 win_rsa_cap
20:58:02 <dag> Should we propose to document the functionality as DSC modules when we refuse to add these modules ?
20:58:43 <dag> it is win_rds_cap
20:58:51 <dag> yes, all three
20:59:06 <dag> it seems to be well supported by the contributor
20:59:33 <dag> Are there DSC resources ? :-D
21:00:03 <dag> Fine for me !
21:00:21 <jborean93> #topic https://github.com/ansible/ansible/pull/36493 win_dns_a
21:01:24 <dag> Really ?
21:01:39 <dag> We did AD + DNS domain
21:01:45 <dag> wouldn't this work with that ?
21:02:22 <dag> I can look into my scripts for this, but it was a single Powershell cmdlet for setting up a DNS domain with AD
21:02:45 <dag> Not for the system itself ?
21:03:02 <dag> nitzmahone: I think so too, but never tested it
21:04:45 <dag> I agree, I would rather have a fulle set of operations, than just A records
21:04:55 <jborean93> #topic https://github.com/ansible/ansible/pull/27634 win_disk_management
21:06:14 <it-praktyk> https://github.com/ansible/ansible/pull/37798
21:06:59 * dag needs to check if the output is consistent
21:08:48 <jborean93> thanks all
21:08:52 <dag> Thanks !
21:08:59 <jborean93> #endmeeting