Thursday, 2019-05-16

*** hongbin has quit IRC00:01
*** yamamoto has quit IRC00:19
*** diablo_rojo has quit IRC00:45
*** d34dh0r53 has joined #openstack-meeting-401:01
*** dklyle has joined #openstack-meeting-402:14
*** dhellmann has quit IRC02:23
*** dhellmann has joined #openstack-meeting-402:23
*** JamesBenson has joined #openstack-meeting-402:26
*** yamamoto has joined #openstack-meeting-402:48
*** hongbin has joined #openstack-meeting-403:14
*** yamamoto has quit IRC03:50
*** radeks_ has joined #openstack-meeting-403:50
*** yamamoto has joined #openstack-meeting-403:51
*** hongbin has quit IRC03:55
*** JamesBenson has quit IRC04:01
*** radeks_ has quit IRC04:40
*** janki has joined #openstack-meeting-404:43
*** gcheresh_ has joined #openstack-meeting-404:55
*** cloudkiller has joined #openstack-meeting-405:11
*** _d34dh0r53_ has joined #openstack-meeting-405:12
*** yboaron_ has joined #openstack-meeting-405:40
*** Luzi has joined #openstack-meeting-405:40
*** hamzy has quit IRC05:44
*** gkadam has quit IRC05:49
*** gkadam has joined #openstack-meeting-405:51
*** e0ne has joined #openstack-meeting-405:53
*** radeks_ has joined #openstack-meeting-406:03
*** radeks_ has quit IRC06:04
*** radeks_ has joined #openstack-meeting-406:04
*** hamzy has joined #openstack-meeting-406:21
*** e0ne has quit IRC06:36
*** admcleod has quit IRC06:39
*** gcheresh_ has quit IRC06:57
*** admcleod has joined #openstack-meeting-407:09
*** gcheresh_ has joined #openstack-meeting-407:12
*** pcaruana has joined #openstack-meeting-407:13
*** ralonsoh has joined #openstack-meeting-407:23
*** iyamahat has quit IRC07:31
*** yamamoto has quit IRC07:33
*** yamamoto has joined #openstack-meeting-407:39
*** slaweq has joined #openstack-meeting-407:40
*** gkadam has quit IRC07:55
*** ktibi has joined #openstack-meeting-407:58
*** e0ne has joined #openstack-meeting-408:08
*** ktibi has quit IRC08:16
*** ktibi has joined #openstack-meeting-408:16
*** ktibi has quit IRC08:16
*** ktibi has joined #openstack-meeting-408:17
*** ktibi has quit IRC08:17
*** ktibi has joined #openstack-meeting-408:18
*** k_mouza has joined #openstack-meeting-408:29
*** gkadam has joined #openstack-meeting-408:45
*** ktibi has quit IRC08:53
*** ktibi has joined #openstack-meeting-408:53
*** ktibi has quit IRC08:56
*** ktibi has joined #openstack-meeting-408:56
*** ktibi has quit IRC09:16
*** ktibi has joined #openstack-meeting-409:16
*** yamamoto has quit IRC10:09
*** ktibi has quit IRC10:11
*** k_mouza has quit IRC10:12
*** yamamoto has joined #openstack-meeting-410:20
*** yamamoto has quit IRC10:25
*** pcaruana has quit IRC10:27
*** k_mouza has joined #openstack-meeting-410:38
*** ktibi has joined #openstack-meeting-410:54
*** k_mouza_ has joined #openstack-meeting-411:08
*** k_mouza has quit IRC11:11
*** ktibi has quit IRC11:17
*** ktibi has joined #openstack-meeting-411:17
*** pcaruana has joined #openstack-meeting-411:37
*** yamamoto has joined #openstack-meeting-411:44
*** yamamoto has quit IRC11:45
*** yamamoto has joined #openstack-meeting-411:45
*** seajay has joined #openstack-meeting-411:59
*** yamamoto has quit IRC12:03
*** yamamoto has joined #openstack-meeting-412:10
*** ktibi has quit IRC12:16
*** ktibi has joined #openstack-meeting-412:17
*** yamamoto has quit IRC12:19
*** seajay has quit IRC12:21
*** seajay has joined #openstack-meeting-412:24
*** janki has quit IRC12:28
*** snapiri has quit IRC12:56
*** howell has joined #openstack-meeting-413:09
*** yamamoto has joined #openstack-meeting-413:15
*** gkadam has quit IRC13:33
*** rosmaita has joined #openstack-meeting-413:38
*** Luzi has quit IRC13:45
*** gcheresh_ has quit IRC13:48
*** pcaruana has quit IRC13:56
*** smcginnis has joined #openstack-meeting-413:56
*** abhishekk has joined #openstack-meeting-413:57
*** JamesBenson has joined #openstack-meeting-414:02
*** jokke_ has joined #openstack-meeting-414:04
jokke_#startmeeting glance14:04
openstackMeeting started Thu May 16 14:04:30 2019 UTC and is due to finish in 60 minutes.  The chair is jokke_. Information about MeetBot at http://wiki.debian.org/MeetBot.14:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:04
*** openstack changes topic to " (Meeting topic: glance)"14:04
openstackThe meeting name has been set to 'glance'14:04
smcginniso/14:04
jokke_#topic roll-call14:04
*** openstack changes topic to "roll-call (Meeting topic: glance)"14:04
jokke_o/14:04
jokke_#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:05
rosmaitao/14:05
jokke_ok, I was late enough so lets get started ;)14:05
jokke_#topic updates14:05
*** openstack changes topic to "updates (Meeting topic: glance)"14:05
jokke_so first recap of PTG plans14:06
jokke_#link  https://etherpad.openstack.org/p/Glance-Train-PTG-planning14:06
*** mattmceuen has left #openstack-meeting-414:06
jokke_we took the cinder way and instead of having separate etherpads for each topic recorded the notes under the topic on that one etherpad14:06
*** JamesBenson has quit IRC14:07
jokke_I have to say I like it ... much easier to navigate than 20 tabs of spread etherpads14:07
rosmaitayes, there is something to be said for that14:07
jokke_shoot14:08
rosmaitalooks like abhishekk had to restart his system due to connectivity problems, we should probably wait a few min14:08
jokke_kk14:08
*** abhishekk has quit IRC14:10
jokke_I have filtered out all joins, parts and nick changes to keep my irc clean so if he dropped I missed it14:10
*** abhishekk has joined #openstack-meeting-414:11
abhishekko/14:11
smcginnisHe's back! :)14:11
rosmaitahooray!14:11
abhishekkapology, had some network issues14:11
jokke_np14:12
jokke_so rosmaita you don't like having everything in one Etherpad?14:12
rosmaitano, it's fine14:12
smcginnisWe've also done by day instead of by topic. Less etherpads, but still not a lot all in one if there ends up being a lot of notes.14:13
rosmaitait's like everything ... occasionally there's probably a topic worth having on its own, but in general this is a good way to do it14:13
abhishekk+114:14
*** JamesBenson has joined #openstack-meeting-414:14
jokke_yeah, I'd love to have etherpad with permalinks so you could have TOC there14:14
rosmaitathat's called a wiki14:14
rosmaita:)14:14
jokke_:P14:14
smcginnis:D14:15
jokke_ok, shall we move on?14:15
abhishekkyep14:15
smcginnisNot sure you want to go through the effort, but Jay has been doing nice cleaned up recaps here: https://wiki.openstack.org/wiki/Cinder#PTG_and_Summit_Meeting_Summaries14:15
jokke_thanks smcginnis will have a look14:15
smcginnisI've found it useful with being able to find the bolded "Action (smcginnis)" parts.14:16
smcginnisSlightly higher chance I will actually do something I signed up for. ;)14:16
jokke_cool :D14:16
jokke_Another thing I wanted to highlight is the Image Encryption weekly meeting. Noticed you guys had put your input into the doodle already14:17
jokke_#link http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005861.html14:17
jokke_for anyone who missed the discussion in the ML14:17
jokke_by the looks of it I finally got my filters fixed and I seem to be able to keep somewhat track whats going on again14:18
jokke_moving on14:18
*** JamesBenson has quit IRC14:18
jokke_#topic release updates/periodic jobs14:18
*** openstack changes topic to "release updates/periodic jobs (Meeting topic: glance)"14:18
abhishekkthat would be me14:19
abhishekkso we are in R-22 week14:19
abhishekkwe have first milestone release in week Jun 03 - Jun 07 which is two weeks away14:19
rosmaitawow that is coming up fast14:20
jokke_yup14:20
abhishekkthe target is to make multi-store stable14:20
abhishekkwe are on track at the moment14:20
abhishekk** Need timely reviews14:20
rosmaitaping me directly for reviews14:20
rosmaita:)14:20
abhishekkcool, thanks14:20
abhishekkRegarding periodic jobs we have only one failure in last three weeks14:21
abhishekkunfortunately that is time out due to parser error14:21
rosmaitacurse you, subparser!14:22
jokke_indeed, but one failure in 3 weeks is great news14:22
abhishekkIn my free time, I am planning to look whether we can get rid of deprecation warnings14:22
jokke_we're really getting there from multiple failures a week to failure in multiple weeks :D14:23
abhishekk(One thing in my mind is comment out mult-store functional and unit tests and add recheck multiple times)14:23
abhishekksome how I am convinced that timeout might be because of we are loading http server for 3-4 tests which is might failing14:24
jokke_hmm-m, why is that failing?14:24
abhishekkMight be socket timeout (not conclusive evidence in the logs though)14:25
jokke_kk14:25
abhishekkBut to make sure, I will run some tests14:25
abhishekkthat's it from my side, we are good to move ahead unless someone has something to say :D14:26
jokke_sounds good to me14:26
jokke_thanks for keeping track on those and thinking of ideas where it might be coming from14:26
*** cloudkiller is now known as blah2314:27
*** blah23 is now known as cloudnull|afk14:27
jokke_#topic QA wants to split tempest jobs14:27
*** openstack changes topic to "QA wants to split tempest jobs (Meeting topic: glance)"14:27
rosmaitajust an awareness thing14:27
rosmaitathe email asked "Thoughts on this approach?"14:28
jokke_#link http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005871.html14:28
rosmaitai didn't have any, but maybe someone else will14:28
jokke_So I did reply to the chain14:28
rosmaitai missed that14:28
abhishekki saw it14:28
rosmaitaok, that's all from me14:28
jokke_I have little problem understanding the proposed split, but maybe I get some response and light to it14:29
jokke_I just hope they take at least my wish into account and we start by splitting the jobs up and running the split jobs in check instead of check and gate for the beginning14:29
jokke_but yeah as long as we don't have QA here to discuss about it with us, thanks rosmaita for bringing this up14:30
jokke_#topic requests u-c bump or not14:31
*** openstack changes topic to "requests u-c bump or not (Meeting topic: glance)"14:31
*** cloudnull|afk is now known as cloudnull14:31
jokke_another good heads up from rosmaita14:31
rosmaitayeah, this may amount to nothing14:31
jokke_#link  http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005956.html14:31
jokke_we might want to look what the failure is and if there is easy way to work around it14:32
jokke_I'm very very happy about the discussion and the direction it's taking on ML14:32
*** yamamoto has quit IRC14:33
rosmaitayeah, i am not sure what's up with stable/queens14:33
jokke_this really isn't the right thing to do with u-c but it was nice to get the heads up and see if work is needed for updating the vulnerable package14:33
jokke_me neither, haven't had time to look into why it breaks yet14:33
*** yamamoto has joined #openstack-meeting-414:33
*** yamamoto has quit IRC14:33
smcginnisIn the requirements meeting yesterday it was decided any backports of those will be held until someone writes up a decent plan on how things should be handled if we actually do want to keep maintaining u-c for these.14:33
rosmaitagood to know14:34
jokke_smcginnis: great14:34
abhishekkcool14:34
*** yamamoto has joined #openstack-meeting-414:34
jokke_smcginnis: yeah updating u-c would send wrong message that we're actually keeping track of CVEs for all of our dependencies and all their supported versions14:35
jokke_happy to hear no-one signed the community up for it but rather we keep the expectations realistic14:35
smcginnisYeah, that's the big concern.14:35
*** d34dh0r53 has quit IRC14:36
jokke_ok, moving on14:36
jokke_#topic multi-store for locations API14:36
*** openstack changes topic to "multi-store for locations API (Meeting topic: glance)"14:36
jokke_abhishekk: go go go!14:36
jokke_;)14:36
abhishekk:D14:36
*** d34dh0r53 has joined #openstack-meeting-414:37
abhishekkMe and jokke_ just had 30 minutes discussion over it just before the meeting14:37
*** pcaruana has joined #openstack-meeting-414:37
abhishekkWe have decided to have a method in each store which will return the prefix of url to match with the location url14:37
abhishekkto decide the actual store for that location14:38
jokke_so to give a little meat around the bones on this, the problem is that lazy update of locations table with the store ID14:38
abhishekkI will work on PoC and jokke_ will help me in case I have any doubts :D14:39
*** yamamoto has quit IRC14:39
jokke_we need a way to determine which store given location actually belongs to and the current store map does not directly give that to us14:39
rosmaitai have never liked the store map14:39
abhishekkneither do I, I will definitely work on refactor the same in next cycle14:40
rosmaitaok, will be interesting to see what you come up with14:40
jokke_rosmaita: why and better ideas to handle it? It's still experimental so speak up now when we still can fix it if there is better ways to handle them14:40
rosmaitawell, the map is ambiguous when you have stores using the same scheme14:41
rosmaitait seemed to be designed on the assumption that that would never happen14:41
*** d34dh0r53 is now known as Guest2890414:41
abhishekkright14:42
jokke_I think abhishekk's original idea was not to care and just crawl through all stores of specific type until we can find the correct one14:42
abhishekkyes14:42
rosmaitaright, but if we have 1000 edge stores, that could be a problem14:42
jokke_So this might be something to think about right _now_ and fix it before we move the design out of experimental and need to worry about the upgrade path to it14:43
rosmaitaagreed14:43
rosmaitai don't have anything off the top of my head14:44
davee_+114:44
jokke_rosmaita: yes, that's why I was reluctant about it from the beginning and have insted us to record the store ids with the location from the very beginning ;)14:44
rosmaitai think the locations metadata was supposed to help with this14:44
jokke_insisted14:44
abhishekkdo we need to care about adding a store as a metadata to location api?14:45
jokke_rosmaita: yes, so that's why we're trying to figure out the recognition pattern now and include that into the store map, so we can update the locations metadata lazy when the image is accessed, so we have the possibly slow recognition process done only once, not every time14:45
jokke_and can still avoid heavy migration job during upgrade14:46
rosmaitaok, that makes sense14:46
rosmaitaand the edge sites will all be new, so won't require migration if we design this right14:46
jokke_when we have the store id recorded to the location, we can then just request correct store object right away14:46
abhishekkYeah14:47
rosmaitawhat will you use for store id?14:47
jokke_rosmaita: indeed, any multi-store image will have that id and will just skip the recognition in the first place14:47
rosmaitai'm asking because we may want to have a store uuid that never changes, and a store name that can change14:48
jokke_rosmaita: so location has store id in the metadata so when the image is requested, we can take correct store id and correct store object to access the data, istead of walking through all of them14:48
rosmaitabecause you know that some operator will decide to rename the stores14:48
rosmaitaright now the store_id does double duty14:49
rosmaitaas name in the info/stores response14:49
abhishekkwe don't have anything like store_uuid14:49
rosmaitayeah, that's why i'm mentioning it14:49
jokke_rosmaita: yup, and then they will get lovely slow access when we need to go through the recognition process again14:49
jokke_but that will be sped up by having the map being able to provide the url prefix to match agains instead of walking through all stores, trying to access the image and grabbing the first one14:50
jokke_specially if that image is in 2300 different ceph stores and someone decides to rename them all14:50
davee_what about having a default store id and override it as needed?14:51
*** JamesBenson has joined #openstack-meeting-414:51
abhishekkwe already have one default store, currently known as default_backend14:52
jokke_So the logic needs to be something like "does it have store id, does that store id still exists in map, does that store has the image" if not any re-recognize the locations14:52
abhishekkjokke_, ++14:52
jokke_that way we get optimized access as long as no-one fucks it up and we get slow access eventually if it gets fucked up but we break nothing14:53
jokke_as long as the store is in config14:53
abhishekkright14:54
abhishekklast 6 minutes to go14:54
jokke_yeah, we can continue this on os-glance if needed14:55
jokke_'topic open discussion14:55
jokke_#topic open discussion14:55
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:55
jokke_the priorities topic was late addition14:55
abhishekkwe have priorities outlined at the end of PTG planning etherpad14:56
jokke_but just highligh the multi-store is our current priority. Sooner in the cycle we get that stable the longer we have opportunity to keep it testing and address any bugs14:56
jokke_lets get that done, clean the deprecations from glance_store and get the 1.0.0 out of the door14:57
jokke_after that we can focus on caching and all the new stuff we have outlined for the cycle14:57
abhishekkack14:58
jokke_so like said any other improvement than having the url prefix available to make the store map better would be great to get out there under discussion asap14:59
jokke_specially if it needs poking in the glance_store side14:59
jokke_and time15:00
jokke_Thanks all!15:00
rosmaitasorry, got pulled into another meeting, will read through the scrollback15:00
jokke_#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Thu May 16 15:00:22 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2019/glance.2019-05-16-14.04.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2019/glance.2019-05-16-14.04.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2019/glance.2019-05-16-14.04.log.html15:00
abhishekkthank you15:00
smcginnisThanks!15:00
*** rosmaita has left #openstack-meeting-415:01
*** smcginnis has left #openstack-meeting-415:01
*** ktibi has quit IRC15:16
*** ktibi has joined #openstack-meeting-415:16
*** ktibi has quit IRC15:16
*** ktibi has joined #openstack-meeting-415:17
*** ktibi_ has joined #openstack-meeting-415:19
*** JamesBenson has quit IRC15:19
*** JamesBenson has joined #openstack-meeting-415:20
*** ktibi has quit IRC15:22
*** roman_g has quit IRC15:36
*** _d34dh0r53_ is now known as d34dh0r5315:38
*** e0ne has quit IRC15:38
*** macza has joined #openstack-meeting-415:39
*** yboaron_ has quit IRC15:44
*** pcaruana has quit IRC15:47
*** yamamoto has joined #openstack-meeting-415:50
*** ktibi_ has quit IRC15:55
*** yamamoto has quit IRC15:58
*** premsankar has joined #openstack-meeting-416:02
*** gcheresh_ has joined #openstack-meeting-416:03
*** dims has quit IRC16:05
*** gcheresh_ has quit IRC16:19
*** k_mouza_ has quit IRC16:40
*** bauzas has quit IRC16:54
*** bauzas has joined #openstack-meeting-416:57
*** ktibi_ has joined #openstack-meeting-416:58
*** ktibi_ has quit IRC17:02
*** dims has joined #openstack-meeting-417:03
*** abhishekk has quit IRC17:04
*** dims has quit IRC17:12
*** dims has joined #openstack-meeting-417:13
*** dklyle has quit IRC17:34
*** pcaruana has joined #openstack-meeting-417:39
*** HagunKim has quit IRC18:13
*** ralonsoh has quit IRC18:20
*** trident has quit IRC18:51
*** trident has joined #openstack-meeting-418:52
*** iyamahat has joined #openstack-meeting-418:53
*** k_mouza has joined #openstack-meeting-419:15
*** k_mouza has quit IRC19:19
*** yamahata has joined #openstack-meeting-419:31
*** pcaruana has quit IRC19:52
*** radeks_ has quit IRC19:58
*** e0ne has joined #openstack-meeting-420:10
*** e0ne has quit IRC20:12
*** diablo_rojo has joined #openstack-meeting-420:48
*** trident has quit IRC20:59
*** trident has joined #openstack-meeting-421:00
*** fdegir has quit IRC21:10
*** fdegir has joined #openstack-meeting-421:11
*** howell has quit IRC21:13
*** howell has joined #openstack-meeting-421:13
*** slaweq has quit IRC21:18
*** hongbin has joined #openstack-meeting-421:32
*** howell has quit IRC21:32
*** JamesBenson has quit IRC21:40
*** JamesBenson has joined #openstack-meeting-421:43
*** JamesBen_ has joined #openstack-meeting-421:44
*** JamesBenson has quit IRC21:47
*** JamesBen_ has quit IRC21:49
*** seajay has quit IRC22:03
*** k_mouza has joined #openstack-meeting-422:16
*** k_mouza has quit IRC22:20
*** hongbin has quit IRC22:39
*** macza has quit IRC22:57
*** slaweq has joined #openstack-meeting-423:05
*** slaweq has quit IRC23:10
*** slaweq has joined #openstack-meeting-423:11
*** slaweq has quit IRC23:16
*** JamesBenson has joined #openstack-meeting-423:18
*** dklyle has joined #openstack-meeting-423:21
*** JamesBenson has quit IRC23:23
*** diablo_rojo has quit IRC23:24
*** dklyle has quit IRC23:35
*** yamamoto has joined #openstack-meeting-423:49
*** diablo_rojo has joined #openstack-meeting-423:52
*** yamamoto has quit IRC23:53

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