Bug 805559

Summary: some cloud resource profiles wont match if storage is added
Product: [Retired] CloudForms Cloud Engine Reporter: wes hayutin <whayutin>
Component: Docs User GuideAssignee: Dan Macpherson <dmacpher>
Status: CLOSED CURRENTRELEASE QA Contact: dgao
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: dmacpher, lbrindle
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: 2012-06-07 06:19:38 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 wes hayutin 2012-03-21 15:26:17 UTC 
Description of problem:

Current:

Procedure 4.7. Creating a New Cloud Resource Profile
Click on the Administer tab.
Click on Content.
Click on Hardware.
Click the New Cloud Resource Profile button.
Type the Name of the cloud resource profile.
Type the amount of Memory for the cloud resource profile.
Type the number of CPUs for the cloud resource profile.
Type the Storage size in gigabytes.
Select the type of system Architecture for the profile. Choose from 32-bit (i386) or 64-bit (x86_64).
Click the Check Matches button to show profiles from cloud resource providers that match your desired configuration.
Click the Save button to save your new cloud resource profiles configuration.


** It should be noted that some providers will not match if customers enter storage data, in these cases it should be left blank **

depending on how the back end provider is setup, but vsphere and rhevm can fall into this category.


Thanks
Comment 2 wes hayutin 2012-03-30 18:56:03 UTC 
assigning to dgao
Comment 3 dgao 2012-03-30 19:44:21 UTC 
verified
Comment 4 Lana Brindley 2012-06-07 06:19:38 UTC 
Document is now available on docs.redhat.com. Please raise a new bug for any further issues.

LKB