00:00:24 #startmeeting Ansible Azure Working Group 00:00:24 Meeting started Thu Aug 9 00:00:24 2018 UTC. 00:00:24 This meeting is logged and archived in a public location. 00:00:24 The chair is nitzmahone. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:00:24 Useful Commands: #action #agreed #halp #info #idea #link #topic. 00:00:24 The meeting name has been set to 'ansible_azure_working_group' 00:00:49 Hello 00:00:54 So far it looks like the spambots haven't found this channel yet :) 00:00:55 hi 00:01:20 Nice :) 00:01:58 hey 00:01:58 #chair yungezz zikalino82 yuwei 00:01:58 Current chairs: nitzmahone yungezz yuwei zikalino82 00:02:07 #chair jborean93 Kylie_ 00:02:07 Current chairs: Kylie_ jborean93 nitzmahone yungezz yuwei zikalino82 00:02:12 Hi all 00:02:14 hello :-) 00:02:18 Hi 00:02:42 Hey Kylie, you want to run things today? 00:02:57 I have some topics related to PR. 1) PR for new modules; 2) PRs Zim you submitted to enable Openshift on Azure 00:03:29 3) Other items planned for 2.7 - Azure stack; VMSS inventory; key vault 00:03:50 For 1), Zim, Catherine and Yuwei, what PR do you want to discuss here? 00:04:12 My vmss inventory pr https://github.com/ansible/ansible/issues/40327 00:04:35 It’s community contribution 00:04:41 I did update 00:04:48 https://github.com/ansible/ansible/pull/41533 00:04:54 auto scale 00:05:34 I see Matt has some comment to the route one 00:05:35 remaining pr for openshift is a part of somebody else's pr https://github.com/ansible/ansible/pull/43695 00:05:58 Yeah, the route stuff is very close- a few minor things and we're ready to merge 00:06:02 Same for the postgres facts 00:06:36 i will change it today 00:06:51 @yuwei: do you know Cai Hao pr for traffic manager? 00:06:52 ok, so i can fix these minto things, and maybe yungezz can merge when fixed? 00:06:59 #action yuwei, update https://github.com/ansible/ansible/pull/41175 per comments 00:07:43 Traffic manager:https://github.com/ansible/ansible/issues/40327 00:08:08 With facts 00:09:10 I was looking at auto scale just before this; tis a big one, so I suspect will take some time and a few rounds 00:10:25 i see 00:10:32 I started review on appgateway again also, but it seems that there are still codepaths that aren't being tested. All these modules that have embedded lists of sub-resources we need to figure out how to handle consistently (ie, is it "make the list like this" vs "add this item") 00:10:33 Matt, when you say postgres facts, do you mean https://github.com/ansible/ansible/pull/43327? 00:11:55 https://github.com/ansible/ansible/pull/43328 00:12:23 Understand the effort for auto scale. Considering feature freeze date is upcoming (end of this month?), it is better to complete it to catch up 2.7:). Thank you. 00:12:38 And traffic manger 00:13:15 Hrm, looks like 2x copies of postgres facts? (43327/43328- I reviewed 43328) 00:13:17 nitzmahone "the list like this" vs "add this item" -- so what's your idea? which one we should follow? 00:13:32 no, there's server and database 00:13:37 facts 00:13:41 ahh 00:13:49 OK, will look at 43327 00:13:52 database stil [WIP] - i need to add tests etc 00:14:33 Then Zim, could you please complete them before next Tuesday? Then Matt and Jordan can have enough time to review them. 00:15:03 yes, i have a few facts modules, but all pretty small 00:15:12 just want to fill the gap 00:15:53 I know another partner is planning to dump a huge wad of modules on us next week- hopefully won't fall to me to review again 00:16:31 Related to Azure? 00:16:32 @Kylie_: how about we send a list of new module for 2.7 to Matt? So Matt could understand our priorities when reviewing prs? 00:17:13 Yes. Let me summarize the list here. 00:18:11 @yungezz, what is the PR for traffic manager? And do we have plan for CDN? 00:18:43 Tm https://github.com/ansible/ansible/pull/43812 00:18:51 Cdn is coming 00:19:08 Yes cdn is planned 00:19:30 Matt, Web App scenario is the top scenario we would like to build and include in 2.7. 00:20:23 It includes Web App (done), App Service Plan (done), Traffic Manager (https://github.com/ansible/ansible/pull/43812) and CDN (upcoming). 00:21:02 OK, good to know 00:21:08 That's probably doable 00:21:33 So long as CDN is in pretty soon- how complex will that one be (multiple modules?) 00:22:23 One module, one facts module 00:22:44 Deep-and-complex arguments, or pretty straightforward? 00:23:07 (every time we do something new, we have to go play with and learn about the resources to see if the module UI makes sense) 00:23:09 Not too deep 00:23:19 cool 00:23:19 Agree 00:24:01 So back to Zim's question about modules that manage lists of sub-resources; there are a few options: 00:24:17 * require a separate module for each sub-resource type 00:24:43 * pick a single fixed strategy for list management ("make it like this" or "add if missing") 00:25:02 * use a mode parameter for each sub-resource list 00:25:27 #1 is a pain, but we do it for more complex sub resources 00:25:45 i am currently doing: "make it like this" 00:25:46 #3 is the most flexible for users, at the expense of somewhat more complex UI 00:26:15 OK cool, so long as that's consistent throughout, that's arguably the more useful of the two 00:26:16 so which one should we do, i will just follow your idea :-) 00:26:39 We also need to communicate that in the docs somehow 00:26:47 i was thinking whether perhaps instread of list we could have dicts 00:26:52 ok 00:27:30 we can always add the mode option in the future if there is demand 00:27:38 yes 00:27:39 what, dict sub-keys with lists? (eg, subnets: { exact: [], ensure_present: [], delete: [] }) 00:27:54 s/delete/ensure_absent/ 00:28:14 hmm... i was thinking of dicts of resources instead of list... well... i think not a good idea... 00:28:52 Yeah, depends on the resource- the dict "key" has to be a single unique value and usable, which works for some but not others 00:29:07 but, (eg, subnets: { exact: [], ensure_present: [], delete: [] }), .... maybe too complex 00:29:32 Yeah, that was my thought too, just wasn't sure where you were going with "use a dict" 00:29:34 I'm not too much a fan of that format 00:29:38 nor I 00:29:44 especially since exact is mutually exclusive to the others 00:29:48 yep 00:29:49 ok, let's stick with "make it like this" list, and possibly add param later 00:29:52 +1 00:29:58 sounds good to me 00:31:33 I've been working with Ryan on the design/impl for the cloud-as-inventory stuff; he was working on it yesterday, but not sure how far along it is yet. May slide into 2.8, but should still be workable for Ignite and/or AnsibleFest demo. 00:31:57 Zim- did they accept your talk? I know they sent out a batch of acceptance, but not sure if they've finished 00:32:18 (they accepted one of my proposals that I wasn't expecting) 00:32:29 @yungezz, you mentioned your solution for key vault depends on cloud-as-inventory. Right? 00:32:31 not yet 00:32:46 Yes 00:32:54 but yesterday i spoke to Stuart Kirk and and we agreed to co-present 00:32:57 I think there was one more batch they still needed to send out, so I don't know if I'm on the hook for 1 or 2-3 talks 00:33:21 Discussed with Matt and Jordan last week, will put it in role for now 00:33:40 Ok. 00:33:43 Maybe revisit it after cloud inventory ready 00:33:47 So the keyvault stuff will likely need to slip into 2.8; I don't want to push the cloud-as-inventory stuff out until it's ready, but keyvault will be an excellent use case to test with 00:34:07 What is rough schedule for 2.8? 00:34:24 Probably February-ish release? 00:34:47 @zikalino82, https://github.com/ansible/ansible/pull/43695 is the only fix you need to enable OpenShift on Azure. Right? Any else? 00:34:50 (we haven't talked calendar yet, but we always have to bake in a little extra time for holidays on the end-of-year stuff) 00:35:16 Kylie_ 00:35:24 yes, just includes too much other stuff... 00:35:49 ugh, "accept_terms" 00:35:50 i created my own pr but closed 00:36:09 maybe i should reopen, because it's really simple and could go in faster 00:36:36 Did you talk w/ the contributor spmp? 00:36:57 yes 00:36:59 he's usually in this chat, was here earlier this morning 00:37:08 but I saw him leave as the meeting started 00:37:09 but silent 00:37:15 All tests green: Can some of you good peple review/approve my PR's: https://github.com/ansible/ansible/pull/43335 https://github.com/ansible/ansible/pull/43588 https://github.com/ansible/ansible/pull/43695 00:37:19 Thanks 00:37:19 s/chat/channel/ 00:37:31 cool he's back 00:37:32 speak of the devil and he shall appear ;) 00:38:07 Welcome spmp back. It is great to have more people join discussion. 00:38:32 aaaah, crap, what did I do 00:38:49 nothing bad I assure you, welcome 00:39:20 Uh huh, thats a fire I see over there, looks good for roasting 8) 00:39:38 #43335, I saw Yuwei add comments. This is to add a new parameter but a bug fix. Jordan or Matt, do you wan to take a look or leave it to Zim and Catherine? 00:40:55 #43588, Yuwei added one comment. This is also to add a new parameter but changes are small. 00:41:05 My only commetn on 43335 is can you un-fix all the formatting changes in the test YAML 00:41:18 Otherwise you're taking attribution on all those 00:41:29 yes, that would be useful 00:41:42 I dont want attribution, just wanted consistent formatting as it got my OCD up. 00:41:52 But... quite a PITA to do 8/ 00:41:58 Right, but you touched all the lines, so you took attribution 00:42:08 Gotta live with what's there 00:42:15 the major thing was test 00:42:49 (I'm a two-spacer-YAML guy myself, so I feel your pain, but "when in Rome" and all) 00:43:13 When it's your module, you can write whatever you want that passes the linter ;) 00:44:16 So anyway, once the attribution issues are fixed on that one, feel free to merge 00:44:50 I am two spacer everwhere, but if spacing is X then use X everywhere. OK doing it now 8( 00:46:37 For https://github.com/ansible/ansible/pull/43695, we really want this fix ASAP because it also will unblock OpenShift set up on Azure. Zim, do you have any suggestion as the reviewer? Thanks. 00:48:54 Yeah, impl looks OK there at a glance, just the matter of the increased testing time 00:49:19 looks like `auth_source` is still in the tests, spmp: is that still needed after what we spoke about this morning? 00:49:21 Do the tests run now with a plan-required image? 00:49:42 Which test? I tried to remove it from everywhere. 00:49:49 on which branch 00:49:53 https://github.com/ansible/ansible/pull/43695/files#diff-767ce3092886ccbc7e8c33b649fe33bf 00:51:19 Oh, I thought I just removed them... 00:52:28 * nitzmahone wonders how much we'll be paying F5 every time we test this thign 00:52:42 #43335 00:52:51 Oooh so much. I can tell you the rate... hold on. 00:53:13 maybe we need to create an image in the marketplace and pay ourselves :) 00:54:29 We already dropped $1000 this month to Microsoft on busted undeleteable load balancers in our Azure subscription ;) 00:54:46 maybe Kylie_ can help follow that up? 00:54:48 (and many hours fighting with support) 00:55:02 $68.80AUD/hr 00:55:15 Yowtch 00:55:33 Good idea @jborean93 8) -10BTC/hr 00:55:57 yea, so in testing this environment build I could have bought two houses (not kidding) with the cost! 00:56:05 We definitely need to find a cheaper thing there; on a test failure, that will hang out for almost an hour 00:56:07 probably more now. 00:56:42 @nitzmahone and @jborean93, yes, our CSS just replied Matt Clay. 00:56:47 I was looking for hooks to note the failure and delete anyway. I hoped/assumed you created a resource group then destroyed it after test. 00:56:53 and if there's other problems, it will get cost-prohibitive quickly, esp since mattclay is still paying the Azure CI bill on his credit card because Microsoft invoicing contact has also ignored us 00:57:26 * nitzmahone wonders why we're paying for this at all, but that discussion has gone nowhere in 3 years 00:57:37 Yea... 00:57:48 We are a case in point as to why you should _not_ be. 00:58:04 You should have another 10 full time devs off our usage 00:59:02 As for "mattclay is still paying the Azure CI bill on his credit card because Microsoft invoicing contact has also ignored us", no idea for this one. Do you raise this before? Do you mean Ansible CI for Azure is under Matt's personal credit card? Will Red Hat pay for it? 00:59:07 Anyway, yeah, we need to figure out a free/very-cheap plan VM for that one 00:59:34 Yes, Red Hat reimburses, but when the bill exceeds $1000/mo the accounting people get grouchy 01:00:07 (we're not supposed to use credit cards for regular stuff this big, but our billing/invoicing contact at Microsoft is unresponsive) 01:00:11 i think perhaps we should have some unit tests for cases like that? 01:00:28 So either we keep it cheap or we'll stop being able to pay the bill 01:00:44 zikalino82 Yeah, that might be a better short-term solution 01:00:59 i actually think there's so many things to test 01:00:59 Module unit tests are rare and tricky 01:01:04 especially idempotence 01:01:09 can't test everything 01:01:14 what about we keep the test there but disable/comment it out 01:01:24 Or make it conditional 01:01:26 I've done that for a few windows modules that require a domain infra 01:01:29 I see. Red Hat has many subscriptions. Can you use one of corp subscription for this one? Or you want but no response from billing/invoicing contact at Microsoft. If it is this case, let me try to ask who could help though I also don't know billing people. 01:01:43 Nobody wants to share their subscriptions 01:01:57 Every time we've asked one of the other groups, they say "sorry, just for us, get your own" 01:02:15 I would guess some of the things we do as part of the CI require some higher level perms some people may not want to give out 01:02:24 That too 01:02:41 Yeah, I did get access to one of the company accounts -- but permissions were inadequate. 01:02:53 We definitely need our own for some things- the way the CI termination stuff works, wouldn't want to have other resources in there or they'd get killed all the time 01:03:45 Making the plan VM tests conditional with `when: enable_plan_vm|bool` or something is probably the best short-term solution 01:03:56 How hard would it be to get your friends at M$ to create a free VM that had a plan and needs terms accepted? 01:04:19 No clue- I've never tried to publish anything in Marketplace 01:05:38 we could publish ubuntu vm with ansible preinstalled ;-) 01:06:01 zikalino82 which part do you need for Openshift- the accept_terms part or the plan part? 01:06:13 (or both) 01:06:14 zikalino82 sounds expensive 01:06:17 no we don't need accept terms 01:06:28 we just need os disk size part 01:09:59 I see a couple of minor issues at a glance around the plan arg validation in the accept_terms case. 01:11:07 So dunno how fast spmp can turn around changes, but if we get off the expensive VMs and fix those, I'm probably fine to merge 43695 01:11:33 Yup, on it now if pos. Pretty easy to change VM. 01:11:38 (should be able to remove auth_source from those tests too at a glance) 01:11:39 What do you want done? 01:11:49 I'll do inline review comments 01:11:56 Nice. Thank you guys. 01:12:19 Hold on, I will check why auth_source is not removed from that branch and push before you review.. 01:14:07 Let me summarize items we discussed today on our high priority list. 01:14:26 Priority 1: 01:14:26 VMSS inventory - customer request 01:14:26 https://github.com/ansible/ansible/pull/40327 01:14:27 New modules for Web App scenario (basic): 01:14:27 Web App (done), App Service Plan (done), Traffic Manager (https://github.com/ansible/ansible/pull/43812) and CDN (upcoming). 01:14:27 New modules for complete scenario: 01:14:27 autoscale: https://github.com/ansible/ansible/pull/41533 (Matt will take a look) 01:14:28 Route table: https://github.com/ansible/ansible/pull/41175 (close to merge) 01:14:28 App gateway: https://github.com/ansible/ansible/pull/39940 (Matt will take a look) 01:14:29 Bug fixes: 01:14:29 https://github.com/ansible/ansible/pull/43335 https://github.com/ansible/ansible/pull/43588 https://github.com/ansible/ansible/pull/43695 01:14:58 Hope we could close discussion for most of them and move to next priority items:). Thank you Matt and Jordan!! 01:15:37 sounds good 01:15:41 Anything else for today? 01:15:43 Any other topic? 01:15:46 No from me. 01:15:49 nor here 01:16:00 no 01:16:10 Thank you all. 01:16:11 Pushed 01:16:18 noice 01:16:24 Thanks all- until next week! 01:16:26 #endmeeting