Free factory software for linux

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.

Workflow::Factory is a Perl module that generates new workflow and supporting objects.

SYNOPSIS

# Import the singleton for easy access
use Workflow::Factory qw( FACTORY );

# Add XML configurations to the factory
FACTORY->add_config_from_file( workflow => workflow.xml,
action => [ myactions.xml, otheractions.xml ],
validator => [ validator.xml, myvalidators.xml ],
condition => condition.xml,
persister => persister.xml );

# Create a new workflow of type MyWorkflow
my $wf = FACTORY->create_workflow( MyWorkflow );

# Fetch an existing workflow with ID 25
my $wf = FACTORY->fetch_workflow( MyWorkflow, 25 );

Public

The Workflow Factory is your primary interface to the workflow system. You give it the configuration files and/or data structures for the Workflow, Workflow::Action, Workflow::Condition, Workflow::Persister, and Workflow::Validator objects and then you ask it for new and existing Workflow objects.

Internal

Developers using the workflow system should be familiar with how the factory processes configurations and how it makes the various components of the system are instantiated and stored in the factory.

Bio::Tools::AlignFactory is a base object for alignment factories.

SYNOPSIS

You wont be using this as an object, but using a dervied class like Bio::Tools::pSW

Holds common Alignment Factory attributes in place

Bio::Factory::SequenceFactoryI is a Perl interface that allows for generic building of sequences in factories which create sequences (like SeqIO).

SYNOPSIS

# do not use this object directly it is an interface # get a Bio::Factory::SequenceFactoryI object like
use Bio::Seq::SeqFactory;
my $seqbuilder = new Bio::Seq::SeqFactory(type => Bio::PrimarySeq);

my $seq = $seqbuilder->create(-seq => ACTGAT,
-display_id => exampleseq);

print "seq is a ", ref($seq), "n";

A generic way to build Sequence objects via a pluggable factory. This reduces the amount of code that looks like
if( $type eq Bio::PrimarySeq ) { ... }
elsif( $type eq Bio::Seq::RichSeq ) { ... }

SWIFT::Factory::ApplicationHeader is a Perl module that provides an Application Header Block (Block 2) for a SWIFT message.

SYNOPSIS

use SWIFT::Factory::ApplicationHeader;
my $hdr2=SWIFT::Factory::ApplicationHeader->new();

This class is primarily intended to be used by the different SWIFT::Factory::MTnnn modules to provide full SWIFT messages for input to the SWIFT network.

Nevertheless, there is nothing prohibiting an application to directly use this class for whatever purpose.

Given reasonable parameter values in the constructor, the string() method in this class will return an Application Header Block (Block nbr 2) that can be used in a SWIFT message sent to the SWIFT network.

CONSTRUCTOR

new( MESSAGE_TYPE=>300, BIC=>VALIDBIC, TERMINAL=>X, BRANCH_CODE=>XXX, MESSAGE_PRIORITY=>N, DELIVERY_MONITORING=>1, OBSOLESCENCE_PERIOD=> )

The parameters may be given in arbitrary order. Many parameters have builtin default values. If the calling application doesnt provide the parameter at all, the object will apply the default value.

MESSAGE_TYPE=>

Technically optional, but its hard to see a reason not to provide this parameter.
A numeric scalar value that indicates the message type being provided. For an MT300 message, use the value 300. For an MT515, use 515. Etc.

BIC=>

An eight character scalar value that contains a valid receiver BIC.
The receiver BIC is technically optional, but it will probably quite rarely make sense to instantiate an object of this class without specifying a BIC.

TERMINAL=>

Optional. A one character scalar value that identifies the receiving terminal.
Default value: X. It is very unusual that the sending party would populate this entity with anything else than the default value. It is thereby recommended that most applications dont provide this parameter at all.

BRANCH_CODE=>

Optional. A three character scalar value that identifies the branch code at the receiver.

Default value: XXX.

MESSAGE_PRIORITY=>

Optional. A one character scalar value indicating the requested network priority for the message.

If given, use one of the values:

SWIFT::Factory::ApplicationHeader::MSG_PRIORITY_SYSTEM();
SWIFT::Factory::ApplicationHeader::MSG_PRIORITY_URGENT();
SWIFT::Factory::ApplicationHeader::MSG_PRIORITY_NORMAL();
Default value provided by the class:
SWIFT::Factory::ApplicationHeader::MSG_PRIORITY_NORMAL();

DELIVERY_MONITORING=>

Technically optional. SWIFT requires this entity for urgent messages. A one digit numeric scalar value or a zero length string.

If given, use one of the values:

SWIFT::Factory::ApplicationHeader::MONITORING_NON_DELIVERY();
SWIFT::Factory::ApplicationHeader::MONITORING_DELIVERY_NOTIFICATION();
SWIFT::Factory::ApplicationHeader::MONITORING_DELIVERY_BOTH();

Default value provided by the class: A zero length string which implies No monitoring.

OBSOLESCENCE_PERIOD=>

