Back to bug 1309746
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Tim Wade | 2016-02-19 01:55:52 UTC | Status | NEW | POST |
| Marianne Feifer | 2016-02-19 18:36:55 UTC | CC | mfeifer | |
| Doc Text | Feature: Create API that allows one to trigger retirement by interacting with a VM object instead of having to do this through a service. Reason: service retirement can trigger retirement via an API call and can result in the retirement of a VM, however without a service one would need to instantiate an automate model and interact with the automate APIs in order to directly retire a VM. Result: Created retire action for VM. | |||
| Doc Type | Bug Fix | Enhancement | ||
| John Prause | 2016-02-19 20:01:02 UTC | Status | POST | MODIFIED |
| CC | jprause | |||
| errata-xmlrpc | 2016-03-22 11:00:08 UTC | Status | MODIFIED | ON_QA |
| John Prause | 2016-03-22 12:32:47 UTC | Fixed In Version | 5.5.3.2 | |
| Joe Rafaniello | 2016-03-22 12:56:48 UTC | CC | jrafanie | |
| Dayle Parker | 2016-03-23 04:10:06 UTC | Doc Text | Feature: Create API that allows one to trigger retirement by interacting with a VM object instead of having to do this through a service. Reason: service retirement can trigger retirement via an API call and can result in the retirement of a VM, however without a service one would need to instantiate an automate model and interact with the automate APIs in order to directly retire a VM. Result: Created retire action for VM. | Virtual machines previously could not be retired directly using an API call. While service retirement could trigger virtual machine retirement via an API call, without a service, it was necessary to use an automate model to retire a virtual machine through the automate APIs. This release adds a REST API retire action so that virtual machine retirement can be triggered directly. |
| Dayle Parker | 2016-03-23 05:41:40 UTC | Doc Text | Virtual machines previously could not be retired directly using an API call. While service retirement could trigger virtual machine retirement via an API call, without a service, it was necessary to use an automate model to retire a virtual machine through the automate APIs. This release adds a REST API retire action so that virtual machine retirement can be triggered directly. | Virtual machines previously could not be retired directly using an API call. While service retirement could trigger virtual machine retirement via an API call, without a service, it was necessary to use an Automate model to retire a virtual machine through the Automate APIs. This release adds a REST API retire action so that virtual machine retirement can be triggered directly. |
| Dayle Parker | 2016-03-24 01:15:24 UTC | Doc Text | Virtual machines previously could not be retired directly using an API call. While service retirement could trigger virtual machine retirement via an API call, without a service, it was necessary to use an Automate model to retire a virtual machine through the Automate APIs. This release adds a REST API retire action so that virtual machine retirement can be triggered directly. | Virtual machines previously could not be retired directly using an API call. While service retirement could as well trigger virtual machine retirement via an API call, without a service, it was necessary to use an Automate model to retire a virtual machine through the Automate APIs. This release adds a REST API retire action so that virtual machine retirement can be triggered directly. |
| dajohnso | 2016-03-24 21:11:07 UTC | QA Contact | dajohnso | nachandr |
| Dave Johnson | 2016-03-28 14:28:06 UTC | QA Contact | nachandr | tlehinev |
| Taras Lehinevych | 2016-03-29 11:22:29 UTC | Status | ON_QA | VERIFIED |
| errata-xmlrpc | 2016-04-13 03:48:56 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-04-13 18:44:32 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-04-13 14:44:32 UTC |
Back to bug 1309746