Thursday, 2018-10-25

*** diablo_rojo has quit IRC01:07
*** diablo_rojo has joined #openstack-meeting-401:20
*** hongbin has joined #openstack-meeting-401:21
*** LiangFang has joined #openstack-meeting-401:32
*** iyamahat_ has joined #openstack-meeting-402:00
*** yamahata has quit IRC02:03
*** iyamahat__ has quit IRC02:03
*** iyamahat_ has quit IRC02:08
*** tinwood has quit IRC02:10
*** tinwood has joined #openstack-meeting-402:11
*** bobh has joined #openstack-meeting-402:13
*** psachin has joined #openstack-meeting-402:54
*** iyamahat has joined #openstack-meeting-403:04
*** diablo_rojo has quit IRC03:21
*** bobh has quit IRC03:32
*** yamahata has joined #openstack-meeting-404:01
*** hongbin has quit IRC04:08
*** janki has joined #openstack-meeting-404:12
*** spsurya has joined #openstack-meeting-404:50
*** yboaron_ has joined #openstack-meeting-405:16
*** Luzi has joined #openstack-meeting-406:00
*** slaweq has joined #openstack-meeting-406:35
*** eyalb has joined #openstack-meeting-407:01
*** pcaruana has joined #openstack-meeting-407:04
*** gibi has joined #openstack-meeting-407:23
*** yboaron_ has quit IRC07:43
*** ktibi has joined #openstack-meeting-408:06
*** celebdor has joined #openstack-meeting-408:13
*** ktibi has quit IRC08:21
*** ktibi has joined #openstack-meeting-408:21
*** yboaron_ has joined #openstack-meeting-408:28
*** ktibi has quit IRC08:30
*** yboaron_ has quit IRC08:32
*** yboaron_ has joined #openstack-meeting-408:32
*** e0ne has joined #openstack-meeting-408:42
*** eyalb has quit IRC09:00
*** salmankhan has joined #openstack-meeting-409:08
*** dangtrinhnt_x has joined #openstack-meeting-409:27
*** dangtrinhnt_x_ has joined #openstack-meeting-409:27
*** dangtrinhnt_x has quit IRC09:32
*** psachin has quit IRC09:35
*** psachin has joined #openstack-meeting-409:40
*** LiangFang has quit IRC09:42
*** dangtrinhnt_x_ has quit IRC09:42
*** yamamoto has quit IRC09:44
*** yamamoto has joined #openstack-meeting-409:45
*** yamamoto has quit IRC09:49
*** dangtrinhnt_x has joined #openstack-meeting-410:01
*** psachin has quit IRC10:03
*** psachin has joined #openstack-meeting-410:05
*** dangtrinhnt_x has quit IRC10:06
*** dangtrinhnt_x has joined #openstack-meeting-410:10
*** dangtrinhnt_x has quit IRC10:14
*** yamamoto has joined #openstack-meeting-410:17
*** psachin has quit IRC10:25
*** psachin has joined #openstack-meeting-410:27
*** yamamoto has quit IRC10:34
*** yamamoto has joined #openstack-meeting-410:35
*** dkrol has joined #openstack-meeting-410:37
*** yamamoto has quit IRC10:39
*** pbourke has quit IRC10:48
*** pbourke has joined #openstack-meeting-410:48
*** psachin has quit IRC11:02
*** dangtrinhnt_x has joined #openstack-meeting-411:04
*** dkrol has quit IRC11:07
*** dangtrinhnt_x has quit IRC11:08
*** dave-mccowan has joined #openstack-meeting-411:16
*** yamamoto has joined #openstack-meeting-411:24
*** itzikb has joined #openstack-meeting-411:25
*** thuydang has joined #openstack-meeting-411:26
dangtrinhnt#startmeeting openstack search12:00
openstackMeeting started Thu Oct 25 12:00:54 2018 UTC and is due to finish in 60 minutes.  The chair is dangtrinhnt. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: openstack search)"12:00
openstackThe meeting name has been set to 'openstack_search'12:00
dangtrinhnt#topic patch stein-1 progress checking12:01
*** openstack changes topic to "patch stein-1 progress checking (Meeting topic: openstack search)"12:01
dangtrinhnt #topic Roll Call12:01
dangtrinhntthuydang, hi12:01
thuydanghi trinh12:02
dangtrinhntyingjun, hi12:02
dangtrinhntYingjun said he will join the meeting but looks like he not available yet12:03
dangtrinhntso we just move on12:03
dangtrinhnt#topic Stein-1 progress check12:03
*** openstack changes topic to "Stein-1 progress check (Meeting topic: openstack search)"12:03
*** gibi has quit IRC12:03
dangtrinhntthuydang, how are you?12:03
thuydangI'm fine, but too busy :-)12:04
dangtrinhntyes, I can see that12:04
dangtrinhntthere was noone here last meeting :)12:04
dangtrinhntSo for the Stein-1 milestone12:04
dangtrinhntdo you have anything to add about the use cases we talked about last time?12:05
thuydangunfortunately not12:05
thuydangwhen should it due?12:05
dangtrinhntthis week12:05
dangtrinhnt:D12:05
thuydanghmm, I'm not clear about timeline yet12:06
dangtrinhnthttps://releases.openstack.org/stein/schedule.html12:06
dangtrinhntThis is the schedule12:06
dangtrinhntIt's not required to release at Stein-1 but I think it's a good idea to evaluate our team's work12:07
thuydangyes, I looked at it. So the stein-1 milestone is Apr next year and we want to have searchlight integrated12:07
*** seajay has joined #openstack-meeting-412:07
thuydangah ok, I mistake it with RC-112:08
thuydangI see12:08
dangtrinhntRC-1 is wait ahead :)12:08
dangtrinhntno problem12:08
*** yingjun has joined #openstack-meeting-412:08
dangtrinhntyingjun hi12:08
dangtrinhnt:)12:08
yingjunHi12:09
thuydangI think use-case will be documentation or event blueprint task12:09
thuydangso I missed milestone 112:09
dangtrinhntthuydang, ok, no worries. Just add the plan on our storyboard12:10
yingjunDid I miss something?12:10
dangtrinhntyingjun, no12:10
dangtrinhntwe just started :D12:10
dangtrinhntIt's great to see another core back :)12:10
thuydanghi yingjun12:10
thuydangI tried to setup openstack and searchlight but not successful after 2 weeks12:11
dangtrinhntthuydang, for the use cases, you can add your plan here: https://storyboard.openstack.org/#!/project/openstack/searchlight12:12
dangtrinhntThe recommended way to try Searchlight is via devstack12:12
thuydangI wanted to see searchlight in action so I can identify some connection points with use-cases12:12
thuydangdevstack is probably the recommended way. I try with openstack ansible though12:13
dangtrinhntWhen working with Ansible, you have to deal with compatibility issues of the services while devstack doing that for you with the built-in constraints12:14
dangtrinhntok, so, you can give me your configuration later in the openstack-searchlight channel to have a look12:15
dangtrinhntyingjun, how are you?12:15
thuydangI see the getting start document of other openstack proejct also, but mostly they say "install devstack" :-)12:15
thuydangso I think we can have a more detailed document for helping new contributor12:16
*** gibi has joined #openstack-meeting-412:16
yingjunKolla-ansible is also supported,it's pretty esay to setup12:16
dangtrinhntthuydang, :) it's great, I will put a note about it.12:16
dangtrinhntyingjun, if you have experience with it, could you please add some docs? :)12:17
thuydangsome pointers are already helpful. I kind of lost in openstack eco12:17
dangtrinhntthuydang, sure, I will put some next week.12:18
thuydang2 years ago the most complicated part was only neutron  :-)12:18
dangtrinhntok, let's get back to the Stein-1 topic12:18
dangtrinhnt:)12:18
dangtrinhntyingjun, you can have a look at our vPTG notes: https://etherpad.openstack.org/p/searchlight-stein-ptg12:19
yingjunOk12:19
dangtrinhntWe about to do these in Stein-112:19
dangtrinhnt  - ES 5.x support    - Fix bugs    - Versioned Nova notifications    - tox use py3 by default    - Docs clean up12:20
dangtrinhntNow only  the "Version Nova notifications" patch left12:20
dangtrinhntyingjun, if you have sometime this week, before Sunday, please review this: https://review.openstack.org/#/c/453352/12:21
dangtrinhntI will do a release on Monday (a little bit late)12:21
dangtrinhntI know you have been a great contributor of Searchlight and really love to have you back12:22
dangtrinhntSearchlight needs you and other contributors12:22
yingjunOk, will do12:22
dangtrinhntthanks12:22
dangtrinhntok, looks like we are on track now :) yay12:24
thuydangthe use-case is planned for stein-2 as I see in vPTG12:25
thuydang:-)12:25
dangtrinhntyes12:25
dangtrinhnt:)12:25
thuydangby that time I'm also targeting some network management survey for my research, good timing12:26
dangtrinhntawesome, thuydang12:26
dangtrinhntjust want to look ahead :)12:26
*** pcaruana has quit IRC12:26
dangtrinhnt#topic Stein-212:26
*** openstack changes topic to "Stein-2 (Meeting topic: openstack search)"12:26
dangtrinhntBesides the use cases, anything else you want to add? yingjun, thuydang?12:27
dangtrinhntyingjun, you must have more experience than us12:27
dangtrinhnt:)12:27
thuydangI would be great if the installation guide is complete by then12:28
dangtrinhntawesome12:29
thuydangI will join some tutorial session in the Openstack summit, especially OS ansible, and probably will compose a developer guide12:29
dangtrinhntI will put it as the 1st priority next week12:29
dangtrinhntCool, thuydang, could you please write some report about that for the team?12:29
thuydangsure12:30
*** janki has quit IRC12:31
dangtrinhntgreat thanks12:31
*** janki has joined #openstack-meeting-412:31
*** liuyulong has quit IRC12:31
yingjunAll good, nothing from me, hope i can still catch up for missing about half year12:32
*** yboaron_ has quit IRC12:32
dangtrinhntyingjun, a big thanks from me. I learn a lot from your patches :D12:33
*** yboaron_ has joined #openstack-meeting-412:33
thuydangCan you explain a bit about release process? do we have to propose some technical changes in each milestone and report to openstack release team?12:33
dangtrinhntno, thuydang12:34
dangtrinhntit depends on us12:34
dangtrinhntwe as a team will decide which ones will be released at each milestone12:35
dangtrinhntBut according to the discussion of the Release management team, we don't have to release at each milestone12:35
dangtrinhntonly the RCs is required12:35
thuydangok, so just make sure searchlight is stable to be included in the next OS version12:36
dangtrinhntthuydang, correct12:36
dangtrinhntyingjun, I'm trying to write a weekly report of what going on with Searchlight here: https://www.dangtrinh.com/search/label/Searchlight12:36
dangtrinhntyou can have a look12:36
thuydangthat's great dangtrinhnt, very helpful12:37
dangtrinhnt:D12:37
yingjunnice12:37
dangtrinhntalso, I'm trying to attract more contributors12:37
dangtrinhntlast week I attended the OS Korea User Group12:38
dangtrinhnthopefully our team will have more people :D12:38
dangtrinhntok, anything you want to talk about this time? thuydang, yingjun12:39
thuydangthat's all from my side12:39
*** pcaruana has joined #openstack-meeting-412:39
dangtrinhntyingjun12:40
yingjunno12:41
dangtrinhntok12:41
dangtrinhntSo, let's end the meeting now. Talk to you guys at the #openstack-searchlight channel12:41
dangtrinhntThank for joining the meeting today :)12:42
dangtrinhnt#endmeeting12:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"12:42
openstackMeeting ended Thu Oct 25 12:42:11 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2018/openstack_search.2018-10-25-12.00.html12:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2018/openstack_search.2018-10-25-12.00.txt12:42
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2018/openstack_search.2018-10-25-12.00.log.html12:42
*** thuydang has left #openstack-meeting-412:43
*** caboucha has joined #openstack-meeting-412:44
*** janki has quit IRC12:56
*** bnemec has joined #openstack-meeting-412:56
*** yamamoto has quit IRC12:56
*** yamamoto has joined #openstack-meeting-412:56
*** itzikb has quit IRC12:57
*** itzikb has joined #openstack-meeting-413:01
*** bobh has joined #openstack-meeting-413:02
*** itzikb is now known as itzikb|afk13:04
*** yboaron_ has quit IRC13:04
*** yboaron_ has joined #openstack-meeting-413:04
*** liuyulong has joined #openstack-meeting-413:08
*** pliu has quit IRC13:15
*** abhishekk has joined #openstack-meeting-413:17
*** rnoriega has quit IRC13:31
*** yamamoto has quit IRC13:31
*** yamamoto has joined #openstack-meeting-413:31
*** d0ugal has quit IRC13:33
*** d0ugal has joined #openstack-meeting-413:34
*** pcaruana has quit IRC13:37
*** rnoriega has joined #openstack-meeting-413:38
*** mhen has joined #openstack-meeting-413:41
*** mjturek has joined #openstack-meeting-413:48
*** Liang__ has joined #openstack-meeting-413:48
*** d0ugal has quit IRC13:49
*** Liang__ is now known as LiangFang13:49
*** itzikb|afk has quit IRC13:56
*** Luzi has quit IRC13:57
*** mjturek has quit IRC13:59
LiangFanghi14:00
abhishekkhi14:01
*** rosmaita has joined #openstack-meeting-414:01
jokke_#startmeeting glance14:01
openstackMeeting started Thu Oct 25 14:01:38 2018 UTC and is due to finish in 60 minutes.  The chair is jokke_. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: glance)"14:01
openstackThe meeting name has been set to 'glance'14:01
abhishekko/14:01
jokke_#topic roll-call14:01
*** openstack changes topic to "roll-call (Meeting topic: glance)"14:01
jokke_#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:01
jokke_o/14:01
mheno/14:01
LiangFango/14:02
rosmaitao/14:02
jokke_#topic updates14:02
*** openstack changes topic to "updates (Meeting topic: glance)"14:02
jokke_First of all, we have S-1 deadline today14:02
rosmaitathat snuck up quickly14:03
jokke_there shouldn't be anything burning waiting to be merged but now is the last moments to yell14:03
jokke_rosmaita: indeed14:03
*** smcginnis has joined #openstack-meeting-414:03
abhishekkI think we should have my functional tests timeout patch in14:03
rosmaitaalso, this would be the last chance to revert the image status change from queued -> active from PATCH add location14:04
jokke_rosmaita: you mean replace?14:04
rosmaitasorry, you are correct, replace14:05
jokke_yes so are we going to keep that or revert it?14:05
rosmaitai am in favor of keeping it14:06
abhishekkme too14:06
jokke_I still think it's unnecessary api change14:06
rosmaitai don't see it as an api change, i see it as a bugfix14:07
smcginnisI don't have enough knowledge there to vote one way or the other.14:07
*** mjturek has joined #openstack-meeting-414:07
jokke_but but taken into account where it is, I really don't have interest to fight about it14:07
rosmaitayeah, pretty low traffic in that part of the api14:08
jokke_need to bump the api version for that 'though14:08
rosmaitanot for S-1, though, i wouldn't think14:08
jokke_you recon it's nuf to do it at the end of the cycle?14:09
abhishekkgenerally we do it at the end of the cycle, right?14:09
rosmaitai really don't think it's necessary for this at all, but i think that's the usual practice, end of cycle14:09
rosmaitano one has complained before14:10
rosmaitaor at least, i haven't payed attention if they have :)14:10
jokke_k, I guess we should be good to go then with S-114:10
jokke_next thing is, Summit is approaching, fast14:10
rosmaitaabhishekk: do you have your func test update patch link handy?14:10
abhishekk(I am talking about this, https://review.openstack.org/#/c/608856/)14:10
jokke_which means spec freeze is approaching fast14:11
abhishekkrosmaita, ^^14:11
jokke_so lets get them specs reviewed and merged what we are going to accept14:12
*** JamesBenson has joined #openstack-meeting-414:12
jokke_which gives us nice brindge to the next topic14:12
jokke_bridge14:12
jokke_#topic validation_data in image locations patch call14:12
*** openstack changes topic to "validation_data in image locations patch call (Meeting topic: glance)"14:12
jokke_imacdonn has been chasing this actively and has new revision out14:13
abhishekknew revision looks good to me, does it going to add new discovery call?14:13
rosmaitaabhishekk: it doesn't mention that, i think the idea is rely on the local operator docs for now14:14
abhishekkrosmaita, ack14:14
rosmaitasince the admin has to allow use of locations anyway, should not be a big deal14:15
jokke_we shoud definitely look to include these details when expanding the discovery endpoint14:15
rosmaitai mean the admin/operator14:15
rosmaitajokke_: ++14:15
*** hongbin has joined #openstack-meeting-414:15
jokke_that said I don't think this will be widely used due to the fact that it opens such a can of worms14:16
rosmaitaalso ++14:16
abhishekkso it will just check it against config set in glance-api.conf and if does not match then returns 40914:16
abhishekkagree14:16
rosmaitaright14:16
abhishekkgot it14:17
jokke_ok, cool14:17
jokke_lets read it through once more with good thought but I think it's getting there (again)14:17
jokke_next up is showing store IDs in image listing14:18
jokke_#topic show store ID in image listing with -vv14:18
*** openstack changes topic to "show store ID in image listing with -vv (Meeting topic: glance)"14:18
jokke_LiangFang: you're up14:18
LiangFanghi erno14:18
LiangFangI prepared the spec, and at this moment, the conclution is to add --include-stores option to image-list14:19
LiangFangopenstack client just have -long, not option like -vv14:19
LiangFangso try to use --include-stores14:20
LiangFangerno, are you agree with this?14:20
rosmaitaLiangFang: are you thinking the --include-stores will work with both "regular" image-list and also image-list -v calls?14:21
jokke_so are you proposing thing change to python-glanceclint or openstackclient?14:21
LiangFangthe change is in python-glanceclient14:22
LiangFangglance -v image-list --include-stores14:22
LiangFangglance image-list --include-stores14:22
LiangFangall can work14:22
rosmaitaexcellent14:22
smcginnisjokke_: osc comes into play from a comment I made about it not really fitting with the standardization they are doing there.14:23
jokke_ok, I have one concern which might be just language thing in the spec14:23
smcginnisI think this new option fits better and is probably easier for a user to discover and use.14:23
rosmaitai think smcginnis had a good point about that14:23
jokke_You're mentioning listing store type, I think that needs to change to store ID (and use those, "fast", "cheap", "reliable" as example) ... we are not going to leak the backend information to the user unless that's how the operator decides to set it14:24
LiangFangOK14:25
jokke_so we're not listing the store type, but it's ID14:25
smcginnisjokke_: Good point.14:25
LiangFangI will update14:25
jokke_other than that, the proposal looks good to me14:25
rosmaitagood catch, i missed that14:25
LiangFangthanks14:25
LiangFangand I also updated the related code14:26
LiangFangand the review is:https://review.openstack.org/#/c/605014/14:26
jokke_thanks, anything else about this?14:27
LiangFangno more14:27
LiangFangthanks14:27
jokke_#topic image size to prevent backend resizes14:27
*** openstack changes topic to "image size to prevent backend resizes (Meeting topic: glance)"14:27
jokke_this is yours as well14:27
LiangFangabout this, last week you mentioned we should consider other component as well, not only cinder14:28
jokke_and first of all I have to say this keeps slipping on me, so no I haven't got to test it yet :(14:28
LiangFangthat's fine:)14:28
jokke_yes so we need to make sure that this addresses any applicable backends (if others than cinder is affected)14:29
LiangFangconsidering this, I think solution 1 is better14:29
jokke_#link https://review.openstack.org/#/c/608400/14:29
LiangFangsolution 1 is:14:29
jokke_^^ is the spec14:29
LiangFangcinder calculate the image size14:30
LiangFangpython-glanceclient: convey the image size via http header14:30
LiangFangglance: extract the image size in request deserialize phase14:30
LiangFangSean mentioned previously that, move the work did in cinder to python-glanceclient14:31
LiangFanglet python-glanceclient to calculate the image size14:32
LiangFangI take a look again this week, seems this is workable14:32
rosmaitaQuick question: the point of this is to provide info that the glance backend driver can use in allocating how much space to store the image, but the 'size' in glance will still be computed as it is now?14:32
abhishekkhow this will fit in case of web-download import method?14:34
LiangFangin current code, size is returned by backend when it finished all the data upload14:34
jokke_So iirc we can't access the request body before all the data has been uploaded to glance (this was either webop or wsgi thing). Whic means that we should know the size before we upload it to backend14:34
LiangFangabhishekk: let me take a think14:35
jokke_also it's definitely the case with image import14:35
abhishekkLiangFang, yes14:35
jokke_so I don't think we should offload the work to glanceclient specially as there is cases when glanceclient can't determine the size before it's iterated the whole image14:36
jokke_those being if the data is streamed to the client from command line or the fd is socket14:37
LiangFangagree14:37
LiangFangso should let the user of glanceclient to give the size14:37
jokke_and these were the reasons why the decision was made not to send the size from client in v2 like it was done in v114:38
jokke_we should let glance-api to calculate the data before upload to the backend14:38
smcginnisAre there any DoS issues with user supplied size input to glanceclient?14:38
jokke_and make sure our upload is not streaming it from local disk in very small chunks14:39
jokke_smcginnis: not really, there is the max image size parameter that eliminates any crazy calls14:40
smcginnisOK, good.14:40
jokke_but yet I think we have all the needed data in the api before we do the upload call, it's just not utilized14:40
LiangFangI seems glance-api don't know the size14:41
jokke_so we update the image size based on the info we got from the backend instead of telling the backend "We have this much data we're dumping into you"14:42
LiangFangI did experiment with ceph as backend, if give size, it can save 30% uploading time14:42
jokke_yeah, I thought that might be the case14:43
jokke_one of the problems we have and this is hitting the edge usecases hard is that we always thought the backends are somewhere close by. We're using extremely small chunks when doing backend transactions. like 4k which is even small for disk writes14:44
LiangFangthe chunk size using by ceph is 8M14:45
LiangFanglvm is 64K14:45
rosmaitaso really, for this purpose, we don't need to know the image size exactly,14:45
jokke_yeah, well with ceph we use rdb which takes care of it14:46
jokke_when ever we chnk it ourselves it's very very small14:46
LiangFangsorry erno, I may not catched your point14:48
jokke_rosmaita: well I'm not sure how cinder behaves if you try to shrink the volume ... the problem is atm, that when we don't know the size, behind the scenes we end up calling cinder resize to expand for each chunk we're sending14:48
jokke_same happens with other backends that actually allocate the space14:48
smcginnisCinder will never shrink, only extend.14:48
jokke_yeah, so we can't just estimate and shrink back to size after we get to the end of the data14:49
abhishekkyes, downsize is not allowed14:49
*** yingjun has quit IRC14:49
jokke_ok, we're running out of time. Lets keep investigating this14:50
LiangFangOK14:50
jokke_#topic python-glanceclient release14:50
*** openstack changes topic to "python-glanceclient release (Meeting topic: glance)"14:50
jokke_rosmaita: the stage is yours14:50
rosmaitaI send something to the ML about this14:51
rosmaita#link http://lists.openstack.org/pipermail/openstack-dev/2018-October/135902.html14:51
rosmaitamaster contains the multihash validation code14:52
abhishekkat the moment 2nd option looks more convenient14:52
rosmaitayes, and smcginnis already has a patch up for that14:53
rosmaitaand now that we've decided that iain's validation_data will use the configured hash algo, i'm not so worried14:53
smcginnisWe can hold the release patch or update it. There's also one up for glance_store.14:54
rosmaitaok, this looked like it could be an issue at the end of last week, not so much now.14:54
rosmaitalet's go with option 214:55
*** bobh has quit IRC14:55
jokke_so we don't have the multihash validation in rocky client and we never ended up backporting that to rocky branch14:55
rosmaitajokke_: correct14:55
jokke_ok, crap14:56
jokke_I thought it had been done, just not tagged14:56
rosmaitagive me a minute to check, pretty sure i;m right though14:57
jokke_just looked the rocky branch, didn't see it there14:57
rosmaitayeah, not there14:58
jokke_so yeah, I guess we need to do the same trickstery we did at the start of rocky14:58
jokke_which is backport, cut 2.13.0 from the stable branch and then 2.14 from master before towards end of the cycle cutting 3.0.014:59
abhishekklast minute to go14:59
jokke_that way we get it for those who insists using the client from rocky branch on their rocky deployment14:59
rosmaitaabhishekk: are you handling glance s-1 release, or do you want me to do it?15:00
jokke_yup, we're out of time, lets wrap this client plan together in #os-glance15:00
jokke_#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Thu Oct 25 15:00:33 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
abhishekkrosmaita, you can15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2018/glance.2018-10-25-14.01.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2018/glance.2018-10-25-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2018/glance.2018-10-25-14.01.log.html15:00
jokke_thanks all15:00
rosmaitaabhishekk: ok15:00
smcginnisrosmaita, jokke_: That makes sense. Thanks!15:00
abhishekkrosmaita, I will catchup from s-215:01
*** smcginnis has left #openstack-meeting-415:01
*** Luzi has joined #openstack-meeting-415:01
*** abhishekk has quit IRC15:05
*** yamamoto has quit IRC15:09
*** yamamoto has joined #openstack-meeting-415:10
*** yamamoto has quit IRC15:16
*** Luzi has quit IRC15:26
*** bobh has joined #openstack-meeting-415:29
*** mjturek has quit IRC15:34
*** bobh has quit IRC15:35
*** yboaron_ has quit IRC15:36
*** bobh has joined #openstack-meeting-415:39
*** mjturek has joined #openstack-meeting-415:40
*** LiangFang has quit IRC15:46
*** yamamoto has joined #openstack-meeting-415:50
*** celebdor has quit IRC15:51
*** liuyulong is now known as liuyulong|away15:54
*** e0ne has quit IRC15:59
*** yamamoto has quit IRC16:26
*** yamamoto has joined #openstack-meeting-416:26
*** salmankhan has quit IRC16:34
*** mjturek has quit IRC16:40
*** imacdonn has quit IRC16:42
*** iyamahat has quit IRC16:42
*** imacdonn has joined #openstack-meeting-416:43
*** mjturek has joined #openstack-meeting-416:50
*** yamahata has quit IRC16:52
*** pcaruana has joined #openstack-meeting-417:03
*** iyamahat has joined #openstack-meeting-417:21
*** yamahata has joined #openstack-meeting-417:24
*** diablo_rojo has joined #openstack-meeting-417:26
*** mjturek has quit IRC17:36
*** JamesBenson has quit IRC18:05
*** JamesBenson has joined #openstack-meeting-418:06
*** rosmaita has left #openstack-meeting-418:12
*** salmankhan has joined #openstack-meeting-418:16
*** salmankhan has quit IRC18:20
*** bnemec has quit IRC18:29
*** bobh has quit IRC18:40
*** njohnston has quit IRC19:07
*** njohnston has joined #openstack-meeting-419:09
*** bobh has joined #openstack-meeting-419:15
*** bobh has quit IRC19:20
*** bobh has joined #openstack-meeting-419:31
*** irclogbot_1 has joined #openstack-meeting-420:02
*** irclogbot_1 has quit IRC20:22
*** imacdonn has quit IRC20:31
*** caboucha has quit IRC20:49
*** bobh has quit IRC21:16
*** irclogbot_1 has joined #openstack-meeting-421:16
*** iyamahat_ has joined #openstack-meeting-421:40
*** iyamahat has quit IRC21:42
*** bobh has joined #openstack-meeting-421:51
*** bobh has quit IRC21:56
*** JamesBenson has quit IRC22:01
*** seajay has quit IRC22:13
*** njohnston has quit IRC22:36
*** njohnston has joined #openstack-meeting-422:36
*** yamamoto has quit IRC23:01
*** yamamoto has joined #openstack-meeting-423:01
*** yamamoto has quit IRC23:06
*** hongbin has quit IRC23:24
*** yamamoto has joined #openstack-meeting-423:44

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