Bug 865955 - [RFE] additonal fields for vsphere_configure around cluster support
[RFE] additonal fields for vsphere_configure around cluster support
Status: CLOSED WONTFIX
Product: CloudForms Cloud Engine
Classification: Red Hat
Component: aeolus-configure (Show other bugs)
1.0.0
Unspecified Unspecified
high Severity medium
: rc
: ---
Assigned To: John Eckersberg
Dave Johnson
: FutureFeature, Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-12 17:48 EDT by Dave Johnson
Modified: 2013-09-19 16:53 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-09-19 16:53:44 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dave Johnson 2012-10-12 17:48:30 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.