Uses of Package
org.jenkinsci.plugins.vsphere.tools
Packages that use org.jenkinsci.plugins.vsphere.tools
Package
Description
-
Classes in org.jenkinsci.plugins.vsphere.tools used by org.jenkinsci.pluginsClassDescriptionMinimal amounts of free resources a host must have right now to be a candidate for a new VM at all (see
VSphereHostSelection.limitShortfall(org.jenkinsci.plugins.vsphere.tools.VSphereHostSelection.HostCandidate, org.jenkinsci.plugins.vsphere.tools.HostLimits)), as opposed toHostWeights, which only decide which of the candidates is preferred.Optional refinements for automatic host selection (seeVSphereHostSelection), already resolved from cloud-level defaults and call-site overrides, soVSphereonly has to apply them.How much each of four measures of a host's free resources counts towards its score when automatically choosing the "most available" host (seeVSphereHostSelection.rank(java.util.List<org.jenkinsci.plugins.vsphere.tools.VSphereHostSelection.HostCandidate>, org.jenkinsci.plugins.vsphere.tools.HostWeights)): free CPU in MHz (absolute: a big host with the same load percentage has more to give), free CPU as a share of the host's CPU capacity (relative: how idle the host is), free memory in MB (absolute), free memory as a share of the host's memory (relative). -
Classes in org.jenkinsci.plugins.vsphere.tools used by org.jenkinsci.plugins.vsphere
-
Classes in org.jenkinsci.plugins.vsphere.tools used by org.jenkinsci.plugins.vsphere.builders
-
Classes in org.jenkinsci.plugins.vsphere.tools used by org.jenkinsci.plugins.vsphere.toolsClassDescriptionThere's a delay between when we give a bunch of nodes to Jenkins (when it asks us to provision some) and when those nodes appear in vSphere and in Jenkins, so we need to keep a record of what's in progress so we don't over-commit.Minimal amounts of free resources a host must have right now to be a candidate for a new VM at all (see
VSphereHostSelection.limitShortfall(org.jenkinsci.plugins.vsphere.tools.VSphereHostSelection.HostCandidate, org.jenkinsci.plugins.vsphere.tools.HostLimits)), as opposed toHostWeights, which only decide which of the candidates is preferred.Optional refinements for automatic host selection (seeVSphereHostSelection), already resolved from cloud-level defaults and call-site overrides, soVSphereonly has to apply them.Told that host selection found no host to use at the moment; seeHostSelectionOptions.withWaitListener(org.jenkinsci.plugins.vsphere.tools.HostSelectionOptions.Listener, boolean).Why automatic host selection found no host to place a new VM on at the moment, which is whenhostSelectionWaitSecondscomes into play.How much each of four measures of a host's free resources counts towards its score when automatically choosing the "most available" host (seeVSphereHostSelection.rank(java.util.List<org.jenkinsci.plugins.vsphere.tools.VSphereHostSelection.HostCandidate>, org.jenkinsci.plugins.vsphere.tools.HostWeights)): free CPU in MHz (absolute: a big host with the same load percentage has more to give), free CPU as a share of the host's CPU capacity (relative: how idle the host is), free memory in MB (absolute), free memory as a share of the host's memory (relative).Where an address falls, as far as vSphere's allocation scheme is concerned.The optional CPU and memory settings a VM is to be created with, in the same operation that creates it, instead of being reconfigured afterwards.What one look at the cluster's hosts found: either the hosts that may be given the new VM, or, if there are none, thereasonwhy not and a description for the log.Describes one candidate host's name, availability and current load, as needed to decide whether/how favourably it can be used for a new clone.A candidate host with its availability score (0 worst ..Waits for a while;Thread.sleep(long)in real life.