Bug 723585

Summary: Create generic hardware profiles and remove provider specific ones
Product: [Retired] CloudForms Cloud Engine Reporter: Mike Orazi <morazi>
Component: aeolus-configureAssignee: Richard Su <rwsu>
Status: CLOSED CURRENTRELEASE QA Contact: wes hayutin <whayutin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.3.1CC: dajohnso, ssachdev, sseago
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-08 13:48:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mike Orazi 2011-07-20 16:11:55 UTC 
Currently the puppet classes for rhevm & vmware create new hardware profiles to ensure that a match can be found on each of the providers.  

This is misleading, because for instance the vsphere-hwp can also match resources on amazon ec2 and it will appear strange to an end user to see a deployable launching resources in amazon when they thought they specified a vsphere specific hwp.


On #aeolus, sseago recommended, "we should probably define two "default" HWPs in the configure script. one 32 bit, one 64 bit, something like 1.5 GB RAM (at least for the 32 bit one so we can match m1.small), and leave storage blank"   

sseago also noted on channel that the test plan for this needs to include launches on both RHEV and VMWare, as there is some doubt on how RHEV will handle a nil value for storage.
Comment 1 Scott Seago 2011-07-20 16:16:39 UTC 
So with RHEV, the issue is that there are RANGE values (instead of fixed ones like ec2 has). A Range HWP property specifies Min, Max, and Default values. What we need to do in condormatic is to make sure that if a match is made where the conductor-specified HWP property is nil, we always use the default value for the HWP range or enum property.
Comment 2 Richard Su 2011-07-21 05:21:58 UTC 
Fixed in aeolus-configure-2.0.1-1.fc14.20110720182607git42b1e20.noarch.rpm
Comment 3 Shveta 2011-07-21 10:35:53 UTC 
No need to create different realms for providers like RHEV and vmware 
hwp1 is the generic profile for all providers.
Comment 4 wes hayutin 2011-08-01 19:54:36 UTC 
release pending...
Comment 5 wes hayutin 2011-08-01 19:56:25 UTC 
release pending...
Comment 7 wes hayutin 2011-12-08 13:48:46 UTC 
perm close