| Summary: | Missing "Import Component Outline "Button in today's build | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Shveta <ssachdev> | ||||||||
| Component: | aeolus-conductor | Assignee: | Matt Wagner <matt.wagner> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | wes hayutin <whayutin> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 1.0.0 | CC: | akarol, athomas, deltacloud-maint, hbrock, slinaber, ssachdev | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | v0.8.0-39 | Doc Type: | Bug Fix | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-05-15 22:39:02 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Shveta
2012-02-22 07:38:43 UTC
This is actually not a bug, it's a (poorly-communicated on our part, I admit) change. Importing Component Outlines is now done within the context of a specific Cloud. The new flow should be: 1. Click "Clouds" 2. Click on one of the specific Clouds in the list (NOT the "Component Outline" tab) 3. Click the "Component Outline" tab in that specific pool 4. An "Import Component Outline" button is present. Actually, I'm going to take this back. What I said is correct, but I was talking this over with Angus and we both agree that the new placement is really pretty hard to find. I think the most sensible thing to do is to make "Import" another tab on the "New Image" page. There are currently tabs to upload a template, or to import from a template URL. I think it makes the most sense to add a third tab, "Import" from the cloud provider, rather than having a separate workflow. After further discussion, it sounds like there should be two changes: 1.) The text should read "Import Image", not "Import Component Outline". You're not importing the _outline_, but the already-built image 2.) We want to add a button next to where we already have the (green) "New Component Outline" button. I think adding a third tab is going to be too confusing, at least in a bug-fix period. This is on the list now: http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-February/009150.html There's also a product patch for #2, since the terminology change is unnecessary upstream. Pushed: 0.9-maint: 61370d12b9bfd433566f894ebab96a0c5e30b2c2 master: ba6805d71f018040e7896366fa7bce3698f0fbe0 0305773 61370d1 Button import image is added. 1. added on cloud page. 2. on the "Component Outline" tab in that specific cloud. see attached screenshot. Name is changed from "Import Component Outline" to "Import image". verified: rpm -qa | grep aeolus aeolus-conductor-doc-0.8.0-39.el6.noarch rubygem-aeolus-image-0.3.0-10.el6.noarch aeolus-configure-2.5.0-16.el6.noarch aeolus-conductor-0.8.0-39.el6.noarch aeolus-conductor-daemons-0.8.0-39.el6.noarch aeolus-all-0.8.0-39.el6.noarch rubygem-aeolus-cli-0.3.0-12.el6.noarch Created attachment 566731 [details]
imprt
Created attachment 566732 [details]
imprt
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 |