Free process automation software for linux

Subversion Automation project is a wrapper around Subversion that automates and standardizes branching and merging.

The primary goal of the project is to simplify the more complex features of Subversion and therefore encouraging their use.

Process Raw Images is a service menu for processing many raw images at once. Supports output to Jpeg, Png and Tiff.

E/AS Automation Solutions is open source software system for help automate your solutions even for personal and/or corporate ones.
E/AS written on CLIP language (CA-Clipper dialect, compiler can be obtained from ITK.ru) and uses CODB (CLIP Object Database) as data storage.
Main features:
- client-server technology (both data and interface forms)
- component infrastructure with interaction between components by messages
- interface forms on XML
- MDI
E/AS contains in typical distribution:
- client software written on clip-ui library
- server software with wrapper for run as daemon
- maintenance tools: CODB console and component manager
- base (form, auth) and example (contact) components
Enhancements:
- completely rewrite code for implement E/AS architecture
- component infrastructure
- own server program instead COBRA
- maintenance tools: CODB console and component manager
- base and example components
- autoupdate views

Konsole DCOP Scheme Automation Tool consists of a bash script which automatically changes the Konsole schema.
This is a Bash script to automatically set the desired Konsole Schema when apps such as VIM and less are executed.
It is a simple Bash script I wrote which allows you to automatically have the desired schema set when apps are run from within the shell.
For example, by default, when the user runs VIM with this script installed, the Konsole schema will switch to "VIM Colors" for the duration the user is in VIM. When the user exits VIM, the schema will change back to whatever it was before VIM was run. Other apps this script is setup for by default are:
$ less
$ man
$ info
$ watch
$ top
$ htop
I decided to create this because I became tired of switching my Konsole schema whenever I ran vim. I am now releasing it to everyone as Im sure someone else out there will find this usefull too.
This is a also nice way to impress your friends with how much more advanced the Linux shell is than those of the competitors! ;)
Users may also wish to enable this for other applications, such as mutt. To do so, simply edit the file ~/.konsole_dcop/schemas and follow the existing syntax.
Enhancements:
- This is the initial release.
- It is expected to be fairly stable and fully usable.
- If you have any bugs to report, please do so in the Issues category of the project homepage. Thank you.

The Stewie Radio Automation Project is a stand-in replacement for the "XMMS playlist on random" style of independent radio station.
Once properly configured, the user will enjoy the low maintenance of a "random playlist" station while still being able to use legal IDs, liners, multiple playlists, and music logs.
Main features:
- Low maintenance
- Multiple playlists
- Liners
- Legal IDs
- Logs every song and liner played
- Records errors and keeps truckin
Enhancements:
- Fixed a few bugs in install script
- Created error log/warning system
- Main script now updates the settings in stewie.conf in order to continue running. The only thing that *should* kill it, is not having any music available in the "master" playlist.
- Config file can be updated while script is running
- install-stewie gives "not found" audio players another chance
- Rewrote README file

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....

PyOPC is a Python library implementing the OPC XML Data Access Protocol Version 1.01 (OPC XML-DA 1.01).

PyOPC supports the easy creation of XMLDA-compliant clients and servers without having to deal with the SOAP protocol and server issues.

The Open Linking and Embedding for Process Control (OPC) consortium released several open standards, which address interfaces for vertical integration in industrial automation.

Historically, OPC used the Distributed Component Object Model (DCOM) for the underlying communication technology. DCOM has the disadvantage of being platform specific: it is only available for Microsoft Windows based systems. Other platforms, such as Linux, can therefore not retrieve fieldbus data from DCOM based servers.

Another disadvantage of DCOM is that it can not easily bypass firewalls, hence access will often be limited to certain segments of a corporate network.
In the last years, a new technology, called SOAP Web services, emerged. [LIV02] defines a Web Service as: ``a method or function that is available for other applications to access over the Internet.. Web services enable Remote Procedure Calls (RPC) and have the following key features:

High level of interoperability:

Web services technologies are all based on strictly defined open standards1.

High networking abilities:

As an underlying communication protocol, Web services utilize Internet protocols such as the Hyper Text Transfer Protocol (HTTP) or the Simple Mail Transfer Protocol (SMTP). These protocols have high networking abilities and may moreover penetrate firewalls.

Protocol legible by humans:

The Simple Object Access Protocol (SOAP)2 is based on the Extended Markup Language (XML), which is legible to humans. This way, testing and debugging of Web services is far easier than with binary protocols.

Documentation:

Another underlying technology of SOAP is the ``Web Service Definition Language (WSDL) which may be used to define the service, especially by constraining the format of the SOAP protocol. WSDL utilizes the XML Schema language for defining these SOAP messages3. These WSDL documents can be utilized by frameworks to generate stubs that provide a base for accessing a Web service.

Validation:

WSDL in combination with a validating XML parser enable the validation of SOAP messages. This way, custom code will never receive syntactically or semantically erroneous data, which should improve the stability of the service.

SOAP Web services are seen as a successor to several alternative technologies such as DCOM and are already broadly accepted by the industry. More information about the SOAP protocol can be found in [SEE02] and [LIV02].

The OPC consortium reacted on this technological evolution by adopting SOAP Web services for their standards. One recent addition of OPC is the "XML Data Access Version 1.0" (XML-DA 1.0) standard. This standard deals with access of underlying fieldbus technologies and covers the following aspects:

Information model:

The specification provides a simple information model, based on ``OPC Items which represent a piece of information, similar to fieldbus data points. These items can be arranged hierarchically.

Data types:

OPC XML-DA adopts several XML-Schema based data types, such as integer, float, date/time specific types. Moreover it defines arrays which are based on these basic types.

Operations:

The standard specifies 8 operations such as reading/writing and browsing which can be used to access the underlying fieldbus.

Subscription:

The specification further introduces a mechanism to retrieve only changed items, called ``Subscription. Clients may thus subscribe to items and use a dedicated polling operation to retrieve changed data.

SubEtha is a sophisticated mailing list manager, similar in many respects to the popular Mailman package. SubEtha is a three-tiered J2EE application using EJB3 and JMS. It is stable and self-hosting.
Main features:
- Very easy installation on Windows and Unix platforms
- A user-friendly web interface for all configuration management
- Virtual domains (ie list@foo.com and list@bar.com are separate lists)
- Users can have multiple email addresses and self-moderate messages from unknown addresses.
- Intelligent attachment handling; attachments can be removed from delivered mail and replaced with a download link to the archives.
- Pluggable, configurable message processing filters which can arbitrarily modify the inbound and outbound message streams. Example filters include attachment stripping, header munging, spam detection, and insertion of advertising.
- Per-list role-based permissions.
- One-step creation of basic list types (ie "Announce-Only List" or "Technical Support List"). The set of available types is pluggable.
- Searchable, threaded archives
- Users can reply to messages from the archives. They can click on a button and have the message resent to them normally.
- Intelligent VERP bounce processing
- Clusterable for nearly unlimited scalability
- Easy integration with any mail transport agent (MTA)
- EJB and SOAP interfaces for automation
- International characters in emails are properly passed through the system and rendered in the web interface
- RESTful, bookmarkable URLs
- A modular SMTP library that can be used outside SubEtha
Enhancements:
- This release works around a a backwards compatibility issue issue where SubEtha would not run on Java 5 because the released code was compiled using Java 6.