Free appliance stores software for linux

rPath Appliance Agent project is an extensible application framework for the administration of appliance devices through a web-based user interface.
The framework is comprised of individual component plugins which offer specialized functionality, such as a message log interface, user account preferences, system updates, and entitlement management capabilities.
You can also develop and add plugins to the rAA framework, extending capabilities and functionality for your specific requirements.
To set up your environment for developing rAA, untar the devel.tar.bz2 tarball in the docs directory into your development directory. It should contain the following files:
- README.devel:
this file.
- dev.cfg:
configuration for the development environment.
- raa:
symbolic link to the rAA installation, usually
/usr/lib/python2.4/site-packages/raa.
- raa-service:
used by the startup script for the rAA service daemon.
- raa_service_dev.conf:
configuration file for the rAA service daemon. This contains a pluginDirs
configuration option. Change or append to its value to add additional
directories in which you are developing plugins.
- raa-web:
startup script for the rAA web layer.
- start-raa-service.sh:
startup script for the rAA service daemon.
Enhancements:
- Enhancements to the backup plugin, and a new plugin has been added to allow users to upload new SSL certificates for rAAs Web servers HTTPS connections.

Virtual Appliances are nano-sized virtual machines with Web user interfaces for deploying instant infrastructure and applications.
The are Gentoo Linux based and optimized for use in VMware.
Summary Instructions for using the Base Virtual Appliance
Download the Virtual Appliance.
If you do not have VMware Player, Workstations, Server, GSX, or ESX, Download VMware Virtual Player or VMware Virtual Server and install it.
Unpack the Virtual Appliance zip or tar.bz2 file.
Use your VMWare product to open and run the VirtualAppliancesBase.vmx file
Observe your VMWare console. The Virtual Appliance IP address will be printed there.
Using your Web Browser, open the Virtual Appliance Management console at https://your_ipaddress:8000/
The Mangement console listens on port 8000 and uses https.
Login to the admin console. The factory username:password is admin:admin.
Change the admin password to something secret through Configuration|Authentication
Enter shared storage information in Configuration|Storage
Your shared storage files will now be available via the webserver on the Virtual Appliance at http://your_ipaddress
Enhancements:
- This is a new Virtual Appliance featuring an instant PostgreSQL server and phpPgAdmin.
- It is a fully self contained Virtual Appliance, only 14MB to download, and ready to use with no configuration.

Confstore is a configuration backup utility. Confstore scans your system for all recognised configuration files and then stores them in a archive. Confstore can also restore configuration from a previously created archive.

Virt-Factory project manages virtualized infrastructure:
Virt-Factory focuses on interacting with large numbers of virtual systems and on addressing some of the interaction problems that brings with it
Virt-Factory is primarily aimed at a fairly formal setting (data center), though we hope it is also useful on smaller scales
While Virt-Factory has some uses for bare-metal systems, it is first and foremost a tool for managing virtual systems. Future development will be much more focused on virtual systems management than bare-metal.
Virt-Factory provides both a web UI, for ease of use, and an XMLRPC API, for scripting of admin actions.
Virt-Factory is built on open-source projects including Cobbler, libvirt, and Puppet.
Today, Virt-Factory provisions and manages hosts and guests. It also addresses some of the problems specific to virtual systems. It creates complete host and guest images from metadata descriptions and centrally manages existing images.
Future work will make it possible to abstract away individual hosts and place guests into a pool of equivalent hosts, simplifying the administrators view of the data center for many tasks.
Whats It Run On?
It is being developed on FC-6. Well add support for FC-7 and RHEL-5 shortly.
How Stable Is It?
At this point, virt-factory an alpha level project that will probably eat your brane. However its getting better every day.
Whats the architecture look like?
Virt-factory provides a central server for managing virtual hosts and guests. The server exposes an XMLRPC API that is used by the Web UI, and can also be used by custom scripts. On Managed systems, a special "node daemon" is installed, which the central server communicates with over secure XMLRPC.
Who is the target user?
Developers who want to be involved in new systems management technology. Users wishing to run a large number of virtual systems that have a key interest in virtualization and system recipes / appliance concepts.
How is Virtualization used?
Virtualization plays a core role in virt-factory and is heavily integrated. The software takes care of the nuts and bolts and can entirely manage your virtualization, though logging into virtualization via xm and virsh is still supported. Virt-factory is about enablement of virtualization as a core systems-management strategy.
How do you treat appliances?
Appliances can be defined purely as metadata ("profiles") rather than binary blobs. The metadata describes the required virtual machines attributes (number of processors, memory etc), the base system installation (as a template data for the kickstart file), and the appliances "personality" as a puppet manifest. This makes it possible to distribute appliances easily, and allows end-users to adapt appliances to their needs while still being able to consume appliance updates.
Enhancements:
- This release concentrates on making the code more stable and easier to install/deploy.

