<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace">Hi,</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">So this email is relevant to my interests as an operator. =)</div><div class="gmail_extra">
<br><div class="gmail_quote">On Tue, Jul 11, 2017 at 9:35 PM, Lance Bragstad <span dir="ltr"><<a href="mailto:lbragstad@gmail.com" target="_blank">lbragstad@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p><b>The future of the templated catalog backend</b><br></p>
<p>Some issues were uncovered, or just resurfaced, with the
templated catalog backend. The net of the discussion boiled down
to - do we fix it or remove it? The answer actually ended up being
both. It was determined that instead of trying to maintain and fix
the existing templated backend, we should deprecate it for removal
[0]. Since it does provide some value, it was suggested that we
can start implementing a new backend based on YAML to fill the
purpose instead. The advantage here is that the approach is
directed towards a specific format (YAML). This should hopefully
make things easier for both developers and users.</p>
<p>[0] <a class="gmail-m_4834420050901709547moz-txt-link-freetext" href="https://review.openstack.org/#/c/482714/" target="_blank">https://review.openstack.org/#<wbr>/c/482714/</a><span style="font-family:monospace,monospace"></span></p></div></blockquote><div><div class="gmail_default" style="font-family:monospace,monospace;display:inline"><br></div></div><div><div class="gmail_default" style="font-family:monospace,monospace;display:inline">We have been exclusively using the templated catalog backend for at least 5 years without any major issues. And it looks like we are now among the < 3% using templated according to the April 2017 user survey. </div><span style="color:rgb(51,51,51);font-family:"Helvetica Neue";font-size:12px">¯\_(</span><span class="gmail-s1" style="color:rgb(51,51,51)">ツ</span><span style="color:rgb(51,51,51);font-family:"Helvetica Neue";font-size:12px">)_/¯</span></div>
<div><div class="gmail_default" style="font-family:monospace,monospace;display:inline"><br></div></div><div><div class="gmail_default" style="display:inline"><font face="monospace, monospace">We choose the templated catalog backend for its simplicity (especially with our CMS) and because it makes no sense (to me) to use and rely on an </font></div><span style="font-family:monospace,monospace">SQL server to serve what is essentially static content<div class="gmail_default" style="display:inline">.</div></span><br></div><div><span style="font-family:monospace,monospace"><div class="gmail_default" style="display:inline"><br></div></span></div><div><span style="font-family:monospace,monospace">Regarding the v3 catalog support, we do have an in-house fix we intended to upstream</span><div class="gmail_default" style="font-family:monospace,monospace;display:inline"> very soon (and just did right now)</div><span style="font-family:monospace,monospace">. [1]</span><span style="font-family:monospace,monospace"><div class="gmail_default" style="display:inline"><br></div></span></div><div><span style="font-family:monospace,monospace"><div class="gmail_default" style="display:inline"><br></div></span></div><div><div><span style="font-family:monospace,monospace">So if </span><span style="font-family:monospace,monospace">the templated catalog backend</span><font face="monospace, monospace"> gets deprecated, </font><div class="gmail_default" style="font-family:monospace,monospace;display:inline">my wish would be to have access to</div><font face="monospace, monospace"> a<div class="gmail_default" style="font-family:monospace,monospace;display:inline">n alternate</div><div class="gmail_default" style="font-family:monospace,monospace;display:inline"> file based</div></font><div class="gmail_default" style="font-family:monospace,monospace;display:inline"> implementation, a production grade implementation</div><font face="monospace, monospace"> ready to be used</font><div class="gmail_default" style="display:inline"><font face="monospace, monospace"> before I get spammed with deprecation warnings in the keystone logs.</font></div></div></div><div><div class="gmail_default" style="display:inline"><font face="monospace, monospace"><br></font></div></div><div><div class="gmail_default" style="display:inline"><font face="monospace, monospace">Thanks</font></div></div><div><span style="font-family:monospace,monospace"><br></span></div><div><div class="gmail_default" style="font-family:monospace,monospace;display:inline">[1] <a href="https://review.openstack.org/#/c/482766/">https://review.openstack.org/#/c/482766/</a></div></div><div><div class="gmail_default" style="font-family:monospace,monospace;display:inline"><br></div></div><div><div class="gmail_default" style="font-family:monospace,monospace;display:inline">--</div></div><div><div class="gmail_default" style="font-family:monospace,monospace;display:inline">Mathieu</div></div></div><br></div></div>