Better VMWare Datastore UI
When picking a datastore to use on a VMWare compute resource, the list of Data Store's should only contain Data Stores that are valid for the particular cluster that the user picked. Instead, it displays a list of all data stores associated with the vSphere instance (multiple clusters). This allows for user error which results in a weird obscure error in Foreman and vSphere.
Additionally, it would be nice if we could show free space information for each data store. This would help the user decide which Data Store the new VM should be placed in.
#1 Updated by Sam Kottler about 10 years ago
- Target version set to 1.2.0
These are all great suggestions that we should work on. Since we are getting close to the 1.1 final release, I'm adding this to the 1.2 backlog.
#2 Updated by Dominic Cleal almost 10 years ago
- Target version deleted (
#3 Updated by Dominic Cleal over 9 years ago
- Has duplicate Feature #2886: Support for VMWare data store clusters added
#4 Updated by Josh Baird over 9 years ago
Additional request - user should have the option to thin or thick provision storage. Currently, everything is thin provisioned with no option to thick provision.
#5 Updated by Dmitry Sakun over 9 years ago
Voting for this one as it's really nice to have this feature otherwise you still have to look into vsphere for a datastore and that breaks the idea of foreman.
May be adding some caching mechanism for the volumes and networks will improve the speed of enumeration process which may take a long time in big Datacenters.
#6 Updated by Derek Wright almost 9 years ago
secs. If it could load only relevant resources for the datacenter selected, load times may increase.
Info from log:
Started GET "/hosts/hostname.domain.com/edit" for x.x.x.x at 2014-05-19 10:27:43 -0400
Processing by HostsController#edit as HTML
Rendered hosts/_progress.html.erb (0.1ms)
Rendered puppetclasses/_selectedClasses.html.erb (0.0ms)
Rendered puppetclasses/_classes_in_groups.html.erb (0.0ms)
Rendered puppetclasses/_classes.html.erb (6.5ms)
Rendered puppetclasses/_class_selection.html.erb (111.4ms)
Successfully decrypted field for Foreman::Model::Vmware Company-WDC-Core
Rendered compute_resources_vms/form/vmware/_network.html.erb (2732.7ms)
Rendered compute_resources_vms/form/vmware/_network.html.erb (2718.9ms)
Rendered compute_resources_vms/form/vmware/_volume.html.erb (16939.5ms)
Rendered compute_resources_vms/form/vmware/_volume.html.erb (18282.3ms)
Rendered compute_resources_vms/form/vmware/_volume.html.erb (17240.1ms)
Rendered compute_resources_vms/form/_vmware.html.erb (59663.2ms)
Rendered hosts/_compute.html.erb (60428.7ms)
Rendered common/_domain.html.erb (23.2ms)
Rendered hosts/_interfaces.html.erb (13.3ms)
Rendered common/os_selection/_architecture.html.erb (4.5ms)
Rendered common/os_selection/_operatingsystem.html.erb (12.9ms)
Rendered hosts/_operating_system.html.erb (23.0ms)
Rendered hosts/_unattended.html.erb (60518.2ms)
Rendered puppetclasses/_class_parameters.html.erb (0.0ms)
Rendered puppetclasses/_classes_parameters.html.erb (15.3ms)
Rendered common_parameters/_inherited_parameters.html.erb (135.1ms)
Rendered common_parameters/_puppetclass_parameter.html.erb (2.7ms)
Rendered common_parameters/_puppetclasses_parameters.html.erb (6.4ms)
Rendered common_parameters/_parameter.html.erb (1.5ms)
Rendered common_parameters/_parameters.html.erb (5.0ms)
Rendered hosts/_form.html.erb (60901.7ms)
Rendered hosts/edit.html.erb within layouts/application (60903.9ms)
Rendered home/_user_dropdown.html.erb (2.2ms)
Read fragment views/tabs_and_title_records-5 (0.2ms)
Rendered home/_topbar.html.erb (3.9ms)
Rendered layouts/base.html.erb (6.1ms)
Completed 200 OK in 60933ms (Views: 60884.6ms | ActiveRecord: 31.4ms)
#7 Updated by Virgil Chereches almost 8 years ago
+1 for datastore cluster support
#8 Updated by larry campbell over 7 years ago
years... is there another issue blocking or duplicate of this?
#9 Updated by Anonymous over 7 years ago
- Description updated (diff)
It's mostly limited by the developer's time looking into it, maybe this also requires changes to fog (I don't know!). Like every open source project we are more than willing to accept pull requests also for this issue, there has just to be somebody who is doing all the work at the end...
#10 Updated by Anonymous over 7 years ago
- Category changed from VM management to Compute resources - VMware
#11 Updated by Timo Goebel almost 7 years ago
- Has duplicate Feature #15115: Filter datastore and network selection added
#12 Updated by Timo Goebel almost 7 years ago
- Assignee set to Timo Goebel
#13 Updated by Angelo Lisco almost 7 years ago
As I requested though #15115, a filtered selection would also be really useful on the network tab as well.
Thank you Timo for taking care of this ;)
#14 Updated by The Foreman Bot almost 7 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3559 added
#15 Updated by Angelo Lisco almost 6 years ago
- Related to Bug #19424: VMware provisioning displays all IP address added
#16 Updated by Marek Hulán over 5 years ago
- Bugzilla link set to 1489516
#17 Updated by Daniel Lobato Garcia about 5 years ago
- Bugzilla link changed from 1489516 to 1467709
#18 Updated by Timo Goebel almost 5 years ago
- Related to Feature #23369: load vmware datastore options asynchronously added
#19 Updated by Marek Hulán about 4 years ago
- Bugzilla link changed from 1467709 to 1489516
#20 Updated by The Foreman Bot about 4 years ago
- Pull request https://github.com/theforeman/foreman/pull/6442 added
#21 Updated by Marek Hulán about 4 years ago
- Fixed in Releases 1.22.0 added
#22 Updated by Ondřej Ezr about 4 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset 870d459893b9510f22314e2e6e1c8e3fead88a55.
Fixes #2113 - VMware filter datastores