Thursday, 2018-11-22

*** hongbin has quit IRC00:36
*** iyamahat has quit IRC01:04
*** yamahata has quit IRC01:04
*** iyamahat has joined #openstack-meeting-401:24
*** Liang__ has joined #openstack-meeting-401:43
*** yamahata has joined #openstack-meeting-401:46
*** psachin has joined #openstack-meeting-403:19
*** janki has joined #openstack-meeting-404:32
*** yamamoto has quit IRC04:49
*** yamamoto has joined #openstack-meeting-405:29
*** yamamoto has quit IRC05:39
*** yamamoto has joined #openstack-meeting-406:14
*** Luzi has joined #openstack-meeting-406:23
*** slaweq has joined #openstack-meeting-406:59
*** radeks_ has joined #openstack-meeting-407:10
*** pcaruana has joined #openstack-meeting-407:22
*** gkadam has joined #openstack-meeting-408:15
*** celebdor1 has joined #openstack-meeting-408:35
*** celebdor1 has quit IRC08:36
*** celebdor has joined #openstack-meeting-408:37
*** slaweq has quit IRC08:56
*** trident has quit IRC08:57
*** trident has joined #openstack-meeting-408:59
*** slaweq has joined #openstack-meeting-409:10
*** slaweq has quit IRC09:14
*** e0ne has joined #openstack-meeting-409:17
*** sambetts_ has quit IRC09:18
*** mrhillsman is now known as openlab09:19
*** sambetts_ has joined #openstack-meeting-409:20
*** openlab is now known as mrhillsman09:20
*** ktibi has joined #openstack-meeting-409:23
*** yboaron_ has joined #openstack-meeting-409:28
*** ktibi has quit IRC09:59
*** ktibi has joined #openstack-meeting-410:00
*** yamamoto has quit IRC10:14
*** salmankhan has joined #openstack-meeting-410:49
*** salmankhan1 has joined #openstack-meeting-410:52
*** salmankhan has quit IRC10:54
*** salmankhan1 is now known as salmankhan10:54
*** yamamoto has joined #openstack-meeting-410:57
*** premsankar has quit IRC11:01
*** yamamoto has quit IRC11:05
*** ktibi has quit IRC11:08
*** yamamoto has joined #openstack-meeting-411:11
*** gkadam has quit IRC11:24
*** gkadam has joined #openstack-meeting-411:28
*** ktibi has joined #openstack-meeting-411:28
*** Liang__ has quit IRC11:34
*** janki has quit IRC11:43
*** dims has quit IRC11:45
*** e0ne has quit IRC11:46
*** yboaron_ has quit IRC11:50
*** ktibi has quit IRC11:52
*** e0ne has joined #openstack-meeting-411:59
*** yamamoto has quit IRC11:59
*** yamamoto has joined #openstack-meeting-412:00
*** bobh has joined #openstack-meeting-412:20
*** yamamoto has quit IRC12:30
*** ktibi has joined #openstack-meeting-412:47
*** yamamoto has joined #openstack-meeting-413:01
*** yamamoto has quit IRC13:06
*** yamamoto has joined #openstack-meeting-413:08
*** yamamoto has quit IRC13:08
*** bobh has quit IRC13:25
*** yamamoto has joined #openstack-meeting-413:26
*** ktibi_ has joined #openstack-meeting-413:33
*** ktibi has quit IRC13:36
*** slaweq has joined #openstack-meeting-413:41
*** Liang__ has joined #openstack-meeting-413:41
*** yamamoto has quit IRC13:41
*** Liang__ is now known as LiangFang13:42
*** liuyulong has joined #openstack-meeting-413:48
*** pcaruana has quit IRC13:50
*** abhishekk has joined #openstack-meeting-413:58
LiangFanghi abhishekk14:00
*** qwebirc39073 has joined #openstack-meeting-414:00
jokke_#startmeeting glance14:00
openstackMeeting started Thu Nov 22 14:00:50 2018 UTC and is due to finish in 60 minutes.  The chair is jokke_. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
jokke_#topic roll-call14:01
*** openstack changes topic to "roll-call (Meeting topic: glance)"14:01
jokke_o/14:01
LiangFango/14:01
Luzio/14:01
abhishekko/14:01
abhishekk(i am not well, i may quit early)14:01
jokke_#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:01
jokke_abhishekk: ok :(14:01
jokke_take care of yourself14:02
abhishekkYes, thank you14:02
LiangFangtake care14:02
jokke_lets get started then, this might be quick one14:02
abhishekkYep, ty14:02
jokke_#topic updates14:02
*** openstack changes topic to "updates (Meeting topic: glance)"14:02
jokke_Just quick hello from the summit14:02
jokke_There was lots of active discussions around Edge and different use cases and needs14:03
LiangFangsome topic about starlingx, right?14:03
jokke_image handling is pretty much top of the list in every one of those, so please keep an eye on and provide any feedback you might have14:03
jokke_LiangFang: there was some discussions with StarlingX as well but I'm more referring to the general edge discussions and OpenStack rather than StarlingX specifically14:04
LiangFangOK14:05
jokke_just wanted to bring up that it's currently the hot topic and we seem to be pretty much in the center of it :)14:05
LiangFangyes14:05
LiangFangstarlingx is based on openstack14:06
LiangFangand glance is the important module of it14:06
jokke_Another thing, now when the Summit is over we have spec freeze approaching next week. If you have any specs still in flight/not submitted ... lets get those worked out14:06
*** slaweq has quit IRC14:07
LiangFangok14:08
jokke_this does not affect spec-lites as before but we want to lock down any bigger feature planning/API changes at this point14:08
LiangFangwhen will open again?14:09
*** pbourke has quit IRC14:09
LiangFangI mean when can we submit spec14:10
LiangFangafter next week14:10
jokke_It will be for the Train cycle. We normally hold off until towards the end of the cycle (somewhere around milestone 3) just to give the time for people to actually work on the stuff agreed for the cycle instead of focusing on future specs14:10
*** pbourke has joined #openstack-meeting-414:11
LiangFangok14:11
LiangFangend of stein cycle is march 2019, right?14:11
jokke_so feel free to draft you Train specs already but don't expect too much feedback etc. before towards the end of the cycle14:11
jokke_10th of April is currently the expected release date14:12
LiangFangok14:12
jokke_ok moving on14:13
jokke_#topic Combined mailing lists discussion14:13
*** openstack changes topic to "Combined mailing lists discussion (Meeting topic: glance)"14:13
jokke_#link http://lists.openstack.org/pipermail/openstack-dev/2018-September/134911.html14:13
*** dims has joined #openstack-meeting-414:14
jokke_So it seems that people are not getting enough spammed by having single dev list yet and there is urge to move everything into a single list14:14
jokke_reminder the new list went live at 19th14:15
jokke_so redo your filters and subscribe to the new list14:15
abhishekkDone14:15
jokke_#topic multi-store adding locations does not default to the default store14:16
*** openstack changes topic to "multi-store adding locations does not default to the default store (Meeting topic: glance)"14:16
jokke_I saw some discussion about this but it seems that the locations api bit us again. abhishekk you have some light you can shed to this?14:16
abhishekkYeah, Brian has found this issue while testing locations stuff14:17
abhishekkWith multiple backend if we try to add location without backend not specified in location metadata then it fails with unknown scheme error14:18
abhishekkimacdonn has done some poc and submitted a patches for the same14:19
LiangFangI met this issue last week14:19
LiangFangalso14:19
LiangFanglocation metadata must be specified14:19
abhishekkI have added some description on the bug14:20
abhishekkjokke_: kindly have a look at that14:21
abhishekkIt looks good to me and brain also finds it ok14:21
jokke_So to not break the API again ... I think we should utilize the default backend _if_ the uri scheme is valid for it (and not reguire the backend to be specified for backwards compatibility) any location that is not for the default should require the backend being specified14:21
jokke_btw this will need at least Nova work as well and we need to coordinate how this is handled14:22
*** Luzi has quit IRC14:22
*** mhen has joined #openstack-meeting-414:23
*** ktibi_ has quit IRC14:23
jokke_any thoughts on that?14:23
abhishekkI need to cheCK from nova prospect14:24
abhishekkMeanwhile could you add your thoughts on the patch?14:24
jokke_Yeah so the nova side where this will break is snapshotting when ceph is used14:24
jokke_yeah, I'll comment on the bug as well14:24
abhishekkThanks, i will check the snapshot case once back to work14:25
jokke_specially if we have multiple ceph backends nova needs to look where the parent image is stored and use that backend id when creating the location for the snapshot14:25
*** pcaruana has joined #openstack-meeting-414:25
abhishekkAck14:26
jokke_it's great that we found it now instead of finding it when people have deployed their edge sites with local ceph clusters and all the snapshots are fecked14:27
abhishekkRight14:27
jokke__This_ is one of the reasons why rolling new features as experimental is good idea :D14:27
abhishekkAgree14:28
jokke_#topic Bug squad meeting to resume from 26th of Nov14:28
*** openstack changes topic to "Bug squad meeting to resume from 26th of Nov (Meeting topic: glance)"14:28
*** qwebirc39073 has quit IRC14:29
abhishekkThis is just announcement14:29
jokke_cool ty14:29
abhishekkWe are resuming this by-weekly meeting since 26 November14:29
jokke_moving on then14:29
abhishekkYes14:30
jokke_#topic FK constrain violation14:30
*** openstack changes topic to "FK constrain violation (Meeting topic: glance)"14:30
LiangFanghi14:30
LiangFangthis is a bug that when doing db purge, foreign key error will happen14:30
LiangFangbecause14:30
abhishekk(i will quit now, will go through logs later)14:30
jokke_#link https://review.openstack.org/#/c/617889/14:30
LiangFangok14:31
jokke_abhishekk: kk, take care buddy14:31
abhishekkjokke_: ty14:31
*** ktibi has joined #openstack-meeting-414:31
*** abhishekk has quit IRC14:31
LiangFangthe bug is the table task_info has the records but14:32
LiangFangsorry14:32
jokke_LiangFang: so I really really suck with databases.14:32
LiangFangbug is https://bugs.launchpad.net/glance/+bug/180364314:32
openstackLaunchpad bug 1803643 in Glance "task_info FK error when running "glance-manage db purge"" [Medium,Confirmed] - Assigned to Liang Fang (liangfang)14:32
jokke_Mind to explain to like to 5 year old? :P14:32
jokke_where do we actually break? I was looking at the bug and I can see failure in logic/functionality but no errors in the bug description14:33
*** rambo has joined #openstack-meeting-414:34
LiangFangwhen there're "deleted" record in table tasks, when trying to delete the records in table tasks14:35
LiangFangexception will happen: like this: DBError detected when purging from tasks14:36
LiangFangbecause table task_info still have record and depends on table tasks14:36
jokke_ok, that makes sense. Does that fail the whole purge or does it just affect the tasks part of it?14:36
LiangFangso we need to purge task_info first14:37
jokke_and/or does it barf something else as well?14:37
LiangFangit will interrupt the db purge cmd14:37
jokke_kk14:38
LiangFangso the db cannot be purged as expected14:38
LiangFang:)14:38
LiangFangsorry for my bad english14:38
jokke_well in that case lets get it fixed. The patch seems to be quite straight forward for it14:38
LiangFangyes14:39
jokke_thanks for looking into it14:39
LiangFangthanks14:39
LiangFangthat's all for this patch14:40
jokke_#topic allowing to add location only when location does not exist14:40
*** openstack changes topic to "allowing to add location only when location does not exist (Meeting topic: glance)"14:40
jokke_#link https://review.openstack.org/#/c/617891/14:40
LiangFangyes, rosmaita have gave comments on this patch14:40
LiangFangIt seems make sense14:40
jokke_yes he seems to have -2 there and his reasoning is very valid14:41
LiangFangyes14:41
LiangFangI agree with him, and about to abandon this patch14:41
LiangFangbut waiting confirm from co-author14:41
LiangFangI'm working on the patches that need to upstream14:42
LiangFangbut the original author is from wind river14:42
jokke_cool, yeah I definitely share his concerns about that patch and it would break the API quite horribly (in a sense that it makes the API to work very very unpredictably)14:42
jokke_#topic Don't percent-encode colon in HTTP headers14:43
*** openstack changes topic to "Don't percent-encode colon in HTTP headers (Meeting topic: glance)"14:43
LiangFangcould you please comment your concern on this patch? thanks14:43
jokke_So there was some discussion about these before and we seem to be doing some quite horrible stuff when encoding the headers. We basically do encode stuff that doesn't need to be encoded and don't properly decode them on the other end14:44
jokke_LiangFang: yeah, I'll add my comment there14:45
LiangFangthanks14:45
jokke_I think the comma is just another example of the behavior and the fix is likely not fully covering14:45
jokke_but it would be decent bandaid for the issue seen now14:45
jokke_I'll check the backport and see it through14:46
LiangFangI have no knowledge on this issue ...14:47
jokke_basically we started precent quoting request headers to be able to follow the rfc for http headers14:48
jokke_problem is that the lib we use for that is not exactly meant to be doing that so it quotes certain characters that are <127 ASCII code range which in turn breaks tons of stuff in the receiving end14:49
jokke_and seems like only way to indicate safe chars to it is providing it a list of them14:49
jokke_so every now and then we discover new characters it's quoting that happens to break some parts of our api14:49
jokke_not great but at least we're breaking only those requests instead of majority of our headers as we used to14:50
jokke_#link https://review.openstack.org/#/c/618362/14:50
jokke_#topic Open Discussion14:51
*** openstack changes topic to "Open Discussion (Meeting topic: glance)"14:51
jokke_there was pointer here. The Community Goals discussion is going on again14:51
LiangFangack14:52
jokke_#link http://lists.openstack.org/pipermail/openstack-discuss/2018-November/000055.html14:52
*** hongbin has joined #openstack-meeting-414:52
jokke_please follow up and do provide feedback.14:52
LiangFangok14:52
jokke_another thing left on the agenda is something quota related, this was from you LiangFang as well?14:53
LiangFangnot from me14:53
jokke_ok ... who added this?14:53
LiangFangit seems be added when the meeting is opened14:53
*** rambo has quit IRC14:54
*** yamamoto has joined #openstack-meeting-414:55
*** psachin has quit IRC14:55
jokke_well just to answer the question as I understand it: No there is no quotas for sharing images, no we do not want one, this is the exact reason why image sharing/accepting happen via out-of-band communications so that these does not spam anyones image lists14:55
jokke_so whoever added the question there and hopefully is reading meeting logs, if that did not aswer the question or you have something to add/needs clarification, please get back to us with it14:57
jokke_Anything else?14:57
LiangFangno from me14:57
*** rambo has joined #openstack-meeting-414:58
jokke_ok ... going 1st14:58
rambohi, all. I  have a question about use shared image with each other, Do we have the quota limit for requests to share the image to each other? For example, someone shares the image with me without stop, how do we deal with it?14:58
jokke_rambo: see my answer 3 lines up ;)14:58
jokke_might be 5 even14:59
*** celebdor has quit IRC14:59
jokke_And we're out of time, thanks everyone and #openstack-glance serves if something pops in between15:00
jokke_#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Thu Nov 22 15:00:15 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2018/glance.2018-11-22-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2018/glance.2018-11-22-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2018/glance.2018-11-22-14.00.log.html15:00
*** rambo has quit IRC15:03
*** yamamoto has quit IRC15:03
*** ktibi has quit IRC15:09
*** celebdor has joined #openstack-meeting-415:16
*** seajay has joined #openstack-meeting-415:18
*** seajay has quit IRC15:47
*** gkadam has quit IRC15:51
*** LiangFang has quit IRC15:55
*** Liang__ has joined #openstack-meeting-416:12
*** ktibi has joined #openstack-meeting-416:13
*** Liang__ has quit IRC16:20
*** e0ne has quit IRC16:28
*** ktibi has quit IRC16:35
*** diablo_rojo has joined #openstack-meeting-416:58
*** celebdor has quit IRC17:10
*** e0ne has joined #openstack-meeting-417:25
*** e0ne has quit IRC17:49
*** e0ne has joined #openstack-meeting-418:07
*** e0ne has quit IRC18:15
*** salmankhan has quit IRC18:32
*** yamamoto has joined #openstack-meeting-419:00
*** yamamoto has quit IRC19:05
*** diablo_rojo has quit IRC19:59
*** iyamahat has quit IRC21:09
*** yamahata has quit IRC21:09
*** yamahata has joined #openstack-meeting-421:11
*** bobh has joined #openstack-meeting-421:13
*** yamamoto has joined #openstack-meeting-421:22
*** slaweq has joined #openstack-meeting-421:23
*** dave-mccowan has joined #openstack-meeting-421:24
*** bobh has quit IRC21:26
*** dave-mccowan has quit IRC21:28
*** yamamoto has quit IRC21:37
*** yamamoto has joined #openstack-meeting-421:40
*** yamamoto has quit IRC22:07
*** yamamoto has joined #openstack-meeting-422:07
*** yamamoto has quit IRC22:08
*** slaweq has quit IRC22:15
*** celebdor has joined #openstack-meeting-422:23
*** isq_ has joined #openstack-meeting-422:40
*** isq has quit IRC22:41
*** yamamoto has joined #openstack-meeting-422:46
*** yamamoto has quit IRC22:57
*** yamamoto has joined #openstack-meeting-423:12
*** slaweq has joined #openstack-meeting-423:13
*** slaweq has quit IRC23:18
*** Liang__ has joined #openstack-meeting-423:27
*** Liang__ has quit IRC23:30

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!