00:00:40 <nitzmahone> #startmeeting Ansible  Azure  Working Group
00:00:40 <zodbot> Meeting started Thu Nov 29 00:00:40 2018 UTC.
00:00:40 <zodbot> This meeting is logged and archived in a public location.
00:00:40 <zodbot> The chair is nitzmahone. Information about MeetBot at http://wiki.debian.org/MeetBot.
00:00:40 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
00:00:40 <zodbot> The meeting name has been set to 'ansible_azure_working_group'
00:01:01 <nitzmahone> #chair jborean93 yungezz yuwei zikalino82 Kylie_
00:01:01 <zodbot> Current chairs: Kylie_ jborean93 nitzmahone yungezz yuwei zikalino82
00:01:10 <jborean93> hey
00:01:14 <yuwei> hi
00:01:21 <Kylie_> I noticed that Matt Clay added some notes yesterday.
00:01:31 <yungezz> Yes
00:01:47 <Kylie_> https://www.irccloud.com/pastebin/UHg4dRxZ
00:01:59 <Kylie_> Reminder to check for the stale_ci label before merging PRs. Ideally use the rebuild_merge bot command instead of manually merging (the bot checks for stale_ci and rebuilds if needed).
00:01:59 <Kylie_> Two PRs were merged which were marked stale_ci and both had CI failures:
00:02:00 <Kylie_> ansible/ansible#46796
00:02:00 <Kylie_> ansible/ansible#47045
00:02:09 <yungezz> We wasn’t aware of the stale_ci tag
00:02:22 <Kylie_> Who will follow up?
00:02:28 <yungezz> Thanks Matt clay for fixing and remind it
00:02:36 <jborean93> yea, from time to time we add more validation checks or just other changes that could cause a text failure in the future
00:02:38 <yungezz> It’s fixed already
00:02:51 <Kylie_> I see.
00:03:08 <jborean93> best to merge by adding a comment saying `rebuild_merge` and the bot will rerun CI if the PR is "stale"
00:03:14 <yungezz> We’ll keep in mind on stale_ci tag
00:03:21 <Kylie_> Ok. I have no other topic. Go ahead for PRs.
00:03:22 <jborean93> sounds good, thanks
00:03:24 <yungezz> Got it
00:03:41 <yungezz> I have a new one
00:05:17 <yungezz> https://github.com/ansible/ansible/pull/48862
00:06:06 <yungezz> zikalino82: do you have prs to review?
00:06:28 <zikalino82> just cosmos db please: https://github.com/ansible/ansible/pull/47181 :-)
00:06:43 <nitzmahone> I still have 47181 and 47602 on my pile; they're somewhat large and complex, so I haven't had time to dig into the underlying resources yet
00:07:18 * nitzmahone just merged the rediscache one- relatively simple
00:07:29 <yungezz> Thanks Matt
00:07:38 * nitzmahone adds 48862
00:07:55 <nitzmahone> Did anybody want to check out 49243?
00:08:07 <nitzmahone> https://github.com/ansible/ansible/pull/49243 (AZ support for VM module)
00:08:14 <zikalino82> pls focus on 47181, i will update 47602
00:08:47 <zikalino82> i can check this
00:08:57 <zikalino82> i will be working on vm soon
00:09:05 <nitzmahone> 👍
00:09:17 <yungezz> Great
00:10:11 <nitzmahone> Anything else exciting happening?
00:10:54 <jborean93> any movement on the Ansible solution template you spoke about last week?
00:11:12 <yungezz> It’s under Microsoft review before live
00:11:41 <yungezz> I m resolving comments
00:13:22 <jborean93> cool
00:14:31 <nitzmahone> Nothing else to talk about on this end today...
00:14:33 <Kylie_> Catherine, do u want to share our plans for new modules?
00:15:44 <yungezz> Sure. We plan to add new modules for service bus, app service environment, devtest lab, vpn in next several weeks
00:16:10 <nitzmahone> Cool- anticipated complexity high/med/low?
00:16:10 <yungezz> And part of api gateway
00:16:19 <nitzmahone> oof, suspect that one will be complex
00:16:26 <yungezz> Yes
00:16:51 <zikalino82> hehe, api gateway could be around 100 modules ;-)
00:18:09 <zikalino82> regarding devtev labs, we will add around 7 modules + 7 facts
00:18:41 <jborean93> that's a lot
00:18:43 <nitzmahone> I'm planning to be on vacation ~ Dec 15-Jan 5, but still plenty of time there. Planned freeze for 2.8 is now ~ late March I believe
00:19:26 <yungezz> I haven’t check detail on service bus yet, might be med to. for app service environment, creation time might be long, need check update from service tram
00:19:39 <nitzmahone> yay, more fun to test :(
00:20:11 <yungezz> +1
00:20:56 <Kylie_> Modules for PaaS are generally not small. Any way to fasten your review? Links for PaaS Scenarios we implement?
00:21:20 <nitzmahone> That definitely helps
00:22:12 <zikalino82> yeah, i think that
00:22:17 <zikalino82> that's a good idea
00:22:27 <Kylie_> Well received.
00:22:39 <zikalino82> perhaps i could create entire devtest labs scenario in a single pr for instance + sample playbook
00:23:14 <nitzmahone> Yeah, also helpful to see how those things work together when considering UI stuff
00:23:21 <yungezz> It will be too large for review..
00:24:02 <zikalino82> i know... but maybe easier to merge entire thing, instead of having halfly merged :-)
00:24:44 <nitzmahone> We're also getting to the point where you all "get it" about the way Ansible stuff should work in general, so we're having to do a lot less back and forth on modules.
00:24:46 <zikalino82> devtest labs is really 2 complex modules + several smaller modules
00:25:54 <nitzmahone> So reviews have been getting much quicker once we actually get around to them
00:26:49 <nitzmahone> But if you have usage samples you can at least link to from PRs (or send under separate cover via email or whatever if they're not ready for public consumption), that definitely helps us see how it should be used in the real world
00:27:22 <zikalino82> ok, we'll link through prs
00:27:22 <nitzmahone> Because I know very little about any of those right now
00:27:52 <nitzmahone> Have done a little with AWS API gateways, nothing with Azure's
00:28:41 <yungezz> We’re trying looking at the difference also
00:28:57 <Kylie_> Zim, for existing ones, you may want to provide some info for HDinsight and cosmos to help Matt complete review before vacation.
00:29:20 <nitzmahone> Yeah, I know zero about either of those services, which is part of the reason I've been slow to review
00:29:24 <zikalino82> i have , i will add the link
00:30:16 <Kylie_> Nice
00:30:21 <zikalino82> cosmos db is pretty simple though.. hd insight is tough.... actually very difficult to get it right based on current api documentation. lots of undocumented things.
00:30:47 <Kylie_> You could share your handwriting:)
00:32:27 <nitzmahone> Cool- I'll keep an eye out for the links on those two
00:33:15 <nitzmahone> Anything else for today?
00:33:24 <yungezz> A minor question, seems we cannot edit wiki page at ansible/community repo
00:33:42 <yungezz> We’re trying to update azure coding guidelines
00:34:00 <nitzmahone> Hrm, lemme check into that. Who has tried to edit?
00:34:06 <yungezz> Cannot see the “edit” button now
00:34:14 <yungezz> Myself and zim
00:34:23 <yungezz> Zim was able to
00:34:32 <yungezz> But not now either
00:35:28 <nitzmahone> There was some group consolidation that happened in the GH org recently, might have gotten lost in the shuffle. You both still have commit on ansible/ansible though, right?
00:35:47 <yungezz> Yes
00:35:55 <nitzmahone> @mattclay --^
00:36:22 <yungezz> Ok, will sync with Matt clay to get help
00:36:33 <yungezz> Thanks Matt
00:36:36 <mattclay> Permissions issue editing the community wiki?
00:36:40 <nitzmahone> Seems like it
00:36:42 <yungezz> Yes
00:36:52 <mattclay> yungezz: Just for you and zim?
00:36:59 <yungezz> And Yue hi
00:37:05 * mattclay looks
00:37:05 <yungezz> Yuwzho
00:40:22 <mattclay> OK, I think you should have access now.
00:40:34 <yungezz> Thanks Matt!
00:41:13 <nitzmahone> Thanks!
00:41:42 <nitzmahone> Shall we close out for the day, then?
00:42:00 <yungezz> Ok, thanks all
00:42:50 <yungezz> Kylie_: zikalino82 anything else from you
00:44:50 <nitzmahone> Sounds like a no... ;)
00:44:56 <nitzmahone> Closing in 5...
00:44:58 <nitzmahone> 4...
00:45:00 <yungezz> :)
00:45:02 <nitzmahone> 3..
00:45:03 <nitzmahone> 2..
00:45:05 <nitzmahone> 1..
00:45:07 <nitzmahone> Thanks all!
00:45:10 <nitzmahone> til next week!
00:45:13 <nitzmahone> #endmeeting