Free software architecture software for linux

PIX Logging Architecture [PLA] is a project allowing for correlation of Cisco PIX Firewall Traffic and IDS Logs.
Centralization of the logs is provided using a MySQL database, supported by a Web-based frontend for Log Viewing, Searching, and Event Management.
PLA is completely coded in the Perl programming language, and uses various Perl modules including Perl::DBI and
Perl::CGI.
Main features:
- Parsing of Cisco PIX Syslog Messages
- Centralized MySQL Database Logging
- Multiple Firewall Support
- Web-based frontend for:
- Cisco PIX Traffic Logs
- Cisco PIX IDS Logs
- Searching Cisco PIX Traffic and IDS Logs
- Cisco PIX Traffic and IDS Statistics
- Event Management (Incident Management)

An open Quality of Service Architecture is an open architecture for the provisioning of Quality of Service related functionality into the Linux kernel.
The project features a flexible, portable and lightweight software architecture for supporting QoS related services on the top of a general-purpose operating system as Linux. The architecture is well founded on formal scheduling analysis and control theoretical results.
At the core of the software there is an adaptive Resource Reservation layer that is capable of dynamically adapting the CPU allocation for QoS aware applications based on its run-time requirements.
As it is highlighted by the AQuoSA architecture, the project is mainly composed of two components:
- the QoS Res module, for which you can browse online the kernel, application and internal APIs
- the QoS Mgr module, for which you can browse online the kernel, application and internal APIs
Enhancements:
- Some bug fixed

Adaptive Quality of Service Architecture (AQuoSA) is an open architecture for the provisioning of adaptive Quality of Service functionality into the Linux kernel. The project features a flexible, portable, lightweight and open architecture for supporting soft real-time applications with facilities related to timing guarantees and QoS, on the top of a general-purpose operating system as Linux.
At the core of the architecture there is an adaptive resource reservation layer that is capable of dynamically adapting the CPU allocation for QoS aware applications based on their run-time requirements.
Timing guarantees are provided through an in-kernel reservation based process scheduler, whose services are exposed to applications through a well-designed API.
A supervisor performs admission control, so that admitting into the system new applications with timing guarantees does not affect the timing guarantees of already admitted applications. Also, it takes care of guaranteeing appropriate security policies in the assignment of timing guarantees to users and user groups, as configured by the system administrator.
A feedback-based QoS control layer may be optionally used by applications who want to keep their timing guarantees by using a CPU allocation that is continuously adapted according to their actual needs. This leaverages the programmer, within certain limits, to hard-code any particular reservation amount within the application, because the best allocation is found out automatically at run-time. Also, this enhances the possibilities for the system to host additional QoS controlled applications. The available control algorithms are well founded on formal scheduling models and control theoretical results.
Enhancements:
- This release introduces a couple of flags useful when creating servers. If QOS_F_PERSISTENT is enabled, a server is allowed to exist beyond detach of the last task. If QOS_F_SOFT is enabled, a server tasks are scheduled by the Linux default scheduler/policy, when outside of the server reservation.
- Also, various stability issues in destroying servers have been fixed, also thanks to a new release of the generic scheduler patch for the Linux kernel (gs-2.2).

Software::Packager::Rpm is a suite of Perl modules providing a common interface for
the creation of platform specific software installation packagers.

add_item()
my %object_data = (
SOURCE => /source/file1,
TYPE => file,
KIND => doc,
DESTINATION => /usr/local/file1,
USER => joe,
GROUP => staff,
MODE => 0750,
);
$packager->add_item(%object_data);

This method overrides the add_item method in Software::Packager. It adds the ability to add extra features used by RPM for each object in the package.

For more details see the documentation in: Software::Packager Software::Packager::Object::Rpm

program_name()
$packager->program_name(SoftwarePackager);
my $program_name = $packager->program_name();

This method is used to set the name of the program that the package is installing. This may in should be the same as the package name but that is not required. It must not contain spaces or a dash "-" and must be all on one line.

version()
$packager->version(1.2.3.4.5.6);
my $version = $packager->version();

This method sets the version for the package to the passed value. The version passed cannot contain a dash "-" or spaces and must be on one line.

release()

This method sets the release version for the package. The release is the number of times the package has been recreated. If the release is not set then a default of 1 is used. It cannot contain spaces, a dash or new lines.

copyright()

This method sets the copyright type for the package. This should be the name of the copyright

source()

This method sets the source location for the package. This should be the URL for the source package used to create this package.

architecture()
$packager->architecture("sparc");
my $arch = $packager->architecture();

This method sets the architecture for the package to the passed value. If no argument is passed then the current architecture is returned. This is the output "from uname -p"

package_name()
my $name = $packager->package_name();

This method returns the name of the package that will be created.

short_description()

$packager->short_description("This is a short description.");
my $description = $packager->short_description();

