<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:10pt"><div id="yui_3_16_0_1_1410305425099_360014" dir="ltr">We manage a fairly large nova-baremetal installation at Yahoo. And while we've developed tools to hit the nova-bm API, we're planning to move to ironic without any support for the nova BM API. Definitely no interest in the proxy API from our end. </div><div id="yui_3_16_0_1_1410305425099_360014" dir="ltr"><br></div><div id="yui_3_16_0_1_1410305425099_360014" dir="ltr">Sometimes you just need to let a thing die. </div><div id="yui_3_16_0_1_1410305425099_360014" dir="ltr"><br></div><div id="yui_3_16_0_1_1410305425099_360014" dir="ltr">-James</div><div id="yui_3_16_0_1_1410305425099_360014" dir="ltr"><br></div><div></div><div id="yui_3_16_0_1_1410305425099_359993"> </div><div id="yui_3_16_0_1_1410305425099_360013">:)=</div> <div class="qtdSeparateBR"><br><br></div><div class="yahoo_quoted" style="display: block;"> <div style="font-family: HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 10pt;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div dir="ltr"> <font size="2" face="Arial"> On Wednesday, September 10, 2014 12:51 PM, Ben Nemec <openstack@nemebean.com> wrote:<br> </font> </div> <br><br> <div class="y_msg_container">-----BEGIN PGP SIGNED MESSAGE-----<br clear="none">Hash: SHA1<br clear="none"><br clear="none">On 09/10/2014 02:26 PM, Dan Smith wrote:<br clear="none">>> 1) Is this tested anywhere? There are no unit tests in the patch<br clear="none">>> and it's not clear to me that there would be any Tempest coverage<br clear="none">>> of this code path. Providing this and having it break a couple<br clear="none">>> of months down the line seems worse than not providing it at all.<br clear="none">>> This is obviously fixable though.<br clear="none">> <br clear="none">> AFAIK, baremetal doesn't have any tempest-level testing at all<br clear="none">> anyway. However, I don't think our proxy code breaks, like, ever. I<br clear="none">> expect that unit tests for this stuff is plenty sufficient.<br clear="none"><br clear="none">Right, but this would actually be running against Ironic, which does<br clear="none">have Tempest testing. It might require some client changes to be able<br clear="none">to hit a Baremetal API instead of Ironic though.<br clear="none"><br clear="none">> <br clear="none">>> 2) If we think maintaining compatibility for existing users is<br clear="none">>> that important, why aren't we proxying everything? Is it too <br clear="none">>> difficult/impossible due to the differences between Baremetal<br clear="none">>> and Ironic? And if they're that different, does it still make<br clear="none">>> sense to allow one to look like the other? As it stands, this<br clear="none">>> isn't going to let deployers use their existing tools without<br clear="none">>> modification anyway.<br clear="none">> <br clear="none">> Ideally we'd proxy everything, based on our current API<br clear="none">> guarantees. However, I think the compromise of just the show/index<br clear="none">> stuff came about because it would be extremely easy to do, provide<br clear="none">> some measure of continuity, and provide us a way to return<br clear="none">> something nicer for the create/update operations than a 500. It<br clear="none">> seemed like a completely fair and practical balance.<br clear="none"><br clear="none">Fair enough. I'm still not crazy about it, but since it already<br clear="none">exists and you say these interfaces don't require much maintenance I<br clear="none">guess that takes care of my major concerns.<br clear="none"><br clear="none">- -Ben<br clear="none">-----BEGIN PGP SIGNATURE-----<br clear="none">Version: GnuPG v1<br clear="none"><br clear="none">iQEcBAEBAgAGBQJUEKsAAAoJEDehGd0Fy7uqM3YIAKaqJPCwyS1l3NoKhj7qmGlT<br clear="none">wqdPspI2LyVgnHY62iq73O6FSpmEp0JzEcuBxHi21gK3tIBrvRr+mOsNtGNoj7Of<br clear="none">84YmcFyWgBR75rRDSLLnVu7rs1LJ0jpGwVzWDi/vmzVoxWdNXwSx223mQTwi9gJ3<br clear="none">n+Rgf0HYOKUwGgDVDpyWFv1DUBo/Hgc3ZdG8pzwnEqONN0bmRlBQMZRJrl2+8Jvj<br clear="none">zTYxDmunWp8FbTdKE80JcQ1YQYjmg4anCzaH0MEwax+j6lxu8MwEtM61ISJ7vV3L<br clear="none">KqTSW2OrjtqKY/9oHSnKiBuD9RInyWhML6pq8jsniadPw+TOatJ4PZaCyTS9XvI=<br clear="none">=cSmK<br clear="none">-----END PGP SIGNATURE-----<div class="yqt8640577841" id="yqtfd84352"><br clear="none"><br clear="none">_______________________________________________<br clear="none">OpenStack-dev mailing list<br clear="none"><a shape="rect" ymailto="mailto:OpenStack-dev@lists.openstack.org" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br clear="none"><a shape="rect" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br clear="none"></div><br><br></div> </div> </div> </div> </div></body></html>