00:00:05 #startmeeting Ansible Azure Working Group 00:00:05 Meeting started Thu Dec 13 00:00:05 2018 UTC. 00:00:05 This meeting is logged and archived in a public location. 00:00:05 The chair is jborean93. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:00:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 00:00:05 The meeting name has been set to 'ansible_azure_working_group' 00:00:21 #chair yungezz zikalino82 yuwei Kylie_ 00:00:21 Current chairs: Kylie_ jborean93 yungezz yuwei zikalino82 00:00:47 Matt has had to run some errands but I believe he may join in on his phone when possible 00:01:01 Ok 00:01:20 doesn't look like there anything on the agenda 00:01:24 #topic open floor 00:01:34 anything you wish to bring up 00:01:54 I have two topics 00:02:30 1. certified modules 00:02:42 2. Inventory 00:03:00 sure let's start with certified modules 00:03:46 As for certified modules, many customers are using rm_deployment. Want to add it into the list. 00:04:48 I haven't seen Matt's report on the current state on modules and adding certified support. Are you talking to someone from Ansible in regards to this? 00:06:18 I see it also was certified (before certified was really a thing) but was bumped back to preview 00:07:05 s/preview/community 00:07:20 Oh, why it’s bumped back to preview 00:07:52 I'm not sure, I know the whole certified talk is sort of new for Azure modules so I think it was pre-emptively set to certified a few releases ago 00:08:44 Ok 00:08:56 I'll bring it up with some others on this side to see what they say 00:09:19 Thanks Jordan 00:09:46 Btw, do you know any other certified modules for other platform? We noticed some news to claim certified for Cisco, F5, and etc. not sure same program or not? 00:10:34 IIRC some Netapp stuff is certified but not sure on that. I've mostly only seen it on the networking side due to that being more reliant on separate vendors 00:12:05 But in terms of adding rm_deployment to the certified list I would bring it up with whoever you are discussing certified modules with. 00:14:11 So far we only discussed the list with Matt and you here. 00:14:21 As technical analysis 00:14:28 hmm I thought there was a separate discussion going on around this but I'm not sure 00:15:01 I'll definitely bring it up with Matt offline if he is unable to make the meeting though 00:15:33 As for certified program, not sure how it runs. There is a separate conversation about how to run this program, what support level is required. 00:15:39 I'm lurking 00:15:55 Waiting for kid to get checked in at dance 00:16:28 Hi Matt 00:16:30 Hi Matt 00:16:32 If we want to add deployment to the review that's fine, but probably need to revisit the return value. IIRC that one was kind of a disaster 00:17:40 I see. Catherine, idea how to refactor return value? 00:18:15 Need to look at it 00:19:03 It's been a long time since I looked at it too, but IIRC it was very "vm flavored" instead of returning arbitrary data from the template. But I could be mistaken. 00:19:25 sounds like we just need to the review list and go from there 00:20:23 And how about removing rm_image from the list since the usage is not high and we want to control the number of modules at this phase (not sure how the program will run). 00:20:49 Works for me 00:20:49 i think rm_image might be higher, i am just fixing a few things that will make it more useful 00:21:12 so i would like to keep it 00:21:14 that's a newer module as well compared to deployment 00:22:49 I believe we will have chances to add more in the future. 00:23:06 Fine either way- since I'm afk, could Kylie send me an email with the modules you want to add/remove and I'll take care of that? 00:25:39 Yes, I will send an email to get all on the same page. Again, this is for technical analysis. Separate discussion to understand the requirements to run this program before moving forward. Thank you all. 00:25:58 #topic inventory 00:27:06 Now the inventory script asked people to use new version. But new version does not work. Catherine, I saw a fix was merged, work now? 00:27:25 I met error, batch name required when size exceeds 20, after that or merged 00:27:35 I sent an email yesterday 00:27:50 Disabling batch should fix that one in the interim, but should be an easy fix 00:28:05 (not sure if you saw my response) 00:28:14 Is it Laurent knowing how to use batch api? 00:28:42 No, I just observed the portal and played with it to figure it out 00:29:00 Disabling batch? Should we get it fixed otherwise performance benefits lost 00:29:03 No docs or public resources I'm aware of on how to use it. 00:29:04 Ok 00:29:12 I just mean in the config 00:29:24 (as a workaround until the name thing is fixed) 00:29:28 We have official doc to teach people how to use dynamic inventory on Azure. Need to update it with new solution. Of course, need to get it work first. 00:29:34 Got it 00:29:37 How did you test it? 00:29:52 looks like `batch_fetch: no` will disable the batch fetching 00:30:09 but that should only be a workaround until the actual issue is fixed 00:30:30 Yes 00:30:37 I had an account with apparently less than 20 hosts in it that I was using. It's prohibitively slow and expensive to test against real servers, so I have a small simulator 00:30:50 I can check portal behaviors also 00:30:50 (eg in CI) 00:30:54 Who is tacking that issue now? 00:31:20 Some people filed issue for this 00:31:29 I can look at it 00:31:42 I may not have time before holiday, but should be an easy fix. 00:32:32 Sounds like I need to repro the name issue and add that check to the simulator 00:34:12 I wonder if they lowered the count for name since I originally wrote/tested, or if I just lucked out not hitting it in testing 00:34:13 # action Matt and Catherine, get new inventory work. 00:34:40 Maybe 00:35:17 I will try to see if could get some contact point on batch api to learn more detail 00:35:20 I only had ~12 hosts in my account, so might not have had a batch bigger than 20 00:35:32 Once it works, we will refresh the doc. The path is different. Will you replace old one on some day? 00:35:56 Gotta make sure it's the right thing, since the public batch api is something totally unrelated 00:36:13 The old one won't go away anytime soon, we should just stop accepting features on it 00:36:38 (just bugfixes) 00:37:04 I see. Then our doc will direct people to the new path once it works. 00:37:38 I am done for my two topics. yungezz yuwei Zim 00:37:52 Any pr you want to raise here? 00:38:02 No from me 00:38:31 I saw Zim closed hdinsight module pr- was that for future cleanup, or ? 00:39:13 Seems zim not here 00:39:34 I will sync with him offline 00:39:40 he's been dropping in an out, maybe some connection issues 00:39:46 Yes 00:40:17 Vmss 00:40:36 Update image Id of vmss 00:40:52 Btw, when is next 2.7 minor release 00:41:00 Can it be back ported? 00:41:01 should be soon 00:41:03 Tomorrow 00:41:05 Yes 00:41:07 Oh 00:41:14 It was locked Monday I think 00:41:24 Next one will be early January 00:41:47 Then we cannot catch it, I mean current one, but next January 00:41:56 You can file the backport anytime, the release manager will merge when they're ready 00:42:05 Got it 00:42:16 Good to know there is another one release. Thank you. 00:42:33 Generally every 3 weeks 00:43:13 (for the actively supported releases, currently 2.6 and 2.7), 2.5 is critical security issues only 00:43:20 2.7 will be around for a while 00:43:28 #action back port the fix to update image id of VMSS to 2.7.x ( early January release) Zim and yungezz 00:43:35 Yeah, 2.8 freeze is mid March 00:43:44 if it's been merged into devel I would create the backport PR now 00:43:58 The RM will merge when it comes closer to the next release 00:44:06 Yes it’s merged into devel 00:44:38 cool, no sense waiting to open the backport PR. It allows you to get everything sorted in case anything comes up and you miss the next window 00:44:52 Yep 00:45:03 Got it 00:45:18 Anything else needed from me? Gotta hit the road to get back home before traffic gets too bad 00:45:39 No topic from me. 00:45:40 No from me. thanks all 00:45:50 Thank you all. 00:45:53 thanks 00:45:58 Bye 00:46:04 #endmeeting