14:00:02 <shardy> #startmeeting tripleo
14:00:03 <openstack> Meeting started Tue Sep  6 14:00:02 2016 UTC and is due to finish in 60 minutes.  The chair is shardy. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:07 <openstack> The meeting name has been set to 'tripleo'
14:00:18 <shardy> #topic rollcall
14:00:23 <beagles> o/
14:00:26 <shardy> hey all, who's around?
14:00:27 <mwhahaha> hi
14:00:28 <EmilienM> hello
14:00:33 <apetrich> o/
14:00:34 <dtantsur> o/
14:00:34 <shadower> hey
14:00:36 <pabelanger> present
14:00:40 <marios> hi \o
14:00:52 <weshay> o/
14:00:59 <myoung> o/
14:01:03 <matbu> o/
14:01:12 <dprince> hi
14:01:24 <jpich> o/
14:01:40 <shardy> Hi, Ok then, lets get started
14:01:44 <shardy> #topic agenda
14:01:49 <shardy> #link https://wiki.openstack.org/wiki/Meetings/TripleO
14:02:01 <shardy> #link https://etherpad.openstack.org/p/tripleo-meeting-items
14:02:08 <sshnaidm> o/
14:02:12 <shardy> If anyone has any one-off items, please add them to the etherpad :)
14:02:25 <shardy> I have one re RC1 but we can cover that in the release topic
14:02:36 <shardy> * one off agenda items
14:02:36 <shardy> * bugs
14:02:36 <shardy> * Projects releases or stable backports
14:02:36 <shardy> * CI
14:02:36 <shardy> * Specs
14:02:38 <shardy> * open discussion
14:03:30 <trown> o/
14:03:33 <adarazs> o/
14:03:39 <shardy> Any other one-off items, or should we jump right to the recurring topics?
14:04:17 <shardy> Ok then, I don't see anything so let's jump to bugs
14:04:20 <shardy> #topic bugs
14:04:25 <thrash> o/
14:04:48 <shardy> So, one request for help here - I know Emilien has done a bunch of bug triage, and I'm struggling to find time to do it regularly
14:05:20 <shardy> can folks please self-triage their own bugs, and help clear the backlog of stuff that's in any state other than Fix Released
14:05:22 <EmilienM> i'll continue today
14:05:52 <shardy> This is related to the release as we need to capture all the release blockers
14:06:13 <shardy> Any other bugs folks want to highlight or discuss now?
14:06:41 <shardy> mcornea has been reporting a few related to composable services/roles, so I created an offial tag for them:
14:06:50 <EmilienM> I use this URL to find bugs goo.gl/kSo5nLcontent_copyCopy short URL
14:06:57 <EmilienM> http://goo.gl/kSo5nL sorry
14:07:03 <shardy> #link https://bugs.launchpad.net/tripleo/+bugs?field.tag=composable-roles
14:07:11 <shardy> Any help with those would be great
14:07:29 <shardy> I think we still have a few hard-coded assumptions around stuff getting deployed on the controller
14:08:00 <shardy> there also seems to be some complexity around how we handle e.g creatinG DB users when a service is deployed on some node other than the one running the DB
14:08:10 <shardy> similar problem to the endpoint creation via puppet I think
14:08:27 <shardy> ideas re fixes welcome
14:09:10 <shardy> Anything else re bugs before we go on to discuss the release?
14:10:07 <shardy> #topic Projects releases or stable backports
14:10:28 <dprince> shardy: yep, Agree we need to iterate on the interfaces around the endpoints, DB, etc.
14:10:30 <shardy> So, we released newton-3, with a bunch of nice features and fixes:
14:10:33 <shardy> https://bugs.launchpad.net/tripleo/+milestone/newton-3
14:10:34 <shardy> woohoo!
14:10:41 <shardy> thanks for all the hard work everyone :)
14:10:49 <EmilienM> nice
14:10:54 <shardy> Now, we have a backlog of remaining stuff for RC1 to deal with:
14:11:03 <shardy> https://launchpad.net/tripleo/+milestone/newton-rc1
14:11:04 <d0ugal> \o/
14:11:29 <shardy> There are 12 FFEs which is a lot more than I hoped for, but many of them just need reviews and passing CI
14:11:35 <EmilienM> 12 blueprints and 50 bugs targeted :-O
14:11:40 <shardy> help landing those and setting them to Implemented would be great
14:12:05 <shardy> EmilienM: I need to scrub the bug list, I think quite a few will get deferred to ocata
14:12:35 <shardy> again, assistance appreciated if you see something there you are assigned to or reported - bump it to ocata if it's not a release blocker
14:12:56 <dtantsur> shardy, ironic is done code-wise, only needs docs to be reviewed and landed
14:13:06 <shardy> dtantsur: ack, thanks for the update
14:13:11 <dtantsur> * unless we find any last-minute bugs of course
14:13:26 <shardy> d0ugal: can you provide a status update on https://blueprints.launchpad.net/tripleo/+spec/mistral-deployment-library ?
14:13:34 * shardy looks around for rbrady
14:14:01 <shardy> I get the feeling we're pretty close there, but it might be good to mail the list with a clear list of remaining patches we need to enable closing that one
14:14:20 <d0ugal> shardy: Sure, I'll prepare an email.
14:14:30 <d0ugal> shardy: I need to check on a few things to see where they are all at :)
14:14:32 <shardy> or is https://etherpad.openstack.org/p/tripleo-mistral-api the definitive list?
14:14:44 <shardy> d0ugal: Ok, thanks - I think a ML update would be useful
14:14:56 <d0ugal> shardy: It is, but I am not sure it is up to date, rbrady was looking after the etherpad.
14:15:01 <d0ugal> Sure, will do.
14:15:18 <shardy> I've been working with mhenkel re the contrail one, it's a new service integration disabled by default, so hopefully we can land that one, there's patches posted
14:16:00 <shardy> I think jaosorior said we should defer https://blueprints.launchpad.net/tripleo/+spec/tls-via-certmonger to ocata
14:16:03 <shardy> so I'll do that
14:16:29 <shardy> which leaves https://blueprints.launchpad.net/tripleo/+spec/custom-roles
14:16:53 <shardy> So, I have a series posted which pretty much completes this, I just need to finish testing it wired in via mistral vs my local tripleoclient hack
14:17:02 <shardy> and address some refactoring after discussions with dprince
14:17:22 <shardy> https://review.openstack.org/#/q/topic:bp/custom-roles+status:open
14:17:36 <shardy> however, it's some major changes to be making at this point in the cycle
14:17:51 <dprince> shardy: but super valuable
14:17:55 <shardy> the feedback I have got is that users want this feature in Newton, so I've been trying to make it happen
14:18:11 <shardy> if folks are OK with that, I'll keep pushing this week and we can try to land it before RC1
14:18:16 <d0ugal> +1
14:18:25 <dprince> shardy: +1
14:18:36 <EmilienM> shardy: yes
14:18:40 <shardy> Ok, thanks
14:18:55 <shardy> In terms of release timing https://releases.openstack.org/newton/schedule.html
14:19:11 <shardy> I propose we cut an RC1 sometime next week to align with the other OpenStack projects
14:19:46 <shardy> Then cut further RC's as needed aiming to declare the release final close to the main Newton release data
14:19:49 <shardy> date
14:19:56 <EmilienM> just FYI: puppet modules will cut stable/newton branch on October 3 or maybe a bit before
14:20:17 <shardy> we have the cycle-trailing deadline, but I'd prefer to treat the extra two weeks as contingency, which I think is the spirit of the cycle-trailing model
14:20:28 <shardy> does that sound resonable to folks?  Any questions?
14:20:41 <dprince> yep, reasonable
14:20:57 <EmilienM> shardy: yes
14:20:59 <marios> thanks shardy sounds good
14:21:47 <shardy> jaosorior: hey I just mentioned you, did we agree to bump https://blueprints.launchpad.net/tripleo/+spec/tls-via-certmonger to ocata?
14:22:05 <shardy> obviously you can continue working on it, but it sounds like there's too much work remaining to land this week?
14:22:08 <jaosorior> shardy: yeah. I don't think it'll be done by RC1
14:22:23 <shardy> jaosorior: Ok, thanks, I'll bump it to ocata-1
14:22:26 <jaosorior> sure
14:22:41 <shardy> Anything else re the release to discuss before we continue?
14:23:23 <shardy> #topic CI
14:23:47 <shardy> derekh, bnemec: you guys want to give us an update of the fun with ovb jobs recently?
14:24:17 <derekh> shardy: sshnaidm is working on it at the moment
14:24:43 <EmilienM> panda: have you investigated why IPv6 new experimental job is failing?
14:25:02 <sshnaidm> for now I clean the environment to free some resources
14:25:03 <derekh> shardy: lots of DB errors creating heat stacks, he's restarted a few things and it now cleaning up old failed resources befor testing things out again
14:25:12 <EmilienM> we have a patch for Ipv6 if anyone can review it please https://review.openstack.org/#/c/363204/
14:25:24 <derekh> shardy: the heat-manage purge command doesn't seem to ave done anything
14:25:33 <shardy> derekh: Ok - do we have any feeling for how the hardware reconfiguration and image caching has been working out?
14:25:52 <shardy> it certainly seems to have helped - is there more we can do in terms of the hardware tuning?
14:26:00 <sshnaidm> shardy, that worked great
14:26:08 <shardy> derekh: Ok, we should reach out to therve about that, IIRC he's fixed that several times now
14:26:15 <derekh> shardy: bnemec has been looking into the HW tuning stuff
14:26:17 <bnemec> EmilienM: I had issues deploying ha with ipv6 on Friday locally.  I'm thinking there may be a legitimate problem, but I haven't had a chance to dig into it yet.
14:26:34 <derekh> shardy: I think the image cache has help a good bit
14:27:03 <EmilienM> bnemec: ok I rebased the Ci patches, i'll also look
14:27:06 <bnemec> The major part of the hardware tuning is done.
14:27:14 <shardy> bnemec: FYI dsneddon was also doing some local IPV6 testing and I believe found some issues
14:27:20 <shardy> not sure on the latest status of that tho
14:27:52 <shardy> bnemec: ack, well thanks for your efforts there, good to see things improving
14:27:53 <bnemec> I would still like to get the RAM layout fixed in the rest of the nodes, and there are a few that haven't been switched to performance mode because they were hosting infra vms that couldn't be taken down.
14:28:12 <EmilienM> shardy: did he send a patch or file launchpads?
14:28:25 <shardy> EmilienM: I'm not sure, will have to follow up and ask
14:28:30 <EmilienM> k
14:29:20 <shardy> Ok, anything else to discuss re CI before we continue?
14:29:36 <matbu> i'm still working on upgrade jobs
14:30:04 <EmilienM> matbu: do you have some progress to share?
14:30:13 <matbu> the UC major upgrade works, i'm fighting a bit with the major OC upgrade
14:30:38 <matbu> i'll probably hve some review to land this week
14:31:10 <shardy> matbu: Ok, sounds good - it'd be great if we can get that passing/landed before the final Newton release
14:31:18 <weshay> +1
14:31:21 <matbu> shardy: ack
14:31:23 <EmilienM> matbu: do we have the undercloud upgrade job green?
14:31:28 <matbu> EmilienM: yep
14:31:42 <shardy> #topic Specs
14:31:42 <EmilienM> I don't see it on https://review.openstack.org/#/c/346995/
14:31:59 <shardy> So, just a reminder that we need to start planning features for Ocata
14:32:03 <matbu> EmilienM: i 'm working on this one : 364859
14:32:09 <matbu> https://review.openstack.org/#/c/364859
14:32:10 <shardy> folks can raise specs, and we need to start thinking about summit session topics
14:32:19 <shardy> I just started https://etherpad.openstack.org/p/tripleo-barcelona-summit-topics
14:32:34 <EmilienM> ok gate-tripleo-ci-centos-7-undercloud-upgrades-nv is green
14:32:35 <shardy> please dump your ideas there and we can discuss them further in future meetings
14:32:40 <matbu> EmilienM: well on the latest CI run, the UC upgrade is the only green :)
14:32:51 <shardy> when we know what our summit session allocation will be
14:32:53 <EmilienM> matbu: should I abandon https://review.openstack.org/#/c/346995/ ?
14:33:15 <matbu> EmilienM: idk what would be the best, only landing UC upgrade in a first pass
14:33:21 <EmilienM> matbu: I would like to keep my patch and merge it when it pass
14:33:29 <matbu> EmilienM: or landing the full review ^
14:33:30 <EmilienM> matbu: so we do baby steps, first undercloud upgrade
14:33:51 <matbu> EmilienM: ack, so may i update your review to make the UC job green ?
14:34:21 <EmilienM> matbu: please yes, add the diff to make it work
14:34:25 <EmilienM> matbu: i'll review it today
14:34:31 <shardy> #topic Open Discussion
14:34:32 <matbu> EmilienM: k cool
14:34:36 <jpich> Is https://etherpad.openstack.org/p/ocata-tripleo superseded by  https://etherpad.openstack.org/p/tripleo-barcelona-summit-topics ?
14:34:42 <EmilienM> shardy: sorry :-) we still had Ci things to discuss
14:35:05 <shardy> jpich: Haha, no, my mistake
14:35:17 <shardy> I'll link to that one instead, oops! :)
14:35:25 <jpich> Ok!
14:36:31 <shardy> jtomasek: Do you have a status update the the UI this week?
14:36:45 <shardy> jtomasek: how close are we to asking for wider feedback/testing?
14:38:04 <d0ugal> I don't think jtomasek is around :) (I pinged him a while ago)
14:38:06 <shardy> or jrist or anyone at all really :)
14:38:33 <shardy> I've not had time to try it, but it'd be great to get eyes on the UI and kick the tyres before the release
14:38:58 <d0ugal> florianf: ^
14:39:04 <d0ugal> or maybe jpich can answer?
14:39:10 <jrist> I am here
14:39:25 <jrist> I am not sure, as I was out yesterday and Friday, if there is much change
14:39:43 <jrist> we will have to take a look this week about a wider UI update
14:40:05 <jrist> if the undercloud install stuff for the UI stuff is in, which I think it is
14:40:06 <d0ugal> jrist: I am sending an email to the list re: mistral status. Maybe a similar one about the UI would be good.
14:40:12 <jrist> d0ugal: roger
14:40:15 <shardy> jrist: Ok, I guess my question really is, when we release TripleO RC1 next week, will we have a fully integrated and basically functional UI?
14:40:27 <jrist> shardy: that's a great question. warrants some testing
14:40:33 <shardy> we're not tracking the UI things in the main launchpad, so I've not got a clear view on it tbh
14:40:51 <jrist> yeah
14:41:26 <shardy> Ok, well we can discuss next week, but again a ML message with a summary and links to the must-have patches would be hugely helpful
14:41:46 <jrist> ok
14:42:03 <EmilienM> should we use lp/tripleo with ui tag for UI things?
14:42:12 <shardy> EmilienM: I think we will do that from ocata
14:42:12 <EmilienM> why UI would be an exception?
14:42:15 <EmilienM> ah excellent
14:42:27 <florianf> shardy, jrist: I haven't been able to test the package and the UI setup myself yet. There's one patch left that we need to start a deployment though.
14:43:07 <d0ugal> florianf: link?
14:43:17 <shardy> We need https://review.openstack.org/#/c/344140/ to land before folks will really start testing it I think
14:43:26 <shardy> need to get a CI pass on that again
14:43:27 <florianf> d0ugal: https://review.openstack.org/#/c/357125/
14:44:05 <shardy> Ok, well help landing those two patches would be good :)
14:44:16 <shardy> Anything else to discuss before we wrap things up?
14:44:33 <marios> shardy: review request on the manila netapp please https://review.openstack.org/#/c/354019/
14:44:41 <marios> shardy: has an ffe, would be nice to land for rc1
14:44:59 <marios> shardy: waiting for the test review at https://review.openstack.org/#/c/362866/ to be green but unrelated undercloud ci issues
14:45:17 <shardy> marios: ack, will check those out, agree landing for RC1 would be good
14:45:20 <marios> shardy: though that only test the generic tidy up, not netapp backend
14:45:23 <marios> shardy: thanks
14:46:11 <shardy> Ok then, if nothing else needs discussion, we can declare an early endmeeting?
14:46:28 <dprince> shardy: thanks
14:46:34 <d0ugal> Thanks!
14:46:47 <shardy> Ok, thanks everyone! :)
14:46:50 <EmilienM> thanks shardy
14:46:54 <shardy> #endmeeting