<div dir="ltr"><div><div>I think it is OK that we keep the current behavior. But we need to note it in api spec clearly.<br><br></div>And I have <span class="">another</span><span class=""> question. :)<br></span></div><span class="">V1 api allows user to use "</span><span class=""><code class="">x-image-meta-id</code>" parameter to create an image. But if I specify a *deleted* image id to create an image, I will get 409 response, however I can not use "list" method to get the image. Should we fix this "bug"? Or just as a kind of </span>constraint?<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-01-27 Fei Long Wang <span dir="ltr"><<a href="mailto:flwang@cn.ibm.com" target="_blank">flwang@cn.ibm.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p><font face="sans-serif">Zhi Yan, FWIW, your concern is reasonable. Thanks for raising it. Based on the Glance v1 strategy, and backward-compatibility concern, maybe we should mark it as won't fix?</font><br>
<br>
<font face="sans-serif"><b>Brian</b></font><font face="sans-serif">, may I get your opinion on this from a product manager perspective? Thanks.</font></p><div class="im"><br>
<br>
<font face="sans-serif">Thanks & Best regards,<br>
Fei Long Wang (王飞龙)<br>
---------------------------------------------------------------------<br>
Tech Lead of Nitrogen (SME team)<br>
Cloud Solutions and OpenStack Development<br>
Tel: 8610-82450513 | T/L: 905-0513 <br>
Email: <a href="mailto:flwang@cn.ibm.com" target="_blank">flwang@cn.ibm.com</a><br>
China Systems & Technology Laboratory in Beijing<br>
---------------------------------------------------------------------<br>
</font><br>
<br>
</div><img src="cid:1__=C7BBF6FEDFB757CD8f9e8a93df938@cn.ibm.com" alt="Inactive hide details for Zhi Yan Liu ---01/27/2014 02:00:49 PM---@flwang, np at all. We can put the input in bug report as a c" border="0" height="16" width="16"><font color="#424282" face="sans-serif">Zhi Yan Liu ---01/27/2014 02:00:49 PM---@flwang, np at all. We can put the input in bug report as a comment or here anyway,</font><div class="im">
<br>
<br>
<font size="1" color="#5F5F5F" face="sans-serif">From: </font><font size="1" face="sans-serif">Zhi Yan Liu <<a href="mailto:lzy.dev@gmail.com" target="_blank">lzy.dev@gmail.com</a>></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">To: </font><font size="1" face="sans-serif">"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>>, </font><br>
</div><font size="1" color="#5F5F5F" face="sans-serif">Date: </font><font size="1" face="sans-serif">01/27/2014 02:00 PM</font><div><div class="h5"><br>
<font size="1" color="#5F5F5F" face="sans-serif">Subject: </font><font size="1" face="sans-serif">Re: [openstack-dev] [glance]A question abount the x-image-meta-property parameter.</font><br>
<hr style="color:#8091a5" align="left" noshade size="2" width="100%"><br>
<br>
<br>
<font size="3" face="serif">@flwang, np at all. We can </font><font face="Arial">put the input in bug report as a comment or here anyway, as far as it can let us/me know the gains/advantages on this "fix".</font><br>
<br>
<font face="Arial">I'd like to know whether there is a </font><font size="3" face="serif">backward-compatibility issue, but seems it's not a big deal? To keep the </font><font size="3" face="sans-serif">image property be case-sensitive is make sense, at last it is better if we keep same </font><font size="3" face="serif">property name as client provided.</font><br>
<br>
<font size="3" face="sans-serif">zhiyan</font><br>
<br>
<font size="3" face="serif">On Mon, Jan 27, 2014 at 11:54 AM, Fei Long Wang <</font><a href="mailto:flwang@cn.ibm.com" target="_blank"><font size="3" color="#0000FF" face="serif"><u>flwang@cn.ibm.com</u></font></a><font size="3" face="serif">> wrote:</font>
<ul style="padding-left:9pt"><font size="3" face="sans-serif">Zhi Yan, </font><font size="3" face="serif"><br>
</font><font size="3" face="sans-serif"><br>
I think you're talking about backward-compatibility, right? I would say it's possible, just like the v2 is not compatible with v1 against this. So that's why I would like to see a bug is opened to track this and then we get also some comments from the end user/product manager perspective to decide to mark it as won't fix or go ahead. </font>
<p><font size="3" face="sans-serif"><br>
Thanks & Best regards,<br>
Fei Long Wang (王飞龙)<br>
---------------------------------------------------------------------<br>
Tech Lead of Nitrogen (SME team)<br>
Cloud Solutions and OpenStack Development<br>
Tel: 8610-82450513 | T/L: 905-0513 <br>
Email: </font><a href="mailto:flwang@cn.ibm.com" target="_blank"><font size="3" color="#0000FF" face="sans-serif"><u>flwang@cn.ibm.com</u></font></a><font size="3" face="sans-serif"><br>
China Systems & Technology Laboratory in Beijing<br>
---------------------------------------------------------------------</font><font size="3" face="serif"><br>
<br>
</font><br>
<img src="cid:1__=C7BBF6FEDFB757CD8f9e8a93df938@cn.ibm.com" alt="Inactive hide details for Zhi Yan Liu ---01/27/2014 01:02:40 AM---One quick question, do you think there is a potential backwar" height="16" width="16"><font size="3" color="#424282" face="sans-serif">Zhi Yan Liu ---01/27/2014 01:02:40 AM---One quick question, do you think there is a potential backward-capability breaking issue for end use</font><font size="3" face="serif"><br>
</font><font size="1" color="#5F5F5F" face="sans-serif"><br>
From: </font><font size="1" face="sans-serif">Zhi Yan Liu <</font><a href="mailto:lzy.dev@gmail.com" target="_blank"><font size="1" color="#0000FF" face="sans-serif"><u>lzy.dev@gmail.com</u></font></a><font size="1" face="sans-serif">></font><font size="1" color="#5F5F5F" face="sans-serif"><br>
To: </font><font size="1" face="sans-serif">"OpenStack Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><font size="1" color="#0000FF" face="sans-serif"><u>openstack-dev@lists.openstack.org</u></font></a><font size="1" face="sans-serif">>, </font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Cc: </font><font size="1" face="sans-serif">"OpenStack Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><font size="1" color="#0000FF" face="sans-serif"><u>openstack-dev@lists.openstack.org</u></font></a><font size="1" face="sans-serif">></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Date: </font><font size="1" face="sans-serif">01/27/2014 01:02 AM</font><br>
<font size="1" color="#5F5F5F" face="sans-serif"><br>
Subject: </font><font size="1" face="sans-serif">Re: [openstack-dev] [glance]A question abount the x-image-meta-property parameter.</font><font size="3" face="serif"><br>
</font></p><hr align="left" noshade size="2" width="100%"><font size="3" face="serif"><br>
<br>
<br>
One quick question, do you think there is a potential backward-capability breaking issue for end user or ISV if we remove existing standardizing/normalizing logic? I'd like to know the gains/advantages on this "fix".<br>
<br>
thanks,<br>
zhiyan<br>
<br>
Sent from my iPad<br>
<br>
On 2014年1月26日, at 23:49, Fei Long Wang <</font><a href="mailto:flwang@cn.ibm.com" target="_blank"><font size="3" color="#0000FF" face="serif"><u>flwang@cn.ibm.com</u></font></a><font size="3" face="serif">> wrote:</font>
<ul style="padding-left:36pt"><font size="3" face="sans-serif"><br>
Hey Jay, thanks for calling my name correctly :) <br>
<br>
Wang Hong, feel free to open a bug to track this. And we can get more info/comments when the patch is reviewed. Thanks.</font><font size="3" face="serif"><br>
</font><font size="3" face="sans-serif"><br>
<br>
Thanks & Best regards,<br>
Fei Long Wang (王飞龙)<br>
---------------------------------------------------------------------<br>
Tech Lead of Nitrogen (SME team)<br>
Cloud Solutions and OpenStack Development<br>
Tel: 8610-82450513 | T/L: 905-0513 <br>
Email: </font><a href="mailto:flwang@cn.ibm.com" target="_blank"><font size="3" color="#0000FF" face="sans-serif"><u>flwang@cn.ibm.com</u></font></a><font size="3" face="sans-serif"><br>
China Systems & Technology Laboratory in Beijing<br>
---------------------------------------------------------------------</font><font size="3" face="serif"><br>
<br>
<br>
<graycol.gif></font><font size="3" color="#424282" face="sans-serif">Jay Pipes ---01/26/2014 11:20:40 PM---On Sun, 2014-01-26 at 18:48 +0800, Fei Long Wang wrote: > Hi Wang Hong,</font><font size="1" color="#5F5F5F" face="sans-serif"><br>
<br>
From: </font><font size="1" face="sans-serif">Jay Pipes <</font><a href="mailto:jaypipes@gmail.com" target="_blank"><font size="1" color="#0000FF" face="sans-serif"><u>jaypipes@gmail.com</u></font></a><font size="1" face="sans-serif">></font><font size="1" color="#5F5F5F" face="sans-serif"><br>
To: </font><font size="1" face="sans-serif">Fei Long Wang/China/IBM@IBMCN, </font><font size="1" color="#5F5F5F" face="sans-serif"><br>
Cc: </font><font size="1" face="sans-serif">"OpenStack Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><font size="1" color="#0000FF" face="sans-serif"><u>openstack-dev@lists.openstack.org</u></font></a><font size="1" face="sans-serif">></font><font size="1" color="#5F5F5F" face="sans-serif"><br>
Date: </font><font size="1" face="sans-serif">01/26/2014 11:20 PM</font><font size="1" color="#5F5F5F" face="sans-serif"><br>
Subject: </font><font size="1" face="sans-serif">Re: [openstack-dev] [glance]A question abount the x-image-meta-property parameter.</font><font size="3" face="serif"> </font>
<p></p><hr align="left" noshade size="2" width="100%"><font size="3" face="serif"><br>
</font><tt><font size="3"><br>
<br>
On Sun, 2014-01-26 at 18:48 +0800, Fei Long Wang wrote:<br>
> Hi Wang Hong,<br>
> <br>
> Good catch. I think the issue is caused by line 244-246, see<br>
> </font></tt><a href="https://github.com/openstack/glance/blob/master/glance/common/utils.py#L244" target="_blank"><tt><font size="3" color="#0000FF"><u>https://github.com/openstack/glance/blob/master/glance/common/utils.py#L244</u></font></tt></a><tt><font size="3"> For the case-matter issue, I think it's a bug. But as for the - to _, I would like to listen Jay's opinion since who is the original author. And obviously, it's intentional change.<br>
<br>
Hi Wang Hong adnd Fei Long,<br>
<br>
It's been a long time since I wrote that :) To be honest, I'm not sure<br>
why -- other than just standardizing/normalizing the input, we did that.<br>
Perhaps it had something to do with vendor-specific properties that had<br>
a prefix that used hyphens, but I'm really not sure... perhaps I am<br>
getting too old :)<br>
<br>
Best,<br>
-jay<br>
<br>
> Inactive hide details for 王宏 ---01/26/2014 05:14:02 PM---Hi all. If<br>
> I use the following command to create an image:王宏 ---01/26/2014<br>
> 05:14:02 PM---Hi all. If I use the following command to create an<br>
> image:<br>
> <br>
> From: 王宏 <</font></tt><a href="mailto:w.wanghong1@gmail.com" target="_blank"><tt><font size="3" color="#0000FF"><u>w.wanghong1@gmail.com</u></font></tt></a><tt><font size="3">><br>
> To: </font></tt><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><tt><font size="3" color="#0000FF"><u>openstack-dev@lists.openstack.org</u></font></tt></a><tt><font size="3">, <br>
> Date: 01/26/2014 05:14 PM<br>
> Subject: [openstack-dev] [glance]A question abount the<br>
> x-image-meta-property parameter.<br>
> <br>
> <br>
> <br>
> ______________________________________________________________________<br>
> <br>
> <br>
> <br>
> Hi all.<br>
> <br>
> If I use the following command to create an image: <br>
> curl -i -H "X-Auth-Token:268c536db05b435bb6e631158744e3f6" -H<br>
> "x-image-meta-property-IMAGE-TYPE:xxx" -H "x-image-meta-name:test" -X<br>
> POST </font></tt><a href="http://127.0.0.1:9292/v1/images" target="_blank"><tt><font size="3" color="#0000FF"><u>http://127.0.0.1:9292/v1/images</u></font></tt></a><tt><font size="3"><br>
> <br>
> I will get the following results:<br>
> {"image": {"status": "queued", "deleted": false, "container_format":<br>
> null, "min_ram": 0, "updated_at": "2014-01-26T08:51:54", "owner":<br>
> "9a38c1cda5344dd288331b988739c834", "min_disk": 0, "is_public": false,<br>
> "deleted_at": null, "id": "696ab97d-0e6f-46f1-8570-b6db707a748b",<br>
> "size": 0, "name": "test", "checksum": null, "created_at":<br>
> "2014-01-26T08:51:54", "disk_format": null, "properties":<br>
> {"image_type": "xxx"}, "protected": false}}<br>
> <br>
> The capital letters in the property will be converted to lowercase<br>
> letters and "-" will be converted to "_"("IMAGE-TYPE"=>"image_type").<br>
> <br>
> Is it a bug? Thanks.<br>
> <br>
> Best regards.<br>
> wanghong_______________________________________________<br>
> OpenStack-dev mailing list<br>
> </font></tt><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank"><tt><font size="3" color="#0000FF"><u>OpenStack-dev@lists.openstack.org</u></font></tt></a><tt><font size="3"><br>
> </font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><tt><font size="3" color="#0000FF"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></tt></a><tt><font size="3"><br>
> <br>
</font></tt><font size="3" face="serif"><br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list</font><font size="3" color="#0000FF" face="serif"><u><br>
</u></font><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank"><font size="3" color="#0000FF" face="serif"><u>OpenStack-dev@lists.openstack.org</u></font></a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><font size="3" color="#0000FF" face="serif"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a><tt><font size="3">_______________________________________________<br>
OpenStack-dev mailing list</font></tt><tt><font size="3" color="#0000FF"><u><br>
</u></font></tt><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank"><tt><font size="3" color="#0000FF"><u>OpenStack-dev@lists.openstack.org</u></font></tt></a><tt><font size="3" color="#0000FF"><u><br>
</u></font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><tt><font size="3" color="#0000FF"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></tt></a><font size="3" face="serif"><br>
</font><p></p></ul>
<font size="3" face="serif"><br>
_______________________________________________<br>
OpenStack-dev mailing list</font><font size="3" color="#0000FF" face="serif"><u><br>
</u></font><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank"><font size="3" color="#0000FF" face="serif"><u>OpenStack-dev@lists.openstack.org</u></font></a><font size="3" color="#0000FF" face="serif"><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><font size="3" color="#0000FF" face="serif"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a><font size="3" face="serif"><br>
</font><p></p></ul>
<tt><font>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
</font></tt><tt><font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></font></tt><tt><font><br>
</font></tt><br>
</div></div><p></p></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a 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>
<br></blockquote></div><br></div>