The short description is just that a short description of the program. It must be all on one line.

description()
$packager->description("This is the description.");
my $description = $packager->description();

The description method sets the package description to the passed value. If no arguments are passed the package description is returned.

The discription can be of any length. It will be formatted by RPM in the following way:
If a line starts with a space it will be printed verbatim.

A blank line signifies a new paragraph.

All other lines will be assumed to be part of a paragraph and will be formatted by RPM.

package()

This method creates the package and returns true if it is successful else it returns undef

Software::Packager::Solaris is the Software::Packager extension for Solaris 2.5.1 and above.

SYNOPSIS

use Software::Packager;
my $packager = new Software::Packager(solaris);

This module is used to create software packages in a format suitable for installation with pkgadd. The process of creating packages is baised upon the document Application Packaging Developers Guide. Which can be found at http://docs.sun.com/ab2/@LegacyPageView?toc=SUNWab_42_2:/safedir/space3/coll1/SUNWasup/toc/PACKINSTALL:Contents;bt=Application+Packaging+Developer%27s+Guide;ps=ps/SUNWab_42_2/PACKINSTALL/Contents

FUNCTIONS

new()

This method creates and returns a new Software::Packager::Solaris object.

add_item()
$packager->add_item(%object_data);

This method overrides the add_item function in the Software::Packager module.

This method adds a new object to the package.

package()

$packager->packager(); This method overrides the base API in Software::Packager, it controls the process if package creation.

package_name()

This method is used to specify the abbreviated package name.

Sun say: (Application Packaging Developers Guide. Page 32) A valid package abbreviation must the criteria defined below:

It must start with a letter. Additional charaters may be alphanumeric and can be the two special charaters + and -.

It must be nine or fewer charaters.

Reserved names are install, new, and all.

For more details see the pkginfo(4) man page.

program_name()

This is used to specify the full package name.

The program name must be less that 256 charaters.

For more details see the pkginfo(4) man page.

architecture()

The architecture must be a comma seperated list of alphanumeric tokens that indicate the architecture associated with the package. The maximum length of a token is 16 charaters. A token should be in the format "instruction set"."platform group" where: instruction set is the output of `uname -p` platform group is the output of `uname -m`
If the architecture is not set then the current instruction set is used.

For more details see the pkginfo(4) man page.

version()

This method is used to check the format of the version and return it in the format required for Solaris.

The version must be 256 charaters or less.

The first charater cannot be a left parenthesis.

The recommended format isi an arbitrary string of numbers in Dewey-decimal format. For more datails see the pkginfo(4) man page.

install_dir()
$packager->install_dir(/usr/local);
my $base_dir = $packager->install_dir();

This method sets the base directory for the software to be installed. The installation directory must start with a "/".

compatible_version()

$packager->compatible_version(/some/path/file);
or
$packager->compatible_version($compver_stored_in_string);

my $compatible_version = $packager->compatible_version();

This method sets the compatible versions file for the software to be installed.

space()

$packager->space(/some/path/file);
or
$packager->space($space_data_stored_in_string);
my $space = $packager->space();

This method sets the space file for the software to be installed.

request_script()

$packager->request_script(/some/path/file);
or
$packager->request_script($request_script_stored_in_string);
my $request_script = $packager->request_script();

This method sets the space file for the software to be installed.

Adaptive Quality of Service Architecture (AQuoSA) is an open architecture for the provisioning of adaptive Quality of Service functionality into the Linux kernel. The project features a flexible, portable, and lightweight software architecture for supporting QoS-related services on top of a general-purpose operating system as Linux.

The architecture is well founded on formal scheduling analysis and control theoretical results. At the core of the architecture there is an adaptive resource reservation layer that is capable of dynamically adapting the CPU allocation for QoS aware applications based on their run-time requirements.

Timing guarantees are provided through an in-kernel reservation based process scheduler, whose services are exposed to applications through a well-designed API.

A supervisor performs admission control, so that admitting into the system new applications with timing guarantees does not affect the timing guarantees of already admitted applications. Also, it takes care of guaranteeing appropriate security policies in the assignment of timing guarantees to users and user groups, as configured by the system administrator.

A feedback-based QoS control layer may be optionally used by applications who want to keep their timing guarantees by using a CPU allocation that is continuously adapted according to their actual needs. This leaverages the programmer, within certain limits, to hard-code any particular reservation amount within the application, because the best allocation is found out automatically at run-time. Also, this enhances the possibilities for the system to host additional QoS controlled applications. The available control algorithms are well founded on formal scheduling models and control theoretical results.

Sorcerer is a source-based Linux distribution for system administrators. The sources are downloaded directly from software authors homepages and mirrors.

Then, they are compiled with the architecture and optimizations that the system administrator specifies.

Finally, it is installed, tracked, and archived for easy removal and upgrades. Sorcerer has both command line and menu driven source mangement programs.