Bug 725623

Summary:	vmware is not listed in generic H/w profile hwp1
Product:	[Retired] CloudForms Cloud Engine	Reporter:	Shveta <ssachdev>
Component:	aeolus-configure	Assignee:	Richard Su <rwsu>
Status:	CLOSED CURRENTRELEASE	QA Contact:	wes hayutin <whayutin>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.3.1	CC:	dajohnso, ssachdev
Target Milestone:	beta
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Shveta 2011-07-26 05:58:22 UTC

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. With reference to bug https://bugzilla.redhat.com/show_bug.cgi?id=723585
2. Created a Provider vmware and added provider account for vsphere
3. Earlier all provider accounts used to get mapped to the generic hardware profile hwp1.
 But now all but vmware is listed when clicked on hwp1.
  
Actual results:


Expected results:


Additional info:

rpm -qa|grep aeolus
aeolus-conductor-doc-0.3.0-2.el6.noarch
aeolus-conductor-0.3.0-2.el6.noarch
aeolus-configure-2.0.1-1.el6.noarch
aeolus-all-0.3.0-2.el6.noarch
rubygem-aeolus-image-0.0.1-3.el6.noarch
aeolus-conductor-daemons-0.3.0-2.el6.noarch

Comment 1 wes hayutin 2011-07-26 14:22:49 UTC

Shveta,
See if you can add a hwp by hand that will bring in the vsphere hwp profiles.
My suggestion is to only set the memory ... and set it to 512. 
Leave the other fields blank.

Thanks...

I'm not 100% clear how bad this issue is.. whether or not the hwp create during configure is not working correctly OR vmware hwp's can not be added at all

This is a blocker *if* vmware/vphsere can not be added at all.

Comment 2 Richard Su 2011-07-26 19:36:41 UTC

Fixed on aeolus-configure-2.0.1-2.el6.noarch

Comment 3 Dave Johnson 2011-07-27 03:16:09 UTC

So I see it listed now but am curious on if it should show up when creating a new hardware profile and checking matches?

Comment 4 wes hayutin 2011-07-27 03:40:36 UTC

Dave, 
vmware hwp should match for memory and cpu, and arch. 
Storage is dynamic and should be left blank for the beta.

Typical matching vmware hwp are:

memory 256
cpu 1
arch x86_64
storage  (blank)

or 

memory 512
cpu 2
arch x86_64
storage (blank)

Comment 5 wes hayutin 2011-07-27 04:07:17 UTC

One additional comment here... The feature has changed a bit since dev changed getting the hwp at provider creation -> to provider account creation.

hwp should not match until provider account credentials have been entered.

Comment 6 Shveta 2011-07-27 09:19:09 UTC

It gets listed now

Comment 7 wes hayutin 2011-08-01 19:57:05 UTC

release pending...

Comment 8 wes hayutin 2011-08-01 19:58:26 UTC

release pending...

Comment 10 wes hayutin 2011-12-08 13:53:24 UTC

perm close

Comment 11 wes hayutin 2011-12-08 13:56:07 UTC

closing out old bugs