Bug 865955

Summary: [RFE] additonal fields for vsphere_configure around cluster support
Product: [Retired] CloudForms Cloud Engine Reporter: Dave Johnson <dajohnso>
Component: aeolus-configureAssignee: John Eckersberg <jeckersb>
Status: CLOSED WONTFIX QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: high    
Version: 1.0.0CC: morazi
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-19 20:53:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dave Johnson 2012-10-12 21:48:30 UTC 
Description of problem:
=====================================
Verifying bug 853126, add vsphere cluster support to imagefactory, we determined that aeolus-configure needs to be able to handle a few more fields within its vsphere_configure and ultimately add them to vsphere.json

from imcleod
==================
In larger vSphere environments it can become necessary to specify an
individual cluster or host to push an image to.  We have added two
fields to the vSphere provider configuration file to allow this to
happen.

"host" - specifies a single vSphere host that the image is to be pushed
to

"computeresource" - specifies the vSphere ComputeResource entity to push
the image to.  This is most often the name of a cluster.


These fields are optional.  If they are not specified the code will push
to the first ComputeResource it can find.  In smaller environments this
is normally fine.