Hi,
I'm working on bug #1420848 which addresses the issue that doing a "service-disable" followed by a "service-enable" against a "down" compute node will result in the compute node going "up" for a while, possibly causing delays to operations that try to schedule on that compute node.
The proposed solution is to add a new "reported_at" field in the DB schema to track when the service calls _report_state().
The backend is straightforward, but I'm trying to figure out the best way to represent this via the REST API response.
Currently we response includes an "updated_at" property, which maps directly to the auto-updated "updated_at" field in the database.
Would it be acceptable to just put the "reported_at" value (if it exists) in the "updated_at" property? Logically the "reported_at" value is just a determination of when the service updated its own state, so an argument could be made that this shouldn't break anything.
Otherwise, by my reading of "https://wiki.openstack.org/wiki/APIChangeGuidelines#Generally_Considered_OK"; it seems like if I wanted to add a new "reported_at" property I would need to do it via an API extension.
Anyone have opinions? Chris __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
