Free process automation software for linux

medini QVT implements OMGs QVT Relations specification in a powerful QVT engine.
The standard is designed for model-to-model transformations to allow fast development, maintenance and customization of process specific transformation rules.
Main features:
- Execution of QVT transformations expressed in the textual concrete syntax of the Relations language
- Trace management enabling incremental update during retransformation
- Key concept enabling incremental update as well as the transition from manual modeling to automation through transformations in the abscence of traces
- Bidirectional transformations

jHomenet is a home automation application. jHomenet uses both X-10 and Dallas Semiconductor 1-Wire network sensors and devices to collect sensor data and control devices.
jHomenet project can be programmed to respond to events, including particular sensor data values or time-of-day events.
Enhancements:
- This is a binary only release that includes several changes.
- Most noticable is the change in the versioning format.
- This change, however, also includes a drastic change in the library versioning and dependency framework.
- Other changes include a revised EventLogger, some UI tweaks, and several new jhomenet-commons JUnit unit tests.
- Some significant changes were also made to the Ant build setup.

Rocks Cluster is a complete "cluster on a CD" solution for x86 and IA64 Red Hat Linux COTS clusters.
Building a Rocks cluster does not require any experience in clustering, yet a cluster architect will find a flexible and programmatic way to redesign the entire software stack just below the surface (appropriately hidden from the majority of users).
Although Rocks includes the tools expected from any clustering software stack (PBS, Maui, GM support, Ganglia, etc), it is unique in its simplicity of installation.
From a hardware component and raw processing power perspective, commodity clusters are phenomenal price/performance compute engines. However, if a scalable ``cluster management strategy is not adopted, the favorable economics of clusters are offset by the additional on-going personnel costs involved to ``care and feed for the machine. The complexity of cluster management (e.g., determining if all nodes have a consistent set of software) often overwhelms part-time cluster administrators, who are usually domain application scientists. When this occurs, machine state is forced to either of two extremes: the cluster is not stable due to configuration problems, or software becomes stale, security holes abound, and known software bugs remain unpatched.
While earlier clustering toolkits expend a great deal of effort (i.e., software) to compare configurations of nodes, Rocks makes complete Operating System (OS) installation on a node the basic management tool. With attention to complete automation of this process, it becomes faster to reinstall all nodes to a known configuration than it is to determine if nodes were out of synchronization in the first place. Unlike a users desktop, the OS on a cluster node is considered to be soft state that can be changed and/or updated rapidly.
This is clearly more heavywieght than the philosophy of configuration management tools [Cfengine] that perform exhaustive examination and parity checking of an installed OS. At first glance, it seems wrong to reinstall the OS when a configuration parameter needs to be changed. Indeed, for a single node this might seem too severe. However, this approach scales exceptionally well, making it a preferred mode for even a modest-sized cluster. Because the OS can be installed from scratch in a short period of time, different (and perhaps incompatible) application-specific configurations can easily be installed on nodes. In addition, this structure insures any upgrade will not interfere with actively running jobs.
One of the key ingredients of Rocks is a robust mechanism to produce customized distributions (with security patches pre-applied) that define the complete set of software for a particular node. A cluster may require several node types including compute nodes, frontend nodes file servers, and monitoring nodes. Each of these roles requires a specialized software set. Within a distribution, different node types are defined with a machine specific Red Hat Kickstart file, made from a Rocks Kickstart Graph.
A Kickstart file is a text-based description of all the software packages and software configuration to be deployed on a node. The Rocks Kickstart Graph is an XML-based tree structure used to define RedHat Kickstart files. By using a graph, Rocks can efficiently define node types without duplicating shared components. Similiar to mammalian species sharing 80% of their genes, Rocks node types share much of their software set. The Rocks Kickstart Graph easily defines the differences between node types without duplicating the description of their similarities. See the Bibliography section for papers that describe the design of this structure in more depth.
By leveraging this installation technology, we can abstract out many of the hardware differences and allow the Kickstart process to autodetect the correct hardware modules to load (e.g., disk subsystem type: SCSI, IDE, integrated RAID adapter; Ethernet interfaces; and high-speed network interfaces). Further, we benefit from the robust and rich support that commercial Linux distributions must have to be viable in todays rapidly advancing marketplace.
Wherever possible, Rocks uses automatic methods to determine configuration differences. Yet, because clusters are unified machines, there are a few services that require ``global knowledge of the machine -- e.g., a listing of all compute nodes for the hosts database and queuing system. Rocks uses an SQL database to store the definitions of these global configurations and then generates database reports to create service-specific configuration files (e.g., DHCP configuration file, /etc/hosts, and PBS nodes file).
Enhancements:
- Rocks v4.3 is released for i386 and x86_64 CPU architectures. New features: Rocks command line - initial release of the Rocks command line which facilitates non-SQL administrative access to the database; PXE First - hosts can now be configured in BIOS with a boot order of CD, PXE, hard disk. Enhancements: based on CentOS 4.5 and all updates as of July 4, 2007; Anaconda installer updated to 10.1.1.63; performance improvement when building torrent files for the Avalanche Installer; database indirects, more flexibility with Rocks variables; Globus updated to gt4.0.4 with web services....

