Bug 1476010
| Summary: | [RFE] Unable to reference vmware customization spec when deploying via REST API | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Ryan Spagnola <rspagnol> |
| Component: | Automate | Assignee: | drew uhlmann <duhlmann> |
| Status: | CLOSED WONTFIX | QA Contact: | Dave Johnson <dajohnso> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.8.0 | CC: | gtanzill, jhardy, jocarter, mfeifer, mkanoor, obarenbo, rspagnol, smallamp, tfitzger |
| Target Milestone: | GA | Keywords: | FutureFeature |
| Target Release: | cfme-future | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-01-25 20:25:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | Feature | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | CFME Core | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 4
Jillian Tullo
2017-10-17 17:24:14 UTC
Ryan - We never supported passing sysprep_custom_spec directly through the API call so I would say that part is an RFE. (Do we want to use this ticket for the RFE or create a new one?) The usual implementation is that the custom_spec is determined in automate or passed as part of the "additional_values" property to automate, then automate can call the "set_customization_spec" method. See https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.5/html/methods_available_for_automation/chap_methods_available_for_use_with_cloudforms_management_engine#sect_vm_provision_task_miq_provision (Search for "set_customization_spec") Do you have any details on the work-around they implemented? I assume it would be using the logic mentioned above. I am not aware of any open issues around this feature. Drew - We can discuss how to implement this directory from the API call. I believe it will require refactoring the set_customization_spec method so that it can be called from the workflow. See https://github.com/ManageIQ/manageiq/blob/master/app/models/mixins/miq_provision_mixin.rb#L186 |