15:00:20 <raildo> #startmeeting oslo-config-plaintext-secrets
15:00:21 <openstack> Meeting started Tue Apr  3 15:00:20 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:23 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:26 <openstack> The meeting name has been set to 'oslo_config_plaintext_secrets'
15:00:27 <raildo> https://etherpad.openstack.org/p/oslo-config-plaintext-secrets
15:00:59 <gagehugo> o/
15:03:35 <raildo> gagehugo, what's up :)
15:04:19 <gagehugo> raildo o/
15:04:28 <gagehugo> having 3 irc meetings at once :)
15:04:37 <raildo> gagehugo, damn
15:04:46 <spilla> o/
15:05:00 <raildo> #topic status check
15:05:36 <raildo> so, I didn't had so much time to work on this work item, but I'm trying to understand the current code on https://github.com/openstack/oslo.config/blob/master/oslo_config/cfg.py#L2320
15:06:33 <raildo> spilla, so, if I'm understanding that correctly, in this first task, we should have a abstract class to work a base class for ConfigOpts, am I right?
15:06:44 <raildo> as a base*
15:06:59 <dhellmann> o/
15:07:22 <dhellmann> hmm, no
15:07:26 <spilla> definitely an abstract base class but i believe it will be for #2
15:07:30 <dhellmann> we just need the new class as a standalone thing
15:08:05 <dhellmann> the 2 new abstract classes will be subclassed by the driver plugins
15:08:22 <raildo> dhellmann, hum, so I'm a little bit lost in what is expected to be in that class, is that open_source_from_opt_group() method?
15:08:27 <dhellmann> and then the instances of those subclasses will be *used* by ConfigOpts, but they won't change ConfigOpts inheritance structure
15:08:41 <dhellmann> the first couple of tasks are just laying groundwork
15:08:55 <dhellmann> we need a class to describe what an option source looks like, what methods it takes
15:09:05 <dhellmann> and we need a class to describe what a driver looks like, what methods *it* takes
15:09:17 <dhellmann> the required methods are described in the spec
15:09:40 <raildo> hum, got it
15:09:43 <dhellmann> the ones we know now, that is, but we may find other methods later as we start implementing things
15:11:01 <dhellmann> the work-list is organized "bottom up" but the spec talks about things a bit more top-down
15:11:04 <dhellmann> so it's a little confusing
15:12:24 <raildo> dhellmann, yep, I believe that the reason that I was a bit lost, but I hope to have a first patch for that by the one of the day
15:12:39 <dhellmann> sounds good
15:12:59 <dhellmann> my availability this week is going to be spotty because I have some personal stuff to take care of, but I will try to do some reviews in the evenings if I can
15:13:18 <raildo> dhellmann, no worries :)
15:15:01 <spilla> im still working on getting a initial patch set up for 2, should be soon as well
15:15:29 <raildo> spilla, sounds great, I hope to poke you more for help in the next days
15:15:54 <spilla> raildo no problem, ill probably do the same :)
15:16:32 <spilla> also next week i will be spotty because of some required training so hoping to get a bunch done before thne
15:16:40 <spilla> or at least a decent chunk
15:17:52 <raildo> having training is always good :)
15:18:19 <raildo> #topic open discussion
15:18:32 <raildo> I don't have anything else from my side
15:19:11 <spilla> same, ill be hovering in openstack-oslo
15:19:43 <raildo> have a good week everyone
15:19:47 <raildo> #endmeeting