Free instance software for linux

xen-shell is a simple console application which allows you to easily allow the owner of a single Xen instance to control it, without the overhead of a web-based control panel.
Using this shell users may:
- Boot/Shutodwn their Xen guest.
- Reboot their Xen guest.
- Connect to the serial console of their runing Xen guest.
- Reimage their system to a pristine state, via xen-tools.
- Manipulate their reverse DNS information
The shell features command history, command completion, and integrated help.
It is ideal for a hosting company who wishes to over "virtual machine" hosting to their customers, and allow them to control their own instance.

OraRep is a PL/SQL snippet (embedded in a shell script) which creates a well-formatted HTML report on a given database instance, providing you with an overview on your instance(s), some hints for performance tuning, and more.
It has been tested with Oracle 8.1.7, 9.0.1, and 9.2. The script easily fits into a cron task to be run on a regular basis. Sample output (HTML) is included.
OSPRep does the same job for Oracle StatsPack Reports based on SnapShot Levels up to 7, and provides additional "plugins" for more detailed reporting on special issues.
The project also optionally creates a separate page with charts to visualize the results and more.
Enhancements:
- This release has working Oracle 10g support.

Class::Method::hash is a Perl module that helps you create methods for handling a hash value.

SYNOPSIS

use Class::MethodMaker
[ hash => [qw/ x /] ];

$instance->x; # empty
$instance->x(a => 1, b => 2, c => 3);
$instance->x_count == 3; # true
$instance->x = (b => 5, d => 8); # Note this *replaces* the hash,
# not adds to it
$instance->x_index(b) == 5; # true
$instance->x_exists(c); # false
$instance->x_exists(d); # true

Creates methods to handle hash values in an object. For a component named x, by default creates methods x, x_reset, x_clear, x_isset, x_count, x_index, x_keys, x_values, x_each, x_exists, x_delete, x_set, x_get.

DiskSearch project is a tool for searching for files on all your removable media disks (e.g. CDs, ZIP disks or backup tapes).

For instance you can search for songs on your MP3-CDs or for a document on your backup DVDs. For advanced queries there is a regular expression search mode.

The search is based on a simple database file which needs to be filled once by adding all your disks to it.

dotnetfromjava is a Java software API to provide access to the .NET APIs without writing native code.

From the Java developers point of view, the main Java object that makes .NET API calls is NetObject. From the .NET developers point of view, NetObject is the RuntimeType of a .NET (Object) Instance.

NetObject is the root object of the dotnetfromjava library and can invoke (nearly) any member via reflection of (nearly) any .NET Object.

Class::StrongSingleton is a stronger and more secure Singleton base class.

SYNOPSIS

package My::Singleton::Class;

use base qw(Class::StrongSingleton);

sub new {
my ($class, %my_params) = @_;
# create our object instance
my $instance = { %my_params };
bless($instance, $class);
# and initialize it as a singleton
$instance->_init_StrongSingleton();
return $instance;
}

1;

# later in your code ...

# create the first instance of our class
my $instance = My::Singleton::Class->new(param => "value");

# try to create a new one again, and
# you end up with the same instance, not
# a new one
my $instance2 = My::Singleton::Class->new(param => "other value");

# calling instance returns the singleton
# instance expected
my $instance3 = My::Singleton::Class->instance();

# although rarely needed, if you have to
# you can destroy the singleton

# either through the instance
$instance->DESTROY();
# or through the class
My::Singleton::Class->DESTROY();

# of course, this is assuming you
# did not override DESTORY yourself

# Also calling instance before calling new
# will returns a new singleton instance
my $instance = My::Singleton::Class->instance();

This module is an alternative to Class::Singleton and Class::WeakSingleton, and provides a more secure Singleton class in that it takes steps to prevent the possibility of accidental creation of multiple instances and/or the overwriting of existsing Singleton instances. For a detailed comparison please see the "SEE ALSO" section.

