Free architect software for linux

GroundWork Monitor Architect or Monarch in short is a full-featured, easy-to-use configuration system for use with Nagios.

Monarch consists of a set of tools that allow a user to easily configure and maintain Nagios, or GroundWork Monitor, without editing the Nagios configuration files directly.

GroundWork Monitor Architect is a both a standalone product for Nagios, and a component of GroundWork Monitor, GroundWorks open source IT infrastructure monitoring solution.

Based on Nagios and several other leading open source technologies, GroundWork Monitor delivers enterprise-class availability and performance for a fraction of the cost of commercial alternatives.

Analysis of Reinforced Concrete Elements will assist its user to find out capacity of various Reinforced Concrete Structural Elements.

The following professionals are the target audience:

Structural Engineers
Civil Engineers
Architect
Builders

Installation:

The software is web-based, so you need web-server (Apache) running with PHP. The installaton is very simple. If your document root is /var/www/html , then on uncompressing downloaded compressed file in this "document root", the URL for ARCE application become: http://YourWebSite/arce/

Linux Napster Client is a console napster client written by Kevin Sullivan. It runs on Linux, OpenBSD, and other systems. Current releases of nap, such as 1.5.4, are very stable. They can run for weeks at a time without crashing or user intervention.
Nap, writtin by Kevin Sullivan sometime in 1999, was one of the first napster clients besides Shawn Fannings original Windows client. It was also the first client that ran on linux. Kevin learned much about the inner workings of the napster protocol by collaborating with Jordan Ritter, who was one of the co-founders of Napster and its Chief Server Architect at the time.
I took over the development of nap in February 2001. First I posted patches, but soon the patches became so long that I started making releases. A lot of features were added, and some existing ones redesigned, to make nap more stable, user-friendly, and reliable. However, the original "look and feel" has been preserved. Probably nap is one of the most robust napster clients for linux today. It has been packaged for a variety of popular platforms, and it is now shipped with some distributions of Debian Linux and OpenBSD.
Enhancements:
- This release changes the default meta-server to www.gotnap.com.

The Argus Open Project is focused on developing network activity audit strategies that can do real work for the network architect, administrator and network user.
LATEST NEWS
Mon Jun 19 10:44:52 EDT 2006 *argus-3.0.0 testing has started!
Welcome to the Argus Open Project, home of Argus, the network Audit Record Generation and Utilization System. The Argus Open Project main goal is developing network activity audit strategies that can do real work for the network architect, administrator and network user.
Argus is a fixed-model Real Time Flow Monitor designed to track and report on the status and performance of all network transactions seen in a data network traffic stream. Argus provides a common data format for reporting flow metrics such as connectivity, capacity, demand, loss, delay, and jitter on a per transaction basis. The record format that Argus uses is flexible and extensible, supporting generic flow identifiers and metrics, as well as application/protocol specific information.
Argus can be used to analyze and report on the contents of packet capture files or it can run as a continuous monitor, examining data from a live interface; generating an audit log of all the network activity seen in the packet stream. Argus can be deployed to monitor individual end-systems, or an entire enterprises network activity. As a continuous monitor, Argus provides both push and pull data handling models, to
allow flexible strategies for collecting network audit data. Argus data clients support a range of operations, such as sorting, aggregation, archival and reporting. There is XML support for Argus data, which makes handling Argus data a bit easier, see ArgusRecord.xsd.
The network transaction audit data that Argus generates has been used for a wide range of tasks including Security Management, Network Billing and Accounting, Network Operations Management and Performance Analysis.
Argus currently runs on Linux, Solaris, FreeBSD, OpenBSD, NetBSD, and MAC OS X and its client programs have also been ported to Cygwin. The software should be portable to many versions of Unix with little or no modification. Performance is such that auditing an entire enterprises Internet activity can be accomplished using
modest computing resources. The Argus Open Project is an ongoing and active project. If you areinterested in participating, check out the mailing lists and sign up today!
Enhancements:
- Multithreaded
- Daemon Support
- Configuration Files
- Syslog Support
- Secure Access
- Audit Record Changes
- Variable Length Records
- Argus Source Identifier
- Sequence Number
- Transaction Reference Number
- Security Layer (ESP) Support
- Application Layer Byte Counts
- Application Layer Data Capture
- Multiprotocol Support
- Enhanced Performance Reporting
- Enhanced TCP Status Reporting
- Enhanced Aggregation Support
- Server Changes
- Improved Accuracy
- Improved Reliability
- Improved Fragment Support
- Multiprotocol Support
- Authenticated Access
- Confidential Access
- Enhanced Physical Interface Support
- Multiple Physical Interface Support
- Multiple Output File Support
- Independant Output Filters
- Server Side Filtering
- Improved Signal Handling
- Daemon Support
- Syslog Event Reporting
- System Configuration
- Environment Variable Support
- Enhanced Performance Reporting
- Response Time Determination Support
- User Data Capture Support
- Client Changes
- Multiple Server Support
- Configurable Output Formats
- Cisco Netflow Record Support
- Environment Variable Support
- Configuration
- XML Data Support
- Excel Data Importation Support
- User Data Printing
- ragrep()
- Support Scripts and Programs
- System startup routines
- Sample configurations
- Sample Argus Archiving scripts
- argusbug Bug reporting tool
- Magic file support
- Documentation
- Better documenation?
- HTML man pages.
- FAQ
- HOW-TO

