-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I think it would be a good idea to have more descriptive names for the predictive loading modules. Predictive loading modules determine what to do with a node at the end of a reservation. In previous releases, they were selected on each management node. In 2.4, they are now assigned to each computer. Regardless of what module is selected, if there is a future reservation scheduled within a somewhat short amount of time, the computer is preloaded for that reservation. Otherwise, the selected module determines what to do. (Technically, there is one other case, but not worth explaining here.) There are currently 3 modules from which to select:
Level 0 - reload the node with the image that was just used Level 1 - look at log data of what are the most popular images and load the node with the most popular image that is not already preloaded somewhere else Level 2 - power off the node, and if it is a VM, unregister it I think these would be better names: Level 0 -> Reload with previous image Level 1 -> Reload based on historical usage Level 2 -> Power off/unregister VM Are these good names? Any suggestions that are more descriptive but still fairly short? Thanks, Josh - -- - ------------------------------- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTU2mkACgkQV/LQcNdtPQMxKQCeKV/2EyeV9VvWULesa1MRuULs eo8An2seNF5zJoAx4vozNuu5pqvq8p7e =daDN -----END PGP SIGNATURE-----
