18:06:04 #startmeeting Ansible New Modules 18:06:04 Meeting started Wed Nov 9 18:06:04 2016 UTC. The chair is gundalow. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:06:04 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:06:04 The meeting name has been set to 'ansible_new_modules' 18:06:19 #chair abadger1999 alikins bcoca jimi|ansible jtanner mattclay nitzmahone 18:06:19 Current chairs: abadger1999 alikins bcoca gundalow jimi|ansible jtanner mattclay nitzmahone 18:06:22 Greetings 18:06:30 yo 18:06:43 * mattclay waves 18:06:52 hi 18:06:53 #topic AWS ELB modules 18:06:58 shaharmor: Hi :) 18:07:01 Hi 18:07:07 #info https://github.com/ansible/community/issues/92#issuecomment-259465655 18:07:23 As i wrote in the Issue, there are new modules that require some attention 18:07:52 I have fixed many bugs locally but wasn't sure if I should wait for the existing PRs maintainers to handle it or create a new one 18:08:28 Because I haven't seem any update on their side for a few days now 18:09:13 "a few days" isn't that long a time for this stuff. People are often doing this in the evenings along side their day jobs 18:09:20 shaharmor: it's much easier for us to review when the full new module is in one PR (I see you've got two outstanding w/ the original contributor) 18:09:31 is wimnat here? 18:09:58 The original contributor is wimnat, then there are some fixes from naslanidis, and also some fixes from me 18:10:07 * resmo waves 18:11:07 hi 18:11:50 ryansb: I understand that, so should I open a new PR with all the fixes merged together? 18:13:03 I think so. Definitely retain authorship w/ wimnat, since they wrote a lot of it based on looking at the PRs 18:13:30 Yup 18:13:45 Ok I'll do that and come back here next week with the updates :) 18:13:50 Also, minor thing: the second module is "elb_target_group", but since that is specific to App load balancer, I think it would make more sense to call it "alb_target_group" 18:14:04 Regarding that 18:14:07 shaharmor: also @ me (also ryansb on github) when you open that so I can help review 18:14:27 I think that since in AWS it appears under ec2, it should start with ec2_ 18:14:41 so something like ec2_alb & ec2_target_group 18:14:58 I don't think that the target group is specifically under alb 18:15:26 ryansb: will do 18:15:33 So that's a bit of a point of contention, since many AWS services don't fall under ec2 (like, an "ec2_kinesis" module would be odd) 18:16:03 maybe prefixing with aws_ would be good practice, but honestly we've been bad about that thus far (for example, cloudformation and cloudformation_facts) 18:16:04 But kinesis doesn't appear under ec2 18:16:22 Target groups are under ECS I thought 18:16:26 No 18:16:40 I have to research the new ALB more before I review, obviously 18:16:59 http://imgur.com/a/ZyRDJ 18:17:14 this is the sidebar of AWS when you're viewing the ec2 section 18:17:46 It might appear under ECS as well 18:17:51 I didn't check 18:18:56 Anyway the name is not the main part here, we can decide about it later 18:19:07 So yeah, ec2_alb (or ec2_application_load_balancer) and ec2_alb_target_group work for me 18:19:25 yeah, so the main bit is: consolidate PRs, and then we can get a proper review on 18:19:35 Ok thanks 18:20:09 Have a good evening 18:26:00 any other modules? 18:28:15 Nothing else on the agenda for the last 21 days 18:28:53 #topic Open FLoor 18:28:57 #topic Open Floor 18:30:58 Merging this meeting into the core public meetings starting next week? 18:31:45 +1 18:32:36 Okay. That's a thing. Gonna happen. So come tuesday/thursday if there's something you need to bring up :-) 18:33:52 \o/ 18:41:12 alright, if nobody has stuff for open floor 18:41:15 #endmeeting 18:41:24 oh, not a chair. gundalow ^ 18:42:31 #endmeeting