15:00:26 <srwilkers> #startmeeting openstack-helm
15:00:27 <openstack> Meeting started Tue Aug  8 15:00:26 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:28 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:30 <openstack> The meeting name has been set to 'openstack_helm'
15:00:32 <jayahn> hi
15:00:39 <srwilkers> hello everyone o/
15:01:32 <lrensing> o/
15:01:33 <jayahn> o/
15:01:38 <srwilkers> here's the etherpad for today -- https://etherpad.openstack.org/p/openstack-helm-meeting-2017-08-08
15:01:46 <xek> o/
15:01:51 <portdirect> \o/
15:02:05 <srwilkers> lets take a few minutes and add anything else to it
15:02:21 <srwilkers> ive got a few items on there to get us started, but wanted to make sure we give about 5 minutes for adding anything extra
15:02:46 <jayahn> yeah, i just got home after several drinks with colleague :)  adding stuff right now.
15:03:21 <srwilkers> oh nice jayahn :)
15:03:50 <alraddarla> o/
15:05:09 <srwilkers> alright, let's get started
15:05:13 <srwilkers> #topic Reviews
15:05:36 <srwilkers> i thought i had more items i'd like eyes on, but the main one for me currently is this one:  https://review.openstack.org/#/c/487877/
15:05:48 <srwilkers> it's dulek's spec for an openstack-exporter for prometheus
15:06:36 * dulek is in an urgent call currently, will try to answer questions though.
15:06:55 <srwilkers> would be nice to get some more eyes on it and offer some feedback.  i think it'd be helpful to get this moving sooner rather than later, and i'd like to support him in this effort as much as possible
15:08:14 <srwilkers> that's the only item i had for reviews -- any others?  i know we got eyes on dulek's fernet stuff and got it merged
15:08:57 <dulek> portdirect: Hey, thanks for testing fernet stuff! :)
15:09:06 <dulek> That's closed now. :)
15:09:16 <portdirect> yeah man - works great :)
15:09:52 <srwilkers> #topic Chart decomposition
15:10:39 <srwilkers> portdirect and i worked on getting the chart decomposition work he started spread to the remainder of the services
15:10:50 <srwilkers> portdirect: want to chime in here?
15:12:36 <portdirect> sorry - was distracted
15:12:37 <openstack> madhukar: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.
15:13:04 <portdirect> yeah - we rolled out a simple mechanism to turn on and off manifeststs as required
15:13:10 <portdirect> this is mostly for development use
15:13:31 <portdirect> but also makes it easier to plug alternative abckends into services (cinder/neutron/nova)
15:14:38 <srwilkers> im pretty pleased with it :)
15:15:11 <srwilkers> but i may be a bit biased ¯\_(ツ)_/¯
15:15:16 <jayahn> it is great stuff
15:15:18 <madhukar> Hi Pete, Do you have the link where we can track Helm Releases?
15:15:32 <madhukar> Hi Pete, Do you have the link where we can track Openstack-Helm Releases?
15:15:55 <srwilkers> hello madhukar o/
15:16:02 <portdirect> hey madhukar  o/
15:16:22 <portdirect> curently we dont have a realease - as we are wanting to get things stabelised a bit 1st
15:16:29 <portdirect> are you going to be at the ptg
15:16:36 <srwilkers> madhukar: that's one of the items we had planned to start discussing at the PTG in Denver in roughly a month
15:17:15 <portdirect> for helm releases we are tracking the current stable release
15:17:30 <madhukar> I would love to be there at the PTG, where can I find more details on the PTG meeting?
15:17:57 <portdirect> srwilkers: ^
15:18:17 <srwilkers> madhukar: you can find all the details here: https://www.openstack.org/ptg
15:18:33 <madhukar> thanks
15:18:37 <srwilkers> no problem :)
15:18:49 <srwilkers> #topic Armada gate
15:18:51 <portdirect> if you cannot make it to denver, we'll try and include you in the discussions surrounding this
15:19:00 <srwilkers> +1
15:19:01 <portdirect> I know its really important to you :)
15:19:50 <srwilkers> so we changed the old 2 node gate to a gate for Armada
15:20:05 <srwilkers> it's not functional yet, but hopefully will be soon :)
15:20:16 <srwilkers> portdirect has been working on that lately
15:20:20 <portdirect> I expect it to be running by EOD :D
15:20:36 <portdirect> just got sidetracked with these meetings things
15:20:41 <srwilkers> portdirect: thats awesome dude :)
15:20:46 <srwilkers> cant wait to see it running
15:21:10 <portdirect> seems like now i get to develop in the 5 minute gaps between calls :D
15:21:19 <jayahn> I know Armada pretty well by now. however, we might need a formal introduction of Armada to openstack-helm community.
15:21:20 <srwilkers> welcome to the corporate life
15:21:37 <portdirect> jayahn: that would be a good idea
15:21:41 <srwilkers> jayahn: +!
15:21:44 <srwilkers> +1, rather
15:21:47 <portdirect> I could get alex and co to join us next week
15:22:01 <srwilkers> that'd be a great idea
15:22:50 <jayahn> skt and at&t has been exchanging requirements and wishlist, that would be even better if we can make it to more broad discussion among here.
15:23:00 <srwilkers> jayahn: agreed
15:23:03 <portdirect> +2
15:23:33 <srwilkers> anyway, thats all ive got on that front
15:23:43 <srwilkers> anything else?
15:23:47 <jayahn> luckly, i found out that skt's requirements and priority is almost exactly overalping with at&t.. that means other folks will have very similar needs.
15:24:16 <srwilkers> jayahn: nice :)
15:24:30 <jayahn> ah, i would like to mention that skt removed SONA specific stuff from neutron decomposition PS.
15:24:55 <jayahn> will have a separate PS only for SONA specific one.
15:25:08 <portdirect> +2 thanks jayan
15:25:31 <portdirect> I'd like to keep the decomposotion stuff as light as possible
15:25:32 <jayahn> internally, we verified combination of sona specific stuff and neutron decomposition work really works.
15:25:52 <portdirect> i'm worried that if we start intodocuting logit to configmaps etc - then it will end up a scary mess
15:26:00 <portdirect> nice
15:27:01 <jayahn> :)
15:27:22 <srwilkers> #topic Ocata requirements
15:27:31 <jayahn> one more thing, about ocata requirements.
15:27:36 <jayahn> yeap
15:27:42 <srwilkers> floors yours :)
15:28:14 <jayahn> we looked at differences of kolla images between newton and ocata. there are few, but not much..
15:28:40 <jayahn> skt will test ocata deployment with openstack-helm till the next week.
15:29:17 <portdirect> madhukar: i think you have been running with ocata?
15:29:24 <jayahn> we are expecting (as portdirect mentioned in etherpad) not much work to make Ocata work
15:30:01 <jayahn> my real question is how openstack-helm will host different openstack versions. j
15:30:28 <jayahn> that surely is bigger discussion as portdirect  mentioned. :)
15:31:02 <portdirect> i think we will need to do one of two things: a branch per version, or a configmap per version
15:31:23 <srwilkers> yeah, i think this ties in to the larger release discussion we have planned.  i think a branch per version would be nice
15:31:24 <portdirect> personally i kinda prefer a branch per version
15:31:30 <srwilkers> portdirect: +1
15:31:35 <jayahn> then, what would be our master branch means.
15:31:46 <portdirect> ideally master :)
15:32:06 <jayahn> ideally... yeap. :0
15:32:06 <portdirect> or the current stable release :(
15:32:27 <portdirect> the latter prob makes most sense - but is dull
15:32:51 <jayahn> so that becomes really our branching and release policy, which we continously said it is ptg topic
15:33:34 <madhukar> Hi Pete, thats right
15:33:55 <madhukar> I had a working ocata setup with openstack-helm
15:34:41 <jayahn> great!
15:36:05 <srwilkers> awesome madhukar :)
15:36:11 <srwilkers> anything else on this topic?
15:36:18 <madhukar> major of the changes where related to the nova-placement api and nova-cells for ocata
15:36:43 <jayahn> making ocata work is one thing, however, how you want to put newton and ocata build in your ci pipeline is another important one to consider. upstream policy certainly influence how you want to setup your ci pipeline. so, i would like to really have this discussion. :)
15:36:48 <jayahn> just statement. :)
15:36:57 <portdirect> +2
15:37:15 <madhukar> +3
15:37:21 <jayahn> i wish ptg is sooner.. :)
15:37:21 <portdirect> I think its also essential that we have a pipeline that deploys N and then upgrades to N+1
15:37:50 <srwilkers> agreed all around
15:38:21 <srwilkers> jayahn: have you determined whether you'll be at the PTG yet/
15:38:27 <srwilkers> im assuming/hoping yes :)
15:38:45 <jayahn> ah, i just got an email from the foundation that I will get travel support..
15:38:52 <jayahn> that means, i will be in denver.
15:39:21 <jayahn> :)
15:39:21 <portdirect> w00t - be great to see you there, will Will be through as well?
15:39:37 <srwilkers> thats awesome! :)
15:40:30 <jayahn> i wish wil can join me there. however, it depends on wil's company, so not much to say from me. :)
15:41:22 <jayahn> anyway, that is all from me today.
15:42:49 <srwilkers> hopefully he'll be able to join
15:43:23 <srwilkers> i think that was the last of the topics we had on the list, so we can either end early or transition to an open discussion.  any preferences?
15:43:48 <dulek> In case of no open discussion starts it might be a good moment to say that this is my last week at Intel.
15:44:05 <dulek> Starting with September I'll still be around in the community, but most likely not focusing directly on OpenStack-Helm.
15:44:15 <dulek> It's not that I'll instantly disappear from #openstack-helm. ;)
15:44:41 <dulek> My outstanding patches will be taken by korzen, xek and mateuszb.
15:44:46 <portdirect> dulek: your work here has been awesome dude - I hope you stick around :D
15:44:51 <dulek> Thanks guys for a lot of fun with our cooperation! :)
15:45:55 <srwilkers> dulek: oh man.  i wish you the best in your future endeavors.  i hope we see you around
15:48:40 <srwilkers> alright, ill go ahead and close the meeting.  good chatting with you all, as always
15:48:51 <srwilkers> we can carry over any discussion to #openstack-helm
15:49:04 <srwilkers> #endmeeting