Additional request - user should have the option to thin or thick provision storage. Currently, everything is thin provisioned with no option to thick provision.

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.

1, I'm working on rolling Foreman out to our production data store and I've noticed when we have hundreds of datastores/networks in our vcenter it slows things down considerably. It seems to really be a pain point for people when trying to use the UI and loading the compute profile takes about 30 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
Parameters: {"id"=>"hostname.domain.com"}
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)

+1 for datastore cluster support

1 for datastore cluster filter from me as well. I notice this feature request has 11 votes and still hasn't been assigned in 2 years... is there another issue blocking or duplicate of this?

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 ;)