<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">There was a patch recently merged ([1]) that works around a bad decision that Cinder and Mistral team</div><div class="">(possible someone else too) to include api version in the name of service type in the catalog. For</div><div class="">example, for Mistral it was initially “workflow” when we were working on a POC of the project but once</div><div class="">we realized that we created a stable API we called it “v2” and changed service type to “workflowv2”.</div><div class="">Now we see it was a bad thing to do (see details in the patch).</div><div class=""><br class=""></div><div class="">I wonder if we can do something to get this fixed in long term. Ideally, i’d like to make it just “workflow”</div><div class="">again but that seems to be not easy now.</div><div class=""><br class=""></div><div class="">Would appreciate your input.</div><div class=""><br class=""></div><div class="">[1] <a href="https://review.openstack.org/#/c/434344/" class="">https://review.openstack.org/#/c/434344/</a></div><div class=""><br class=""></div><div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Renat Akhmerov</div><div class="">@Nokia</div></div>
</div>
<br class=""></div></body></html>