Bug 1324962 - Template initialization parameters do not exist in API
Summary: Template initialization parameters do not exist in API
Keywords:
Status: CLOSED DUPLICATE of bug 1253710
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: 3.6.5.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Juan Hernández
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-07 17:00 UTC by sefi litmanovich
Modified: 2016-04-07 18:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-07 18:46:02 UTC
oVirt Team: Infra
Embargoed:
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description sefi litmanovich 2016-04-07 17:00:42 UTC
Description of problem:

Cloud init or sysprep configuration is available in template level on the webadmin, exactly like vm entity. Setting some cloud init parameters in template will be inherited successfully to a vm created from the template as it should.

Problem is that while this is possible under webadmin, the initialization attribute and it's sub-attributes do not exist under a template entity in then API, so setting these values through API is impossible.

The solution in my opinion should be one of two:

1. we add initialization attribute to template, same as in vm so API and webadmin work the same.

2. Decide that this should not be configured in template level (which might be the way we want to do it, since initialization should be for a specific vm), in which case the initial run tab in template menu should disappear, or blocked or any such solution. 

Version-Release number of selected component (if applicable):
rhevm-3.6.5.1-0.1.el6

How reproducible:
always

Steps to Reproduce:
1. Create a template in webadmin -> set some values under 'initial run' sub-menu.
2. With sdk or REST API GET template entity


Actual results:
The values you set under 'initial run' are nowhere to be found.

Expected results:
as mentioned above, 1 of the 2 solutions.

Comment 1 Juan Hernández 2016-04-07 18:46:02 UTC
This will be added in version 4.0 of the engine, see bug 1253710.

*** This bug has been marked as a duplicate of bug 1253710 ***


Note You need to log in before you can comment on or make changes to this bug.