Monday, 2024-08-19

*** bauzas_ is now known as bauzas00:55
*** bauzas_ is now known as bauzas06:15
*** bauzas_ is now known as bauzas06:43
*** bauzas_ is now known as bauzas11:48
Luzi#startmeeting image_encryption13:00
opendevmeetMeeting started Mon Aug 19 13:00:36 2024 UTC and is due to finish in 60 minutes.  The chair is Luzi. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
opendevmeetThe meeting name has been set to 'image_encryption'13:00
Luzi#topic Roll Call13:00
LuziI'll wait a few minutes for people to show up13:01
fungiohai13:03
mheno/13:03
Luzihi fungi13:03
Luzii wrote a mail to the ml, i hope some people from cinder and glance will also show up13:04
fungii saw, thanks for the update too13:05
Luziwell it seems, we are the only ones13:08
Luzi#topic Image Encryption Patches13:08
Luziwhile i had PTO, mhen thankfully started (and nearly finished) the implementation13:08
fungirosmaita was around in irc earlier, though not sure if he's been following the glance parts of this effort13:08
Luzihttps://review.opendev.org/q/topic:%22LUKS-image-encryption%2213:08
fungier, cinder i meant13:09
fungithanks mhen!13:09
rosmaitao/13:11
Luzihi13:11
mhenhi :)13:11
Luzihere is an update: while i was on PTO mhen implemented nearly everything: https://review.opendev.org/q/topic:%22LUKS-image-encryption%2213:11
Luziwe discussed one thing, were we have a question for Cinder and Glance:13:12
Luzia transition is needed from the old Glance image metadata naming (cinder_encryption_*) to the new one (os_encrypt_*)13:12
Luziso, how should we proceed with this topic?, because there will be images in the database with the old metadata names13:13
rosmaitai talked about this a bit with Rajat (who has a holiday today) on friday13:15
Luzioh good13:15
rosmaitai think you'll need a deprecation period like you outlined in your email13:15
Luziokay, we already identified the places, which we need to adjust.13:16
rosmaitaand you can possibly write an extension to the glance-manage tool that could migrate the metadata keys in the glance database13:16
rosmaitaone thing i'm not sure about is that the cinder_encryption_deletion_policy has been documented for a while13:17
Luzidocumentation is on my list13:18
rosmaitaso, if someone puts cinder_encryption_key_deletion_policy = no_delete (or whatever the real value is)13:18
rosmaitaand there is also os_encryption_key_deletion_policy == on_deletion already on the image13:18
rosmaitado we need to worry about that?  i.e., should we respect what the person is trying to do?  because they won't get an error message13:19
rosmaitathat's the only reason i can think of for honoring the cinder_encryption_* metadata beyond a one or 2 cycle deprecation period13:19
rosmaitasorry, what i meant about the documentation comment, is that the old name cinder_encryption_... has been documented a while back, and is in the current docs (i think)13:20
mhenIt is here: https://docs.openstack.org/glance/latest/user/common-image-properties.html13:20
mhenour patchset will update this page with the new attributes13:21
mhenmaybe we should mention the old names in the descriptions?13:21
rosmaitayes, say something about them being silently ignored13:22
rosmaitaand maybe backport a doc change saying something about the metadata key will no longer be functional starting with the 2025.1 release or something13:23
Luziokay that sounds good13:24
rosmaitai guess the main issue is whether it is a good user experience to have the os_encryption_* override the cinder_encryption_* if both are present13:24
mhenshould we implement some safeguards preventing the creation of images with both or the addition of the other when one is already present?13:26
rosmaitanot sure, we don't want to to get too complicated (which opens an opportunity for bugs)13:27
mhenright13:27
rosmaitahonestly, the cinder encrypted volume workflow was designed so that the end user didn't need to know about this stuff13:27
rosmaitaso i'm not sure that a lot of people are hacking into the workflow13:28
rosmaitawe had to document it in glance since we had one service deleting a resource created by another service13:28
mhenyou'd have to know about the hexlify tweak in order to actively use it, which is not documented afaik13:29
rosmaitayeah, although you  could use the barbican secret for something else, and not know about the hexlify13:30
mhenah you  mean consuming the cinder-created secret for something else as a user`13:31
mhen?13:31
rosmaitaexactly13:32
rosmaitalooking at the cinder docs now to see if we say "do not mess with the cinder_* metadata on images"13:32
Luziis there somewhere documented to not use secrets created by OpenStack for something else, but to create a new one?13:32
Luzior that you should not re-use secrets, e.g. one secret for 2 or 3 images?13:33
rosmaitai don't see anything13:36
rosmaitagimme a minute to grep the docs instead of using a web search engine13:36
rosmaitadon't see 'cinder_encrypt' showing up anywhere in the current cinder docs13:38
Luziokay, I will take a look into the docs13:39
rosmaitai think the idea was that since encrypted volumes were supposed to "just work" for end users, we don't explain the details anywhere (i guess to keep people from getting ideas)13:39
Luziso let me summarize: we add a deprecation period for the old metadata name and adjust the patches accordingly13:40
Luzii will take a look into the glance-manage tool and write an extension to change names in the database13:41
Luzithat way we will only have the problem with users creating new images with the old metadata names, so we provide documentation13:42
Luzidid i get everything?13:42
rosmaitai think so ... the upgrade path for operators is: 1. install 2024.2 or later, new resources get os_encrypt* metadata, legacy cinder_encrypt* metadata is still honored for a deprecation period13:43
rosmaita2. run the glance-manage to update all the legacy encrypt metadata to os_encrypt*13:44
rosmaita3. at this point, no openstack service will create cinder_encrypt* metadata ... so if you still see some being created, must be by a user13:44
rosmaita4. reach out to the user and notify them that shortly the cinder_encrypt* will no longer work13:44
Luziyeah13:45
rosmaita3 & 4 sounds like a pain for operators, but we don't really think so, because it would mean that end users are making use of an undocumented "feature"13:45
rosmaitaso we don't expect that this will happen a lot13:46
Luzithen it would be nice to have someone beside us, reviewing and/or testing the patches - to tell us if we missed something important13:47
rosmaitamight be a good idea to run that upgrade path by operators (i think put "[ops]" in the subject) and see if anyone objects13:47
fungiit sounded like some of the operators in the scs community had an interest in these features, maybe they could provide feedback?13:48
rosmaitaok, i will put reviewing these patches on my to-do list ... feel free to bug me on wednesday if you haven't seen any action13:48
LuziI will ask them too13:48
rosmaitafungi: ++13:48
Luzithank you rosmaita 13:48
rosmaitawell, don't thank me yet!13:48
Luzi:D13:49
Luziokay, does anyone of you have any other questions or concerns?13:49
Luziregarding the image encryption13:49
fungii did not13:50
rosmaitai think we're good13:52
Luziokay, thank you for joining this meeting and have a nice week :)13:52
Luzi#endmeeting image_encryption13:52
opendevmeetMeeting ended Mon Aug 19 13:52:23 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:52
opendevmeetMinutes:        https://meetings.opendev.org/meetings/image_encryption/2024/image_encryption.2024-08-19-13.00.html13:52
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/image_encryption/2024/image_encryption.2024-08-19-13.00.txt13:52
opendevmeetLog:            https://meetings.opendev.org/meetings/image_encryption/2024/image_encryption.2024-08-19-13.00.log.html13:52
fungithanks Luzi!13:52
*** weechat2 is now known as hemna_13:52
*** bauzas_ is now known as bauzas18:39
*** bauzas_ is now known as bauzas22:38

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!