Bug 1484024 - - [RFE] - VMware MANUAL Placement to Support ONLY Folders
Summary: - [RFE] - VMware MANUAL Placement to Support ONLY Folders
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: 5.9.0
Assignee: William Fitzgerald
QA Contact: Leo Khomenko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-22 13:20 UTC by William Fitzgerald
Modified: 2018-03-01 13:15 UTC (History)
7 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-01 13:15:53 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:0380 0 normal SHIPPED_LIVE Moderate: Red Hat CloudForms security, bug fix, and enhancement update 2018-03-01 18:37:12 UTC

Description William Fitzgerald 2017-08-22 13:20:46 UTC
I wish for the manual placement selection to support only the use of the "VMware Folder", after that the placement statemachine should be invoked to use the least utilised host and datastores that reside in the list that have access to the folder.


Original closed BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1341150

Comment 2 William Fitzgerald 2017-08-22 13:22:59 UTC
John,

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

Thanks

Billy

Comment 3 William Fitzgerald 2017-09-01 15:50:58 UTC
John replied, The environment tab will only have the cluster as an option.

Billy

Comment 4 William Fitzgerald 2017-09-01 15:53:47 UTC
I meant only the folder

Comment 7 CFME Bot 2017-09-18 21:56:52 UTC
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/6cc6195db0df077283a5558e8aab3b9cce4ec20c

commit 6cc6195db0df077283a5558e8aab3b9cce4ec20c
Author:     Greg McCullough <gmccullo>
AuthorDate: Mon Sep 18 16:28:00 2017 -0400
Commit:     Greg McCullough <gmccullo>
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 8 CFME Bot 2017-09-21 15:11:27 UTC
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/317ac5000db1ae2927e72881380b3f10207c0682

commit 317ac5000db1ae2927e72881380b3f10207c0682
Author:     william fitzgerald <wfitzger>
AuthorDate: Thu Sep 7 16:37:51 2017 -0400
Commit:     william fitzgerald <wfitzger>
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 9 William Fitzgerald 2017-09-28 21:19:43 UTC
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 12 errata-xmlrpc 2018-03-01 13:15:53 UTC
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.