Thursday, 2019-09-19

*** slaweq has quit IRC00:02
*** slaweq has joined #openstack-meeting-400:18
*** slaweq has quit IRC00:23
*** dave-mccowan has quit IRC00:47
*** macz has quit IRC00:52
*** dave-mccowan has joined #openstack-meeting-400:53
*** Liang__ has joined #openstack-meeting-401:05
*** Liang__ is now known as LiangFang01:21
*** yamamoto has joined #openstack-meeting-401:30
*** yamamoto has quit IRC02:33
*** roman_g has quit IRC02:35
*** yamamoto has joined #openstack-meeting-403:05
*** psachin has joined #openstack-meeting-403:34
*** k_mouza has joined #openstack-meeting-403:46
*** k_mouza has quit IRC03:50
*** gcheresh has joined #openstack-meeting-404:16
*** gcheresh has quit IRC04:20
*** gcheresh has joined #openstack-meeting-404:38
*** pcaruana has joined #openstack-meeting-404:42
*** gcheresh has quit IRC04:42
*** Luzi has joined #openstack-meeting-404:50
*** gcheresh has joined #openstack-meeting-405:19
*** janki has joined #openstack-meeting-405:21
*** radeks has joined #openstack-meeting-405:28
*** belmoreira has joined #openstack-meeting-406:17
*** ralonsoh has joined #openstack-meeting-406:28
*** LiangFang has quit IRC06:51
*** Liang__ has joined #openstack-meeting-406:51
*** Liang__ is now known as LiangFang06:52
*** psachin has quit IRC06:53
*** slaweq has joined #openstack-meeting-407:07
*** e0ne has joined #openstack-meeting-407:17
*** slaweq has quit IRC07:20
*** belmoreira has quit IRC07:25
*** slaweq has joined #openstack-meeting-407:33
*** roman_g has joined #openstack-meeting-407:42
*** yamamoto has quit IRC08:13
*** k_mouza has joined #openstack-meeting-408:31
*** lpetrut has joined #openstack-meeting-408:33
*** lpetrut has quit IRC08:39
*** lpetrut has joined #openstack-meeting-409:05
*** yamamoto has joined #openstack-meeting-409:06
*** wuchunyang has joined #openstack-meeting-409:08
*** wuchunyang has quit IRC09:10
*** slaweq has quit IRC09:25
*** k_mouza has quit IRC09:26
*** gcheresh has quit IRC09:26
*** gcheresh has joined #openstack-meeting-409:26
*** slaweq has joined #openstack-meeting-409:27
*** yamamoto has quit IRC09:32
*** LiangFang has quit IRC09:35
*** yamamoto has joined #openstack-meeting-409:38
*** k_mouza has joined #openstack-meeting-409:39
*** k_mouza has quit IRC09:41
*** k_mouza has joined #openstack-meeting-409:44
*** janki has quit IRC09:57
*** yamamoto has quit IRC10:10
*** yamamoto has joined #openstack-meeting-410:12
*** trident has quit IRC10:35
*** e0ne has quit IRC10:42
*** trident has joined #openstack-meeting-410:48
*** pcaruana has quit IRC10:54
*** yamamoto has quit IRC11:13
*** pcaruana has joined #openstack-meeting-411:17
*** yamamoto has joined #openstack-meeting-411:17
*** k_mouza has quit IRC11:17
*** e0ne has joined #openstack-meeting-411:21
*** macz has joined #openstack-meeting-411:28
*** macz has quit IRC11:32
*** yamamoto has quit IRC11:42
*** yamamoto has joined #openstack-meeting-411:46
*** yamamoto has quit IRC11:57
*** yamamoto has joined #openstack-meeting-412:00
*** k_mouza has joined #openstack-meeting-412:27
*** k_mouza has quit IRC12:31
*** yamamoto has quit IRC12:33
*** rihabb has quit IRC12:47
*** fdegir has quit IRC12:47
*** rihabb has joined #openstack-meeting-412:48
*** fdegir has joined #openstack-meeting-412:48
*** lpetrut has quit IRC12:48
*** slaweq has quit IRC13:07
*** yamamoto has joined #openstack-meeting-413:16
*** yamamoto_ has joined #openstack-meeting-413:17
*** macz has joined #openstack-meeting-413:21
*** yamamoto has quit IRC13:21
*** yamamoto_ has quit IRC13:24
*** macz has quit IRC13:26
*** pcaruana has quit IRC13:28
*** wuchunyang has joined #openstack-meeting-413:34
*** yamamoto has joined #openstack-meeting-413:43
*** rosmaita has joined #openstack-meeting-413:52
*** Luzi has quit IRC13:53
*** pcaruana has joined #openstack-meeting-413:54
*** JamesBenson has joined #openstack-meeting-413:55
*** abhishekk has joined #openstack-meeting-413:56
*** macz has joined #openstack-meeting-414:03
jokke_#startmeeting glance14:07
openstackMeeting started Thu Sep 19 14:07:09 2019 UTC and is due to finish in 60 minutes.  The chair is jokke_. Information about MeetBot at http://wiki.debian.org/MeetBot.14:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:07
*** openstack changes topic to " (Meeting topic: glance)"14:07
openstackThe meeting name has been set to 'glance'14:07
jokke_#topic roll-call14:07
*** openstack changes topic to "roll-call (Meeting topic: glance)"14:07
abhishekko/14:07
jokke_sorry for late start14:07
jokke_o/14:07
rosmaitao/14:07
*** belmoreira has joined #openstack-meeting-414:07
*** macz has quit IRC14:07
jokke_we have empty schedule so lets get started and see how much stuff wil come up14:08
jokke_#topic release updates14:08
*** openstack changes topic to "release updates (Meeting topic: glance)"14:08
jokke_glance 19.0.0b1 was tageed this week14:08
jokke_tagged even14:08
jokke_that was our milestone release for T3 to promote people testing specially the caching changes14:09
abhishekkis it?14:09
jokke_hopefully someone finds it helpful14:09
abhishekkcool14:10
jokke_abhishekk: yup, it was released yesterday14:10
abhishekkhave we tagged client as well?14:10
abhishekkso, client is yet needs to be released14:12
jokke_I hope so ... my client release patch was abandoned so I assume someone felt more important taking care of it14:12
abhishekkI haven't seen any release patch for client14:13
jokke_there is new 2.17.0 tag14:14
abhishekkhttps://review.opendev.org/#/c/675319/14:15
abhishekkthierry has done it14:15
jokke_so I guess ttx looks after out release patches from now on14:16
abhishekkrosmaita, has proposed 2nd patch on it14:16
jokke_we'll just assume ttx knows when and what to release :P14:16
abhishekk:D14:17
jokke_that should be all, apart from RC time approaching quickly14:18
abhishekkso we do need rc1 for rethinking FS and location compatibility patch14:18
jokke_so reviews reviews reviews14:18
*** macz has joined #openstack-meeting-414:19
jokke_#topic Open Discussion14:19
*** openstack changes topic to "Open Discussion (Meeting topic: glance)"14:19
belmoreiraany change for https://review.opendev.org/#/c/671707/ to be included in Train release?14:19
rosmaitabelmoreira: i think it is fine, i just have not had time to actually test it14:21
jokke_belmoreira: so that is good one to bring up. I have few questions about the approach/need14:21
rosmaitajokke_: tell us more14:22
abhishekkshould it be treated as bug??14:22
jokke_belmoreira: iirc we already delete all custom properties from the image when it gets deleted.14:22
jokke_Yeah, why do we actually need this and why it's filed as bug?14:22
*** macz has quit IRC14:23
jokke_and is there something this does that the revised (which doesn't anymore delete the id from images table) purge doesn't address14:23
*** wuchunyang has quit IRC14:23
rosmaitawell, all the rows other than ID, like name, etc14:24
belmoreirain order to be completely compliant with GDPR we can't continue to have something that was deleted by a user14:24
*** wuchunyang has joined #openstack-meeting-414:24
belmoreiraand in image tables we continue to have important information allowing to track the user14:25
belmoreiraalso we can't purge this table because the problem of UUID reutilization14:25
belmoreirathat's why we propose to obfuscate this information14:26
jokke_5cc9d999352c21d3f4b5c39d3ea9d4378ca86544 modified purge in a way that it does not delete the ID from images table anymore14:27
jokke_that's my point14:27
jokke_and we did backport that as well14:28
rosmaitayes, but the owner is still in there14:28
*** e0ne has quit IRC14:28
abhishekkso, still wonder why it is treated as bug :o14:32
rosmaitabecause purge doesn't purge?14:32
abhishekkonly because it is related to ossn-0075?14:33
jokke_but this is request for new feature because don't want to use purge14:33
*** pcaruana has quit IRC14:33
abhishekk+114:34
rosmaitai disagree -- the fix for ossn-0075 left some stuff around that it shouldn't have14:34
belmoreirano... obfuscate complements purge14:34
rosmaitaso this change fixes that fix14:34
rosmaitai don't see what the big deal is about this14:34
rosmaitathe operator wants to respect ossn-007514:34
rosmaitabut also wants to purge the db14:35
*** michael-beaver has joined #openstack-meeting-414:35
rosmaitabut i think the key point here is that the patch was posted in july, so if this should be a feature, someone should have told belmoreira a bit sooner than this week14:35
*** wuchunyang has quit IRC14:36
jokke_rosmaita: and like I said that was addressed on the patch pointed out above. _IF_ purge leaves data behind that is considered as personal data under GDPR regulations, we should fix purge, not introduce yet another command to do th job purge was supposed to do14:36
abhishekkwe should have reviewed it earlier :(, but due to lack of visibility or overload of work we missed it14:37
abhishekkbelmoreira, sorry for that14:37
jokke_what comes problematic about that is _if_ user id is considered such personal data that cannot be stored for audit purposes under those regulation once user deletes that resource, we would need to scrape all logfiles for that as well14:38
rosmaitawell, i assume log files are purged at some point14:38
belmoreirajokke_ we do...14:38
rosmaitayou need the userid in the logs to see who's doing stuff14:38
rosmaitaso i don't think this is a slippery slope14:38
rosmaitabut i think jokke_ has a good point that we should just put this into the 'purge' command14:39
rosmaitathen it is definitely a bug fix and not a feature14:39
abhishekkthat makes sense14:39
jokke_and all it needs to touch if that is the owner uuid14:39
rosmaitaso a "regular" purge will obfuscate the images table but not delete anything14:39
*** wuchunyang has joined #openstack-meeting-414:40
abhishekkso no need of purge_images_table as well?14:40
jokke_rosmaita: not from the images table, it will still clean the rest of the tables14:40
belmoreirain my opinion will be less confusing if we have it as a different action14:40
jokke_abhishekk: that is still needed for those who don't care about the OSSN-0075 and wants to just wipe everything14:41
abhishekkack14:41
rosmaitaright, we still have regular purge and dangerous purge14:41
abhishekkhaha14:41
rosmaitabut why not obfuscate all columns?14:41
jokke_yeah, the point of splitting those two were that purge can be used for clienup while still making sure the uuid won't be reused14:42
belmoreiraops already rely in the purge feature (purging images or not) and changing that behaviour is always problematic14:42
abhishekkwe can add flag to existing purge command to toggle for obfuscate or purge??14:43
rosmaitabelmoreira: well, it wouldn't really change, it will purge all tables except 'images' and will obfuscate all deleted rows in images table14:43
rosmaitai don't know if we need a flag, when you purge, your intention is to delete everything14:43
jokke_abhishekk: that doesn't change anything about it being just yet another command to do the job14:43
rosmaitawe have to keep the uuid around because of ossn-007514:43
abhishekkyep14:43
jokke_so my question really is is there reason to keep the obfuscated data in the db?14:44
belmoreirabut can we make sure that is the bahaviour that small/private clouds would like to have?14:44
belmoreirajokke_ ossn-007514:44
jokke_which turns to a question, why don't you purge instead as that doesn't expose the security issue14:44
*** sgrasley has joined #openstack-meeting-414:44
*** wuchunyang has quit IRC14:45
belmoreirajokke_ now i'm lost14:45
jokke_belmoreira: my point exactly. purge as of how it works atm. does not expose the system to OSSN-007514:45
*** macz has joined #openstack-meeting-414:45
rosmaitayes, but it leaves the 'owner' (at least) in the images table in deleted rows taht are not removed14:46
rosmaitai am missing your point, i think14:46
belmoreirabut leaves the "owner" i nthe images table14:46
jokke_and my point is, is there any reason it should if it's a problem having it there?14:46
jokke_as in is there any reason why purge shouldn't just remove the owner uuid from the record and we don't need obfuscate14:47
rosmaitaok, now i understand14:47
rosmaitayou are arguing "no 'obfuscate' commmand" you are not arguing "no obfuscation"14:48
rosmaitaphilosophical difference14:48
rosmaita(the use/mention distinction)14:48
jokke_yes, so I'm not expert by any means on GDPR, I do not know if storing uuid of the user is considered as personal information and we should worry in the first place. If it is, then we should just whack it out with purge which does not open ossn-0075 anymore14:50
*** macz has quit IRC14:50
rosmaitai agree with jokke_ , though i would say let's just reset all the deleted rows to default values (except for the id) so we never have to worry again14:51
belmoreiraas operator I prefer to run small/descriptive commands. In that case purge is not purge anymore14:51
rosmaitabelmoreira: well, it effectively purges the images table14:51
jokke_it purges everything _but_ the images table14:52
abhishekkwe have 8 minutes left14:52
rosmaitayeah, that's what i meant by "effectively" -- it's a functional purge because the data is gone, but the rows are still there14:52
belmoreirathis means that we remove the 2 level purge, right?14:53
rosmaitabut, we should probably listen to the only operator in the room! :)14:53
rosmaitano, we'd still have to have the "dangerous" purge for people who really want to clean out the db and don't care about ossn-007514:53
belmoreiraright14:54
rosmaitaso the change erno is suggesting is that we just automatically do obfuscation as part of the "regular" purge process14:54
rosmaitathen you don't need an extra command14:54
belmoreiraI'm fine with that...14:55
rosmaitai think it is a cleaner solution14:55
jokke_So outside of preference of usage. Lets talk about how we need to prioritize this. If we want to introduce obfuscation feature as it's proposed now, it's really not a bug, lets get lite spec for it and schedule it for U, if we just need to whack owner on current purge as it doesn't meet privacy requirements, I'm fine getting that in as bugfix and even backporting it as far as the OSSN-007514:55
jokke_migitation patch was backported14:55
rosmaitai agree, on bugfix14:55
abhishekkso we can include that in rc114:55
rosmaitabut i still wonder about the other values, i think just reset them to the defaults and then this will never come up again14:56
jokke_what other values14:56
rosmaitachecksum, visibility, etc14:56
belmoreirarosmaita +114:56
rosmaitajust reset everything except the image id14:57
abhishekkfine by me as well14:57
jokke_well none of them are personal information, so definitely not GDPR consideration. Which is what has been causing my confusion of this proposal in the first place14:58
jokke_as it was based on GDPR issue, but it was touching stuff all over the place14:58
abhishekklast 2 minutes to agree on14:58
rosmaitai don't see the problem with just resetting it all14:59
rosmaitabut that's just me14:59
abhishekkNote: are we going to host next meeting?14:59
rosmaita(and belmoreira and abhishekk)14:59
*** yamamoto has quit IRC14:59
jokke_good point14:59
jokke_No meeting next week14:59
abhishekkack14:59
rosmaitahey, this is not specifically related to belmoreira's patch, but jokke_ and abhishekk should look at this: https://review.opendev.org/#/c/671707/3/glance/db/sqlalchemy/api.py@146914:59
jokke_kk15:00
rosmaitait is bound to bite us in the butt eventually15:00
jokke_will be on #os-glance if there is still something, we're out of meeting time15:00
jokke_Thanks all!15:00
rosmaitabye15:00
jokke_#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Thu Sep 19 15:00:34 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-09-19-14.07.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2019/glance.2019-09-19-14.07.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2019/glance.2019-09-19-14.07.log.html15:00
abhishekkthank you all15:01
*** rosmaita has left #openstack-meeting-415:01
*** e0ne has joined #openstack-meeting-415:02
*** slaweq has joined #openstack-meeting-415:03
*** yamamoto has joined #openstack-meeting-415:05
*** wuchunyang has joined #openstack-meeting-415:06
*** yamamoto has quit IRC15:10
*** wuchunyang has quit IRC15:12
*** gcheresh has quit IRC15:17
*** k_mouza has joined #openstack-meeting-415:24
*** abhishekk has quit IRC15:26
*** k_mouza has quit IRC15:28
*** k_mouza has joined #openstack-meeting-415:29
*** macz has joined #openstack-meeting-416:10
*** e0ne has quit IRC16:14
*** macz has quit IRC16:15
*** k_mouza has quit IRC16:25
*** k_mouza has joined #openstack-meeting-416:34
*** igordc has joined #openstack-meeting-416:44
*** e0ne has joined #openstack-meeting-416:45
*** k_mouza has quit IRC16:59
*** mbuil has quit IRC16:59
*** mbuil has joined #openstack-meeting-416:59
*** pcaruana has joined #openstack-meeting-417:01
*** pcaruana has quit IRC17:14
*** ralonsoh has quit IRC17:21
*** gmann_afk is now known as gmann17:21
*** pcaruana has joined #openstack-meeting-417:25
*** pcaruana has quit IRC17:55
*** igordc has quit IRC18:20
*** michael-beaver has quit IRC18:25
*** trident has quit IRC18:45
*** radeks has quit IRC18:51
*** trident has joined #openstack-meeting-418:55
*** trident has quit IRC19:01
*** trident has joined #openstack-meeting-419:10
*** macz has joined #openstack-meeting-419:49
*** yamamoto has joined #openstack-meeting-419:49
*** pcaruana has joined #openstack-meeting-419:51
*** yamamoto has quit IRC19:53
*** gcheresh has joined #openstack-meeting-419:54
*** gcheresh has quit IRC20:00
*** yamamoto has joined #openstack-meeting-420:31
*** pcaruana has quit IRC20:31
*** igordc has joined #openstack-meeting-420:33
*** yamamoto has quit IRC20:36
*** e0ne has quit IRC21:00
*** bobmel has joined #openstack-meeting-421:01
*** slaweq has quit IRC21:01
*** bobmel has quit IRC21:03
*** e0ne has joined #openstack-meeting-421:12
*** yamamoto has joined #openstack-meeting-421:20
*** JamesBenson has quit IRC21:29
*** JamesBenson has joined #openstack-meeting-421:31
*** yamamoto has quit IRC21:32
*** yamamoto has joined #openstack-meeting-421:35
*** JamesBenson has quit IRC21:36
*** yamamoto has quit IRC21:44
*** yamamoto has joined #openstack-meeting-421:44
*** e0ne has quit IRC22:24
*** macz has quit IRC22:25
*** notmyname has quit IRC22:30
*** notmyname has joined #openstack-meeting-422:31
*** igordc has quit IRC22:44
*** macz has joined #openstack-meeting-422:52
*** macz has quit IRC22:54
*** macz has joined #openstack-meeting-422:54
*** yamamoto has quit IRC22:57
*** igordc has joined #openstack-meeting-423:01
*** yamamoto has joined #openstack-meeting-423:03
*** bobmel has joined #openstack-meeting-423:03
*** yamamoto has quit IRC23:08
*** yamamoto has joined #openstack-meeting-423:08
*** bobmel has quit IRC23:08
*** yamamoto has quit IRC23:12
*** yamamoto has joined #openstack-meeting-423:12
*** yamamoto has quit IRC23:26
*** yamamoto has joined #openstack-meeting-423:28
*** e0ne has joined #openstack-meeting-423:30
*** e0ne has quit IRC23:30
*** yamamoto has quit IRC23:31
*** yamamoto has joined #openstack-meeting-423:31
*** yamamoto has quit IRC23:39
*** yamamoto has joined #openstack-meeting-423:46
*** wuchunyang has joined #openstack-meeting-423:47
*** JamesBenson has joined #openstack-meeting-423:47
*** yamamoto has quit IRC23:48
*** yamamoto has joined #openstack-meeting-423:49
*** JamesBenson has quit IRC23:51
*** macz has quit IRC23:54
*** e0ne has joined #openstack-meeting-423:55
*** e0ne has quit IRC23:55

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