Here is a description of how it all works. First, the user creates the first Singleton instance of the class in the normal way.

my $obj = My::Singleton::Class->new("variable", "parameter");

This instance is then stored inside a lexically scoped variable within the Class::StrongSingleton package. This prevents the variable from being accessed by anything but methods from the Class::StrongSingleton package. At this point as well, the new method to the class is overridden so that it will always return the Singleton instance. This prevents any accidental overwriting of the Singleton instance. This means that any of the follow lines of code all produce the same instance:

my $instance = $obj->instance();
my $instance = My::Singleton::Class->instance();
my $instance = $obj->new();
my $instance = My::Singleton::Class->new();

Personally, I see this an an improvement over the usual Gang of Four style Singletons which discourages the use of the new method entirely. Through this method, a user can be able to use the Singleton class in a normal way, not having to know its actually a Singleton. This can be handy if your design changes and you no longer need the class as a Singleton.

Solaris::MapDev Perl module contains a map between instance numbers and device names.

SYNOPSIS

use Solaris::MapDev qw(inst_to_dev dev_to_inst);
my $disk = inst_to_dev("sd0");
my $nfs = inst_to_dev("nfs123");
my $inst = dev_to_inst("c0t0d0s0");
mapdev_data_files(path_to_inst => "/copy/of/a/path_to_inst",
mnttab => "/copy/of/a/mnttab",
dev_ls => { "/dev/rdsk" => "ls-lR/of/dev_dsk",
"/dev/rmt" => "ls-lR/of/dev_rmt" });
my $tape = inst_to_dev("st1");

This module maps both ways between device instance names (e.g. sd0) and /dev entries (e.g. c0t0d0). Vanilla SCSI disks, SSA disks, A1000, A3000, A3500 and A5000 disks are all catered for, as are tape devices and NFS mounts.

FUNCTIONS

inst_to_dev($inst)

Return the device name name given the instance name

dev_to_inst($dev)

Return the instance name given the device name

get_inst_names

Return a sorted list of all the instance names

get_dev_names

Return a sorted list of all the device names

mapdev_data_files

This tells mapdev to use data held in copies of the real datafiles, rather than the current "live" files on the system. This is useful for example when examining explorer output. A list of key-value pairs is expected as the arguments. Valid keys-value pairs are:

path_to_inst => "/copy/of/a/path_to_inst",

A valid path_to_inst file. This is mandatory.

mnttab => "/copy/of/a/mnttab",

A valid /etc/mnttab file. This is optional - if not
specified, no information on NFS devices will be displayed.

dev_ls => { "/dir/path" => "/ls-lR/of/dir/path",
... });

A hash containing path/datafile pairs. The paths should
be one of /dev/rdsk, /dev/osa/rdsk, /dev/osa/dev/rdsk or
/dev/rmt. The datafiles should be the output of a "ls -l"
of the specified directory. A single file containing a
recursive "ls -Rl" of /dev is also acceptable.

mapdev_system_files

This tells mapdev to revert to using the current "live" datafiles on the system - see "mapdev_data_files()"

Net::Amazon::EC2 is a Perl interface to the Amazon Elastic Compute Cloud (EC2) environment.

SYNOPSIS

use Net::Amazon::EC2;

my $ec2 = Net::Amazon::EC2->new(
AWSAccessKeyId => PUBLIC_KEY_HERE,
SecretAccessKey => SECRET_KEY_HERE
);

# Start 1 new instance from AMI: ami-XXXXXXXX
my $instance = $ec2->run_instances(ImageId => ami-XXXXXXXX, MinCount => 1, MaxCount => 1);

my $running_instances = $ec2->describe_instances();

foreach my $inst (@{$running_instances}) {
print "$inst->{instance}[0]{instanceId}n";
}

# Terminate instance

my $result = $ec2->terminate_instances(InstanceId => $instance->{instance}[0]{instanceId});

If an error occurs in communicating with EC2, the return value will be undef and $ec2->{error} will be populated with the message.