| Summary: | [Docs] Add more details for edit VM and templates | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Aziza Karol <akarol> |
| Component: | Documentation | Assignee: | Red Hat CloudForms Documentation <cloudforms-docs> |
| Status: | CLOSED WONTFIX | QA Contact: | Red Hat CloudForms Documentation <cloudforms-docs> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.7.0 | CC: | adahms, hhudgeon, istein, jhardy, obarenbo |
| Target Milestone: | GA | ||
| Target Release: | cfme-future | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | doc | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-10-09 00:03:59 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Aziza Karol
2016-11-28 06:56:16 UTC
Greg McCullough
12/15/16
As I recall, the "Custom Identifier" field was added at the request of a user so they could set a value of their choosing to identify the VM. The feature was implemented by storing the value in a custom attribute field named "custom_1". (At the time custom_# fields were direct columns on the vms table.)
It is not used internally or by the provider.
John Hardy
1/3/16
We should document the setting of Custom Identifier and Description as these are both available in the UI as stated above.
The setting of custom_2 or > can be done in automate using
vm.custom_set('custom_2', ’TWO')
And shows up in the UI too, should also be documented though probably the example should be in the automate guide with a reference to that in the UI guide for Ops.
Thank you for raising this bug. We have evaluated this request, and while we recognize that it is a valid request for the documentation, we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Andrew Dahms. |