Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1483636 - [RFE] - VMware MANUAL Placement to Support ONLY Clusters
[RFE] - VMware MANUAL Placement to Support ONLY Clusters
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate (Show other bugs)
5.8.0
Unspecified Unspecified
medium Severity medium
: GA
: 5.9.0
Assigned To: William Fitzgerald
Alex Newman
vsphere:provision
: FutureFeature, RFE
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-21 10:18 EDT by William Fitzgerald
Modified: 2018-03-01 08:15 EST (History)
9 users (show)

See Also:
Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-03-01 08:15:53 EST
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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:0380 normal SHIPPED_LIVE Moderate: Red Hat CloudForms security, bug fix, and enhancement update 2018-03-01 13:37:12 EST

  None (edit)
Description William Fitzgerald 2017-08-21 10:18:06 EDT
I wish for the manual placement selection to support only the use of the "VMware Clusters", after that the placement statemachine should be invoked to use the least utilised host and datastores that reside in the list that are in the selected Cluster.

Original closed BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1341152
Comment 2 William Fitzgerald 2017-08-22 09:24:32 EDT
John,

  Do we need to remove the other fields from the environment tab?

Thanks

Billy
Comment 4 William Fitzgerald 2017-08-22 14:14:14 EDT
Leo,

  I'm waiting for John Hardy to reply.  I think John just wants to select the cluster and not to have to select anything else. I'm not sure if John wants just the cluster in the environment tab.   

Billy
Comment 5 William Fitzgerald 2017-09-01 11:50:19 EDT
Leo,

John replied, The environment tab will only have the cluster as an option.

Billy
Comment 6 Dave Johnson 2017-09-01 12:45:43 EDT
Please assess the impact of this issue and update the severity accordingly.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.

If it's something like a tracker bug where it doesn't matter, please set it to Low/Low.
Comment 10 CFME Bot 2017-09-18 17:56:46 EDT
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/6cc6195db0df077283a5558e8aab3b9cce4ec20c

commit 6cc6195db0df077283a5558e8aab3b9cce4ec20c
Author:     Greg McCullough <gmccullo@redhat.com>
AuthorDate: Mon Sep 18 16:28:00 2017 -0400
Commit:     Greg McCullough <gmccullo@redhat.com>
CommitDate: Mon Sep 18 16:28:00 2017 -0400

    Allow forcing the provision task placement_auto method to true.
    
    Supports dialogs where the user has access to limited environment tab placement fields, such
    as folder or cluster, and auto-placement is still required to select the remaining fields.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1483636
    https://bugzilla.redhat.com/show_bug.cgi?id=1484024

 app/models/miq_provision.rb       |  2 +-
 spec/models/miq_provision_spec.rb | 40 +++++++++++++++++++++++++++++++++++++++
 2 files changed, 41 insertions(+), 1 deletion(-)
Comment 11 CFME Bot 2017-09-21 11:11:22 EDT
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/317ac5000db1ae2927e72881380b3f10207c0682

commit 317ac5000db1ae2927e72881380b3f10207c0682
Author:     william fitzgerald <wfitzger@redhat.com>
AuthorDate: Thu Sep 7 16:37:51 2017 -0400
Commit:     william fitzgerald <wfitzger@redhat.com>
CommitDate: Thu Sep 21 10:13:19 2017 -0400

    Automate - VMware placement to support only Clusters or only Folders.
    
    Manual placement selection to support only the use of "VMware clusters" and
    to support only the use of "VMware folders".
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1483636
    https://bugzilla.redhat.com/show_bug.cgi?id=1484024

 ..._provision_vmware_cluster_dialogs_template.yaml | 696 +++++++++++++++++++++
 ...q_provision_vmware_folder_dialogs_template.yaml | 686 ++++++++++++++++++++
 2 files changed, 1382 insertions(+)
 create mode 100644 product/dialogs/miq_dialogs/miq_provision_vmware_cluster_dialogs_template.yaml
 create mode 100644 product/dialogs/miq_dialogs/miq_provision_vmware_folder_dialogs_template.yaml
Comment 12 William Fitzgerald 2017-09-28 17:20:47 EDT
I added how to test these changes in the PR https://github.com/ManageIQ/manageiq/pull/15951

Please let me know if you have any questions.

Thanks

Billy
Comment 15 errata-xmlrpc 2018-03-01 08:15:53 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:0380

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