13:00:15 <redrobot> #startmeeting barbican 13:00:15 <opendevmeet> Meeting started Tue Sep 7 13:00:15 2021 UTC and is due to finish in 60 minutes. The chair is redrobot. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:15 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:00:15 <opendevmeet> The meeting name has been set to 'barbican' 13:00:39 <redrobot> #topic Roll Call 13:00:39 <redrobot> Courtesy ping for ade_lee dave-mccowan d34dh0r53 hrybacki jamespage Luzi lxkong mhen moguimar raildo rm_work tosky xek nearyo oleksandry 13:02:13 <tosky> hi (but no news really) 13:02:27 <redrobot> Hi tosky! 13:02:36 <redrobot> #topic Liaison Updates 13:02:41 <redrobot> No news from Tosky 13:02:56 <redrobot> Also no news from me. (I've been trying to keep an eye out for Oslo news) 13:03:08 <tosky> oh, maybe a technical question (but for later) 13:03:18 <redrobot> #topic Open Discussion 13:03:21 <redrobot> :D 13:04:19 <redrobot> tosky what's up? 13:06:37 <tosky> so 13:07:00 <tosky> I was looking for a way to test encryption with a different key size 13:07:20 <tosky> I was hoping to find a configuration key which would have just switched all key sizes for all tests 13:07:36 <tosky> there is none in tempest (buu), so that's a problem, ok 13:07:43 <tosky> then I've checked barbican-tempest-plugin 13:07:55 <tosky> and there seems to be a configuration key here: https://opendev.org/openstack/barbican-tempest-plugin/src/branch/master/barbican_tempest_plugin/config.py 13:08:29 <tosky> key_size (and cypher), BUT it seems it's only relevant for the Ephemeral storage encryption test 13:08:44 <tosky> added here back in the days: https://opendev.org/openstack/barbican-tempest-plugin/commit/ab903f340b10446257ce33ab36151d8849f9792e 13:09:40 <tosky> now... I'm not even sure the test itself uses that configuration options (neither key_size nor cypher!) 13:09:42 <tosky> https://opendev.org/openstack/barbican-tempest-plugin/src/branch/master/barbican_tempest_plugin/tests/scenario/test_ephemeral_disk_encryption.py 13:09:46 <tosky> so I'm puzzled 13:10:24 <tosky> I guess such a key could be added (maybe even in tempest, now that we have a stable scenario manager) and used all around for any test which creates an encyrpted volume? 13:11:28 <redrobot> I'll have to dig into the tempest-plugin code, but I would not be surprised to see those options not used 13:13:19 <redrobot> Yeah, looks like we're not using that at all 13:13:33 <redrobot> that same commit added this create_keypair function https://opendev.org/openstack/barbican-tempest-plugin/src/branch/master/barbican_tempest_plugin/tests/scenario/manager.py#L101-L108 13:13:58 <redrobot> tosky we can certainly change anything needed to get these options working 13:19:18 <tosky> okidoki, it would be very useful to be able to change the key size globally without having to rewrite custom tests 13:19:54 <redrobot> for sure 13:20:20 <redrobot> #help we need to update the tempest plugin to actually use the key size option 13:20:26 <redrobot> #topic Bug Review 13:21:14 <redrobot> I did add a new bug report last week: 13:21:17 <redrobot> #link https://storyboard.openstack.org/#!/story/2009170 13:21:47 <redrobot> in a nutshell, Barbican returns 500 errors when you turn on scope enforcement 13:21:52 <redrobot> for some APIs 13:22:03 <redrobot> I'm currently working on getting that sorted out. 13:24:24 <redrobot> That's all I have for today 13:24:27 <redrobot> thanks for joining tosky! 13:24:32 <redrobot> #endmeeting