14:00:35 <EmilienM> #startmeeting tripleo
14:00:36 <openstack> Meeting started Tue Mar  7 14:00:35 2017 UTC and is due to finish in 60 minutes.  The chair is EmilienM. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:37 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:40 <openstack> The meeting name has been set to 'tripleo'
14:00:43 <EmilienM> #topic agenda
14:00:49 <EmilienM> * review past action items
14:00:50 <EmilienM> * one off agenda items
14:00:52 <EmilienM> * bugs
14:00:54 <EmilienM> * Projects releases or stable backports
14:00:56 <EmilienM> * CI
14:00:58 <EmilienM> * Specs
14:01:00 <EmilienM> * Week roadmap
14:01:02 <EmilienM> * open discussion
14:01:04 <EmilienM> Anyone can use the #link, #action and #info commands, not just the moderatorǃ
14:01:06 <EmilienM> o/
14:01:07 <jrist> o/
14:01:09 <shardy> o/
14:01:11 <mwhahaha> o/
14:01:11 <dtantsur> o/
14:01:16 <radez> o/
14:01:21 <Ng> o/
14:01:23 <owalsh> o/
14:01:24 <marios> o/
14:01:28 <ccamacho> Hey TripleOers! (~˘▾˘)~
14:01:39 <beagles> o/
14:01:41 * EmilienM turns on the second coffee machine, already empty
14:02:08 <EmilienM> #topic review past action items
14:02:11 <EmilienM> EmilienM to propose RC2 by end of next week: done (release yesterday). Note: final Ocata is pushed tomorrow.
14:02:16 <EmilienM> team to make progress on reviewing Pike specs: still in progress
14:02:16 <jaosorior> o/
14:02:35 <EmilienM> I plan to spend time on specs this week, but any help is welcome!
14:02:42 <EmilienM> #topic one off agenda items
14:02:45 <EmilienM> #link https://etherpad.openstack.org/p/tripleo-meeting-items
14:03:09 <EmilienM> do we have any specific items to discuss ?
14:03:35 <EmilienM> it seems like nope
14:03:49 <EmilienM> #topic bugs
14:03:53 <EmilienM> #link https://launchpad.net/tripleo/+milestone/pike-1
14:04:00 <EmilienM> I moved all ocata-rc2 bugs to pike-1
14:04:13 <EmilienM> (see ML post about it)
14:04:13 <jtomasek> o/
14:04:22 <EmilienM> is there any specific bug to discuss this week?
14:04:28 <cdearborn> o/
14:04:35 <matbu> o/
14:04:46 <shardy> I had one,
14:05:06 <EmilienM> sure, go ahead
14:05:07 <shardy> https://bugs.launchpad.net/tripleo/+bug/1635409
14:05:07 <openstack> Launchpad bug 1635409 in tripleo "parameter_merge_strategies: merge behaves like overwrite" [High,In progress] - Assigned to Steven Hardy (shardy)
14:05:19 <shardy> So I discussed this with jistr recently, and took another look
14:05:40 <shardy> it's going to be tricky to fix as we have code in tripleoclient and tripleo-common which expects a merged environment
14:05:57 <shardy> I'm going to start work on it, but one of the first changes is we have to remove user-environment.yaml
14:06:04 <shardy> and instead store each environment
14:06:15 <shardy> jtomasek: will that break the UI?
14:06:34 <shardy> I'll need to push each environment into the environment list in the mistral environment
14:06:41 <shardy> and store each file in swift
14:07:00 * jtomasek looks
14:07:15 <shardy> anyway, we don't have to get into details now, but I wanted to raise awareness that we'll need to make changes to fix this
14:07:30 <weshay> o/
14:07:37 <jpich> I think it might work *better* with the UI, if they're enabled via the 'environments' key in the Mistral env (aka fix https://bugs.launchpad.net/tripleo/+bug/1642583 at the same time :))
14:07:37 <openstack> Launchpad bug 1642583 in tripleo "When deploying from the CLI the GUI doesn't show the environments that were used" [Medium,Triaged]
14:07:42 <shardy> I hope it'll fit quite well with the plan-envrionment stuff already in-progress
14:07:56 <shardy> jpich: OK, great, that's basically what we need I think
14:08:05 <shardy> a list of environments, which we then pass to heat
14:08:35 <shardy> that will work the same with plan-environment, so we need to figure out if I should base my changes on that vs the mistral environment
14:08:52 <jtomasek> shardy, it will deffinitely not break UI, I think it will actually fix one of the big compatibility problems of CLI and GUI
14:09:14 <jpich> Sounds great to me, thanks for raising it
14:09:20 <shardy> jtomasek: Ok, great - I'll spend some more time on then and ask you to review the tripleo-common changes when they're ready
14:09:30 <jtomasek> shardy, thanks
14:09:55 <EmilienM> great, anything else?
14:09:56 <radez> EmilienM: https://blueprints.launchpad.net/tripleo/+spec/tacker-service-integration this was completed the same time congress was completed and is in ocata already. I see that it got labled pike. was that intentional?
14:10:08 <radez> not a bug, but in the link you posted a bit a go
14:10:28 <EmilienM> radez: moving it to ocata
14:10:32 <radez> thx
14:10:35 <jtomasek> shardy, you probably want to use existing action in tripleo-common - to update list of environments
14:11:09 <shardy> jtomasek: Ok, then the change to plan-environment should be transparent?
14:11:19 <jtomasek> shardy, yes
14:11:25 <shardy> excellent, thanks :)
14:12:01 <EmilienM> any other bug before we move on?
14:12:23 <EmilienM> shardy: thanks for this one
14:12:27 <EmilienM> #topic projects releases or stable backports
14:13:07 <EmilienM> so we are releasing tripleo ocata final this week
14:13:10 <EmilienM> wouhoo
14:13:27 <jpich> yay
14:13:38 <EmilienM> if you need to backport bugfixes, make sure they are reported in launchpad first and mentionned in the commit message
14:13:56 <EmilienM> is there any specific question or comment about release management?
14:14:10 <jpich> This is kinda early days still but... do we have an idea when will be the first stable release for ocata? :-)
14:14:40 <jpich> Context: A few volunteers contributed translations to tripleo-ui, but as we found and fixed i18n issues the translation ratios dropped. I'd like to let the i18n team know we've stabilised now, and what's the deadline if they want to be included in our next point release.
14:14:50 <EmilienM> jpich: I don't think we planned it yet, but we could do it next week if you want
14:15:05 <EmilienM> I mean, you could even do it yourself for tripleo-ui
14:15:25 <EmilienM> submit a patch in openstack/releases (but before patch packages.json and reno conf.py)
14:15:28 <jpich> Ok, so we're pretty flexible with stable releases then? Even for deliverables
14:15:45 <jpich> Excellent, that's helpful to know. Thanks!
14:15:46 <EmilienM> I think so yes
14:16:11 <EmilienM> anything else about releases?
14:16:33 <EmilienM> #topic CI
14:16:48 <EmilienM> the upgrade jobs on stable/ocata are voting
14:17:20 <EmilienM> but the upgrade jobs on master are non voting for now, until we fix some issues with tripleo-ci repo when upgrading to pike
14:17:35 <EmilienM> please don't ignore the upgrade jobs on master though, they should pass (I tested last night)
14:18:01 <adarazs> I'd like to announce it/remind everybody that we're planning to switch over a set of jobs to be driven by Quickstart on Monday, 13th of March.
14:18:27 <EmilienM> adarazs: ok, Monday next week then. Can you share the list?
14:18:44 <adarazs> it's the scenario jobs for now.
14:19:04 <adarazs> if we finish with it, also some OVB jobs.
14:19:07 <EmilienM> are they stable?
14:19:27 <EmilienM> when you say "scenario jobs", do you also mean scenario upgrades jobs?
14:19:37 <adarazs> I think they were running successfully on tripleo-ci for a while.
14:19:55 <EmilienM> adarazs: they run pingtest right? (and not tempest)
14:20:09 <sshnaidm> adarazs, oooq scenario jobs on tripleo-ci?
14:20:10 <adarazs> yes, I think they are running pingtest.
14:20:17 <panda|zZ> yes, they ar
14:20:19 <panda|zZ> e
14:20:51 <EmilienM> just to make sure, we plan to switch the multinode-scenario001,002,003,004 but not the upgrades ones right?
14:20:58 <adarazs> hm, I am not sure about the state of the upgrade jobs. I saw a couple of outstanding reviews for them and I'm not sure they will be merged by Monday if they go with the same pace as they did so far.
14:21:10 <EmilienM> we can wait for the upgrade jobs
14:21:12 <EmilienM> step by step :)
14:21:17 <weshay> no changes will be made to the upgrade jobs on Monday
14:21:26 <EmilienM> I would start by multinode jobs next week, and the week after OVB , etc etc
14:21:35 <adarazs> okay.
14:21:39 <EmilienM> baby steps
14:21:49 <panda|zZ> yeah, falling down and screaming a lot
14:21:53 <EmilienM> :D
14:21:55 <adarazs> heh
14:22:06 <shardy> lol :)
14:22:08 <EmilienM> any question or info about CI to share?
14:22:37 <EmilienM> #topic specs
14:22:40 <EmilienM> #link https://review.openstack.org/#/q/project:openstack/tripleo-specs+status:open
14:22:52 <EmilienM> so like we said before, a lot of Pike specs are still under review
14:23:10 <EmilienM> if you have some time to review them, that would be appreciated
14:23:24 <EmilienM> is there anyone who wants to talk about a specific spec?
14:23:57 <EmilienM> #topic open discussion
14:24:18 <EmilienM> I'll be afk tomorrow and Thursday, I'm going to Boston for OpenStack TC / UC / Board meetings
14:24:30 <weshay> https://blueprints.launchpad.net/tripleo/+spec/increase-cadence-of-tripleo-promotions  It's not 100% clear to me how we can accomplish this w/o getting in trouble w/ openstack infra
14:24:37 <weshay> looking for suggestions
14:25:16 <mwhahaha> why would we get in trouble with infra?
14:25:20 <EmilienM> weshay: so, like we said at PTG, we need to ask infra if we can have a new pipeline
14:25:37 <EmilienM> AFIK pabelanger was saying we could create a new one
14:25:51 <EmilienM> and if it's not the case, we could handle promotion jobs in RDO CI like we did for Puppet OpenStack
14:25:57 <weshay> ok.. that is good news.. I was not able to attend the PTG
14:26:12 <EmilienM> weshay: please kick off a discussion on openstack dev
14:26:20 <weshay> will do, thanks
14:26:24 <EmilienM> weshay: and include [infra] and [tripleo]
14:27:10 <EmilienM> anything else for this week?
14:27:54 <EmilienM> thanks everyone for your presence and your hard work! see you online
14:27:56 <EmilienM> #endmeeting