Bug 783133 - remove build/push capabilities from deployable page
Summary: remove build/push capabilities from deployable page
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: rc
Assignee: Jan Provaznik
QA Contact: wes hayutin
URL: https://qeblade31.rhq.lab.eng.bos.red...
Whiteboard:
: 770358 770574 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-19 13:50 UTC by wes hayutin
Modified: 2012-05-15 22:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-15 22:17:04 UTC

Attachments (Terms of Use)
ss (127.21 KB, image/png)
2012-01-19 13:50 UTC, wes hayutin 		no flags Details
build_push_removed (225.71 KB, image/png)
2012-01-31 13:49 UTC, Shveta 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0583 0 normal SHIPPED_LIVE new packages: aeolus-conductor 2012-05-15 22:31:59 UTC

Description wes hayutin 2012-01-19 13:50:02 UTC 
Description of problem:

Angus and team agreed to:

remove build/push capabilities from deployable page

see screenshot
Comment 1 wes hayutin 2012-01-19 13:50:31 UTC 
Created attachment 556277 [details]
ss
Comment 2 Angus Thomas 2012-01-19 14:11:40 UTC 
The decision here is to keep the "Build" section in the deployable details UI, but to remove the controls, making it read-only.

There's value in the way that the build section shows status etc., which we need to preserve.

However, having two separate areas in the app from which build & push can be invoked, and representing the functionality differently in each location has, in the testing so far, served to cause confusion.

So, in the deployable details page, the view of build status will be read-only.
Comment 3 Jan Provaznik 2012-01-20 15:15:10 UTC 
patch sent: https://fedorahosted.org/pipermail/aeolus-devel/2012-January/008218.html
Comment 4 Matt Wagner 2012-01-25 14:58:31 UTC 
*** Bug 770574 has been marked as a duplicate of this bug. ***
Comment 5 Hugh Brock 2012-01-25 19:20:36 UTC 
*** Bug 770358 has been marked as a duplicate of this bug. ***
Comment 6 Jan Provaznik 2012-01-26 14:10:43 UTC 
pushed, commit 6f815cef67b012454f0ef371058627bc5b6b33b7
Comment 7 Steve Linabery 2012-01-27 06:33:39 UTC 
e43afe0 6f815ce in aeolus-conductor-0.8.0-13
Comment 9 Shveta 2012-01-31 13:49:27 UTC 
Created attachment 558622 [details]
build_push_removed
Comment 10 Shveta 2012-01-31 13:50:22 UTC 
Build and Push controls removed from UI


Verified in

rpm -qa|grep aeolus
aeolus-conductor-doc-0.8.0-16.el6.noarch
aeolus-configure-2.5.0-11.el6.noarch
aeolus-conductor-daemons-0.8.0-16.el6.noarch
rubygem-aeolus-image-0.3.0-6.el6.noarch
aeolus-all-0.8.0-16.el6.noarch
aeolus-conductor-0.8.0-16.el6.noarch
rubygem-aeolus-cli-0.3.0-7.el6.noarch
Comment 11 errata-xmlrpc 2012-05-15 22:17:04 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-0583.html
Note You need to log in before you can comment on or make changes to this bug.