| Summary: | [RFE] Everything created from catalog items are not necessarily "services"(e.g. Not a Virtual Machine) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Mike Dahlgren <mdahlgre> | ||||
| Component: | Provisioning | Assignee: | John Hardy <jhardy> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Shveta <sshveta> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 5.6.0 | CC: | cpelland, jhardy, obarenbo, simaishi | ||||
| Target Milestone: | GA | Keywords: | FutureFeature | ||||
| Target Release: | 5.7.5 | ||||||
| Hardware: | All | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | service | ||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-12-18 14:27:28 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | CFME Core | Target Upstream Version: | |||||
| Attachments: |
|
||||||
John - Please review this RFE. I have been asked about this before and I believe it makes sense to create an option for a service template so it is not visible in the users "My Service" list after order completion. Maybe we do not delete them, but instead create a flag so they are archived and filtered out of the main list. The best solution would be for CloudForms to be smart enough that if a "yum update" was performed against a server with Ansible, that job and results would be tied to the VM in question.(Similar to how Ansible Tower works). However in the short term just having an option to hide these non-services from the user is a much need stopgap. Mike - Also wanted to point out that the object that represents the service instance in automate supports a "remove_from_vmdb" method. So you could implement this today if you did want to completely remove the object from the database. |
Created attachment 1210291 [details] Image of service that is not a service Description of problem: CloudForms makes the assumption that every Catalog item ordered is a "service" and has VM information which is not necessarily the case. For example if a user creates a service that is not a VM such as a WordPress site, database, or just runs an Ansible job. Then there needs to be an option to automatically delete the corresponding "service" once finished. Attached is a screen shot of running an Ansible job directly that patches any host you run it against. No point in having a persistent "service" that shows CPU/Memory/Disk infomation that is not a VM. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Connect CloudForms to Ansible 2.Create a simple Ansible job that performs a simple task on a VM 3.Run that job ten times. Actual results: Ten "services" are created that make no sense as they are not VM's, and have no state of their own. Expected results: When creating the order dialog the user is given a choice to "delete service on completion" Additional info: