{"push_id":809440404,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"cfa09c353fe08b04891e57d36064480f944f5703","before":"78fcfb66d098c74cc9fb678951f1fd1a16340efa","commits":[{"sha":"cfa09c353fe08b04891e57d36064480f944f5703","author":{"email":"59e5b8140de97cc91c3fb6c5342dce948469af8c@redhat.com","name":"Juan Hernandez"},"message":"restapi: Remove scheduling policy built-in names and thresholds\n\nIn the past the specification of scheduling policies for clusters was\nbased in built-in names and thresholds. For example a cluster that used\nthe evenly distributed scheduling policy was represented as follows:\n\n  <cluster>\n    <name>mycluster</name>\n    <scheduling_policy>\n      <policy>evenly_distributed</policy>\n      <thresholds high=\"80\" duration=\"120\"/>\n    </scheduling_policy>\n    ...\n  </cluster>\n\nThis mechanism was replaced with a top level /schedulingpolicies\ncollection where scheduling policies can be defined with arbitrary names\nand properties. For example, the same scheduling policy is represented\nas follows in that top level collection:\n\n  <scheduling_policy>\n    <name>evenly_distributed</name>\n    <properties>\n      <property>\n        <name>CpuOverCommitDurationMinutes</name>\n        <value>2</value>\n      </property>\n      <property>\n        <name>HighUtilization</name>\n        <value>80</value>\n      </property>\n    </properties>\n  </scheduling_policy>\n\nThe representation of the cluster references the scheduling policy with\nits identifier:\n\n  <cluster>\n    <name>mycluster</name>\n    <scheduling_policy id=\"...\"/>\n    ...\n  </cluster>\n\nTo preserve backwards compatibility the old \"policy\" and \"thresholds\"\nelements were preserved. The scheduling policy representation embedded\nwithin the cluster was also preserved. All these things have been\ncompletely removed now, so the only way to specify a scheduling policy\nwhen retrieving, creating or updating a cluster is to reference an\nexisting one using its identifier. For example, when retrieving a\ncluster only the \"id\" (and \"href\") will be populated:\n\n  GET /clusters/{cluster:id}\n  <cluster>\n    ...\n    <scheduling_policy id=\"...\" href=\"...\"/>\n    ...\n  </cluster>\n\nWhen creating or updating a cluster only the \"id\" will be accepted.\n\nChange-Id: Iefabfc9b1d81ac650c2a7e352e9cbef9f1e63b49\nSigned-off-by: Juan Hernandez <juan.hernandez@redhat.com>","distinct":true,"url":"https://api.github.com/repos/oVirt/ovirt-engine/commits/cfa09c353fe08b04891e57d36064480f944f5703"}]}