00:00:02 <nitzmahone> #startmeeting Ansible Azure Working Group
00:00:02 <zodbot> Meeting started Thu Nov 15 00:00:02 2018 UTC.
00:00:02 <zodbot> This meeting is logged and archived in a public location.
00:00:02 <zodbot> The chair is nitzmahone. Information about MeetBot at http://wiki.debian.org/MeetBot.
00:00:02 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
00:00:02 <zodbot> The meeting name has been set to 'ansible_azure_working_group'
00:00:16 <nitzmahone> #chair yungezz zikalino82 yuwei
00:00:16 <zodbot> Current chairs: nitzmahone yungezz yuwei zikalino82
00:00:21 <nitzmahone> Hey all !
00:00:26 <zikalino82> hello
00:00:30 <yuwei> hi
00:00:36 <yungezz> Hello
00:01:11 <jborean93> hey
00:01:17 <nitzmahone> #chair jborean93
00:01:17 <zodbot> Current chairs: jborean93 nitzmahone yungezz yuwei zikalino82
00:01:28 <Kylie_> Hi
00:01:30 <nitzmahone> #chair Kylie_
00:01:30 <zodbot> Current chairs: Kylie_ jborean93 nitzmahone yungezz yuwei zikalino82
00:02:08 <yungezz> I have one thing to share, another team in Microsoft working on some network device os is trying to contribute to ansible
00:02:18 <yungezz> Mainly on network
00:02:24 <Kylie_> yes, go ahead. Sonic
00:02:33 <yungezz> Yes
00:03:37 <nitzmahone> Do they need something, or just FYI?
00:03:43 <nitzmahone> (FMI? ;) )
00:03:48 <yungezz> They’re still evaluating which folder to go to and release cycle
00:03:53 <yungezz> Just FYI
00:04:18 <Kylie_> Do they know who they should talk to? From Ansible networking?
00:04:24 <yungezz> No
00:05:31 <Kylie_> Then I believe Matt or Jordan can help connect them with the right people.
00:06:01 <nitzmahone> Probably go to #ansible-network or #ansible-devel on IRC (mostly during US Eastern Time working hours)
00:06:45 <nitzmahone> I guess it depends if they're needing technical information or more business side
00:07:58 <Kylie_> I think both. They already had code in GitHub and got them work. Need to see how to upstream them.
00:08:28 <Kylie_> However I was not in the meeting with them yesterday but Catherine was. So above is my personal understanding:).
00:08:51 <nitzmahone> 2.8 should include all the necessary stuff to do "out of band" distribution, which is what we'll be encouraging for pretty much everything once it's out
00:09:04 <nitzmahone> (via Galaxy, with proper support for plugins etc)
00:09:06 <yungezz> Yes, They’re evaluating where and how
00:09:15 <yungezz> And integration test
00:10:05 <nitzmahone> 2.8 release will likely be a longer development cycle than normal; it's looking like final release at the beginning of May
00:10:46 <yungezz> So from 2.8, galaxy is ready for role collection?
00:10:57 <Kylie_> Once cloud provider parts move to "out of band" distribution, what is the working model?
00:11:23 <yungezz> Is there plan to move cloud provider out of core?
00:11:24 <Kylie_> May, it is a long cycle.
00:11:44 <nitzmahone> Yeah
00:12:35 <nitzmahone> We're not planning to actively "eject" anything right now, but once Galaxy is viable for general distribution, Ansible's release cycles will likely slow down to 1-2 times a year
00:13:25 <nitzmahone> The Galaxy parts will come after 2.8, but there's "chicken and egg" problem if we're both waiting on each other, so Ansible will ship with the necessary bits first.
00:14:25 <Kylie_> Will you only take care of "core"? Or do you still take the responsibility for Ansible role for Azure?
00:14:28 <nitzmahone> The intent is to make it so that there are no "compromises" to shipping in Galaxy, and to allow bugfixes and features to roll on whatever cadence the code owners want, rather than waiting for Ansible releases.
00:14:49 <yungezz> So after our azure role ready with necessary plugin, existing cloud modules will be moved out of core?
00:14:50 <Kylie_> You mean core will be released 1-2 times a year. And customers could have core plus different roles for their usage.
00:14:52 <nitzmahone> We're trying to get it so that we're only needing to focus on the core stuff
00:15:12 <nitzmahone> s/roles/"collections", but yeah
00:16:27 <yungezz> Any guideline on how to prepare right role with necessary plugin so far?
00:16:39 <Kylie_> I see. Need to see how to convince customers to use core + roles since currently some customers only buy in upstream releases instead of roles.
00:16:43 <yungezz> Role collections
00:16:52 <nitzmahone> Not yet; that will come after Ansible can actually consume it and the Galaxy server bits to support it have gone live
00:17:00 <yungezz> Got it
00:17:42 <yungezz> So our new modules will go into 2.8 by now?
00:17:46 <nitzmahone> But Azure was one of my primary use cases for designing a lot of this stuff
00:18:02 <nitzmahone> Yeah, nothing changes for now, just telling you what's coming
00:18:48 <yungezz> Great
00:18:49 <Kylie_> Good to know. Thank you Matt.
00:18:51 <nitzmahone> Out-of-band distribution of Azure modules/content was one of the primary use-cases in mind for this when designing it, so we'll be testing all that internally
00:19:20 <nitzmahone> (whenever it's all ready and you decide you want to publish things that way, you can probably just take our sample repackaging and run with it)
00:19:34 <yungezz> That’s great:)
00:20:14 <Kylie_> We will introduce Ansible to our internal open source community tomo
00:20:18 <nitzmahone> It's been a busy week, but I managed to get to most of the queued reviews from the last few weeks- just two more to finish (cosmosdb and rediscache)
00:20:39 <yungezz> Thanks Matt
00:21:06 <nitzmahone> Oy, cosmosdb API is ... interesting
00:21:55 <Kylie_> tomorrow. I would like to double confirm 3 concepts - Ansible open source; Ansible engine; Ansible Tower. It is clear for Ansible Tower. Ansible engine is a release of Ansible open source. Right? Or anything else in Ansible engine? Do you know it? Thanks.
00:22:26 <jborean93> AFAIK Ansible engine is Ansible open source just with support
00:22:51 <yungezz> Ansible engine is paid, right
00:23:06 <nitzmahone> Yes, we're trying very hard to keep Ansible Engine exactly equivalent to upstream Ansible core open source releases
00:23:06 <Kylie_> Thank you Jordan. Understand it now.
00:23:39 <jborean93> yuungezz: yep engine is paid
00:23:41 <nitzmahone> (it's a strange model for Red Hat, usually the supported packaged product differs from the upstream in various ways)
00:23:58 <Kylie_> Then when we talk about certified modules, it is related to Ansible engine (pay support for certified part?).
00:24:42 <nitzmahone> I think the "support for certified content" is a separate SKU above Engine support, but $business (shrug) ;)
00:25:25 <Kylie_> I see. Thank you for information:). And BTW, the team is also preparing for topic submission for Red Hat Summit.
00:25:33 <nitzmahone> nice
00:26:00 <nitzmahone> I submitted the same module dev talk I did at 'Fest; might or might not submit something else before the deadline (soon!)
00:27:08 <Kylie_> Catherine, I am done for my topics. Do you want to talk about PR in detail?
00:27:29 <Kylie_> Nice, Matt. We may meet again in Boston:).
00:27:41 <yungezz> I ‘ m good
00:27:44 <nitzmahone> Excellent!
00:27:53 <yungezz> Will check or comments
00:27:58 <yungezz> Pr
00:28:00 <nitzmahone> Any other PRs you need looked at other than cosmos and redis?
00:28:16 <yungezz> No more from me
00:28:30 <yuwei> no from my side
00:28:36 <yungezz> zikalino82: do you have any like hdinshgt?
00:28:39 <Kylie_> @zikalino82 and @yuwei, any PR you want to discuss here?
00:28:41 <zikalino82> oh, yes
00:28:47 <zikalino82> just a sec
00:29:25 <zikalino82> this one: https://github.com/ansible/ansible/pull/47602
00:29:58 * nitzmahone adds to queue
00:30:11 <nitzmahone> #action nitzmahone to review https://github.com/ansible/ansible/pull/47602
00:30:53 <nitzmahone> Well, if nothing else today, short meeting! :D
00:31:00 <Kylie_> Thank you all:)
00:31:06 <yungezz> Thanks all
00:31:11 <jborean93> thanks
00:31:11 <yungezz> Bye
00:31:16 <nitzmahone> #endmeeting