Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionVaratharaja Perumal G
2017-02-03 15:07:12 UTC
1. Proposed title of this feature request
[RFE] Auto select datastore while provisioning the host in VMware.
2. What are the nature and description of the request?
When we create a compute profile, Satellite recognizes the datastore cluster, But then it ask us to select a datastore. The customer feels that the datastore should be selected based on VMWare's storage recommendation at the time of the VM build. That's the whole point of the datastore cluster - Cu should be able to provision 100 VMs at a time and not have to worry about filling up single datastore. Satellite should negotiate with VMWare to evenly distribute the VMs. Cu don't want to configure different compute profile for each datastore. He wants to use a single compute profile where it negotiates for datastore to avoid manual work.
3. Why does the customer need this?
Tie the compute profile only to a datastore cluster so we do not need multiple profiles.
Satellite should then negotiate the target datastore with vSphere at the time of building a host.
Make Satellite provisioning aware of vSphere Storage DRS to support the above.
4. How would the customer like to achieve this?
Customer want to achieve this from WebUI or API
5. Is there already an existing RFE upstream or in Red Hat Bugzilla?
Not that I'm aware of.
8. Does the customer have any specific timeline dependencies and which release
Sooner is better.
9. Would the customer be able to assist in testing this functionality if implemented?
yes
Build:Satellite 6.4.0 snap21
Created a Host with Storage Pod, that is a data-store cluster
When we select the storage pod we can no more select the data-store and host will automatically be provisioned in the data-stores that are present in Storage pod by Vmware cluster Policy.
PFA for the host settings
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:2927