CGI::Application::Plugin::Authentication::Store is a base module for building storage classes for the CGI::Application::Plugin::Authentication plugin.

SYNOPSIS

package CGI::Application::Plugin::Authentication::Store::MyStore;
use base qw(CGI::Application::Plugin::Authentication::Store);

sub fetch {
my $self = shift;
my @params = @_;
...
}

sub save {
my $self = shift;
my %params = @_;
...
}

sub delete {
my $self = shift;
my @params = @_;
...
}

This module is a base class for all storage classes for the CGI::Application::Plugin::Authentication plugin. Each storage class is required to provide three methods that fetch, save and delete data from the store. The information that is saved will be text based, so there is no need to flatten any of the data that is to be stored.

issPolicy is a free open-source utility for converting an ISS RealSecure Network Sensor and ISS Proventia Inline Appliance Policy to a static HTML file.
Written in Perl, issPolicy allows for granular parsing of ISS RSNS and ISS Proventia policies (also refer to the "support" section), and supports a wide variety of features (see "features" section) allowing the HTML generation to be customized based on different policy parameters.
Main features:
- issPolicy automatically detects whether the policy is a ISS RealSecure Network Sensor or ISS Proventia Inline Appliance policy and generates a static HTML file based on the policy type and its features.
- issPolicy extracts the following information from the ISS RealSecure Network Sensor Policy:
- Signatures Policy (Signature Name, Signature Description, Signature Status, Signature Priority, Configured Responses, Logging Type)
- IP Filters Policy (Filter Name, Filter Description, Filter Status, Protocol, Source Address, Source Port, Destination Address, Destination Port)
- Event Filters Policy (Filter Name, Filter Description, Filter Status, Filtered Event, Source Address, Source Port, Destination Address, Destination Port)
- issPolicy extracts the following information from the ISS Proventia Inline Appliance Policy:
- Signatures Policy (Signature Name, Signature Description, Signature Status, Signature Priority, Configured Responses, Logging Type, Drop Options, DynamicBlock Options)
- IP Filters Policy (Filter Name, Filter Description, Filter Status, Protocol, Source Address, Source Port, Destination Address, Destination Port)
- Event Filters Policy (Filter Name, Filter Description, Filter Status, Filtered Event, Source Address, Source Port, Destination Address, Destination Port)
- issPolicy contains various useful options allowing for a tailored HTML Policy file to be generated, based on one or more of the following criteria:
- Signature Policy Criteria:
- Whether signature is enabled or disabled
- Based on signature priority (High, Medium, or Low)
- Whether drop is enabled [only on ISS Proventia Inline Appliance Policies]
- Based on drop options (ConnectionWithReset, Connection, or Packet) [only on ISS Proventia Inline Appliance Policies]
- Whether dynamicblock is enabled [only on ISS Proventia Inline Appliance Policies]
- Based on dynamicblock options (IsolateTrojan, BlockWorm, BlockIntruder) [only on ISS Proventia Inline Appliance Policies]
- IP Filter Policy Criteria:
- Whether IP filter is enabled or disabled
- Event Filter Policy Criteria:
- Whether Event Filter is enabled or disabled
- issPolicy uses an "API" structured format, pushing the entire policy to hash arrays, allowing the possibility for other output methods to be developed (CSV, XML, etc...)

PHP FastFileCache caches output from dynamic PHP scripts, and stores them in files for fast retrieval under high server load.

Fear Stats project generates player stats from F.E.A.R. server log files, and stores them in a MySQL database.
Enhancements:
- Improved Scoring Calculations for all game modes
- Created new Sub to handle checking for existing records.
- Transactoins now fully supported for InnoDB
- Corrected Players Objective Score not calculating into total session score.