15:00:07 <srwilkers> #startmeeting openstack-helm
15:00:08 <openstack> Meeting started Tue Jul 25 15:00:07 2017 UTC and is due to finish in 60 minutes.  The chair is srwilkers. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:09 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:11 <openstack> The meeting name has been set to 'openstack_helm'
15:00:20 <korzen> hello
15:00:24 <xek> o/
15:00:28 <srwilkers> hello everyone o/
15:00:29 <jayahn> o/
15:00:30 <alraddarla> o/
15:01:04 <dulek_mobile> Hi.
15:01:15 <srwilkers> heres the agenda for today:  https://etherpad.openstack.org/p/openstack-helm-meeting-2017-07-25
15:01:22 <srwilkers> feel free to add to it as we move along
15:01:45 <srwilkers> #topic PTG reminder
15:02:19 <srwilkers> just a reminder, we've got an etherpad started to start drafting topics to chat about in denver for those who will be present:  https://etherpad.openstack.org/p/openstack-helm-denver-ptg-topics
15:02:31 <srwilkers> myself, lrensing and portdirect will be there for certain
15:02:57 <jayahn> dan from skt will be there, i am not sure I can go or not yet.
15:03:12 <srwilkers> i hope you can make it jayahn :)
15:04:05 <srwilkers> but feel free to add to this etherpad, and any topics you place in there can be included in the weekly meetings.  we dont necessarily need to wait until september to chat about them
15:04:26 <jayahn> two main blockers; my company's funding, my wife's approval. :)
15:05:07 <srwilkers> im all too familiar with the second in that list :)
15:05:21 <srwilkers> #topic Spec directory patch: https://review.openstack.org/#/c/482643/7
15:05:54 <srwilkers> i cant see who added this topic as they're unnamed in the agenda etherpad
15:05:56 <korzen> can we gat this merged
15:06:04 <korzen> get*
15:06:06 <srwilkers> yeah
15:06:11 <korzen> I did add it ;)
15:06:18 <srwilkers> i noticed there was some feedback left by you and dulek_mobile :)
15:06:27 <srwilkers> ill get that addressed, then we can get it moved in
15:06:35 <dulek_mobile> Yeah, don't mind my review too much, we can fix up docs in follow up patch.
15:06:36 <korzen> I wanted to start work on more specs
15:06:43 <srwilkers> korzen: awesome
15:06:57 <jayahn> way to go korzen
15:07:01 <srwilkers> duleks mention of the exporter stuff for prometheus would also make it nice to get merged in if he wants to draft one
15:07:12 <dulek_mobile> Yup!
15:07:50 <korzen> so I have checked why the spec is not rendered
15:08:10 <korzen> and would be simpler if spec directory would be under doc
15:08:18 <korzen> not outside of it
15:08:31 <korzen> because we cannot create the rendered list
15:08:45 <srwilkers> yeah, that makes sense
15:08:52 <srwilkers> that'd be an ideal placement i think
15:09:20 <korzen> in other OpenStack projects, specs are placed in separate repos
15:09:56 <korzen> like for example: https://github.com/openstack/neutron-specs
15:10:12 <korzen> and then you have: https://github.com/openstack/neutron-specs/tree/master/specs
15:10:25 <korzen> which is containing the release name
15:10:56 <korzen> but for our use, we can take it simple
15:11:02 <korzen> ale hold the specs inside docs
15:11:14 <srwilkers> yeah, i think that'd be a better fit for now
15:11:33 <srwilkers> as soon as we wrap up today, ill get it moved and link for reviews
15:12:34 <korzen> ok, I guess we are ok
15:12:46 <srwilkers> #topic Neutron multiple SDN bp: https://blueprints.launchpad.net/openstack-helm/+spec/neutron-multiple-sdns
15:12:58 <korzen> that is another one from me ;)
15:13:18 <srwilkers> awesome :) floors yours
15:13:26 <korzen> so I have created the bp for multiple SDN work
15:14:00 <korzen> I have updated portdirect's patch: https://review.openstack.org/#/c/481225
15:14:09 <korzen> which I like very much
15:14:25 <korzen> I am currently wrapping up the idea in a spec
15:14:39 <jayahn> korzen: awesome
15:14:54 <korzen> so that we can agree on how to continue work with multiple SDN
15:15:02 <srwilkers> okay, cool
15:15:41 <korzen> when we settle down the spec and above patch, we can continue with my Linuxbridge implementation: https://review.openstack.org/#/c/466293
15:16:13 <korzen> also SONA work is related
15:16:31 <korzen> which can benefit from decomposable neutron chart
15:16:49 <jayahn> true.
15:17:09 <korzen> As I commented in SONA review
15:17:22 <korzen> most stuff is reusable from neutron chart
15:17:23 <jayahn> we saw that, and really appreciate your effort.
15:18:44 <korzen> I'm planning to work on calico SDN as an example of how multiple SDNs can fit into OSH
15:19:40 <korzen> jayahn, yes, thanks for the patch of SONA it really helped to see what are requires to base neutron chart
15:19:58 <korzen> requirements*
15:20:38 <korzen> any questions?
15:21:01 <jayahn> not for now.
15:21:08 <srwilkers> not from me -- im looking forward to seeing where this all goes :)
15:21:10 <korzen> ok, so we can proceed :)
15:21:41 <srwilkers> #topic opencontrail helm chart
15:21:52 <srwilkers> blueprint referenced is here:  https://blueprints.launchpad.net/openstack-helm/+spec/opencontrail-helm-chart
15:22:12 <srwilkers> v1k0d3n: i think this was yours.  floors yours :)
15:23:09 <korzen> is he online?
15:23:22 <srwilkers> it doesnt appear so
15:23:49 <srwilkers> we can check back at the end to see if he's here
15:24:04 <srwilkers> #topic chart orchestration
15:24:10 <srwilkers> jayahn: floors yours :)
15:24:25 <jayahn> this is just our note for chart orchestration requirements.
15:24:50 <jayahn> at skt, we have tried landscaper, but not happy with it. now, we are again exploring this space.
15:25:05 <jayahn> at&t armada is also an important activity for openstack-helm.
15:25:47 <jayahn> thus, anyone who are interested in this discussion, pls put your idea/ story / requirements in etherpad.
15:25:49 <jayahn> https://etherpad.openstack.org/p/openstack-helm-chart-orchestration-discussion
15:26:59 <jayahn> that is all from me.
15:27:33 <jayahn> we ca surely discuss during ptg event
15:27:45 <srwilkers> yeah, i see that being a big part of the discussion there
15:27:57 <srwilkers> would be awesome to get more feedback before then :)
15:28:28 <korzen> I will take a loot
15:28:31 <korzen> look*
15:28:54 <jayahn> from our experience, this is not just "how to deploy" problem, it will affects how operator operate openstack and how developers use this tool at development phase.
15:29:17 <jayahn> and how CI will leverage this tool as well.
15:29:34 <jayahn> so, we tends to go deep when we discuss this topic inside skt. ;)
15:30:01 <jayahn> any further question?
15:30:07 <srwilkers> not from me :)
15:31:09 <srwilkers> reached out to v1k0d3n -- he's going to hop online
15:31:49 <v1k0d3n> ok
15:31:52 <v1k0d3n> sorry...here now
15:31:58 <srwilkers> #topc opencontrail helm chart
15:32:05 <srwilkers> #topic opencontrail helm chart
15:32:09 <v1k0d3n> so was just wondering if there was a status on the opencontrail, or if there was any need for help.
15:32:10 <srwilkers> words are hard today -- floors yours :)
15:32:59 <srwilkers> v1k0d3n: i haven't heard any updates on the status here.  might be something to ping portdirect about in openstack-helm later today
15:33:50 <srwilkers> are there acceptable images for opencontrail?  i haven't dug deep enough to know for certain
15:36:36 <srwilkers> ill put this on next week's meeting agenda and follow up with madhukar about the blueprint he filed
15:36:40 <srwilkers> any other questions?
15:37:12 <v1k0d3n> ok. i guess nobody can speak to this.
15:37:19 <v1k0d3n> that works.
15:37:21 <v1k0d3n> thanks man
15:37:28 <srwilkers> no problem :)
15:37:40 <srwilkers> #topic open discussion
15:37:56 <srwilkers> any other topics/questions/concerns anyone would like to chat about?  we've got about 20 minutes left
15:38:55 <dulek_mobile> My usual fernet review beg? :) I would love to close that topic.
15:39:08 <srwilkers> dulek_mobile: i'd really like to get it closed too
15:39:25 <dulek_mobile> :)
15:39:33 <srwilkers> ill try to rally everyone today and get consensus here
15:40:03 <korzen> any plans to have a release schedule for OSH?
15:40:06 <dulek_mobile> Great, thank you!
15:41:01 <jayahn> that would be really good discussion on release stuff. i see that is in ptg agenda.
15:41:13 <srwilkers> dulek_mobile: no problem :)
15:41:21 <v1k0d3n> yes....omg please yes releases
15:41:25 <srwilkers> jayahn: korzen: yeah, that'd be best suited for PTG i think
15:41:41 <srwilkers> i think that's a perfect topic
15:42:22 <dulek_mobile> So no releases till September?
15:43:54 <srwilkers> i dont think we're too far off from having a chat about targeting a time line
15:44:34 <srwilkers> personally, id like to see the operational bits, like LMA, get in a better spot first.  the neutron backend stuff will help quite a bit as well
15:45:19 <dulek_mobile> Okay, got you.
15:45:30 <korzen> yes, it would be good to see some list what should be be completed to call it a release readyness
15:45:32 <v1k0d3n> we should have some potential dates, and communicate these
15:45:51 <jayahn> are there any plan to include "openatack version" in osh release policy?
15:46:15 <v1k0d3n> good question
15:46:40 <jayahn> because of differences on various stuff, it will be difficult to make a "generalized" chart to cover multiple versions of openstack, or is it possible?
15:47:46 <srwilkers> we haven't broached that topic yet.  for now, we've just been focused on one version to keep development moving along
15:47:56 <srwilkers> but it's defiintely something that will need to be considered further down the road
15:48:46 <jayahn> i was just curious, since the upstream release policy probably affects how we do internal release in our ci pipeline, including versioning.. :)
15:49:15 <jayahn> not high priority.
15:49:59 <srwilkers> yeah, thats a good point.  more reason to have this chat in person at the PTG :)
15:50:09 <jayahn> yeap, agreed.
15:50:34 <v1k0d3n> yeah great topic for PTG.
15:51:00 <srwilkers> any other topics?
15:51:28 <v1k0d3n> it would minimize some of the confusion users would have on what works, what does, etc. plus it would give the team breathing room, because they can say use version xyz. less fire drills.
15:51:31 <v1k0d3n> no more from me.
15:51:46 <jayahn> no more from me
15:51:59 <korzen> I'm good
15:52:14 <srwilkers> yeah v1k0d3n, fair point :)
15:52:34 <srwilkers> awesome.  ill go ahead and close out the meeting then.  we can continue any further discussion in openstack-helm
15:52:38 <srwilkers> good chat as always :)
15:52:46 <srwilkers> #endmeeting