| Summary: | "Component Outline" overloaded/ improperly used | ||
|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Steve Reichard <sreichar> |
| Component: | aeolus-conductor | Assignee: | Angus Thomas <athomas> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | wes hayutin <whayutin> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.0.0 | CC: | akarol, dajohnso, deltacloud-maint, hbrock, mitch, scollier, ssachdev, sseago |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-30 17:12:56 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
(In reply to comment #0) > Description of problem: > > My understanding is that a "Component Outline" is the TDL a.k.a System Template > that describes how to build an image. > > 1. In the Clouds tab, there is a green button "New Component Outline". This > would imply making a new recipe to build an image. Doesn't this button start > the process for making an new Application for AppForm? Yes it starts the process for the workflow, but you are importing a template... It does not create the application.. So.. no.. thats not correct > > 2. Also in the clouds tab, there is the "Component Outlines" 'sub-tab'. This > used to be images, which make sense. It provides the status of build and > pushed along with the access to viewing the TDL. Since the "Component Outine" > is the description of how to build something, seems like that should be > "Component" which should be title for the sub-tab? fair point > > > 3. In the images sub tab there is a button that is titles "Import Component > Outlines" To me this means that we would be importing the system template > exported from System Engine. I know it is actually the button used to import > VM/templates/AMIs. While not exavtly sure of the right name ("Import > Component"), this name is very mis-leading. known issue.. finally getting some traction w/ devel to fix. Should be in the next few builds > > > Version-Release number of selected component (if applicable): > > [root@cf-cloudforms9 imagefactory]# > /pub/scripts/post_install_configuration_scripts/cf-versions > Red Hat Enterprise Linux Server release 6.2 (Santiago) > Linux cf-cloudforms9.cloud.lab.eng.bos.redhat.com 2.6.32-220.4.2.el6.x86_64 #1 > SMP Mon Feb 6 16:39:28 EST 2012 x86_64 x86_64 x86_64 GNU/Linux > postgresql-8.4.9-1.el6_1.1.x86_64 > mongodb-1.8.2-3.el6.x86_64 > euca2ools-1.3.1-4.el6_0.noarch > ruby-1.8.7.352-5.el6_2.x86_64 > rubygems-1.8.10-1.el6.noarch > deltacloud-core-0.5.0-5.el6.noarch > rubygem-deltacloud-client-0.5.0-2.el6.noarch > package libdeltacloud is not installed > hail-0.8-0.2.gf9c5b967.el6_0.x86_64 > puppet-2.6.11-1.el6_1.noarch > aeolus-configure-2.5.0-14.el6.noarch > iwhd-1.2-3.el6.x86_64 > imagefactory-1.0.0rc5-1.el6.noarch > aeolus-conductor-daemons-0.8.0-28.el6.noarch > aeolus-conductor-0.8.0-28.el6.noarch > [root@cf-cloudforms9 imagefactory]# > > > > How reproducible: > > > Steps to Reproduce: > 1. > 2. > 3. > > Actual results: > > > Expected results: > > > Additional info: OK. Point 1 is in fact not a bug (Wes explains above); point 2 is a PM issue, Angus will follow up; and point 3 is being taken care of as part of the fix to 796052. We'll leave this open for point 2 until Angus has a resolution from PM. For point 2, the images themselves are actually called 'Components' when they're imported (as in a realized component outline). The tab should read 'Components' instead of Component Outline while the action button should read 'Import' Actually, Hugh -- I think this is a bug. For all 3 points --1, 2, and 3 -- we should keep it as 'Image' as it is upstream. It looks like what happened is someone translated "Image" as "Component Outline" in the product rather than translating "Template" as "Component Outline" The fix is to move this _back_ to image. 1 - There are now two green buttons "Import Image" and "New Component Outline". Each uses correct terminology, and accurately reflects its purpose. 2 - I believe that the term which makes sense to refer to the output from imagefactory, is an image. A "component" is, I believe, a combination of image UUID, hardware profile and name, ready to be used in an application blueprint. I'd refer to PM's specification of "Component Blueprint" as the preferred term to describe what is rederred to in the application template syntax as an assembly. Given that an assembly is referred to at a component blueprint, a single image cannot be a component. On that basis, I don't believe that the current references in the UI to "images", which all refer very specifically to a single bootable filesystem, should change. For those reasons, I believe that the current use of "Component Outlines", as described in point 2 above, is correct. The content under that tab does indeed deal in component outlines as the top -level objects, and allows control of built instances based on the selected component outline. 3 - This has now been fixed, to read "Import Image" I'm not sure about the upstream naming here, but imported images are called 'Components'. An Image is not a named concept in CF 1.0. If there is any questions, please let me know. sounds and looks like this is good 2 go in beta4 for the time being, moving to verified... [root@qeblade31 iwhd]# rpm -qa | grep aeolus | sort aeolus-all-0.8.0-41.el6.noarch aeolus-conductor-0.8.0-41.el6.noarch aeolus-conductor-daemons-0.8.0-41.el6.noarch aeolus-conductor-doc-0.8.0-41.el6.noarch aeolus-configure-2.5.0-18.el6.noarch rubygem-aeolus-cli-0.3.0-13.el6.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch |
Description of problem: My understanding is that a "Component Outline" is the TDL a.k.a System Template that describes how to build an image. 1. In the Clouds tab, there is a green button "New Component Outline". This would imply making a new recipe to build an image. Doesn't this button start the process for making an new Application for AppForm? 2. Also in the clouds tab, there is the "Component Outlines" 'sub-tab'. This used to be images, which make sense. It provides the status of build and pushed along with the access to viewing the TDL. Since the "Component Outine" is the description of how to build something, seems like that should be "Component" which should be title for the sub-tab? 3. In the images sub tab there is a button that is titles "Import Component Outlines" To me this means that we would be importing the system template exported from System Engine. I know it is actually the button used to import VM/templates/AMIs. While not exavtly sure of the right name ("Import Component"), this name is very mis-leading. Version-Release number of selected component (if applicable): [root@cf-cloudforms9 imagefactory]# /pub/scripts/post_install_configuration_scripts/cf-versions Red Hat Enterprise Linux Server release 6.2 (Santiago) Linux cf-cloudforms9.cloud.lab.eng.bos.redhat.com 2.6.32-220.4.2.el6.x86_64 #1 SMP Mon Feb 6 16:39:28 EST 2012 x86_64 x86_64 x86_64 GNU/Linux postgresql-8.4.9-1.el6_1.1.x86_64 mongodb-1.8.2-3.el6.x86_64 euca2ools-1.3.1-4.el6_0.noarch ruby-1.8.7.352-5.el6_2.x86_64 rubygems-1.8.10-1.el6.noarch deltacloud-core-0.5.0-5.el6.noarch rubygem-deltacloud-client-0.5.0-2.el6.noarch package libdeltacloud is not installed hail-0.8-0.2.gf9c5b967.el6_0.x86_64 puppet-2.6.11-1.el6_1.noarch aeolus-configure-2.5.0-14.el6.noarch iwhd-1.2-3.el6.x86_64 imagefactory-1.0.0rc5-1.el6.noarch aeolus-conductor-daemons-0.8.0-28.el6.noarch aeolus-conductor-0.8.0-28.el6.noarch [root@cf-cloudforms9 imagefactory]# How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: