Tuesday, 2017-03-14

*** salv-orlando has quit IRC00:09
*** browne has quit IRC00:37
*** gcb has quit IRC00:42
*** tovin07_ has joined #openstack-oslo00:51
openstackgerritKiseok Kim proposed openstack/oslo.log master: Fix bug in log_method_call decorator  https://review.openstack.org/44490800:55
*** sdague has quit IRC00:57
*** jamielennox is now known as jamielennox|away00:58
*** jamielennox|away is now known as jamielennox01:12
*** browne has joined #openstack-oslo01:18
*** browne has quit IRC01:18
*** zhangjl has joined #openstack-oslo01:19
openstackgerritAnthony Washington proposed openstack/oslo.policy master: Add additional param to policy.RuleDefault  https://review.openstack.org/43907001:23
*** eck` is now known as eck`gone01:25
*** tovin07 has joined #openstack-oslo01:42
*** yamamoto has joined #openstack-oslo01:43
*** zz_dimtruck is now known as dimtruck01:57
*** zzzeek has quit IRC02:30
*** zzzeek has joined #openstack-oslo02:31
*** yamahata has quit IRC02:42
*** salv-orlando has joined #openstack-oslo03:10
*** nicolasbock has quit IRC03:13
*** salv-orlando has quit IRC03:15
*** ihrachys has joined #openstack-oslo03:23
*** ihrachys has quit IRC03:44
*** Dinesh_Bhor has joined #openstack-oslo03:55
*** ihrachys has joined #openstack-oslo04:15
*** ihrachys has quit IRC04:25
*** links has joined #openstack-oslo04:35
*** ihrachys has joined #openstack-oslo04:36
*** salv-orlando has joined #openstack-oslo05:11
*** dimtruck is now known as zz_dimtruck05:12
*** salv-orlando has quit IRC05:15
*** gcb has joined #openstack-oslo05:17
*** claudiub has joined #openstack-oslo05:51
*** ihrachys has quit IRC05:56
*** nkrinner_afk is now known as nkrinner06:06
*** salv-orlando has joined #openstack-oslo06:12
*** yamahata has joined #openstack-oslo06:15
*** salv-orlando has quit IRC06:17
*** salv-orlando has joined #openstack-oslo06:26
openstackgerritWangBinbin proposed openstack/oslo.utils master: Replace six.iteritems() with .items()  https://review.openstack.org/44531406:26
*** david-lyle has quit IRC06:27
*** eezhova has joined #openstack-oslo06:47
*** lpetrut has joined #openstack-oslo06:49
*** e0ne has joined #openstack-oslo06:51
*** zhangjl has quit IRC07:00
*** zhangjl has joined #openstack-oslo07:01
*** nkrinner has quit IRC07:09
*** nkrinner has joined #openstack-oslo07:14
*** tesseract has joined #openstack-oslo07:20
*** salv-orl_ has joined #openstack-oslo07:23
openstackgerritMerged openstack/oslo.concurrency master: Updated from global requirements  https://review.openstack.org/44512307:25
*** salv-orlando has quit IRC07:26
*** e0ne has quit IRC07:28
*** eezhova has quit IRC07:39
*** pcaruana has joined #openstack-oslo07:50
*** lpetrut has quit IRC07:55
*** claudiub has quit IRC07:55
*** zzzeek has quit IRC08:00
*** zzzeek has joined #openstack-oslo08:00
*** shardy has joined #openstack-oslo08:04
openstackgerritMerged openstack/oslo.config master: Handle both - and _ forms of deprecated opts  https://review.openstack.org/43875208:05
*** salv-orl_ has quit IRC08:10
*** eezhova has joined #openstack-oslo08:15
*** jaosorior has joined #openstack-oslo08:24
openstackgerritMerged openstack/oslo.utils master: Updated from global requirements  https://review.openstack.org/44513208:24
*** aarefiev_afk is now known as aarefiev08:32
openstackgerritMerged openstack/oslo.cache master: Updated from global requirements  https://review.openstack.org/44512208:40
*** jpena|off is now known as jpena08:43
openstackgerritMerged openstack/oslo.i18n master: Updated from global requirements  https://review.openstack.org/44512508:46
*** e0ne has joined #openstack-oslo08:50
openstackgerritMerged openstack/oslo.log master: Updated from global requirements  https://review.openstack.org/44512608:50
*** salv-orlando has joined #openstack-oslo08:54
*** jpena is now known as jpena|off08:56
openstackgerritMerged openstack/oslo.db master: Updated from global requirements  https://review.openstack.org/44512408:57
*** jpena|off is now known as jpena09:03
*** lucas-afk is now known as lucasagomes09:15
openstackgerritJuan Antonio Osorio Robles proposed openstack/oslo.messaging master: Add "ssl" option for amqp driver  https://review.openstack.org/43856309:18
*** pblaho has quit IRC09:31
openstackgerritMerged openstack/oslo.service master: Updated from global requirements  https://review.openstack.org/44513109:43
*** pblaho has joined #openstack-oslo09:46
*** tovin07_ has quit IRC10:03
*** nicolasbock has joined #openstack-oslo10:04
*** pblaho has quit IRC10:10
*** gcb has quit IRC10:11
*** salv-orlando has quit IRC10:18
*** boden has joined #openstack-oslo10:18
*** zhangjl has left #openstack-oslo10:20
*** pblaho has joined #openstack-oslo10:23
*** chenying_ has quit IRC10:32
*** chenying_ has joined #openstack-oslo10:32
*** salv-orlando has joined #openstack-oslo10:45
*** salv-orl_ has joined #openstack-oslo10:46
*** lpetrut has joined #openstack-oslo10:46
*** nicolasbock has quit IRC10:46
*** sdague has joined #openstack-oslo10:47
*** nicolasbock has joined #openstack-oslo10:48
*** salv-orlando has quit IRC10:49
*** salv-orl_ has quit IRC10:51
*** Guest91536 has quit IRC11:03
*** yassine has joined #openstack-oslo11:03
*** yassine is now known as Guest4711:04
*** cdent has joined #openstack-oslo11:09
*** links has quit IRC11:36
*** gordc has joined #openstack-oslo11:43
*** links has joined #openstack-oslo11:48
dimsjd_ : etcd upto 3.0.17 seems to work fine with tooz ("tox -e py27-etcd")12:13
dimsjd_ : 3.1.3 fails on 2 tests12:14
dimsat least intermittently12:16
dimshmm, IPCTestAPI, switching to linux to see if it's any better there12:29
*** ansmith has joined #openstack-oslo12:33
openstackgerritDavanum Srinivas (dims) proposed openstack/tooz master: [WIP] Try latest etcd - 3.1.3  https://review.openstack.org/44547012:34
*** eck`gone is now known as eck`12:43
*** kgiusti has joined #openstack-oslo12:51
*** links has quit IRC12:52
*** links has joined #openstack-oslo12:53
*** amotoki has joined #openstack-oslo12:54
*** lucasagomes is now known as lucas-hungry12:55
jd_dims: IPC tests are not working well on Darwin if that is what you're seeing13:02
dimsjd_ : yep13:02
jd_I never dug why, since well, nobody really care :)13:02
dims:)13:02
sileht/1/1513:24
thervedims, jd_ : I was thinking about reviving the work around using etcd as a backend for oslo.config13:38
therveAny interest/opinion?13:38
jd_no opinion13:39
jd_merely interested13:39
jd_I'm not sure I really see the use case but I want to be convinced13:39
jd_;)13:39
thervejd_, Well, the use case is to remove the config files :)13:39
jd_why are they a problem?13:40
therveAnd ship the configuration in etcd itself13:40
-openstackstatus- NOTICE: Gerrit is going to be restarted due to performance problems13:40
*** ChanServ changes topic to "Gerrit is going to be restarted due to performance problems"13:40
therveBecause they are stuff that you need to manage on disks on all your nodes13:40
therveInstead of an API to call13:40
jd_therve: got an example?13:42
thervejd_, Of using etcd behind oslo.config?13:42
jd_therve: yes, the kind of problem it solves that you can't solve with files13:42
jd_I just want to hear a good use case :)13:42
dimstherve : seen this already? (https://review.openstack.org/#/c/440835/) - bnemec is starting small there, objective would be what you stated13:42
dimsbnemec : around? ^13:43
*** jpena is now known as jpena|lunch13:43
thervejd_, https://gist.github.com/chmouel/05fb715f96344161268c13:43
thervedims, Yeah I followed the discussion. The actual implementation is a much more trivial subject13:44
thervejd_, It's not really about not solving it with files, but rather not use files...13:44
jd_therve: yeah so I guess being more stateless?13:45
thervejd_, Right13:46
-openstackstatus- NOTICE: Gerrit has been successfully restarted13:46
*** ChanServ changes topic to "Gerrit has been successfully restarted"13:46
thervejd_, For example, kolla is doing some relatively weird stuff to expose configuration to the various openstack services13:46
therveUsing volumes to have files available, maintaining the files on the volumes...13:47
dimstherve : i'd support the use case, having hit this in several places13:47
jd_therve: yeah I see13:48
jd_makes sense13:48
dimstherve : another example the keystone folks needed for was fernet keys, they initially wanted to use oslo.config but ended up defining their own stuff13:49
jd_therve: does it play well with things like e.g. Puppet?13:49
dimslbragstad : right? ^13:49
thervejd_, Well puppet only manages files. But it's easy to have them not step on each other toes13:49
thervedims, I guess that's another issue. They need the config to be reloaded, right?13:50
jd_therve: so how are you supposed to fill etcd then?13:50
thervejd_, TBD? :)13:50
* lbragstad reads back13:50
jd_therve: ok :)13:50
thervejd_, I think https://review.openstack.org/#/c/440835/ is the other side of the issue13:50
dimstherve : y, we'll need some way to tell processes when things changed too (like the log level stuff)13:50
jd_dims: SIGHUP?13:52
thervedims, jd_ : https://github.com/chmouel/oslo.config/commit/01ee54dd5219b1434eaac422055b58e77694d89f is the kind of change I'm thinking about currently13:52
therve(2 years old yesterday, woo)13:52
*** ChanServ changes topic to "#openstack-oslo"13:52
-openstackstatus- NOTICE: Gerrit has been successfully restarted13:52
*** lucas-hungry is now known as lucasagomes13:53
dimstherve : :) we need to convince dhellmann too13:53
thervedims, Yeah I'm testing the waters13:54
dimstherve : here's another old one https://review.openstack.org/#/c/243114/13:55
dhellmanndims, therve : as soon as someone can explain to me how to tell a service how to connect to etcd with a unique id that lets an operator configure different instances of the same type of service in different ways *without using a config file* then I'm on board.13:55
dimsthere you go therve :) ^13:56
dhellmannyou have to solve the deployment problem before any of the rest of the work is going to make sense13:56
thervedhellmann, OK, what about: nova --etcd-server http://10.0.0.1/openstack/nova/b79647f9-588a-47c2-be4e-310ac5291f9213:56
therveThough I'm not sure you really want to configure the instances differently13:57
*** links has quit IRC13:57
dhellmanntherve : some of the services other than nova may need to be configured differently13:58
dhellmannI assume there are some sort of credentials that would go in a URL like that13:58
thervedhellmann, Sure you can always define some kind of service class, no? IE not an unique ID13:58
therveI don't know if etcd supports auth. jd?13:59
jd_I can't think of any service configured differently, that sounds weird13:59
jd_therve: it does IIRC13:59
thervedhellmann, At any rate, you need some kind of bootstrap, sure. Why is that an issue?14:00
dhellmannjd_ , therve: in the past, the reason given for doing this was to make deployment tools "simpler" because they would be able to send the same config file to every host. If every host needs a unique URL, that argument doesn't make sense. There may be other reasons for using etcd, but I don't think I've heard any of them. I'm not against doing it, I just want to make sure there's some sort of user-visible benefit beyond14:01
dhellmann "etcd is what kubernetes uses"14:01
dhellmannwe also have to handle the mutable/immutable config option situation14:02
dhellmannsome options are cached inside code, so changing them in etcd won't change the service behavior14:02
dhellmannthat's not a blocker, but we need to make sure we're communicating with deployers about limitations like that14:03
dhellmann(or fix the code to not cache the values)14:03
therveTrue, I don't have a plan to solve everything14:03
therveFTR I don't really care about k8s14:03
therveI want to deploy heat in a container. Having to push config files to that container is just kind of ridiculous14:03
dhellmannI don't want us to push out a half-baked feature without at least thinking through some of these issues14:03
therveIt's like having a VM and manually doing the network14:04
dhellmannmy point is that moving from static config to remotely served config is more than just providing a way to fetch things from urls or etcd14:04
thervedhellmann, It may be, but it doesn't have too in step 1?14:05
dhellmannwe have some assumptions built into our services right now that we have to address14:05
*** ihrachys has joined #openstack-oslo14:05
therveYeah but it's a chicken and egg problem. We''re not going to do anything while those issues are not addressed?14:05
therveMeanwhile, even fetching config remotely at startup would be a win to me14:05
dhellmannaddress them in a spec, to at least have them written down with some sort of thought applied14:05
dhellmannfetching config remotely once at startup is one design we could do easily. does it buy us what we want?14:06
dhellmannwhat's the access pattern for config in etcd? one option at a time?14:06
therveTo me it's better than mounting docker volumes and copying files to it14:06
dhellmannI'm not arguing otherwise. I'm suggesting that you work through more of the problem than writing an etcd driver for oslo.config so that when we roll this out into real services it works.14:07
therveI'm not sure what you mean by access pattern14:07
dhellmannfor a typical application reading its config from etcd, does it fetch all of the config at one time or does it ask for individual config options as it needs them?14:07
dhellmanndo deployers using etcd for config for other applications expect that if they change etcd the application notices that change automatically?14:08
therveI'm not a deployer and I don't use etcd, so I can't tell you14:08
dhellmannor do they expect to kill the container and start a new one each time they change the config?14:08
dhellmannwe should get some input from someone who can answer those questions14:09
dhellmannmaybe the architecture working group can help identify some people14:09
therveI guess14:10
therveIt feels that we'll enter bikeshedding hell, and we'll talk about it again in 2 years :)14:12
dhellmannso instead we should build something that may not meet anyone's real requirements?14:12
dhellmannthe driver is the easy part of this change.14:12
dhellmannI'll start a mailing list thread14:13
therveWell yeah. That's why I think we should do it! :)14:13
dimsexperimental :)14:13
therveMeeting anyone's requirements is also a good way to make sure we want do anything at all14:13
therves/want/won't14:13
dhellmannif you don't know what you're building, why are you in such a hurry to start?14:14
therve?14:14
therveI have a need, with a solution that works for me14:15
therveIt's unfair to say "in a hurry", when discussions started 2 years ago and nothing happened14:16
*** zz_dimtruck is now known as dimtruck14:18
dhellmannbut it's somehow fair to say that these questions I have are bikeshedding?14:19
therveNo, I wasn't referring to your questions14:19
dimsdhellmann : we can lay out exactly what we can do - example "applications can load the whole config just like we would load a whole file"14:21
dimsdhellmann : and see what kind of feedback we get14:21
dhellmanndims : that would be a good step to take14:21
dimstherve : i like the idea of a uuid or something to load options specific to a "thingy". would we have a base set of options and layer on the key/value pairs specific to a uuid?14:22
dimstherve : that will turn into a question on how an operator would populate and maintain the etcd store14:23
thervedims, Right, we need to define some kind of structure14:24
dimstherve : so let's lay down some structure, say a tool to set/update (may be from config files?) and the access pattern in a spec14:24
dhellmanndo we need to build something to load config? or can we use existing tools for that?14:25
dimsdhellmann : load from config (we have) and then save into etcd store (we will need)14:25
dimstherve : if we can just point folks to existing etcd tools that others use, that may be good too, we don't need to invent14:26
dhellmannyeah, that's what I meant, do we actually need to do that? or can we just tell operators to use their normal etcd tools to set values in the store?14:26
dimsright dhellmann14:26
dimswe can just define the structure we expect14:27
dhellmannright14:28
dhellmanndims, therve : maybe one of you should start that ML thread, since I'm out next week for PTO14:29
dimstherve : are you up for it? :)14:30
thervedims, Not sure to be honest :)14:31
dimstherve : how about we get something into a spec first and then ML14:32
*** shardy has quit IRC14:37
*** shardy has joined #openstack-oslo14:37
*** edmondsw has joined #openstack-oslo14:40
*** pblaho has quit IRC14:43
thervedims, Sorry, I shouldn't have started this discussion. I'm too tried to drive it.14:47
dimstherve : understood. though may i ask you to drop your ideas/thoughts into an etherpad? i can peel that onion next :)14:49
therveSure14:50
*** jpena|lunch is now known as jpena14:51
dimsthanks therve !14:52
*** Syed__ has joined #openstack-oslo14:52
*** edmondsw has quit IRC14:53
*** pblaho has joined #openstack-oslo15:08
openstackgerritDavanum Srinivas (dims) proposed openstack/tooz master: Switch tests to use latest etcd - 3.1.3  https://review.openstack.org/44547015:17
thervedims, https://etherpad.openstack.org/p/oslo.config_etcd_backend15:20
dimstherve : cool. so multiple urls means aggregate from all these sources (in the specified order)15:26
thervedims, Yeah it's the same semantic as multiple config-files currently15:27
dimsright, makes sense15:28
dimsthen we don't have to dictate the url structure15:28
*** SamYaple has joined #openstack-oslo15:28
dimsSamYaple : here about config files i mentioned? :)15:29
*** mtanino has quit IRC15:29
*** spsurya has joined #openstack-oslo15:30
SamYapledims: mayhaps15:31
dimsSamYaple : so background, many times in the past we've had requests for oslo.config information to be not in a file.. so we have talked about backends like etcd, trying to re-raise that topic with this etherpad - https://etherpad.openstack.org/p/oslo.config_etcd_backend15:33
SamYapleis this semi-related to the discussion we had come out of the PTG?15:34
dimsy15:34
SamYaplei think jesse brought up the etcd point15:34
SamYaplecool15:34
dimsSamYaple : thoughts here or on the etherpad.15:35
dimsbnemec : ^15:35
SamYapledims: pinged odyssey4me on OSA with the etherpad as well. strong interest there15:42
SamYapledims: looks like multistr opts are not going to work here15:43
dimsSamYaple : need to refine the tree structure to support that15:44
SamYapleive been thinking for a while on how to support multistr in any standard non-hacked-ini format, and im just not seeing how15:44
SamYaplewhat would that look like in etcd or any other format?15:45
SamYaplein yaml i might call it a list, but what about cases where you specify it in multiple configs15:45
dimsexample /openstack/heat/oslo_messaging_notifications/key/1 -> "abc" /openstack/heat/oslo_messaging_notifications/key/2 -> "xyz"15:46
*** srwilkers has joined #openstack-oslo15:47
SamYapledims: so are 1 and 2 arbitrary?15:47
SamYaplewhat if you are overriding 'key' with a second config15:48
SamYapleor appending15:48
dimsSamYaple : do we allow append in the command line when we use config files? overriding would be picking up the key's values from the last url15:49
*** lpetrut has quit IRC15:51
SamYapledims: i meant more in relation to the 1/2 naming15:52
dimsSamYaple: added the question under challenges in etherpad15:52
SamYapledims: danke15:52
dimsack, let's add stuff there and see if anyone has a better idea :)15:52
*** salv-orlando has joined #openstack-oslo16:03
thervedims, Aren't lists managed after file parsing?16:03
therveI thought they were16:04
*** salv-orlando has quit IRC16:05
*** salv-orlando has joined #openstack-oslo16:05
*** eezhova has quit IRC16:11
*** salv-orlando has quit IRC16:13
*** aarefiev is now known as aarefiev_afk16:14
*** nkrinner is now known as nkrinner_afk16:30
*** e0ne has quit IRC16:31
*** yamahata has quit IRC16:32
*** Dinesh_Bhor has quit IRC16:37
*** david-lyle has joined #openstack-oslo16:42
*** pblaho has quit IRC16:45
*** Dinesh_Bhor has joined #openstack-oslo16:48
*** d0ugal has quit IRC16:55
*** mhickey has joined #openstack-oslo17:11
*** david-lyle_ has joined #openstack-oslo17:13
*** david-lyle has quit IRC17:13
*** yamahata has joined #openstack-oslo17:13
*** pblaho has joined #openstack-oslo17:22
*** eezhova has joined #openstack-oslo17:25
*** lucasagomes is now known as lucas-afk17:26
*** jaosorior has quit IRC17:45
*** mhickey has quit IRC17:45
*** tesseract has quit IRC17:49
*** browne has joined #openstack-oslo17:55
openstackgerritMerged openstack/tooz master: Switch tests to use latest etcd - 3.1.3  https://review.openstack.org/44547017:58
*** d0ugal has joined #openstack-oslo17:58
*** jpena is now known as jpena|away18:00
*** pcaruana has quit IRC18:03
*** d0ugal has quit IRC18:04
*** lpetrut has joined #openstack-oslo18:29
*** mkoderer has quit IRC18:37
*** eezhova has quit IRC18:42
*** shardy is now known as shardy_afk18:45
ihrachyssileht: fyi reported the RFE for oslo.messaging to allow to set timeout for all RPC communication as discussed during ptg: https://bugs.launchpad.net/oslo.messaging/+bug/167283618:50
openstackLaunchpad bug 1672836 in oslo.messaging "[RFE] allow to set hard RPC timeout" [Undecided,New]18:50
ihrachysas for backoff RPC client, there is already a WIP from boden and a bug: https://bugs.launchpad.net/oslo.messaging/+bug/166744518:50
openstackLaunchpad bug 1667445 in oslo.messaging "[RFE] Backing off RPC client" [Undecided,New]18:50
bodenyes, the WIP patch has had some discussion in the past, but not for awhile https://review.openstack.org/#/c/407722/18:52
*** amotoki has quit IRC18:56
*** eck` is now known as eck`gone19:18
*** jdandrea has joined #openstack-oslo19:31
*** eck`gone is now known as eck`19:52
*** ihrachys has quit IRC19:59
*** lpetrut has quit IRC20:05
*** david-lyle_ is now known as david-lyle20:12
*** e0ne has joined #openstack-oslo20:13
*** e0ne has quit IRC20:18
*** e0ne has joined #openstack-oslo20:21
*** mpotdar has joined #openstack-oslo20:22
dimsharlowja : are you thinking of reworking tooz to support what Jay is doing?20:25
*** eezhova has joined #openstack-oslo20:28
harlowjadims  the idea crossed my mind about 15 minute ago, lol20:29
dimsy saw your email and was wondering20:29
harlowjasome of the ideas maybe20:29
harlowjasome are not right imho20:29
harlowjaits really just a more capable member filtering api imho20:30
harlowjafiltering/searching20:30
harlowjaand concept of maintenance mode20:30
harlowjathe rest i believe is mappable to tooz20:30
harlowjabut ya, i'll wait on doing any work there :-P20:33
*** dimtruck is now known as zz_dimtruck20:38
openstackgerritAnthony Washington proposed openstack/oslo.policy master: Add additional param to policy.RuleDefault  https://review.openstack.org/43907020:39
*** mhickey has joined #openstack-oslo20:45
*** jdandrea has quit IRC20:58
*** mpotdar has quit IRC20:59
*** zz_dimtruck is now known as dimtruck21:03
*** jpena|away is now known as jpena|off21:07
*** e0ne has quit IRC21:15
*** e0ne has joined #openstack-oslo21:17
*** e0ne has quit IRC21:28
*** e0ne has joined #openstack-oslo21:32
*** dimtruck is now known as zz_dimtruck21:36
*** zz_dimtruck is now known as dimtruck21:37
*** mhickey has quit IRC21:38
*** e0ne has quit IRC21:42
*** srwilkers has quit IRC21:47
*** eezhova has quit IRC21:49
*** cdent has quit IRC21:57
*** ihrachys has joined #openstack-oslo22:08
*** kgiusti has left #openstack-oslo22:14
*** ihrachys has quit IRC22:16
*** boden has quit IRC22:47
*** gordc has quit IRC22:51
lifelessdhellmann: hey23:21
dhellmannlifeless : hi! how're things?23:22
lifelessdhellmann: I haven't had time to prep a PR for Python's NEWS file management yet :(23:22
lifelessdhellmann: things are good but crazy busy23:22
dhellmannlifeless : I have a local branch I'm working on, but I keep getting distracted23:22
dhellmannlet me push that somewhere you can see it23:22
lifelessdhellmann: I think we have 2 days left?23:22
dhellmannlifeless : https://github.com/dhellmann/cpython/tree/add-reno23:23
dhellmannoh, there was a deadline?23:23
dhellmanndamn23:23
dhellmannI think the things left to do are break up some of the existing news to make examples, and then to update the build to generate Misc/NEWS instead of having the file checked in23:24
lifelesshttps://github.com/python/core-workflow/issues/6#issuecomment-28450317423:24
dhellmannharlowja, jd_, sileht, bknudson_ : do any of you want to chime in on this thread about the folks asking oslo to adopt castellan? http://lists.openstack.org/pipermail/openstack-dev/2017-March/113863.html23:26
harlowjahmmmm23:26
harlowjai was thinking about it :-P23:26
dhellmannharlowja : ^^23:26
dhellmannoh, got you the first time :-)23:26
dhellmannwho am I missing. flaper87 ^^23:26
dhellmannlifeless : I missed that comment. I was traveling.23:28
*** sdague has quit IRC23:29
dhellmannlifeless : it is not at all clear to me that the python-dev team is interested in using reno, based on the comments. they seem not to recognize that the benefit is you don't have to think about things like version numbers any more.23:30
dhellmannat least in advance of writing the ntoes23:30
*** dimtruck is now known as zz_dimtruck23:31
lifelessdhellmann: that seems like education. Whats the command you're using to build Misc/NEWS - just 'reno', or does it need parameters?23:39
dhellmannlifeless : it would be something like "reno report" and then redirected to a file, but the news file currently contains info that won't be in any notes so we'll have to accommodate the legacy information somehow23:40
dhellmannI thought maybe of moving NEWS to NEWS-legacy and then concatenating that with the output of "reno report" as a temporary solution, until the news file no longer needs to include the old data23:40
lifelessok23:41
lifelesswhat info is missing?23:44
dhellmannlet me look at my notes23:45
dhellmannlifeless : https://etherpad.openstack.org/p/reno-cpython23:45

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!