Thursday, 2018-09-27

*** mjturek has quit IRC00:03
*** slaweq has joined #openstack-meeting-400:11
*** slaweq has quit IRC00:15
*** seajay has joined #openstack-meeting-400:18
*** seajay has quit IRC00:35
*** iyamahat has quit IRC01:19
*** yamahata has quit IRC01:19
*** hongbin has joined #openstack-meeting-401:19
*** liuyulong has joined #openstack-meeting-401:32
*** iyamahat has joined #openstack-meeting-401:44
*** diablo_rojo has quit IRC02:33
*** liuyulong has quit IRC02:48
*** psachin has joined #openstack-meeting-402:48
*** markvoelker has joined #openstack-meeting-402:50
*** slaweq has joined #openstack-meeting-403:11
*** slaweq has quit IRC03:15
*** dave-mccowan has quit IRC03:46
*** hongbin has quit IRC03:47
*** haleyb has quit IRC04:07
*** dave-mccowan has joined #openstack-meeting-404:49
*** macza has joined #openstack-meeting-405:03
*** macza has quit IRC05:08
*** slaweq has joined #openstack-meeting-405:11
*** slaweq has quit IRC05:15
*** mtreinish has quit IRC05:37
*** mtreinish has joined #openstack-meeting-405:38
*** bnemec has quit IRC05:39
*** mtreinish has quit IRC05:56
*** mtreinish has joined #openstack-meeting-405:59
*** slaweq has joined #openstack-meeting-406:11
*** njohnston has quit IRC06:14
*** slaweq has quit IRC06:15
*** njohnston has joined #openstack-meeting-406:15
*** slaweq has joined #openstack-meeting-406:23
*** pcaruana has joined #openstack-meeting-406:33
*** diablo_rojo has joined #openstack-meeting-406:55
*** Luzi has joined #openstack-meeting-407:06
*** diablo_rojo has quit IRC07:27
*** celebdor has joined #openstack-meeting-407:32
*** gkadam has joined #openstack-meeting-407:36
*** e0ne has joined #openstack-meeting-408:12
*** lkoranda has quit IRC08:12
*** iyamahat has quit IRC08:19
*** alexchadin has joined #openstack-meeting-408:21
*** janki has joined #openstack-meeting-408:27
*** gkadam is now known as gkadam-afk08:52
*** gkadam-afk is now known as gkadam08:59
*** janki has quit IRC09:13
*** salmankhan has joined #openstack-meeting-409:16
*** pbourke has quit IRC09:24
*** pbourke has joined #openstack-meeting-409:24
*** alexchadin has quit IRC09:42
*** yamamoto has quit IRC10:17
*** yamamoto has joined #openstack-meeting-410:25
*** yamamoto has quit IRC10:46
*** yamamoto has joined #openstack-meeting-410:48
*** yamamoto has quit IRC10:49
*** macza has joined #openstack-meeting-411:11
*** macza has quit IRC11:15
*** alexchadin has joined #openstack-meeting-411:22
*** yamamoto has joined #openstack-meeting-411:23
*** pcaruana has quit IRC11:50
*** salmankhan has quit IRC12:08
*** seajay has joined #openstack-meeting-412:08
*** e0ne has quit IRC12:09
*** e0ne has joined #openstack-meeting-412:09
*** yamamoto has quit IRC12:14
*** yamamoto has joined #openstack-meeting-412:16
*** pcaruana has joined #openstack-meeting-412:39
*** alexchadin has quit IRC12:43
*** bobh has joined #openstack-meeting-412:59
*** haleyb has joined #openstack-meeting-413:04
*** liuyulong has joined #openstack-meeting-413:15
*** njohnston has quit IRC13:15
*** njohnston has joined #openstack-meeting-413:16
*** bnemec has joined #openstack-meeting-413:18
*** mjturek has joined #openstack-meeting-413:20
*** e0ne has quit IRC13:22
*** rosmaita has joined #openstack-meeting-413:23
*** rosmaita has left #openstack-meeting-413:25
*** rosmaita has joined #openstack-meeting-413:26
*** e0ne has joined #openstack-meeting-413:26
*** yamamoto has quit IRC13:31
*** yamamoto has joined #openstack-meeting-413:31
*** abhishekk has joined #openstack-meeting-413:32
*** psachin has quit IRC13:36
*** iyamahat has joined #openstack-meeting-413:36
*** salmankhan has joined #openstack-meeting-413:45
*** mhen has joined #openstack-meeting-413:51
jokke_#startmeeting glance14:00
openstackMeeting started Thu Sep 27 14:00:01 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:00
*** openstack changes topic to "roll-call (Meeting topic: glance)"14:00
jokke_o/14:00
Luzio/14:00
mheno/14:01
rosmaitao/14:01
abhishekko/14:03
jokke_#topic updates14:03
*** openstack changes topic to "updates (Meeting topic: glance)"14:03
*** JamesBenson has joined #openstack-meeting-414:03
jokke_First of all the periodic jobs: there was keystone tips failure, will need to keep eye on that and if it keeps failing see what is breaking it. Others are green14:05
jokke_Based on the PTG we have quite a bit calmer cycle feature wise coming but reminder that the spec proposals will stay open until after Berlin Summit14:06
*** LiangFang has joined #openstack-meeting-414:07
jokke_I have yet to update the store driver maintainer page so will try to get that done by tomorrow eob14:07
abhishekkack14:08
jokke_I think that's pretty much it from quick updates from me14:08
jokke_I did merge bunch of the zuul stuff that was sent in scripted14:09
jokke_so if you think there was something that got messed up in the job definitions have a look and blame me :)14:10
LiangFangack14:11
jokke_#topic patch call to to replace locations14:11
*** openstack changes topic to "patch call to to replace locations (Meeting topic: glance)"14:11
jokke_so we're back to imcdonns favorite child14:12
jokke_which is also on my still to do list for this week. So I will have mail going to the ops list before next week checking if anyone else is using that API14:12
abhishekk ok14:13
rosmaitai don't see any reason why it makes sense for add /0 to have different behavior from replace {}14:13
jokke_But in short, so there is couple of mistakes in Iain's statements to the dev mailing list14:14
jokke_first, that after replacing the empty list there is nothing one can do to get the image out of queued, that's not trye, all the mechanisms that works before the replace call is made will still work after14:15
jokke_so one doesn't just need to delete the image record14:15
rosmaitajokke_: what's the workaround?14:15
jokke_rosmaita: so like it has always been patch call to add location does the status change, as does image upload and image import14:17
rosmaitabut i mean in the situation where you just did the replace and are now in queued, what would you do?14:18
jokke_and this is where me and Iain disagree ... I did agree on his initial statement that it's a bug that if you use the locations API there is _no_ way to activate the image as he stated when he came to us14:18
rosmaitaok, so the workaround is to add /0 in the first place14:18
jokke_rosmaita: you do add and then you either delete or replace to get to single source of truth14:19
jokke_rosmaita: no, that's the orginal idea how that API should work14:19
jokke_you don't replace unless you're actually in need to replace something :)14:19
jokke_I just thing no-one thought that one would want to start by replace and just built the whole final locations list by hand14:20
rosmaitasort of ... but it is legitimate to replace an empty list with a populated list14:20
rosmaitaanyway, i didn't realize there was the workaround14:21
rosmaita(though i still think the replace situation is a bug!)14:21
rosmaitabut the existence of a workaround does change the backport situation, i think14:22
jokke_so my biggest problem with this is that we changed iirc deprecated API that has been stable for years based on bug that was filed on assumption "There is no way to do this at all"14:22
rosmaitawell, i think a key thing is that we want consistent behavior in the api, and add /0 and replace {} should behave the same, i think14:24
jokke_and yes if I was designing that API from scratch I definitely would take this use case in consideration and make sure the API behaves well, now the problem is really the API stability contract14:24
rosmaitai guess the key thing at this point is that we need a clear direction for how we will handle this.  i understand both your and ian's frustration, but i personally don't know how to resolve this14:26
*** smcginnis has joined #openstack-meeting-414:26
jokke_but I'm kind of willing to let this slip in if there is no outcry us breaking someone else's process by us changing this. Is it valid bug for backporting within our stable rules, I don't think so but we can ask the rest of the stable folks after we make sure it's ok to keep in master14:27
smcginnisSorry, I'm on the road and missed it. What's the stable change?14:28
jokke_that is kind of where I'm at now14:28
jokke_smcginnis: we're talking about the patch call replace locations to make image active14:28
smcginnisAh, OK. Thanks!14:29
*** iyamahat has quit IRC14:30
*** yamamoto has quit IRC14:32
jokke_And just that ye all are on the same page, I have no intention to make a rush call on this. We kind of need to make the call if we're reverting the patch on master by milestone 1 as at that point it will be in tagged release but what comes to backporting it into Rocky and perhaps before, I need to know that we're not on war path with everyone else to make one user able to use their preferred ap14:33
jokke_i call instead of the one that just works14:33
*** yamamoto has joined #openstack-meeting-414:33
*** yamamoto has quit IRC14:33
*** yamamoto has joined #openstack-meeting-414:34
*** abhishekk has quit IRC14:34
jokke_IMO we have been in enough wars for changing our stable APIs before ;)14:34
*** abhishekk has joined #openstack-meeting-414:34
rosmaitaspeaking of which ... i take it you didn't like my proposal to make 'private' the default visibility?14:35
jokke_rosmaita: actually we did ... IIRC that was what was originally agreed and the feedback has been it would make lots of users happier14:36
rosmaitaoh wow, that's good to hear -- i may pick that up14:37
rosmaitai have like a 3 day window to do some glance work14:37
jokke_:)14:37
jokke_ok, if nothing else on this lets move on14:37
abhishekk great, then please review my patches14:38
*** yamamoto has quit IRC14:38
rosmaitaone thing14:38
jokke_shoot14:38
rosmaitahttps://etherpad.openstack.org/p/glance-imacdonn-relnote14:38
rosmaitathis was the description of the relnote for the replace change i wrote up14:38
jokke_#link https://etherpad.openstack.org/p/glance-imacdonn-relnote14:38
rosmaitai think it may be slightly inaccurate14:38
rosmaitaanyway, just pointing it out in case it will be helpful to advance the discussion14:39
smcginnisThat looks good to me.14:39
jokke_yeah, that's based on the original assumption that there is no way, in which case this change would have made sense14:40
rosmaitaalso, i speak of "adding" instead of "replace"14:40
jokke_yup14:40
abhishekk+114:40
rosmaitawhich is sort of the same thing, but inaccurate in this context14:40
jokke_and the add already does behave like the reno proposal claims to change it to14:41
jokke_;)14:41
rosmaitai must admit, i misunderstood the situation14:41
jokke_so did I initially14:41
jokke_that's why I was like "Yes that does sound like nasty bug"14:42
rosmaitaok, in one sense we don't want to rush, but on the other, we do need to get it out of master pronto if we don't want to make this change14:42
rosmaitaall i did was verify the bug, didn't think of trying a workaround14:42
jokke_and then I started to look the code and wen't "WWaait!" and the discussion was left there when I went to PTO and meanwhile the change was merged ;)14:42
*** yamamoto has joined #openstack-meeting-414:43
jokke_rosmaita: like said I'm willing to let this slip if there is no outcry of us changing it from the API folks and operators. Because it does make sense in logical way14:44
rosmaita++14:44
jokke_if it breaks anyone, I rather revert it and tell Iain "Sorry but you need to use the api call that already does it for you"14:44
jokke_ok lets move on before we run out of time14:45
jokke_#topic image encryption proposal14:45
*** openstack changes topic to "image encryption proposal (Meeting topic: glance)"14:45
mhenhello all :)14:45
Luzihi :)14:45
jokke_hey!14:45
mhenwe'd like to propose the introduction of an encrypted image format in OpenStack14:45
mhenwe have written a spec for it and have a basic implementation ready which we'd like to contribute14:45
mhenbased on the code alone Glance would be the least affected project (mostly Nova, Cinder and OSC are involved)14:46
jokke_could you link the spec for us, please?14:46
mhenbut we figured you are responsible for the image concept in OpenStack anyhow14:46
mhenso since the old cross-project contribution workflow is outdated, we're currently wondering where the best place to put the spec would be, actually14:46
jokke_oh, Ok14:46
mhenany suggestions?14:47
jokke_so that's a good question. I'd say you likely need to write 4 specs to all involved projects describing what you are trying solve and how it affects that project14:47
jokke_and I don't mean 4 specs to each repo14:48
jokke_but a spec to those 4 projects you need to change to make this happen14:48
rosmaitamhen: quick question, you mean a new value for the disk_format or container_format properties?14:48
mhenrosmaita, exactly, 'container_format' specifically14:48
rosmaitamhen: i wonder whether a new property would be better14:49
smcginnisThinking from the Cinder side - I would expect the changes to not be too disruptive. So I think if you came to Cinder with changes saying they are for "the new encryption format from Glance" that we can probably just have a blueprint, not a full spec.14:49
rosmaitaothewise, you might have encrypted_gzip, encrypted_raw, etc14:49
smcginnisI guess it really depends on the extent of the changes needed.14:49
Luzijokke_ but wouldn't it be better, if people from all involved project could discuss this in one repo?14:50
smcginnisI woud start with describing your goal with a ML post.14:50
smcginnisThat woud be the best forum for cross-project discussion.14:50
jokke_Luzi: yes I do agree, but like mhen said the cross project specs were sacked :(14:50
jokke_what smcginnis just said, yes!14:51
mhenso we could use appropriate excerpts of the spec and post in on the ML?14:51
mhen*it14:51
rosmaitamhen: yes, that would be the best way to get started14:51
mhenthat sounds reasonable, thanks for the suggestion!14:51
jokke_mhen: just quick question as if you just were thinking of new container_format where are you planning to store the secrets?14:52
smcginnisI think so. Expain your use case(s), describe the changes you plan to make, and get input from affected projects. And have the opportunity for other interested parties to get involved too.14:52
mhenjokke_, key manager (e.g. Barbican) for now14:52
*** yamamoto has quit IRC14:52
mhenwe have other mechanisms in the work but they are currently not ready for contribution14:52
jokke_mhen: ok, in that case you would likely want to have reserved property where to store that in glance as well14:53
mhenjokke_, that's what our implementation currently does basically14:53
rosmaitamhen: have you looked at how we handle the digital signatures?14:53
mhenwe did, yes14:53
rosmaitaok, cool14:53
jokke_one thing we have learned is that as glance has freeform properties for images, users really hates everyone using them as they wish ;)14:54
mhenwe contributed image signature generation for OSC recently14:54
rosmaitanice14:54
jokke_cool. Then I think the easiest for you guys get on this is like smcginnis proposed ML thread, get everyone on board and after that to file the specs or blueprints to affected projects14:55
mhenregarding the ML thing: iirc, there's a new combined ML coming up. It's still fine to post on the current openstack-dev?14:56
jokke_for something like this we will want spec to glance-specs repo. It's even more for ducumenting the future change and book keeping than us just wanting to fight the design14:56
smcginnisYes, no changes have been made yet, so posting to openstack-dev would be best.14:56
* rosmaita has completely missed the discussion about a new ML14:56
* jokke_ too14:57
smcginnisrosmaita: You've been busy. ;)14:57
mhenjokke_, we figured as much, that's why we came here first :)14:57
jokke_mhen: gr814:57
mhenok, then we will do as you advised and post on the ML soon14:58
jokke_mhen: just that you know. The image encryption has been discussed quite a bit and everyone has been kind of going away at the point when we have told them it's not Glance's job to encrypt those images but we're more than happy to keep track of it. By the looks of it you guys are taking the right approach ;)14:58
mhenI see. I can confirm that most code changes have to happen elsewhere, like I initally stated ;)14:59
jokke_;)14:59
jokke_I look forward for the ML post14:59
jokke_anything else you need from us now?15:00
mhennope that would be sufficient for now, thanks for the talk!15:00
*** hamzy_ has quit IRC15:00
jokke_well if so, we're out of time so lets continue if needed and Open discussion in #openstack-glance15:00
jokke_thanks all!15:00
jokke_#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:01
openstackMeeting ended Thu Sep 27 15:00:58 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2018/glance.2018-09-27-14.00.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2018/glance.2018-09-27-14.00.txt15:01
*** abhishekk has quit IRC15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2018/glance.2018-09-27-14.00.log.html15:01
*** smcginnis has left #openstack-meeting-415:03
*** Luzi has quit IRC15:13
*** LiangFang has quit IRC15:14
*** spiette_ is now known as spiette15:21
*** dave-mccowan has quit IRC15:23
*** mjturek has quit IRC15:24
*** hamzy_ has joined #openstack-meeting-415:26
*** yamamoto has joined #openstack-meeting-415:28
*** hamzy has joined #openstack-meeting-415:29
*** hamzy_ has quit IRC15:30
*** mjturek has joined #openstack-meeting-415:33
*** dave-mccowan has joined #openstack-meeting-415:42
*** macza has joined #openstack-meeting-415:47
*** e0ne has quit IRC15:51
*** rosmaita has left #openstack-meeting-415:59
*** mjturek has quit IRC15:59
*** liuyulong has quit IRC16:00
*** yamamoto has quit IRC16:02
*** dave-mccowan has quit IRC16:08
*** diablo_rojo has joined #openstack-meeting-416:17
*** bobh has quit IRC16:37
*** bobh has joined #openstack-meeting-416:42
*** e0ne has joined #openstack-meeting-416:52
*** e0ne has quit IRC16:54
*** diablo_rojo has quit IRC17:05
*** salmankhan has quit IRC17:06
*** e0ne has joined #openstack-meeting-417:16
*** mjturek has joined #openstack-meeting-417:16
*** gkadam has quit IRC17:20
*** iyamahat has joined #openstack-meeting-417:21
*** hamzy_ has joined #openstack-meeting-417:31
*** hamzy has quit IRC17:32
*** hamzy_ has quit IRC17:35
*** hamzy has joined #openstack-meeting-417:35
*** hamzy has quit IRC17:37
*** iyamahat_ has joined #openstack-meeting-417:38
*** iyamahat has quit IRC17:39
*** diablo_rojo has joined #openstack-meeting-417:56
*** yamamoto has joined #openstack-meeting-418:00
*** iyamahat_ has quit IRC18:02
*** iyamahat has joined #openstack-meeting-418:05
*** dims_ is now known as dims18:05
*** bobh has quit IRC18:12
*** mjturek has quit IRC18:31
*** salmankhan has joined #openstack-meeting-418:37
*** salmankhan has quit IRC18:41
*** bobh has joined #openstack-meeting-418:45
*** hongbin has joined #openstack-meeting-418:47
*** mjturek has joined #openstack-meeting-418:52
*** iyamahat has quit IRC18:56
*** yamamoto has quit IRC19:01
*** iyamahat has joined #openstack-meeting-419:05
*** mjturek has quit IRC19:11
*** mjturek has joined #openstack-meeting-419:13
*** iyamahat has quit IRC19:27
*** bobh has quit IRC19:30
*** bobh has joined #openstack-meeting-419:30
*** hamzy has joined #openstack-meeting-419:38
*** e0ne has quit IRC19:42
*** hamzy has quit IRC19:44
*** e0ne has joined #openstack-meeting-419:47
*** e0ne has quit IRC19:50
*** pcaruana has quit IRC19:54
*** bobh has quit IRC20:01
*** iyamahat has joined #openstack-meeting-420:02
*** e0ne has joined #openstack-meeting-420:08
*** diablo_rojo has quit IRC20:08
*** hamzy has joined #openstack-meeting-420:09
*** diablo_rojo has joined #openstack-meeting-420:11
*** mjturek has quit IRC20:11
*** hamzy has quit IRC20:20
*** hamzy has joined #openstack-meeting-420:20
*** hamzy has quit IRC20:25
*** mjturek has joined #openstack-meeting-420:26
*** diablo_rojo has quit IRC20:26
*** hamzy has joined #openstack-meeting-420:28
*** mjturek has quit IRC20:29
*** macza has quit IRC20:31
*** macza has joined #openstack-meeting-420:32
*** hamzy has quit IRC20:34
*** hamzy has joined #openstack-meeting-420:34
*** mjturek has joined #openstack-meeting-420:43
*** hamzy has quit IRC20:43
*** mjturek has quit IRC20:58
*** yamamoto has joined #openstack-meeting-420:59
*** mjturek has joined #openstack-meeting-421:00
*** mjturek has quit IRC21:02
*** e0ne has quit IRC21:14
*** bobh has joined #openstack-meeting-421:18
*** bobh has quit IRC21:18
*** yamamoto has quit IRC21:48
*** diablo_rojo has joined #openstack-meeting-421:57
*** seajay has quit IRC22:00
*** macza has quit IRC22:38
*** macza has joined #openstack-meeting-422:38
*** macza has quit IRC22:51
*** macza_ has joined #openstack-meeting-422:51
*** iyamahat has quit IRC22:59
*** celebdor has quit IRC23:10
*** macza_ has quit IRC23:18
*** iyamahat has joined #openstack-meeting-423:19
*** hongbin has quit IRC23:26
*** bobh has joined #openstack-meeting-423:28
*** iyamahat has quit IRC23:38

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