Description of problem:
Currently the template entity in REST API is not consistent with the template menu in UI, as in UI one can define a specific host and an affinity for the template (similar to these configurations for vm), but on API, as opposed to vm entity, the template entity does not include the placement_policy attribute and it's sub-attributes that correspond to these options in UI.
This requires one of two possible solutions:
1. Remove/Blank out these configurations on the template menu in UI if we decide they should be only configurable on vm level.
2. Add/show the placement_policy attribute and it's sub attributes in REST API.
Version-Release number of selected component (if applicable):
rhevm-220.127.116.11-0.1.el7.noarch and down
Steps to Reproduce:
1. Set a specific host and set no migration for a template via UI->template menu -> Host sub tab
2. Call get on that template via REST API
The template xml doesn't include the information you just configured in UI (as explained above)
The template xml should reflect all the template's configurations including those added in step 1.
We won't be perusing this issue any more. If someone needs it, patches are welcomed.