Skip to content
This repository has been archived by the owner on Jan 8, 2021. It is now read-only.

Change ClusterComputeResource to ComputeResource #104

Open
Haeki opened this issue May 7, 2020 · 0 comments
Open

Change ClusterComputeResource to ComputeResource #104

Haeki opened this issue May 7, 2020 · 0 comments

Comments

@Haeki
Copy link

Haeki commented May 7, 2020

Is your feature request related to a problem? Please describe.
I am not sure if this is a good idea but changing from vim.ClusterComputeResource to vim.ComputeResource would cause "clusters" with a single ESX Host to be found. The script would automatically create a cluster with the name of the Host. The Host is added to the cluster and the cluster to the already created cluster group.

Although single hosts rarely have many VMs the main advantage in my opinion would be that the VMs are added to the right cluster and can also be filtered by cluster group or cluster.

Advantages:

  • The already created cluster group would be used
  • The VMs are separated between the different locations/clusters
  • VMs can be filtered by the cluster / cluster group

Disadvantages would be:

  • single hosts aren't a real cluster
  • more clusters
  • clusters with a single host and few VMs
  • ??

Describe the solution you'd like
Change the vc_obj_views from
"clusters": vim.ClusterComputeResource,
to
"clusters": vim.ComputeResource,

Describe alternatives you've considered
Keep the current System with the Standalone ESXi Host Cluster

Additional context
I'm interested in getting feedback on this. Maybe I'm missing some other disadvantages or problems.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant