| Summary: | RFE: aeolus-image list completed pushes | ||
|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | wes hayutin <whayutin> |
| Component: | rubygem-aeolus-image | Assignee: | Martyn Taylor <mtaylor> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | wes hayutin <whayutin> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 0.3.1 | CC: | akarol, dajohnso, morazi, slinaber, ssachdev |
| Target Milestone: | beta | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
wes hayutin
2011-07-18 17:45:29 UTC
wondering/hoping we can do something to address this for beta.. Mike, can I get your opinion here? To elaborate on the problem... its difficult to determine when a pushed job is actually finished when building/pushing multiple templates. To find out a user would have to trace through the image factory log and match the image UUID to some lines in the factory log. The Completed message in the factory does indicate which UUID is complete 2011-07-18 22:53:35,586 DEBUG imagefactory.BuildJob.BuildAdaptor pid(12965) Message: Raising event with agent handler (<ImageFactoryAgent(Thread-1, initial)>), changed percent complete from 0 to 100 2011-07-18 22:53:35,587 DEBUG imagefactory.BuildJob.BuildAdaptor pid(12965) Message: Raising event with agent handler (<ImageFactoryAgent(Thread-1, initial)>), changed status from PUSHING to COMPLETED Wes, So there's no real way through iwhd or imagefactory right now to determine when a build has been pushed (key thing to note here is that we push Builds not Images) We allow pushing Images through CLI for convenience only. Now for some reason iwhd does have a tag on image which lets us know if its been pushed and what the last build that was pushed is. So providing a user does not try and push an image, whilst a previous push of the same image is in progress. We should be able to display enough data for a user to determine the push status So how about we add a 'LATEST BUILD PUSH' field to the list images output, this will display the last completed push for this image, if it empty then the image has not been pushed at all. So With regards to checking the build status: after some poking around it seems we have to do this check on the target-image. And in actual fact can already be determined from the aeolus-image list --target-images command. When the initial build has started the user is given a build id, target image id, and image id. Once the target-image id is returned as part of that list command it means the target image is completed. I will get a patch ready for the push status and update the docs accordingly for the build status and push status. Unfortunately, given the timescale that's the closest we can realistically get to STATUS updates for user. commit a508cf05c0350119749afefd8ed367304abc42d3
Author: Martyn Taylor <mtaylor>
Date: Thu Jul 21 16:50:00 2011 +0100
Update Doc to show listing completed builds
commit f475955efa9217ca48d098eaf0155f734432a87f
Author: Martyn Taylor <mtaylor>
Date: Thu Jul 21 16:23:47 2011 +0100
BZ#723934 Check bucket exists in iwhd
Sorry That last commit is not correct it should be:
commit a508cf05c0350119749afefd8ed367304abc42d3
Author: Martyn Taylor <mtaylor>
Date: Thu Jul 21 16:50:00 2011 +0100
Update Doc to show listing completed builds
commit 312eabe82a1549d2f6a767408c349b22b47d06a6
Author: Martyn Taylor <mtaylor>
Date: Wed Jul 20 17:10:11 2011 +0100
BZ#722994 Added Latest Push Field to List Images"
This is added in order to determine if an image has been pushed, and what the last successfully pushed build was
Works in some instances so marking this as verified and opening up a specific issue here, bug 725932. removing from tracker release pending... release pending... perm close closing out old bugs |