Hi all, At the design summit in Austin, I took an action item after the anomaly resolution to file a spec to separate operator-set and ironic-set maintenance. Now that CI testing is done and we're making progress on other priorities, I took time today to submit the RFE bug and a draft spec. https://bugs.launchpad.net/ironic/+bug/1596107 https://review.openstack.org/334113 I want to make sure we have a consensus on the path forward before investing more time in the spec. I've defined some parts of the problem and a potential solution as I see it, but would appreciate input, especially from someone with more experience modifying existing API objects. Thanks in advance, Jay Faulkner OSIC -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160624/d877d08b/attachment.html>