14:59:26 #startmeeting oslo-config-plaintext-secrets 14:59:27 Meeting started Tue May 29 14:59:26 2018 UTC and is due to finish in 60 minutes. The chair is rmascena. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:59:28 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:59:31 The meeting name has been set to 'oslo_config_plaintext_secrets' 14:59:43 #link https://etherpad.openstack.org/p/oslo-config-plaintext-secrets 14:59:44 o/ 15:00:57 #topic roll call 15:01:09 ping dhellmann, spilla 15:01:17 ping bnemec 15:01:19 o/ 15:02:28 ok, so let's start it :) 15:02:34 #topic current status 15:02:56 moguimar, I believe that you can talk more about that for us :) 15:03:14 #link https://review.openstack.org/#/c/554316 15:04:27 since our call last week I was able to fix the return type of the ConfigurationSource::get() method 15:04:46 o/ 15:04:49 I'm currently working on the additional test cases 15:05:09 I had a setback with my computer last friday, only got it back working today. 15:06:29 I'll add more tests to cover the option value discovery in multiple sources, to make sure that they follow the spec 15:07:26 moguimar, thanks for the status :) 15:07:39 #topic owners for remaining work for Rocky-2 15:08:03 what is our deadline for Rocky-2? 15:08:11 so besides the current stuff that moguimar is taking care of, we still have two steps in the working items list remaining 15:08:39 Rocky-2: something closer to Jun 04 15:09:02 so, it's will be pretty hard to have this done for rocky-2 =/ 15:09:40 #link https://releases.openstack.org/rocky/schedule.html 15:11:29 bnemec, dhellmann well, I would like to confirm that still not feasible having at least this INI driver as a FFE, which means finishing the steps 7-8 on the work items list 15:11:47 Ensure the sample generator emits an example group 15:11:53 and add a separate cache for values coming from external sources 15:12:50 So feature freeze isn't technically until R-3, although IIRC Oslo generally observes feature freeze a couple of weeks before that to allow time for adoption of new features. 15:13:38 I think this ended up being somewhat less invasive to the existing code than we originally expected, so it's possible we could land it as long as it happens before feature freeze. 15:14:03 We'd need to take a closer look and see what the risk is. 15:14:17 bnemec, gotcha, I think that since we reduce our scope, will be nice to have that as an "experimental" for this release 15:14:36 and we can fix everything that is needed and add the castellan driver for the next release 15:15:10 Yeah, I think that sounds good. 15:15:23 The ini driver by itself isn't the end goal here anyway. 15:15:36 yeah, exactly 15:16:17 ok, so let's keeping work to finish this final steps ASAP and we can evaluate if make sense to ask for a FFE for this ini driver 15:16:49 So that might be another work item - to make sure the documentation says this is an experimental feature in Rocky. 15:17:10 bnemec, ++ I'll add that to the list 15:17:55 In fact I don't know if we have a documentation bullet point yet, so that's a missing item anyway. This will require doc updates in general. 15:18:45 bnemec, yeah, that's something that I had in mind, document our to use the ini driver and how to implement a new driver 15:20:26 Yep, sounds good. 15:21:44 #action raildo to starting documenting how to use the INI driver and how to implement a new one 15:21:49 /me slips in the back late 15:22:23 dhellmann, hey :) 15:22:49 apologies for being late 15:22:54 also got pulled into a meeting and am catching up, sorry! 15:23:17 so, based on our current status, we still need to define the owners for topic 7 and 8 in the etherpad, some volunteer? 15:24:18 I'm curretly working on item 5, but I can take one of them as soon as I'm done with item 5 15:25:35 I like the idea of finishing the work we have and then picking up the next task 15:25:53 that way we aren't waiting on someone to finish 4 things 15:26:25 dhellmann, yeah, I believe that we maybe have to many opening tasks right now 15:26:45 * dhellmann nods 15:27:10 rmascena: any suggestion on marking tasks done? 15:27:38 moguimar, so, if the patch is not set as WIP, it should be ready for review 15:27:43 and kind of done on our side 15:28:30 moguimar, also, you can add more details in the etherpad if needed 15:28:50 so everyone can be aware if it's missing some step in the work item 15:29:29 #open discussion 15:29:53 we only have one minute remaining, something else? 15:30:32 not on my end 15:30:54 so, thanks everyone, have a good week! 15:30:59 #endmeeting