ClusterSelection: Get datastores directly from cluster#23
Merged
jswager merged 2 commits intojenkinsci:masterfrom Feb 3, 2015
Merged
ClusterSelection: Get datastores directly from cluster#23jswager merged 2 commits intojenkinsci:masterfrom
jswager merged 2 commits intojenkinsci:masterfrom
Conversation
In our Vsphere setup, searching for Datastores under the cluster doesn't work.
When calling getDataStoreClusters on a cluster, the cluster is found though.
Unfortunately I don't know enough about the vmware vim25 api to know why the
datastore wasn't found.
It is found if I don't pass in the cluster for the searching and the searching
takes place on the root entity.
Pass in logger to Vsphere clone method so that output can be seen in jenkins
console.
While testing this I realized that several arguments are not expanded.
Cluster for instance is not expanded in either Clone or Deploy.
This would mean that ${CLUSTER} for instance wouldn't be expanded.
Improved logging messaging as well so errors in configuration are easier to find.
Only change between clone and deploy is to not set a snapshot when deploying a vm from a template. Refactored cloneVm method into smaller methods for easier readability.
jswager
added a commit
that referenced
this pull request
Feb 3, 2015
ClusterSelection: Get datastores directly from cluster
|
@damienbiggs I believe this change broke some things. My vSphere doesn't have any clusters configured. I was using the Datacenter name before, but after upgrading from 2.2 to 2.4 this no longer works. |
Collaborator
Author
|
Sorry about that. |
|
@damienbiggs Absolutely I can test. Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In our Vsphere setup, searching for Datastores under the cluster doesn't work.
When calling getDataStoreClusters on a cluster, the cluster is found though.
Unfortunately I don't know enough about the vmware vim25 api to know why the
datastore wasn't found.
It is found if I don't pass in the cluster for the searching and the searching
takes place on the root entity.
Pass in logger to Vsphere clone method so that output can be seen in jenkins
console.
While testing this I realized that several arguments are not expanded.
Cluster for instance is not expanded in either Clone or Deploy.
This would mean that ${CLUSTER} for instance wouldn't be expanded.
Improved logging messaging as well so errors in configuration are easier to find.