15:00:24 #startmeeting oslo-config-plaintext-secrets 15:00:26 Meeting started Tue Mar 20 15:00:24 2018 UTC and is due to finish in 60 minutes. The chair is raildo. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:29 The meeting name has been set to 'oslo_config_plaintext_secrets' 15:00:32 o/ 15:00:35 #link https://etherpad.openstack.org/p/oslo-config-plaintext-secrets 15:00:48 #chair dhellmann 15:00:49 Current chairs: dhellmann raildo 15:01:14 hey dhellmann :) 15:01:25 hi, raildo! 15:02:50 dhellmann, we changed our meeting time due a conflict with the new keystone meeting time 15:02:58 dhellmann, this time is good for you? 15:03:10 the wifi here is a bit laggy 15:03:24 yes, this should be ok 15:03:42 ok, that's fine 15:03:44 how about everyone else? 15:04:44 I don't see spilla online 15:04:51 spilla was the guy who suggested this time slot, I pinged him to see if he will be able to join us 15:04:56 ok 15:05:02 looks like he is online, but not on this channel 15:05:07 ah 15:06:10 but I believe that we can start and he can catch up later 15:06:17 sure 15:06:24 #topic status check 15:06:37 I put together an incomplete example patch for how I thought the config_source option should work 15:06:38 #link https://review.openstack.org/554316 15:07:04 that takes advantage of the existing parser by registering the option as a regular option 15:07:13 yeah, I saw that, thanks for doing that work, I hope to review it int he next days 15:07:24 it's incomplete because we can't actually do anything with a given set of options for a source until we have some drivers 15:07:53 the spec lays out several other steps that have to come before this one 15:08:09 dhellmann, so, are you saying that we should implement the castellan driver, before have that merged? 15:08:28 I don't know if spilla started in the middle of the list because he wanted to experiment with some stuff that wasn't clear or what 15:08:41 no, the spec describes a "http" driver that we can have in-tree 15:09:08 hang on... 15:09:18 * gagehugo sneaks in late 15:09:21 ok, got it. so let's set an action item to sync this with spilla 15:09:28 http://specs.openstack.org/openstack/oslo-specs/specs/queens/oslo-config-drivers.html#work-items 15:09:49 gagehugo, hey gagehugo we are talking about the alternative approach that dhellmann proposed here https://review.openstack.org/#/c/554316/1 15:09:57 this patch is the 5th item on that list 15:10:17 gagehugo, do you have any idea where are spilla? :D I pinged him but I got no responses 15:10:32 yeah let me yell at him 15:10:41 spilla, hey \o 15:10:42 he's sitting across from me :) 15:10:43 o/ 15:10:50 i thought it auto joined this channel, oops 15:11:24 raildo yeah I saw that yesterday, will take a look 15:11:50 spilla, did you had a chance to check the dhellmann's patch: https://review.openstack.org/#/c/554316/1 15:12:04 ^ also looking at that, was going to setup a meeting with him to go through it and work on it 15:12:20 spilla, I mean, looks like we still need to define a new driver for loading configuration from simple URLs to be used as a test case, before using it 15:12:26 yeah, I'm happy to set up a hangout or whatever to go through things 15:12:41 that would be great :) 15:12:44 right, the spec lays out steps and although they aren't numbered they are in order 15:12:56 with the idea that each can build on the work done in the previous step 15:13:26 this was one of the trickier parts to get right, but we won't actually want to land the patch until some of the other stuff is in place 15:13:42 we can set it up as a series of patches so that other reviewers can understand how the parts interact 15:14:10 ok 15:14:15 ++ 15:14:26 dhellmann, ++ imo, that would be the best approach for that, having a dependecy between patches to keep that in order to be merged 15:14:32 in other projects we might use a feature branch for the work, but openstack doesn't really use feature branches 15:14:59 raildo agreed, just have to make sure dependencies don't get all over the place 15:15:04 raildo : exactly 15:15:21 if we keep it as a series it should work out ok 15:15:36 someone can start with that first item and when we get to the bit I did we can rebase onto the others 15:15:47 and finish it, of course, since it's incomplete 15:16:47 spilla, I remember that you said that someone was going to start the base class for a configuration driver, is that still valid? 15:17:31 yes, they got pulled back into project-tags for keystone. I will check with him to see if he is available 15:17:33 should we create an action item for someone here for this specific task? 15:18:01 it would be good to know who is going to work on each part 15:18:33 dhellmann, agreed 15:19:08 I was planning to work more in the castellan driver and custodia-castellan stuff, but I can stop for a while and get some tasks on this first tasks 15:19:21 I added a section to the top of the etherpad 15:20:56 spilla, can you go here and add your name in the specific tasks that you're covering with your patch: https://etherpad.openstack.org/p/oslo-config-plaintext-secrets 15:21:25 yep, also i can put mine on hold for any earlier tasks 15:25:22 spilla, let's set a deadline for like next meeting? so you can confirm of they will be able to help us on this first task or someone can put their name in this first task, at least? 15:26:30 ok, I am good to switch gears to it asap. ill see what nhelgesen's availability is like 15:26:34 I know you all have other things to do, so what sort of availability do all of you have for working on this? 15:27:45 dhellmann, for the next two/three weeks I'll be busy with a bunch of downstream stuff, but after that, I hope to be almost full time on this feature 15:27:51 also my i believe dhellmann's patch is a reimplementation of mine (fixed in etherpad) 15:28:30 spilla : yes, that's right 15:28:41 raildo : ok 15:28:55 what's the timeline looking like? is our goal still the first milestone? 15:29:08 I do not have much availability unfortunately right now 15:29:12 i should be available to work on this most of my time for the next few weeks 15:29:18 #link https://releases.openstack.org/rocky/schedule.html 15:29:21 im double checking on that 15:29:42 spilla : ok, good. I will try to keep time open to review and work with you on details 15:29:49 we have a bit more that 1 month for rocky-1 15:30:05 yes, that's not a lot of time 15:30:09 so, that start to become a bit trick 15:30:34 yeah, maybe rocky-2 instead 15:31:01 dhellmann, spilla let's try to define at least some of this tasks for rocky-1? 15:31:40 my concern if we slip things too late in the schedule is that it's changing things at such a low level 15:31:47 so yeah, let's see how far we can get by the first milestone 15:32:26 I believe that we can finish at least a few work items from this list (two or three) for rock-1 15:32:46 and then we can measure our effort to finish it for rocky-2 15:32:53 ok 15:32:59 ++ 15:33:04 since we have a bunch of that done in the item 5 15:35:45 dhellmann, spilla I believe that's it for today, let's focus to get this first items done ASAP :) 15:36:36 sounds good, I'll watch for patches to review :-) 15:36:57 dhellmann, sounds great 15:37:06 Let's get this done! :D 15:37:18 have a good week everyone 15:37:22 #endmeeting