Pre-Made Appliances


Tomcat WebServer

Tomcat is web server appliance based on the Sun Java machine and Apache Tomcat, a Java Servlet and Java Server Pages container developed under the Apache License. Tomcat provides standards-compliant support for Servlets and JSPs. Tomcat can work as standalone web server or as application server.
Tomcat 32Bit - Application Server
Resource Minimum Maximum Default
CPU 0.1 16 0.3
Memory 128MB 4GB 512MB
Bandwidth 1Mbps 2Gbps 250Mbps
Tomcat 64Bit - Application Server
Resource Minimum Maximum Default
CPU 0.1 16 0.3
Memory 128MB 64GB 512MB
Bandwidth 1Mbps 2Gbps 250Mbps


Web Server

Web is a web server appliance based on the Apache open-source web server software. Web serves static web content and executes scripts from a user-configurable read-only content volume. The paths to the documents and scripts are configurable, so that the same volume can be shared between multiple web servers and/or other appliances serving different content. Web server has three generic output terminals intended for accessing external services from scripts on the content volume. The db terminal is for accessing a MySQL database; the fs terminal is for accessing shared file storage (using NFS); and the aux terminal is for sending e-mail messages to an SMTP server. The log terminal can be used to connect Web to a shared file system on which Web can store its logs.
Web Server 32/64Bit - Web Server
Resource Minimum Maximum Default
CPU 0.1 16 0.3
Memory 128MB 32GB 512MB
Bandwidth 1Mbps 2Gbps 250Mbps
Web Server Software - Web Server
Apache PHP Python Perl
2.2.3 5.1.6 2.4.3 5.8.8
MySQL Client Distro Distro  
5.0.22 CentOS 5 - 32bit CentOS 5 - 64bit  


MySQL Database Server

MySQL is a database appliance based on the MySQL database engine. It provides an easy way to add a database to any application. MySQL stores the database on an application-defined volume that can be configured on each MySQL instance. MySQL automatically creates an empty database when it starts on an empty volume. MySQL server has two generic output terminals intended for accessing external services from scripts on the content volume. The log terminal can be used to connect MySQL to a shared file system on which MySQL can store its logs; mon terminal can be used to monitor the MySQL server from the monitor appliances (listed on this page).
MySQL Server 32Bit - Database Appliances
Resource Minimum Maximum Default
CPU 0.10 16 0.40
Memory 128MB 32GB 512MB
Bandwidth 1Mbps 2Gbps 250Mbps
MySQL Server 64Bit - Database Appliances
Resource Minimum Maximum Default
CPU 0.10 16 0.40
Memory 128MB 32GB 512MB
Bandwidth 1Mbps 2Gbps 250Mbps


MySQLR Database Server

MySQLR is a database appliance based on the MySQL database engine. It provides an easy way to add a database to any application. The appliance can also be used in complex MySQL replication scenarios. The appliance is based on MYSQL5 (CentOS 5/MySQL 5) but also handles database replication. Database replication enables data from one MySQL database server (known as "master") to be replicated to one or more MySQL database servers (known as "slaves"). The MySQLR appliance can be setup for master-slave as well as master-master replication and replication with more than two masters. The replication setup, management and monitoring is done via a web interface. The web interface provides an easy way to start replication with close to zero downtime on the master. It can also be used to repair a replication in case of problems. The web interface can be used for copying databases from older database appliances like MySQL and MySQL5. MySQLR also provides an easy way for managing and browsing your database (based on phpMyAdmin).
MySQLR Server 32bit - Database Appliances
Resource Minimum Maximum Default
CPU 0.10 16 0.40
Memory 128MB 32GB 512MB
Bandwidth 1Mbps 500Mbps 1Mbps


PGSQL Database Server

