14:00:09 #startmeeting tripleo 14:00:09 Meeting started Tue Feb 14 14:00:09 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:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:13 #topic agenda 14:00:13 The meeting name has been set to 'tripleo' 14:00:15 o/ 14:00:17 o/o/ 14:00:20 * review past action items 14:00:20 /o~ 14:00:22 o/ 14:00:22 * one off agenda items 14:00:24 * bugs 14:00:26 * Projects releases or stable backports 14:00:28 * CI 14:00:30 * Specs 14:00:32 o/ 14:00:32 * Week roadmap 14:00:34 * open discussion 14:00:36 Anyone can use the #link, #action and #info commands, not just the moderatorǃ 14:00:38 Hi everyone! who is around today? 14:00:45 o/ 14:00:49 hey all 14:01:14 * EmilienM proposes a quick meeting so folks can get back to work 14:01:19 o/ hey guys 14:01:23 o/ 14:01:34 #topic review past action items 14:01:45 EmilienM to create etherpad with list of granted FFE for ocata: done - all FFE are merged. 14:01:51 team to review https://review.openstack.org/#/q/topic:bp/overcloud-upgrades-per-service and https://review.openstack.org/#/q/topic:bp/overcloud-updates-per-service_fixup: still WIP 14:01:58 o/ 14:02:01 o/ 14:02:04 owalsh / EmilienM to work together on short term solutions for nova blockers: done. 14:02:15 o/ 14:02:16 o/ 14:02:18 o/ 14:02:43 quick info on nova, we need https://review.openstack.org/#/c/432954 to be backported so stable/ocata Ci will work in tripleo 14:02:50 o/ 14:02:55 owalsh: ^ we can catchup on that topic later 14:03:07 owalsh: I created a list of actions for this week: https://trello.com/c/zyzKZ9MX/65-ocata-tripleo-nova-placement-backport 14:03:14 gfidente / EmilienM to help Dell to get Scale-IO on time for ocata https://review.openstack.org/#/c/422238/: done & thanks gfidente! 14:03:19 team to review https://review.openstack.org/#/q/topic:bp/octavia-service-integration: done 14:03:23 EmilienM to propose RC1 by end of this week if possible or next week: postponed to this week (hopefully) 14:03:26 EmilienM to double check about novajoin blueprint & ffe status: done, postponed to pike 14:03:29 team to look at ovs-2.6 blueprints and give feedback: done, approved for pike-2 14:03:32 karthiks post on ML about ovs-2.6 blueprints and ask for feedback: done 14:03:35 High - team to work on Critical / High bugs for ocata-rc1: WIP 14:03:38 Medium - team to finish features with granted FFE and help in review: done 14:03:41 Low - Pike planning - prepare specs, prepare PTG: done: schedule is ready: https://etherpad.openstack.org/p/tripleo-ptg-pike 14:03:45 #info PTG schedule is ready, please review 14:03:47 #link PTG schedule https://etherpad.openstack.org/p/tripleo-ptg-pike 14:04:11 o/ 14:04:12 = 14:04:17 any question / feedback before we jump to next topic? 14:04:18 o/ 14:04:25 o/ 14:04:37 #topic one off agenda items 14:04:41 #link https://etherpad.openstack.org/p/tripleo-meeting-items 14:04:45 o/ 14:04:57 no topic this week? let's move forward then 14:04:59 EmilienM: none 14:04:59 yup 14:05:09 #topic bugs 14:05:12 #link https://launchpad.net/tripleo/+milestone/ocata-rc1 14:05:59 there are a bunch of High / Critical bugs in progress 14:06:21 And we're still working on landing a few remaining patches for composable upgrades 14:06:25 https://review.openstack.org/#/q/status:open+project:openstack/tripleo-heat-templates+branch:master+topic:bp/overcloud-upgrades-per-service 14:06:25 I would ask folks to update their bugs if not done already 14:06:40 EmilienM: this one was filed today by mcornea... https://bugs.launchpad.net/tripleo/+bug/1664304 the way we are planning on applying puppet wont work but there is a fixup in progres https://review.openstack.org/#/c/433641/ and there are a number of folks testing 14:06:40 Launchpad bug 1664304 in tripleo "Upgrading compute nodes fails with: Error: Evaluation Error: Error while evaluating a Function Call, Could not find data item step in any Hiera data file and no default supplied at /etc/puppet/modules/tripleo/manifests/profile/base/ceph/client.pp:27:11 on node overcloud-novacompute-0.localdomain" [Critical,In progress] - Assigned to Sofer Athlan-Guyot (sofer-athlan-guyot) 14:06:49 I'd suggest we declare the BP complete as soon as we land nova support, then handle any remaining upgrade issues as bugfixes? 14:06:56 and if you feel like the bug you're working on or you reported has a fix that needs to be backported, please tag is 'ocata-backport-potential' 14:06:57 +1 14:07:12 shardy: works for me 14:07:19 shardy: yeah i think that one is pretty important though (as important as the nova one) and we'l have to land it for the 'basic' workflow 14:07:30 shardy: i mean the one ^^^ bug/1664304 14:08:18 marios: ack, thanks - yeah I just meant we can track things more closely via bugs vs the umbrealla blueprint 14:08:34 #action upgrade squad to move remaining work in bugs instead of blueprint 14:08:39 sounds like we're already doing that, so it'd be good to close off the BP given the end-of-cycle deadline looming 14:08:49 yes makes sense to me thanks shardy 14:09:02 shardy: do you want to do it now? 14:09:17 or wait for the tht/nova patch 14:09:42 fwiw, i'm ok to wait until Thursday 14:09:42 EmilienM: I was hoping we'd land the nova patch, but I'll sync with folks after the meeting so we can decide if that's going to happen very soon or not 14:09:48 ok 14:10:20 shardy: EmilienM i think we are really close matbu has been updating it regularly 14:10:32 I would like to highlight a bug reported by bnemec yesterday: https://bugs.launchpad.net/tripleo/+bug/1664418 14:10:32 Launchpad bug 1664418 in tripleo "HA deployments taking close to the CI timeout" [High,Triaged] 14:10:35 it's a bit concerning tbh 14:10:39 lots of folks owalsh and others helping to review 14:10:44 shardy: for my side, im just testing a little fix, but then if owalsh and ansiwen is ok to land (on the latest revision) then it's cool 14:10:55 matbu: ack, Ok great, thanks for the update 14:11:01 we might need some eyes on this bug report, if anyone has time to investigate ^ 14:11:04 would be nice if we can land that before we branch rc1 14:11:20 yep 14:11:49 can you use links please? 14:12:02 I need to know which patch(es) exactly we're waiting for 14:12:08 yep 14:12:10 secs 14:12:19 https://review.openstack.org/405241 14:12:58 matbu: that's all? 14:13:12 #info https://review.openstack.org/#/c/405241/ is the last blocker before merging stable/ocata 14:13:27 EmilienM: https://review.openstack.org/#/c/433641/ too i think ? shardy ? 14:14:06 EmilienM: for the nova patch yes 14:14:12 shardy: i mean it is the one for the puppet apply bug https://bugs.launchpad.net/tripleo/+bug/1664304 14:14:12 Launchpad bug 1664304 in tripleo "Upgrading compute nodes fails with: Error: Evaluation Error: Error while evaluating a Function Call, Could not find data item step in any Hiera data file and no default supplied at /etc/puppet/modules/tripleo/manifests/profile/base/ceph/client.pp:27:11 on node overcloud-novacompute-0.localdomain" [Critical,In progress] - Assigned to Sofer Athlan-Guyot (sofer-athlan-guyot) 14:14:12 marios: yes would be good to land that too, but anything with a bug reference we can backport 14:14:39 ok, let's move forward 14:14:48 anything else about bugs this week? 14:14:49 no pressure chem :D 14:15:11 #topic projects releases or stable backports 14:15:14 marios: it's working 100% :) 14:15:17 #info Essential release blocker: composable upgrades 14:15:22 no major update to announce 14:15:34 I already sent a status on Sunday - feel free to ask questions 14:15:50 the tl;dr is we expect to release tripleo ocata rc1 by Friday and we'll have stable/ocata by then 14:16:17 #action EmilienM to propose RC1 by end of this week (postponed) 14:16:21 #link Ocata release patch https://review.openstack.org/#/c/428416/ 14:16:36 any question about release management? 14:16:49 reminder to add release notes to patches now 14:16:55 including ui! 14:17:00 o/ apologies for the tardiness 14:17:20 jrist: right, release notes for all projects that are released 14:17:27 #topic CI 14:17:31 #info tripleo multinode upgrades job is currently broken: attempt to fix it with https://review.openstack.org/#/c/433646/ 14:18:06 except bnemec's bug report with timeout, OVB jobs & multinode (except upgrades) are working & pretty stable AFIK 14:18:24 when that's fixed we should probably move it into the check queue for tripleo-ci and make it voting on tripleo-ci & tripleo-heat-templates 14:18:46 #info CI Squad meeting notes http://lists.openstack.org/pipermail/openstack-dev/2017-February/112036.html 14:18:47 my main concern now is stable/ocata jobs: https://review.openstack.org/#/c/426231/ to have the ipv6 job we need the backport in nova 14:18:55 o/ 14:18:55 https://en.wikipedia.org/wiki/House_of_Cards_(UK_TV_series) 14:18:57 oops 14:18:59 lol 14:19:09 shardy: making it voting means moving to gate, not only check queue 14:19:22 EmilienM, containers job is broken, testing now patch of jistr 14:19:27 multinode jobs seem to have slown down a bit too 14:19:34 EmilienM: sure, I'm saying we should consider doing that, since it's been stable until this regression 14:19:45 slagle: :( it might be related to the steps changes 14:19:51 i wonder if it's just b/c we have moved so much puppet stuff to run at earlier steps 14:20:01 so now we're running things an additional 2 or 3 times 14:20:03 to be honest, I would have avoided this change, but the thing with nova placement & cells was really required 14:20:29 slagle: well, resources are not supposed to be recreated at every puppet run, since puppet is idempotent 14:20:40 slagle: but the time to "check" the resources takes time, yes 14:20:54 and compiling catalogs, etc etc 14:20:59 idempotent really has nothing to do with it 14:21:15 right, I'm just saying it should not take that long but I'm probably under estimating 14:22:18 slagle: we might want to take it offline after the meeting or this week, I would like to run some investigations 14:22:50 sshnaidm: ok thx for the info, any bug report? 14:23:04 anything else about CI this week? 14:23:15 EmilienM, yes, https://bugs.launchpad.net/tripleo/+bug/1664569 14:23:15 Launchpad bug 1664569 in tripleo "Containerized overcloud fails due to missing EndpointMap parameter" [High,In progress] - Assigned to Jiří Stránský (jistr) 14:23:26 yup 14:23:31 sshnaidm: thanks 14:23:52 all periodic jobs green today 14:24:06 some good news :-) 14:24:20 yeah, I feel like I'm on vacation. 14:24:25 lol 14:24:38 .. and then I look at the review backlog 14:24:40 if you're bored, let me know we have a ton of bugs :-) 14:24:41 jinx! 14:24:54 ok next topic 14:24:57 #topic specs 14:24:58 #link https://review.openstack.org/#/q/project:openstack/tripleo-specs+status:open 14:25:07 #link https://review.openstack.org/#/q/project:openstack/tripleo-specs+status:open 14:25:38 I proposed a squad for Python 3. I would like to talk about it at PTG 14:25:43 #link Python 3 squad https://review.openstack.org/#/c/425294/ 14:26:06 #action EmilienM to propose a Python3 session & invite RDO folks 14:26:54 anyone wants to talk about a spec in particular? 14:27:19 #topic week roadmap 14:27:27 #action High - team to work on last Critical / High bugs for ocata-rc1 14:27:29 #link High - ocata-rc1 https://launchpad.net/tripleo/+milestone/ocata-rc1 14:27:31 #action Medium - Pike planning - prepare specs, prepare PTG 14:27:33 #link Pike PTG https://etherpad.openstack.org/p/tripleo-ptg-pike 14:27:35 #info Next week is PTG in Atlanta, no TripleO weekly meeting 14:27:49 #action jrist to finish House of Cards before PTG 14:28:02 anything else we need to achieve this week? 14:28:02 lol 14:28:04 lol 14:28:07 thanks EmilienM 14:28:34 is it ok if we don't run a meeting next week? 14:28:43 I think most of us will be in Atlanta 14:29:13 #topic open discussion 14:29:27 do we want to talk about the logo now? 14:29:34 yes 14:29:35 :) 14:29:36 I forwared an email I got from marketing 14:29:41 forwarded* 14:30:07 first question: do we have strong opinions on keeping our current logo? 14:30:44 I remember dprince was a bit worried about that, though he's not here so I'll ask him offline 14:30:50 AFAICT keeping our current logo isn't actually an option? 14:31:01 shardy: why that? 14:31:33 the mail from Heidi says "But for official channels like the website, we need a logo to represent TripleO that’s cohesive with the rest of the set. " 14:31:41 ya, that was my understanding as well 14:31:47 right, there isn't really any option 14:31:49 sadface 14:31:59 I find that weird tbh 14:32:00 which to me implies, we can't keep our current logo for official/foundation use, we have to use one validated by the foundation 14:32:02 it doesn't seem that much of the feedback was incorporated about the logo that we provided 14:32:04 we have to accept their logo if we want to be included in "official" branding 14:32:06 so Carlos asked if we can have them adapt the current one 14:32:09 IF keeping current logo was an option, I would be +1 on that... but I dont think it is 14:32:25 wdyt about the proposed logo? 14:32:37 * EmilienM will miss the real owl 14:32:39 I think it looks like a falcon more than an owl 14:32:44 Yeah, I prefer the current logo, and my feedback was basically "make it look more like the current logo" 14:32:45 I think there were some good feedback about 'what was wrong with the new logo' besides "not liking it" 14:32:47 and it has no personality 14:33:14 but I'm not sure what choice we have, other than perhaps asking to do more iterations on what has been proposed 14:33:18 there was also a request to have someone dedicated to working with the illustrator to iterate quickly on something more to our liking 14:33:26 ccamacho: would you want to do that ^ 14:33:36 ccamacho, jrist: would you be interested to propose a new logo that meets requirements? Or do we want to ask them to re-iterate on a new one? 14:33:58 I currently don't have access to illustrator but I could stab at it with inkscape 14:34:21 if they are not willing to incorporate feedback from the project, the logo doesn't represent us anyway 14:34:22 I'm not clear if the requirements are defined, other than the illustrators have a common theme they're going for? 14:34:23 hey trown EmilienM jrist sure 14:34:35 jrist: I was not talking about the adobe program, but a real human :P 14:34:36 jrist: I think trown meant the person in charge of illustration 14:34:42 rbrady: I think the comment was the feedback recieved wasn't specific/actionable enough 14:34:50 EmilienM: oh 14:34:59 so we probably can try to give more specific feedback to iterate towards something which everyone is OK with 14:35:08 I was talking about adobe illustrator 14:35:11 my mac died 14:35:12 the thing is that I believe they didn't iterate from the first logo "the current logo" they did something from scratch 14:35:19 seems like a pretty poor use of developer time at this point in the cycle but 14:35:28 shardy: I agree 14:35:34 did they happen to do any updates based on feedback? 14:35:36 it doesn't seem like it 14:35:38 fwiw ironic is having a similar issue 14:35:42 and I would continue offline if you don't mind, to let people doing their work 14:35:50 sure 14:36:02 jrist: I think the concentric circles were added to attempt to encapsulate the OoO theme 14:36:02 yeah, too bad the illustrators did not take any of the feedback and reiterate on the logo 14:36:21 shardy: I guess I disagree on the actionable part. 14:36:22 shardy: perhaps 14:36:39 jtomasek, ccamacho, jrist: do you want to take action and reply with graphical details on what you expect? 14:37:07 sure but it might be violent 14:37:14 lol 14:37:16 sure, Ill start a draft this afternoon/night 14:37:17 oh no did I type that? 14:37:18 EmilienM, jrist we can try to propose illustrators to turn our logo into one that is compliant with general style 14:37:26 lets keep it constructive ;) 14:37:31 shardy: :) 14:37:34 just joking 14:37:38 I agree, let's be constructive and open :D 14:37:42 jtomasek: sounds like a good idea 14:37:47 I think the idea is con convert what we have to be compliant with the styles 14:38:00 yeahp 14:38:03 agreed 14:38:18 yeah - it'd be cool if we could propose a variation on the current logo that moves closer to the foundation themes 14:38:34 kudos to anyone with the skills to do that /me doesn't :) 14:38:50 ok I'll reply to Heidi using the thread on openstack-dev 14:38:51 haha but I dont' have your skills, that's why we're a team 14:39:14 do we have any other topic for this week? 14:39:46 #action EmilienM to reply to Heidi and ask Design team to re-propose a new logo that would be a variation on the current logo that moves closer to the foundation themes 14:40:03 thanks folks for your time! 14:40:07 jrist: enjoy TV shows 14:40:13 oh and see you next week 14:40:13 lol 14:40:14 #endmeeting