14:00:22 #startmeeting glance 14:00:23 Meeting started Thu Feb 15 14:00:22 2018 UTC and is due to finish in 60 minutes. The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:24 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:26 The meeting name has been set to 'glance' 14:00:32 o/ 14:00:33 #topic roll call 14:00:46 hi abhishekk, hope you are feeling better (or at least decent) 14:00:59 o/ 14:01:02 rosmaita, yes better 14:01:08 o/ 14:01:14 hi scott 14:01:19 hey all 14:01:20 and erno 14:01:42 i'll get started right away 14:02:01 my plan is quick meeting, and then we can re-convene in glance channel to figure out final stuff for RC-2 14:02:06 #topic updates 14:02:20 point releases for ocata (14.0.1) and pike (15.0.1) 14:02:28 those include the eventlet fix 14:02:50 in other news, we lost diverse-affiliation tag again: "Glance no longer has diverse affiliation, 85% of core reviews coming from Red Hat and Verizon (55% for Red Hat alone)" 14:03:02 not much we can do about that 14:03:14 but it does impact the postgres situation 14:03:27 in that no one working on the project actually uses it 14:03:36 but i will say more about that later 14:03:59 ok, that's all for updates, let's talk about rc-2 14:04:04 #topic RC-2 14:04:26 oh yeah, i forgot to post the agenda link 14:04:29 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 14:04:54 ok, what we're trying to get done in RC-2 are the bugs for interoperable image import 14:05:04 and some postgres fixes 14:05:18 we're tracking the progress here: 14:05:28 #link https://etherpad.openstack.org/p/glance-queens-rc1-patches 14:06:07 like i said, let's go into the details after the meeting 14:06:15 ok 14:06:18 it would be good to get RC-2 released today 14:06:46 but there is always tomorrow -- anyway, we can discuss later 14:06:51 #topic RC-3 14:06:56 there will be an RC-3 14:07:08 what i'd like is to get the postgres situation figured out 14:07:25 the situation is that there may be problems migrating an existing postgres database 14:07:49 i filed a bug to track that, gimme a minute to find the link 14:08:28 #link https://bugs.launchpad.net/glance/+bug/1749466 14:08:29 Launchpad bug 1749466 in Glance "postgresql db migration broken in queens" [Critical,Triaged] - Assigned to Ameed Ashour (ameeda) 14:08:39 and i see someone has already filed another one 14:08:51 #link https://bugs.launchpad.net/glance/+bug/1749640 14:08:51 Launchpad bug 1749640 in Glance "db sync fails for mysql while adding triggers" [High,In progress] - Assigned to Abhishek Kekane (abhishek-kekane) 14:09:25 let's discuss a strategy for dealing with this after the meeting after discussing rc-2 14:09:36 ok 14:09:50 ok 14:09:55 i'd like to shoot for tuesday for RC-3 14:10:09 sounds good 14:10:19 the final release candidate needs to be done late next week 14:10:31 Monday would be great, Tue night GMT pretty much the latest or we'll be screwed 14:10:39 we need to release at Thu IIRC 14:10:51 ok, good point 14:11:05 we will have to timebox and aim for Monday 14:11:51 we can discuss the parameters of the timebox after the meeting 14:12:03 i don't want people going insane over the weekend 14:12:04 ok' 14:12:10 ++ 14:12:28 ok, next item 14:12:35 #topic the uWSGI situation 14:12:42 this impacts the next topic, too 14:12:54 ok, so our recommendation has been don't use glance with uWSGI 14:13:10 we are going to continue that recommendation in Queens 14:13:16 is there any more info on this one? 14:13:28 unfortunately as it was pointed out in #os-glance while ago we do not officially indicate that anywhere 14:13:54 i think it says that in the running glance under httpd docs 14:13:58 i will check 14:14:21 i will also submit a patch removing our completion of uwsgi support from the community goals 14:14:25 IIRC that doc just eplains how to do it ... we never made the change to state there that it should not be done 14:14:42 ok, will have to check 14:15:08 anyway, the impact is that if you want to run tasks in devstack ... 14:15:21 you need to set WSGI_MODE=mod_wsgi 14:15:25 in your local.conf 14:15:35 that starts glance in systemd 14:15:43 but uses the "regular" glance wsgi server 14:15:56 ok 14:16:02 is it Glance only or does it push all the services under systemd? 14:16:14 well, it's a bit weird 14:16:18 Is there a glance specific solution? 14:16:28 yes, do not use uwsgi 14:16:48 esberglu: as in do not deploy glance under Apache 14:16:51 so what happens when you do that is that glance and keystone run slightly differently 14:16:52 Yeah I thought that WSGI_MODE affected more than glance, not super familiar though 14:17:21 yeah, i am focused on glance, so i am not 100% sure what happens to the other services 14:17:29 this is what i have observed: 14:17:30 I am not 100% sure but I suspect that wsgi mode is more global as well 14:17:44 (1) in default devstack: 14:17:44 rosmaita: ok, cool ... well that's good to know anyways ... makes life much easier for testing things 14:18:06 sry, go ahead 14:18:07 everything runs under systemd AND in a uwsgi "container" 14:18:30 (2) when you use WSGI_MODE=mod_wsgi 14:18:50 everything except keystone (and maybe one or two other things) runs under systemd 14:18:54 including glance 14:19:24 the diff is that the glance systemd starts /path/glance --conf /etc/glance-api.conf 14:19:28 something like that 14:19:36 keystone is run out of apache 14:19:38 so we need to figure out how to change all our test jobs to do that as well 14:20:07 if you do systemctrl status apache2.service you can see what httpd is running 14:20:40 well, the glance functional tests don't use devstack 14:20:51 but yeah, we do need to do something 14:21:11 the mod_wsgi support is supposed to be pulled from devstack 14:21:39 i will put up a patch to introduce a new var to decide whether glance runs under uwsgi or not 14:21:47 yeah, what I mean is that we need to have tempest jobs for glance doing that as well 14:22:14 yeah, apparently tempest doesn't cover any tasks stuff, or we'd be seeing problems 14:22:36 so, the key point for the next 2 weeks is 14:22:54 put the WSGI_MODE thing in your local.conf so you can test out image import 14:23:50 ok, so esberglu i have kind of put a damper on your next item 14:24:10 mtreinish has been working on some fixes to get glance working better with uwsgi 14:24:24 but the key thing is that we absolutely need tasks for image import 14:24:48 and the uwsgi upload fixes have not been tested at scale 14:25:15 so i think we need to declare the uwsgi stuff experimental 14:25:31 agree 14:25:35 and if people really want it, they can propose some specs 14:26:01 and we can discuss what would really be needed to get it done correctly 14:26:43 #topic pike backport for image-create 14:26:49 esberglu that's you 14:26:58 unfortunately I totally agree ... running glance in uwsgi container has almost no priority to atm. specially looking our resources and backlog 14:27:15 "to me atm." 14:27:26 I was looking at this bug 14:27:27 https://bugs.launchpad.net/glance/+bug/1703856 14:27:28 Launchpad bug 1703856 in Glance "502 Bad gateway error on image-create" [High,Fix released] - Assigned to Matthew Treinish (treinish) 14:27:45 And this backport 14:27:46 https://review.openstack.org/#/c/525994/ 14:28:08 But if the recommendation is to not use uwsgi I'm guessing that won't get in? 14:30:03 jokke_ you are still release czar atm 14:30:18 esberglu: I'm very reluctant to approve that backport and claim that "Now it's ok to run Glance Pike in uwsgi" 14:31:02 found the doc: https://docs.openstack.org/releasenotes/glance/pike.html#known-issues 14:31:12 that's just really really bad idea and backporting that to Pike just to get devstack working out of box is kind of those things that has priority sowhere so far I can't see it ;) 14:31:46 agree 14:32:13 i will make sure that advice is repeated in the queens release notes 14:32:31 and put up a patch to the admin docs 14:33:07 which just say, by the way, *if* you want to run glance under httpd, we recommend uwsgi ... there's also a note saying that it may not work 14:33:07 1) Upstream reviews, Fix for glance deployment with postgresql 14:33:08 2) More upstream reviews, Fix release critical issues 14:33:08 3) None 14:33:16 sorry ignore that 14:34:03 :) 14:34:04 ok, guess we covered that 14:34:14 just one thing 14:34:17 Thanks for the info 14:34:17 sorry esberglu but thank you for attending 14:34:20 as a bit of clarification 14:35:00 my biggest problem with that is that fixing such thing we as upstream community reinforce supporting such deployments and we really can't afford doing so atm. 14:35:32 it's not so much technical problem as it is principal/political 14:35:40 agree 14:36:04 yes, and a key aspect is that we must have more & better test coverage 14:36:04 so if you really need to have that patch in, carry it in your own deployment on your own risk that the next thing will break 14:36:19 because it will entail separating out the task stuff into a separate service 14:36:22 the patch itself is not bad and it's in queens 14:36:34 which as jokke_ says is not technically a problem 14:36:45 but it has an enormous potential to affect stability 14:37:22 so we will need QA resources if that is to happen 14:37:35 and our community is too small atm 14:37:57 ok, anything else? 14:37:58 I'm ready for next topic :) 14:38:01 me too 14:38:14 #topic PTG planning 14:38:23 jokke_ this is you 14:38:38 Ok, so PTG is coming faster than anyone can see from the release rush! 14:39:22 which means I want to start nailing down our PTG planning at latest Monday 14:39:35 i would like to propose that we combine the queens retrospective with a guiness brewery tour 14:39:43 don't know whether the logistics on that are reasonable, though 14:39:55 someone told me they have wi-fi at guiness 14:40:07 Please do have a look on the planning etherpad, make any additions you might want to bring up and mark your interest 14:40:14 There's a nice pub area in there too. :) 14:40:48 rosmaita: my vote goes to Jamesons' ... it's better tour and we might need some stronger tools :P 14:41:02 Hah 14:41:05 jokke_ you are PTL for a reason! good choice 14:41:24 So Wed morning that is! :P 14:41:48 how early does it open? 14:41:55 I need to check 14:42:16 but I think we get Glance sessions well started if we lubricate it with Whiskey 14:42:21 If Jameson hasn't changed much in the last 18 years, they had a nice pub area too. 14:42:38 smcginnis: oh they do and they still serve the best Irish Coffee ever 14:42:45 ok, i will leave it up to you Dublin experts to pick the place 14:42:56 exactly 14:43:01 but seriously, we could do the retrospective there 14:43:07 combine business & pleasure 14:43:13 just a suggestion 14:43:13 I'll keep that in mind 14:43:16 cool 14:43:21 put it into the etherpad :P 14:44:11 but that's all form me about that topic, just get your input in so I don't need to come out with my own agenda for the week 14:44:23 no-one will like that :D 14:44:36 ok, so jokke_ what do you say that deadline for proposals is 23:59 utc tomorrow? 14:44:40 #deathByPowerpoint 14:44:49 what deadline for getting votes onto the etherpad? 14:44:54 rosmaita: 0900 UTC Mon Morning 14:45:18 after that I start composing the schedule 14:45:32 not doing it over the weekend 14:45:35 ok, i will include that on the priority email 14:45:47 tyty 14:46:06 #topic open discussion 14:46:22 anyone? 14:46:32 one quick one 14:47:05 Hi, I am looking for a workaround of https://bugs.launchpad.net/glance/+bug/1703856. I have already applied patches https://review.openstack.org/#/c/493654/ (Glance) and https://review.openstack.org/492651 But still facing issue in my devstack Pike with bad gateway 502 error 14:47:07 Launchpad bug 1703856 in Glance "502 Bad gateway error on image-create" [High,Fix released] - Assigned to Matthew Treinish (treinish) 14:47:18 request for all ... anyone in the audience who really really cares about stable releases 14:47:54 Please come forward ... our Stable-maint group basically consists of myself and rosmaita and that will get backporting stuff very difficult 14:48:05 ++ 14:49:08 for example 544801 is pending to find external reviewer as it's my patch, I technically shouldn't +2 it and Abhishek is not stable-core so Brian should not merge it in by himself 14:49:58 so we really could do some help there 14:50:24 mbindlish, just go through the previous discussion which will help you to understand the situation of uwsgi 14:50:27 mbindlish i don't have a workaround for that and we are in queens rc-time, don't think anyone here will be able to help 14:50:42 also, what abhishekk said 14:50:43 ok 14:51:41 anything else? 14:52:04 so should we shift to openstack-glance? 14:52:24 yes, and i will try to make it quick because i know it is late for you 14:52:39 ok, thanks everyone! don't forget jokke_ 's request about the PTG planning 14:52:43 #endmeeting