<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Mar 17, 2018 at 9:49 PM, Doug Hellmann <span dir="ltr"><<a href="mailto:doug@doughellmann.com" target="_blank">doug@doughellmann.com</a>></span> wrote:</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space"><span style="color:rgb(0,0,0);font-family:BitstreamVeraSansMono-Roman;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;display:inline!important;float:none">Both of those are good ideas.</span></div></blockquote><div><br></div><div>A<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">gree. I like the socket idea a bit more as I can imagine some operators don't want config file changes automatically applied. Do we want to choose one to standardize on or allow each project (or operators, via config) the choice?</span></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space"><span style="color:rgb(0,0,0);font-family:BitstreamVeraSansMono-Roman;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;display:inline!important;float:none">I believe adding those things to oslo.service would make them available to all applications.<span class="m_6081604665436059672Apple-converted-space"> </span></span></div></blockquote><div><br></div><div>Not necessarily - this discussion started when the Keystone team was discussing how to implement this, given that keystone doesn't use oslo.service. That said, it should be easy to implement in services that don't want this dependency, so +1.</div><div><br></div><div>// jim</div></div></div></div>