VMware Infrastructure Perl Toolkit Code

Added experimental app to license multiple ESX 3.x hosts managed by a single VirtualCenter, or a single ESX 3.x host, or display license usage for the same.

removed unnessary file vmclone_guestcustomize.xsd

Fixes:
- VMUtil.pm to add checking for InvalidArgument exception
file modified : apps\AppUtil/VMUtil.pm
- remove unnessary file guestinfo_customize.xsd
since this has been superceded by guestinfo.xsd
file removed : apps\schema/guestinfo_customize.xsd

List of Utility Applications submitted

General
--------
connect.pl
vidiscovery.pl
viversion.pl

Host
-----
dsbrowse.pl
hostevacuate.pl
hostops.pl
hostdiagnostics.pl
hostinfo.pl

VirtualMachine
----------------
guestinfo.pl
sharesmanager.pl
snapshotmanager.pl
vdiskcreate.pl
vmclone.pl
vmcontrol.pl
vmcreate.pl
vminfo.pl
vmmigrate.pl
vmreconfig.pl
vmregister.pl
vmsnapshot.pl
vmtemplate.pl

ResourcePool
--------------
resourcepool.pl

Performance
--------------
viperformance.pl

There are 3 modules with common functionality
AppUtil
--------
HostUtil.pm
VMUtil.pm
XMLInputUtil.pm

new xml schema and sample data files have also been
added for vmcreate and vmreconfigure apps.

Add check $properties being undef'd in update_view_data and set_view_data lines 496 and 516
This avoids a warning being printed out each time this parameter to these 2 subroutines is passed as undef.

Add beta1 documentation.

First checkin of reference / utility applications built using the ViPerl toolkit.

Applications provide host and vm information and operations.

Fix issue of sessionfile or (username, password) absense
not being handled as an invalid command option.

This fix ensures the absense of these args is handled as
a parameter validation error, and usage is printed out as a result.

Verified that --help and --version work as expected with these options absent.

Experimental support for selectively filtering views.

Added a new 'properties' argument to the view commands get_view(s) and
find_entity_view(s). The argument is a list of property paths to be
retrieved from the server. These can be full paths and are not
restricted to top-level managed properties. For example, to populate a
virtual machine view with just the power state information, you can
write:

my $vm_view = Vim::find_entity_view(view_type => 'VirtualMachine',
filter => { 'name' => 'foo' },
properties => [
'runtime.powerState' ]);

To retrieve properties from a filtered view, you should use the new
get_property method of the view. For example:

my $state = $vm_view->get_property('runtime.powerState');

Note that you can also get subproperties of the retrieved property:

my $vm_view = Vim::find_entity_view(view_type => 'VirtualMachine',
filter => { 'name' => 'foo' },
properties => [ 'config.hardware' ]);
my $memsize = $vm_view->get_property('config.hardware.memoryMB');

And that get_property works with fully-populated views as well. So:

my $vm_view = Vim::find_entity_view(view_type => 'VirtualMachine',
filter => { 'name' => 'foo' });
my $memsize = $vm_view->get_property('config.hardware.memoryMB');

Is equivalent to:

my $vm_view = Vim::find_entity_view(view_type => 'VirtualMachine',
filter => { 'name' => 'foo' });
my $memsize = $vm_view->config->hardware->memoryMB;

When using a filtered view, any attempts to read a property that wasn't
retrieved from the server will act the same as if the property were
unset.

The use of property filters is intended primarily as a performance
optimization to reduce the latency and network bandwidth of retrieving
full views of a large number of objects. In general, you should start
with full views and only switch to filtered views when tuning
application performance.

Note also that this support is currently experimental and may change or
be removed in the future.

This implements solution where PrimType
type is used to denote types of primitives for serialization. Because primitives types are
essentially 'untyped' in Perl, we need a way to detect whether a singular is string, boolean, short, long , etc. There may be ways to make this easier
on users but it will likely require a lot of engineering effort to make it happen (guess based on specific API calls maybe?) and after looking at
this solution, it doesn't look so terrible to me. I've added a bonus sample that uses this new type for scheduled task creation