<div dir="ltr">Tatiana,<div>Thanks for filing the bug and putting in a patch!</div><div>Cheers,</div><div>Praveen</div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Aug 17, 2016 at 1:45 AM Tatiana Ovtchinnikova <<a href="mailto:t.v.ovtchinnikova@gmail.com">t.v.ovtchinnikova@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Filed a bug: <a href="https://bugs.launchpad.net/horizon/+bug/1614000" target="_blank">https://bugs.launchpad.net/horizon/+bug/1614000</a></div><div dir="ltr"><br><div><div class="gmail_extra"><br><div class="gmail_quote">2016-08-17 11:19 GMT+03:00 Tatiana Ovtchinnikova <span dir="ltr"><<a href="mailto:t.v.ovtchinnikova@gmail.com" target="_blank">t.v.ovtchinnikova@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>It is definitely a bug in Horizon. The additional columns "Implementation", "Component" and "Resource" are representative for a limited resource type group only. Since Heat allows to specify a URL as a resource type, we should not use these columns at all. "Type" column and filter will do just the same trick.<span><font color="#888888"><br><br></font></span></div><span><font color="#888888">Tatiana.</font></span><div><div><br><div><div><div class="gmail_extra"><br><div class="gmail_quote">2016-08-17 1:22 GMT+03:00 Rob Cresswell <span dir="ltr"><<a href="mailto:robert.cresswell@outlook.com" target="_blank">robert.cresswell@outlook.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p dir="ltr">This sounds like a bug on the Horizon side. There is/was a patch regarding a similar issue with LBaaS v2 resources too. It's likely just an incorrect assumption in the logic processing these names.</p><span><font color="#888888">
<p dir="ltr">Rob</p></font></span><div><div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 16 Aug 2016 11:03 p.m., "Zane Bitter" <<a href="mailto:zbitter@redhat.com" target="_blank">zbitter@redhat.com</a>> wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
On 16/08/16 17:43, Praveen Yalagandula wrote:<br>
> Hi all,<br>
> We have developed some heat resources for our custom API server. We<br>
> followed the instructions in the development guide<br>
> at <a href="http://docs.openstack.org/developer/heat/pluginguide.html" rel="noreferrer" target="_blank">
http://docs.openstack.org/developer/heat/pluginguide.html</a> and got<br>
> everything working. However, the Horizon "Resource Types" panel is<br>
> returning a 500 error with "TemplateSyntaxError: u'resource'" message.<br>
><br>
> Upon further debugging, we found that the Horizon is expecting all Heat<br>
> resource type names to be of form<br>
> <implementation>::<component>::<resource>. However, we didn't see this<br>
> requirement in the heat development documents. Some of our resource<br>
> types have just two words (e.g., "Avi::Pool"). Heat itself didn't care<br>
> about these names at all.<br>
<br>
Given that Heat has a REST API specifically for validating templates,<br>
it's surprising that Horizon would implement its own, apparently<br>
incorrect, validation.<br>
<br>
> Question: Is there a general consensus is to enforce<br>
> the <implementation>::<component>::<resource> format for type names?<br>
<br>
No. We don't really care what you call them (although using OS:: or<br>
AWS:: as a prefix for your own custom types would be very unwise). In<br>
fact, Heat allows you to specify a URL of a template file as a resource<br>
type, and it sounds like that might run afoul of the same restriction.<br>
<br>
> If so, can we please update the heat plugin guide to reflect this?<br>
> If not, we can file it is as a bug in Horizon.<br>
<br>
+1 for bug in Horizon.<br>
<br>
- ZB<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
</div>
</div></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div></div></div></div></div>
</blockquote></div><br></div></div></div>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>