Thursday, 2019-11-21

*** k_mouza has quit IRC00:00
*** slaweq has joined #openstack-meeting-400:10
*** macz has quit IRC00:11
*** slaweq has quit IRC00:15
*** slaweq has joined #openstack-meeting-400:19
*** k_mouza has joined #openstack-meeting-400:23
*** slaweq has quit IRC00:24
*** k_mouza has quit IRC00:27
*** k_mouza has joined #openstack-meeting-400:27
*** k_mouza has quit IRC00:31
*** k_mouza_ has joined #openstack-meeting-400:31
*** k_mouza_ has quit IRC00:32
*** k_mouza has joined #openstack-meeting-400:33
*** JamesBenson has joined #openstack-meeting-400:33
*** k_mouza has quit IRC00:34
*** k_mouza has joined #openstack-meeting-400:34
*** slaweq has joined #openstack-meeting-400:37
*** JamesBenson has quit IRC00:37
*** k_mouza has quit IRC00:38
*** slaweq has quit IRC00:42
*** slaweq has joined #openstack-meeting-400:44
*** slaweq has quit IRC00:48
*** slaweq has joined #openstack-meeting-400:51
*** k_mouza has joined #openstack-meeting-400:52
*** slaweq has quit IRC00:55
*** k_mouza has quit IRC00:56
*** slaweq has joined #openstack-meeting-400:57
*** Liang__ has joined #openstack-meeting-400:58
*** slaweq has quit IRC01:01
*** slaweq has joined #openstack-meeting-401:02
*** k_mouza has joined #openstack-meeting-401:10
*** slaweq has quit IRC01:13
*** k_mouza has quit IRC01:16
*** slaweq has joined #openstack-meeting-401:16
*** roman_g has quit IRC01:17
*** slaweq has quit IRC01:21
*** slaweq has joined #openstack-meeting-401:28
*** slaweq has quit IRC01:32
*** dave-mccowan has joined #openstack-meeting-401:35
*** dave-mccowan has quit IRC01:42
*** k_mouza has joined #openstack-meeting-401:45
*** k_mouza has quit IRC01:50
*** k_mouza has joined #openstack-meeting-401:50
*** slaweq has joined #openstack-meeting-401:50
*** k_mouza has quit IRC01:52
*** k_mouza_ has joined #openstack-meeting-401:52
*** slaweq has quit IRC01:55
*** k_mouza_ has quit IRC01:56
*** slaweq has joined #openstack-meeting-401:58
*** slaweq has quit IRC02:10
*** slaweq has joined #openstack-meeting-402:23
*** slaweq has quit IRC02:30
*** slaweq has joined #openstack-meeting-402:31
*** slaweq has quit IRC02:35
*** slaweq has joined #openstack-meeting-402:47
*** macz has joined #openstack-meeting-402:50
*** slaweq has quit IRC02:52
*** macz has quit IRC03:32
*** macz has joined #openstack-meeting-403:33
*** macz has quit IRC03:37
*** igordc has quit IRC05:11
*** Luzi has joined #openstack-meeting-405:58
*** gcheresh has joined #openstack-meeting-406:19
*** lpetrut has quit IRC06:21
*** macz has joined #openstack-meeting-406:22
*** macz has quit IRC06:27
*** slaweq has joined #openstack-meeting-406:39
*** slaweq has quit IRC06:44
*** pcaruana has joined #openstack-meeting-407:27
*** slaweq has joined #openstack-meeting-408:44
*** ralonsoh has joined #openstack-meeting-408:45
*** Liang__ has quit IRC09:34
*** liuyulong has quit IRC10:06
*** e0ne has joined #openstack-meeting-410:10
*** roman_g has joined #openstack-meeting-410:14
*** macz has joined #openstack-meeting-410:30
*** macz has quit IRC10:35
*** slaweq has quit IRC12:39
*** slaweq has joined #openstack-meeting-413:17
*** abhishekk has joined #openstack-meeting-413:39
*** tosky has joined #openstack-meeting-413:57
*** rosmaita has joined #openstack-meeting-413:58
abhishekk#startmeeting glance14:00
openstackMeeting started Thu Nov 21 14:00:03 2019 UTC and is due to finish in 60 minutes.  The chair is abhishekk. 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
abhishekk#topic roll call14:00
openstackThe meeting name has been set to 'glance'14:00
*** openstack changes topic to "roll call (Meeting topic: glance)"14:00
jokke_o/14:00
abhishekk#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:00
davee_o/14:00
abhishekko/14:00
*** yebinama has joined #openstack-meeting-414:00
rosmaitao/14:01
yebinamao/14:01
abhishekkcool, nice turnaround today14:01
abhishekkLets start14:01
abhishekkSkipping updates part as don't have any update to share14:01
abhishekk#topic release/periodic jobs update14:01
*** openstack changes topic to "release/periodic jobs update (Meeting topic: glance)"14:01
abhishekkSo, milestone 1 is just two weeks away14:02
abhishekkand we have plenty on the plate to finish14:02
abhishekkNeed reviews on specs14:02
jokke_yes, will get on that today or tomorrow14:03
abhishekkOn periodic jobs front everything is good14:03
jokke_hopefully both14:03
abhishekkjokke_, thank you14:03
toskyo/14:03
abhishekkboth are interrelated14:03
abhishekkenough from this topic14:04
abhishekk#topic import image in multi stores14:04
*** openstack changes topic to "import image in multi stores (Meeting topic: glance)"14:04
abhishekk#link https://review.opendev.org/#/c/669201/1114:04
abhishekkSpecs looks in good shape and everything is covered what we discussed in PTG14:05
abhishekkthanks to yebinama for that14:05
yebinamaThanks for the reviews :)14:05
yebinamaThere is just one point left14:06
abhishekkWe just had one question, are we only targeting this to change import API and not old upload API14:06
abhishekkyebinama, do you have anything else in mind?14:06
jokke_ok, I put this as priority review on top of my queue14:06
abhishekkgreat14:06
yebinamaabhishekk No that was the same point14:06
abhishekkrosmaita, if you get some time, please have a look as well14:06
rosmaitaack14:07
rosmaitai'll make some time today14:07
abhishekkyebinama, jokke_ will address that on specs, lets move ahead14:07
jokke_abhishekk: yes, only image import. As the image upload is asynchronous, keeping the client hanging there for 3hours waiting glance to upload the image to 10 stores sounds like horrible idea14:07
abhishekkrosmaita, \o/14:07
jokke_sorry, image upload is synchronous, not async14:07
abhishekkjokke_, yes, makes sense14:08
yebinamajokke_ ok14:08
jokke_we would also need to make the image upload to cache the data locally instead of streaming it right through etc. too many things that can go wrong14:09
abhishekkjokke_, right14:09
abhishekkmoving ahead14:10
abhishekk#topic copy existing image in multiple stores14:10
*** openstack changes topic to "copy existing image in multiple stores (Meeting topic: glance)"14:10
abhishekk#link https://review.opendev.org/#/c/694724/214:10
abhishekkThis design is dependent on importing image in multiple stores14:10
abhishekkI have tried to cover all the discussion from the shanghai PTG14:11
abhishekkWould like to have some reviews before I could start with the PoC14:11
abhishekkInitial idea is, I will introduce one new task which will copy the existing image in staging area and link that task to regular import flow14:12
jokke_abhishekk: I've been toying around this already. I'll put this second on the queue right after the import and look how they align easiest way to get them done14:12
abhishekkjokke_, great14:12
abhishekkthat's it, moving to Open discussion14:13
abhishekk#topic Open Discussion14:13
*** openstack changes topic to "Open Discussion (Meeting topic: glance)"14:14
jokke_Just on the copy import job.14:14
abhishekkgo ahead14:14
jokke_The way I've been looking into it is to have it's own flow, first doing some verifications (like having access to all the stores etc.) and then pulling it down (likely) to staging and ...14:15
jokke_yebinama: this nxt part involves you as well14:15
abhishekkjokke_, that is what I have covered in the specs (hopefully I have covered verification part as well)14:16
jokke_we'd like to have that multi store upload loop task in a place where it can be easily importd to the copy job as well, so not integrated part of the current glance-direct flow14:16
*** lkoranda has joined #openstack-meeting-414:16
jokke_so we don't need to duplicate it all over the place14:17
abhishekkmakes sense14:17
yebinamayes sure14:17
jokke_best case scenario would be to import the tasks into those 2 and just inject them to the correct part of the flow if needed14:17
abhishekk+q14:18
abhishekk+114:18
jokke_there is lots of tasks in those flows I've been hoping to do the same but just haven't had time to refactor them14:18
abhishekkI can do that once PoC or yebinama's patch is up for reference14:19
jokke_yebinama: so if you write the task itself in a way that it can handle uploading to 1 store or to multiples, that would be best as then we can just replace the current upload task with that in all of our flows and get the benefit everywhere14:19
yebinamaYep that's what I've done14:20
jokke_yebinama: amazing!!!!14:20
yebinamaI've modified set_data to handle a list of stores14:20
yebinama(or one if using old configuration)14:20
jokke_gr8 ... I'll have a look on your patch after I've reviewed the spec and lets get those moving14:21
yebinamaI think I'll just have to slightly change it14:21
abhishekk++14:21
yebinamasince I set image.locations at the end14:21
yebinamaI will have to update it instead14:21
jokke_yeah, we need to look into that for failure control14:21
abhishekkyebinama, you need to check before every import if image is still available or not14:21
yebinamaabhishekk yes I need to change that to14:22
jokke_yebinama: yeah, that was one thing we were discussing in the PTG, we want to check in between every store that the user did not delete the image in between and we just keep wasting resources14:22
*** lkoranda has quit IRC14:23
yebinamajokke_ if you have time to take a look at the code I've already uploaded, maybe you could say if this feels right or not14:23
jokke_I hopefully have also test environment soon so I can play around how this actually behaves :D14:23
jokke_yebinama: yes I will do14:23
yebinamagreat :)14:23
abhishekkjokke_, o/14:24
yebinamaIt's based ont the first version of the specs but the essential is here14:24
abhishekkanything else on this14:24
jokke_yebinama: cool, np lets get this hammered down asap14:25
jokke_I think I'm covered on this for now14:25
abhishekkcool14:25
abhishekktosky, thank you for your backport patch, stable/stein job is passing now after making it base patch14:25
abhishekk#link https://review.opendev.org/#/c/695176/14:26
toskyoh, I missed the changed topic14:26
abhishekkjokke_, rosmaita kindly have a look and lets get this rolling14:26
toskyI explained everything in my last comment on https://review.opendev.org/#/c/691308/14:26
toskyso I needed another patch to make the usage of python2 explicit (a backport of a jokke_'s patch) and another one to satisfy the request to remove py3514:27
toskyfor a grand total of 5 patches :)14:27
abhishekktosky, yes thank you for following up with infra team14:27
toskyalso, if you can please merge this grenade patch: https://review.opendev.org/#/c/695102/14:27
jokke_tosky: thanks for taking care of that :)14:28
abhishekktosky, ack14:29
rosmaitatox is weird14:29
abhishekk+2, :D14:30
abhishekkcool, anything else14:31
abhishekkwe have 30 minutes left :D14:31
davee_Did I read correctly that a new goal is to rewrite the new developer and PTL get started docs for all projects to make them more consistent and same location for each project?14:31
jokke_ok, so I have + vote on all of them that are left :P14:31
*** tosky_ has joined #openstack-meeting-414:31
jokke_davee_: I'm not sure I heard that there is community goal to have per project contributor and ptl guides, which we do have14:32
*** tosky has quit IRC14:32
jokke_I'm sure if people are interested of moving/rewriting them they can allocate some bodies to do that :P14:33
abhishekk:P14:33
*** tosky_ is now known as tosky14:33
abhishekkshall we wrap early to utilize remaining time?14:34
davee_well if it does drop, I will volunteer to work on that one14:35
jokke_I don't have anything else apart from that cluster awareness approach if we want to discuss that here14:35
abhishekkjokke_, we can14:35
jokke_davee_: feel free to have a look what the community goa is actually after and close any gaps we might have if you have spare time for it14:36
jokke_So I got some BBQ, wine and beer into me at Sunday night with good friend of mine and we were discussing about message queues, as you would in that state14:37
jokke_And we were talking about the problem of having fanout rpc calls that needs to be somehow coordinated and only ran once14:37
abhishekkI could also use some BBQ and beer while working on Copy tasks :P14:39
abhishekkjokke_, any workaround you found?14:39
jokke_So most likely the easiest and smartest way to do this is actually define "dry runs" for those tasks we want to be done on some other node than the one receiving the original request, and when we get responses of either success or failure from the dry run we then use more traditional rpc call to actually request the operation to be performed by only one node14:40
jokke_the dry run doesn't need to be actual non changing run of the function called, but we would need to define those dry run functions that are checking the prerequisites. Like for delete "can this node access all the locations - if yes, respond success; if no respond failure14:42
*** fdegir has quit IRC14:42
jokke_and then the original requestor filters the successes from the response queue, picks one randomly and sends the actual call to that host14:42
abhishekkif that node return failure then we will divert that call to another node?14:43
*** fdegir has joined #openstack-meeting-414:43
jokke_well the node has already checked that it meets the requisites, so if it fails then we need to log error out as something more drastic is going on why we can't fulfil the request we thought we should14:44
abhishekkok14:44
jokke_so at that point we just report failure to the client and log error out of it14:44
*** georgk has quit IRC14:44
abhishekkgot it14:44
*** georgk has joined #openstack-meeting-414:45
abhishekksounds like a good plan14:45
jokke_so for example delete, if the client is connected to node that can't reach all locations, the client will just see the request taking bit longer due to this rpc dance14:45
jokke_we always process the calls locally if we can to optimize the time used14:45
*** Luzi has quit IRC14:46
*** davee_ has quit IRC14:46
abhishekkright14:46
jokke_so ofr end user the difference would be that the calls that previously would just fail, might now take longer but succeed ... the responses etc. will be the same14:46
abhishekkyes14:47
jokke_but by doing this "dry run" we avoid all kind of locking and race condition hell we would have had to tackle otherwise14:48
abhishekkSo we need dry run logic for each plugin/task14:48
jokke_for each call we plan to do over the cluster awareness rpc14:48
abhishekkyes14:48
abhishekkdelete, import, copying and caching (so far)14:49
jokke_which is great in a sense that we don't need to know everything and have it defined. We make the framework to work and we introduce those things based on where we see the need to utilize the cluster awareness14:49
jokke_mhm14:49
abhishekkagree14:50
*** davee_ has joined #openstack-meeting-414:50
abhishekkcool, I will spend some time after milestone 1 on this14:50
jokke_I think we can literally start with the delete as it's the most simple use case and expand from there14:50
abhishekkyou stole my words :D14:50
jokke__BUT_ we need to get the framework to work first ... which is causing the grey hair and hopefully I have debugging environment for it soon14:51
*** rosmaita has quit IRC14:51
*** bobmel has joined #openstack-meeting-414:51
jokke_If this sounds reasonable. I get back to work and modify the approach accordingly14:52
abhishekkjokke_, yes once we have environment it will be pretty easy to debug and analyze14:52
abhishekksounds good to me14:52
jokke_that's all from me unless anyone has questions about this14:52
abhishekkI don't have any, will ping you if something pops up14:53
*** tosky has quit IRC14:54
abhishekkCool, thank you guys, see you next week14:54
jokke_thanks all14:54
yebinamabye14:54
*** yebinama has quit IRC14:54
abhishekk#endmeeting14:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:54
openstackMeeting ended Thu Nov 21 14:54:56 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2019/glance.2019-11-21-14.00.html14:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2019/glance.2019-11-21-14.00.txt14:55
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2019/glance.2019-11-21-14.00.log.html14:55
*** tosky has joined #openstack-meeting-414:57
*** abhishekk has quit IRC14:57
*** tosky has left #openstack-meeting-414:57
*** JamesBenson has joined #openstack-meeting-414:59
*** igordc has joined #openstack-meeting-415:01
*** pcaruana has quit IRC15:02
*** lkoranda has joined #openstack-meeting-415:02
*** rosmaita has joined #openstack-meeting-415:03
*** rosmaita has left #openstack-meeting-415:04
*** lkoranda has quit IRC15:04
*** igordc has quit IRC15:05
*** igordc has joined #openstack-meeting-415:06
*** igordc has quit IRC15:14
*** igordc has joined #openstack-meeting-415:14
*** pcaruana has joined #openstack-meeting-415:20
*** bobmel has quit IRC15:43
*** armstrong_ has joined #openstack-meeting-416:54
*** JamesBen_ has joined #openstack-meeting-416:54
*** JamesBen_ has quit IRC16:55
*** e0ne has quit IRC16:56
*** JamesBenson has quit IRC16:58
*** gcheresh has quit IRC17:26
*** michael-beaver has joined #openstack-meeting-417:50
*** pcaruana has quit IRC17:51
*** pcaruana has joined #openstack-meeting-418:14
*** gmann is now known as gmann_afk18:38
*** pcaruana has quit IRC18:42
*** ralonsoh has quit IRC18:55
*** pcaruana has joined #openstack-meeting-419:06
*** armstrong_ has quit IRC19:41
*** admcleod has quit IRC20:14
*** admcleod has joined #openstack-meeting-420:17
*** e0ne has joined #openstack-meeting-420:36
*** gmann_afk is now known as gmann20:45
*** openstack has joined #openstack-meeting-421:16
*** ChanServ sets mode: +o openstack21:16
*** dave-mccowan has joined #openstack-meeting-421:21
*** pcaruana has quit IRC21:25
*** gcheresh has joined #openstack-meeting-421:32
*** e0ne has quit IRC21:33
*** gcheresh has quit IRC21:38
*** e0ne has joined #openstack-meeting-422:29
*** e0ne has quit IRC22:30
*** slaweq has quit IRC23:17
*** slaweq has joined #openstack-meeting-423:27
*** slaweq has quit IRC23:32
*** slaweq has joined #openstack-meeting-423:35
*** slaweq has quit IRC23:40
*** slaweq has joined #openstack-meeting-423:44
*** slaweq has quit IRC23:48

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