PGSQL is a database appliance based on the PostgreSQL database engine. It provides an easy way to add a database to any application. PGSQL is an enterprise-style database appliance that supports many features that are currently not supported by the MYSQLx appliances. Some of these features include stored procedures, triggers, views and user-defined data types. PGSQL stores the database on an application-defined volume that can be configured on each PGSQL instance. PGSQL optionally creates an empty database when it starts on an empty volume. The PGSQL database volume cannot be shared among multiple PGSQL instances (one database volume per PGSQL instance). PGSQL clients access the configured database through the in terminal. The database requests are processed and completed back through the same terminal. PGSQL allows any valid Postgres user to access the database through the in terminal (the appliance has one preconfigured superuser role: standard 'postgres'). PGSQL can be configured with the maximum number of concurrent connections supported through in.
PostgreSQL Server 32Bit - Database Appliances
Resource Minimum Maximum Default
CPU 0.1 16 0.40
Memory 128MB 32GB 512MB
Bandwidth 1Mbps 2Gbps 250Mbps
PostgreSQL Server 64Bit - Database Appliances
Resource Minimum Maximum Default
CPU 0.1 16 0.40
Memory 128MB 32GB 512MB
Bandwidth 1Mbps 2Gbps 250Mbps


NAS File Server

The NAS appliance is a shared file storage appliance. It provides file storage accessible over HTTP, NFS, and CIFS file protocols. The NAS appliance serves files contained within a configured (pluggable) data volume thus providing the ability for the content served by the appliance to be changed easily as well as the ability for the volume to have varied sizes. For example, if NAS is being used to store log files, the data volume does not need to be as large as what may be needed to store content for an apache server. The root directory of the volume is shared and the HTTP, NFS, and CIFS (samba) servers see the same volume, at the same root. The NFS server exposes the volume as a shared named /mnt/data. The CIFS server exposes the volume as a share named share. The root directory of the volume is accessible for read-only access by the HTTP server and for read-write access by the NFS and CIFS (samba) server. The security for http access may be open (no user/pwd), fixed single user/pwd (from property) or from .htpasswd file stored within the root directory of the data volume. The CIFS access is anonymous. It is assumed that only appliances that are allowed to access the volume are connected to the cifs terminal. This eliminates the need to configure complex security settings on the client and server and makes it possible to simply connect appliances that need file access to the cifs input.
NAS File Server 32bit - Misc. Appliances
Resource Minimum Maximum Default
CPU 0.1 16 0.2
Memory 64MB 32GB 256MB
Bandwidth 1Mbps 2Gbps 250Mbps


Load Generator

LOAD is a load generator which generates HTTP requests on its out terminal. Load generation is controlled through a simple web interface (GUI) exposed by LOAD. The GUI is accessed through the ctl terminal. The GUI also displays historical results of load generation. LOAD is capable of generating a maximum of 4000 requests per second and is designed to test how well your application can handle requests.
Load Generator - Misc. Appliances
Resource Miniumum Maximum Default
CPU 0.1 2.0 0.30
Memory 160MB 1GB 160MB
Bandwidth 1Mbps 100Mbps 1Mbps


Session-aware HTTP Load Balancer

HLB is a switch for distributing workload to multiple Web servers of the same type. Its operation is transparent both to the client and to the servers - each client sees it as one server and each server sees incoming requests as if they came directly from a client. Incoming HTTP requests are checked for association with a multi-request session and routed to one of the servers, as follows: * Requests not associated with any session (not having the session cookie present) are distributed using simple round-robin selection. * Requests that carry a session cookie are directed to the same server as the one that issued that cookie in the first place, if that server is alive; otherwise the next server from the round-robin schedule is chosen (note that taking down a server at runtime will break the client's session and require a re-login; the same will happen if the server dies on its own). The cookies are expired if replaced/deleted upon server request or upon a configurable timeout.
HLB Load Balancer 32bit - Switch Appliances
Resource Minimum Maximum Default
CPU 0.05 4 0.10
Memory 64MB 256MB 64MB
Bandwidth 1Mbps 2Gbps 200Mbps