ControlTier application aims to be a complete enterprise-ready automation solution. It is our goal to provide the tools needed to automate the build, release, deployment, configuration, and control of distributed, multi-tier applications. When it comes to ease of use and out of the box functionality, we havent met all of our goals yet but we are working hard to do so. Any comments, questions, or criticisms are always welcome.
ControlTier coordinates and automates the chain of events that take place when you build and deploy a collection of integrated applications (what we call a "site").
Youll use ControlTier to:
- Coordinate your build processes (interfaces with build tools like Ant)
- Manage your build artifacts and other deployable resources in a structured repository
- Coordinate the distribution, configuration, and control of the various applications that makeup a site
Unlike most automation solutions that are focused exclusively on hardware and OS provisioning in production environments, ControlTier was built to focus on the application build and deployment processes that run all the way from Development, through QA, and into Production.
Main features:
- Framework for sequencing and coordinating automation
- Configuration management database
- Logical remote management (manage lots of things as one logical unit, no matter where they physically reside)
- GUI based development and operations tools
- Improved reuse and componentization of your existing scripts and configurations
- Change detection and configuration validation
- Application status discovery and detection
- Fine-grain access control
- Release migration tools
- Logging (with environment context built-in)
- Reporting and correlation tools
- Cross-platform support (Linux, Solaris, Windows, Mac OS X, etc.)
Enhancements:
- This is a major upgrade of both the ControlTier automation framework as well as the pre-built automation modules and workflows that come with the framework.

MySysop is a PHP tool with AJAX support for managing MySQL server settings and monitoring process, variables, and status.
Enhancements:
- This version has a prototype window for the dialog window, new stats, and minor bugfixes.

bibEC Process Card is a multiple gateway credit card payment processor.
This class is meant to process credit card payments via one of multiple payment gateways that are supported.
Currently the class supports the following payment gateways: Plug and Pay, Authorize.net, ViaKlix, and paynet . Changing between payment gateways is mostly a matter of changing the class constructor parameter.
The class provides a payment gateway independent API with functions for:
- Logging the payment activity
- Set the payment gateway authentication credentials
- Set the paying customer details
- Set the ship to details
- Set the credit card details
- Set the valuta
- Specify the order details
- Submit the payment processing request and retrieving the results
The payment submission is done securely when possible using PHP SSL socket connections or the Curl extension for PHP or the Curl command line.

htop is an interactive process viewer for Linux.
htop project requires ncurses. Tested with Linux 2.4 and 2.6.
Enhancements:
- This release contains stability and statistics fixes.
- Upgrading is recommended.

File::Backup is a Perl module for easy file backup & rotation automation.

SYNOPSIS

use File::Backup;

backup( from => "/source/path", to => "/destination/path" );
backup( from => "/kansas/*", to => "/oz" );

purge_backups(
to => "/destination/path",
compress => 0,
keep => 5,
timeformat => "YYYYMMDD_hhmmss",
);

This legacy module implements archival and compression (A.K.A "backup") and file rotation and is an implementation of tar and gzip calls.