Optional. A numeric scalar value expressing the delay in units of 5 minutes. I.e. 3 means 15 minutes and 20 means 100 minutes.

Maximum three digits long. See the relevant SWIFT handbook for details.
Default value provided by the class: A zero length string which implies No obsolescence period.

Bio::Tree::DistanceFactory is a Perl module to construct a tree using distance based methods.

SYNOPSIS

use Bio::Tree::DistanceFactory;
use Bio::AlignIO;
use Bio::Align::DNAStatistics;
my $tfactory = Bio::Tree::DistanceFactory->new(-method => "NJ");
my $stats = Bio::Align::DNAStatistics->new();

my $alnin = Bio::AlignIO->new(-format => clustalw,
-file => file.aln);
my $aln = $alnin->next_aln;
# Of course matrix can come from a different place
# like PHYLIP if you prefer, Bio::Matrix::IO should be able
# to parse many things
my $jcmatrix = $stats->distance(-align => $aln,
-method => Jukes-Cantor);
my $tree = $tfactory->make_tree($jcmatrix);

This is a factory which will construct a phylogenetic tree based on the pairwise sequence distances for a set of sequences. Currently UPGMA (Sokal and Michener 1958) and NJ (Saitou and Nei 1987) tree construction methods are implemented.

Gtk2::Ex::MindMapView::ContentFactory is a maker of standard content.

SYNOPSIS

use Gtk2::Ex::MindMapView::ContentFactory;

This module is internal to Gtk2::Ex::MindMapView. This factory makes content that can be passed to a Gtk2::Ex::MindMapView::Border.

This module is called by Gtk2::Ex::MindMapView::ItemFactory.

The following types of content may be created:
Gtk2::Ex::MindMapView::Content::EllipsisText - Displays text with optional ellipsis (...).

Gtk2::Ex::MindMapView::Content::Picture - Displays a picture.

Gtk2::Ex::MindMapView::Content::Uri - Displays a URI. User may click on the URI.

INTERFACE

Properties

browser (string)

A browser command. Is executed when a user clicks on a link. The command contains a "%s" which is the insertion point for the url (see below). When the user clicks on a Gtk2::Ex::MindMapView::Content::Uri, the browser command is built and executed.

font_desc (Gtk2::Pango::FontDescription)

A Pango font description that styles text displayed to the user.

pixbuf (Gtk2::Gdk::Pixbuf)

A pixbuf that is displayed to the user.

text (string)

Text to be displayed.

text_color_gdk (Gtk2::Gdk::Color)

The color of the text to be displayed.

type (string)

The type of content to create (see above).

uri (string)

Typically, an URL that may be clicked on to start up the browser defined by the browser property (see above).

view (Gtk2::Ex::MindMapView)

The canvas on which content is drawn.

Methods

new (view=>$view)

Constructor for this factory. Pass in a Gtk2::Ex::MindMapView argument.

create_content (type=$content_type, ...)>
Returns a new Gtk2::Ex::MindMapView::Content object.

DIAGNOSTICS

Invalid Gtk2::Ex::MindMapView argument.

You must pass in a Gtk2::Ex::MindMapView argument.

Unexpected content type: $content_type

The only content type that is supported are those that are predefined, such as Gtk2::Ex::MindMapView::Content::EllipsisText.

Gtk2::Ex::MindMapView::HotSpot::ToggleFactory is a Maker of standard toggle items.

SYNOPSIS

use Gtk2::Ex::MindMapView::HotSpot::ToggleFactory;

This factory makes toggles that are used to expand or collapse the tree of items shown in the mind map.

The following types of toggles are currently supported:

Gtk2::Ex::MindMapView::HotSpot::Toggle::Round - The standard round toggle.

This factory is used by the Gtk2::Ex::MindMapView::ItemFactory.

INTERFACE

Properties

item (Gtk2::Ex::MindMapView::Item)

The item to attach the grip to.

border (Gtk2::Ex::MindMapView::Border)

The border that is used to determine the type of toggle to create.

side (string)

The side of the item to attach to. May be: left or right.

fill_color_gdk (Gtk2::Gdk::Color)

The color of the toggle.

outline_color_gdk (Gtk2::Gdk::Color)

The color of the toggle outline.

hotspot_color_gdk (Gtk2::Gdk::Color)

The color of the toggle when it is engaged.

Methods

new ( ...)

Constructor for the toggle factory.

create_toggle (item=>$item, border=>$border, side=>$side, ...)

Creates a new Gtk2::Ex::MindMapView::HotSpot::Toggle given the Gtk2::Ex::MindMapView::Item that the toggle will attach to. The Gtk2::Ex::MindMapView::Border is used to determine what toggle to return to the caller. The side may be left or right.

DIAGNOSTICS

Invalid item. Item must be a Gtk2::Ex::MindMapView::Item
You must pass in a Gtk2::Ex::MindMapView::Item argument.

Invalid side. Must be right or left
You must set the side to be either: left or right.

Unexpected border: $border
You must give one of the known border types at this time.