DBI::FAQ is a Perl module for the Frequently Asked Questions of the Perl5 Database Interface.

What is DBI, DBperl, Oraperl and *perl?

To quote Tim Bunce, the architect and author of DBI:

``DBI is a database access Application Programming Interface (API)
for the Perl Language. The DBI API Specification defines a set
of functions, variables and conventions that provide a consistent
database interface independant of the actual database being used.

In simple language, the DBI interface allows users to access multiple database types transparently. So, if you connecting to an Oracle, Informix, mSQL, Sybase or whatever database, you dont need to know the underlying mechanics of the 3GL layer. The API defined by DBI will work on all these database types.

A similar benefit is gained by the ability to connect to two different databases of different vendor within the one perl script, ie, I want to read data from an Oracle database and insert it back into an Informix database all within one program. The DBI layer allows you to do this simply and powerfully.

DBperl is the old name for the interface specification. Its usually now used to denote perl4 modules on database interfacing, such as, oraperl, isqlperl, ingperl and so on. These interfaces didnt have a standard API and are generally not supported.

Heres a list of DBperl modules, their corresponding DBI counterparts and support information. Please note, the authors listed here generally do not maintain the DBI module for the same database. These email addresses are unverified and should only be used for queries concerning the perl4 modules listed below. DBI driver queries should be directed to the dbi-users mailing list.

However, some DBI modules have DBperl emulation layers, so, DBD::Oracle comes with an Oraperl emulation layer, which allows you to run legacy oraperl scripts without modification. The emulation layer translates the oraperl API calls into DBI calls and executes them through the DBI switch.

Heres a table of emulation layer information:

Module Emulation Layer Status
------ --------------- ------
DBD::Oracle Oraperl Complete
DBD::Informix Isqlperl Under development
DBD::Ingres Ingperl Complete?
DBD::Sybase Sybperl Working? ( Needs verification )
DBD::mSQL Msqlperl Experimentally released with
DBD::mSQL-0.61

The Msqlperl emulation is a special case. Msqlperl is a perl5 driver for mSQL databases, but does not conform to the DBI Specification. Its use is being deprecated in favour of DBD::mSQL. Msqlperl may be downloaded from CPAN via:

http://www.perl.com/cgi-bin/cpan_mod?module=Msqlperl

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

Blackbird Enterprise Service Bus is the first enterprise service bus (ESB) for PHP developers. The project provides a run-time container that loads, manages, and executes classes, provides connectivity and utility services to access external resources, such as message queues and collects and exposes metrics data to management tools
Main features:
- Use PHP to rapidly develop applications and application integration services
- Easy to learn and use - get coding in minutes
- Written for developers by developers
- Command-line and protocol-driven management and monitoring
- Easy object configuration, deployment, and load/unload tasks
- Less memory usage than a Java ESB
- Metrics collection, making it easy to develop monitoring and management tools
- Extensible protocol handler layer - supports STOMP , SMTP, and Jabber out of the box
What Its Not:
- A full-blown, Java ESB like Apache ServiceMix
- A replacement for other middleware, such as Apache ActiveMQ
- As fast, in theory, as a compiled language (although see below)
- Fully object-oriented (because PHP is not)
- Written by architects for architects
Why Are You Doing This When Already Exists?
ITema provides managed, hosted applications to small businesses, with an emphasis on integration. Part of our vision is to offer our customers choice, so they arent locked into a specific product or vendor. We need very good integration technology or well end up with an unmanageable spider web of integration hooks. An ESB is tailor-made for this type of work. It gives us the loose coupling we need to let applications run independently, and handles grunt-work tasks like communicating via message queues so we can focus on writing the code that does the real work.
The available Java ESB products didnt meet our needs. PHP was a more natural choice, but there was no ESB available for it. We decided it was better for us to write what we needed than to try to shoehorn what we were doing into another product. Our hope is that by releasing Blackbird under the GPL, other developers will get as much out of it as we have.
Blackbird isnt intended to be an isolated project, or a replacement for a Java ESB. In fact, we anticipated that it could be very useful to use both a Java and PHP ESB at the same time, in different layers of an architecture. Blackbirds design makes this straightforward, and it expects to communicate via STOMP with a message queue such as Apache ActiveMQ. It can even use the same ActiveMQ instance that supports a ServiceMix environment, so writing a Blackbird component to communicate with a ServiceMix component is easy!