<html><body>
<p><font size="2" face="sans-serif">I would think a on v2 extension is needed</font><br>
<font size="2" face="sans-serif">for v2.1 , mircoversion is a way but not very sure it's needed.</font><br>
<br>
<font size="2" face="sans-serif">Best Regards! <br>
<br>
Kevin (Chen) Ji ¼Í ³¿<br>
<br>
Engineer, zVM Development, CSTL<br>
Notes: Chen CH Ji/China/IBM@IBMCN Internet: jichenjc@cn.ibm.com<br>
Phone: +86-10-82454158<br>
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC </font><br>
<br>
<img width="16" height="16" src="cid:1__=C7BBF496DFC56CF28f9e8a93df938@cn.ibm.com" border="0" alt="Inactive hide details for Chris Friesen ---03/11/2015 04:35:01 PM---Hi, I'm working on bug #1420848 which addresses the issue t"><font size="2" color="#424282" face="sans-serif">Chris Friesen ---03/11/2015 04:35:01 PM---Hi, I'm working on bug #1420848 which addresses the issue that doing a</font><br>
<br>
<font size="1" color="#5F5F5F" face="sans-serif">From: </font><font size="1" face="sans-serif">Chris Friesen <chris.friesen@windriver.com></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)" <openstack-dev@lists.openstack.org></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Date: </font><font size="1" face="sans-serif">03/11/2015 04:35 PM</font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Subject: </font><font size="1" face="sans-serif">[openstack-dev] [nova] need input on possible API change for bug #1420848</font><br>
<hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br>
<br>
<br>
<tt><font size="2"><br>
Hi,<br>
<br>
I'm working on bug #1420848 which addresses the issue that doing a <br>
"service-disable" followed by a "service-enable" against a "down" compute node <br>
will result in the compute node going "up" for a while, possibly causing delays <br>
to operations that try to schedule on that compute node.<br>
<br>
The proposed solution is to add a new "reported_at" field in the DB schema to <br>
track when the service calls _report_state().<br>
<br>
The backend is straightforward, but I'm trying to figure out the best way to <br>
represent this via the REST API response.<br>
<br>
Currently we response includes an "updated_at" property, which maps directly to <br>
the auto-updated "updated_at" field in the database.<br>
<br>
Would it be acceptable to just put the "reported_at" value (if it exists) in the <br>
"updated_at" property? Logically the "reported_at" value is just a <br>
determination of when the service updated its own state, so an argument could be <br>
made that this shouldn't break anything.<br>
<br>
Otherwise, by my reading of <br>
"</font></tt><tt><font size="2"><a href="https://wiki.openstack.org/wiki/APIChangeGuidelines#Generally_Considered_OK">https://wiki.openstack.org/wiki/APIChangeGuidelines#Generally_Considered_OK</a></font></tt><tt><font size="2">" it <br>
seems like if I wanted to add a new "reported_at" property I would need to do it <br>
via an API extension.<br>
<br>
Anyone have opinions?<br>
<br>
Chris<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
</font></tt><tt><font size="2"><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></font></tt><tt><font size="2"><br>
<br>
</font></tt><br>
</body></html>