r49 - 01 May 2009 - 12:07:13 - EricTYou are here: Wiki >  AppLogic24 Web > CatGenericLinux
ALERT! AppLogic 2.4 Documentation The latest production release is AppLogic 3.0.30

LINUX5, LINUX64, OSOL, OSOL64, SOL10, WIN03S, WIN03E, WIN03DC, WIN03W: Generic Servers

ALERT! In order to use Windows-based appliances in AppLogic you must have the 3tera Windows enhancement hotfix installed on your grid.

linux.PNG At a Glance
Catalog System
Category Generic
User volumes no
Min. memory See table below
OS Linux/Solaris/Windows
Constraints no
Questions/Comments:
LINUXx Ask Forum
Solaris Ask Forum
WIN03x Ask Forum

Functional Overview

LINUX5, LINUX64, OSOL, OSOL64, SOL10, WIN03S, WIN03E, WIN03DC and WIN03W are general server appliances. They can be branched to make new server appliances: singletons or server classes.

Each includes a reasonably complete installation of its OS, including the GCC compiler if available. This allows installing and building software on the branched appliances.

The generic server appliances are designed to be used in two ways:

  • As a customized server, by branching the base class to form singleton and modifying its class volume appropriately
  • As a template for building other server appliances, by using it as a base to create new application-specific or global catalog classes.


ALERT! Here 'server' means virtual server. Virtual servers are similar to appliances in all aspects except intent (virtual servers are made to be logged into for the installation of additional software) and volume size (much bigger than appliance's volumes).

IDEA! If you don't need GCC and the ability to build on the server appliance, consider using the LUX5 generic appliance template instead of LINUX5.

Name Latest Version OS Notes
LINUX5 1.2.1 CentOS 5  
LINUX64 1.2.1 CentOS 5 (64bit)  
OSOL 1.0.0 OpenSolaris build 2008.11  
OSOL64 1.0.6 OpenSolaris build 2008.11  
SOL10 1.0.4 Solaris 10 build GA This appliance is currently not distributed with AppLogic. Please contact Technical Support for more information.
WIN03S/WIN03E/WIN03DC/WIN03W 1.0.5 Windows Server 2003 32-bit Standard/Enterprise/DataCenter/Web Edition SP2 These appliances are currently not distributed with AppLogic. Please see the Windows Installation Reference for instructions on how to create these appliances.

Boundary

Resources

Linux based servers

Resource Minimum Maximum Default
CPU 0.05 16 0.25
Memory 64 MB 32 GB 256 MB
Bandwidth 1 Mbps 2 Gbps 100 Mbps

OpenSolaris servers

Resource Minimum Maximum Default
CPU 0.2 16 0.5
Memory 384 MB 32 GB 512MB
Bandwidth 1 Mbps 2 Gbps 100 Mbps

Solaris 10 server

Resource Minimum Maximum Default
CPU 0.5 16 0.5
Memory 384 MB 32 GB 512MB
Bandwidth 1 Mbps 2 Gbps 100 Mbps

Windows based servers

Resource Minimum Standard Maximum Enterprise Maximum DataCenter Maximum Web Maximum Default
CPU 0.1 4 8 4 2 0.25
Memory 256 MB 4 GB 32 GB 32 GB 2 GB 512 MB
Bandwidth 1 Mbps 2 Gbps 2 Gbps 2 Gbps 2 Gbps 100 Mbps

Terminals

Name Dir Protocol Description
in in any Generic input
out out any Generic output for a single host
net out any Generic output for subnet access
mon out cce Sends performance and resource usage statistics.

IDEA! One use of the net output is to connect it to the Subnet Output Gateway in order to download software to be installed on the server. Once you are finish installing, you can disconnect the gateway (or make it standby).

IDEA! If you branch one of the server appliances in order to create your custom appliances, you may want to remove the unnecessary interfaces.

Properties

(none)

Volumes

Servers have only a boot volume (instantiable class volume). There are no placeholder volumes (although when you branch this class to create a customized server, you can add a placeholder volume).


Notes

Solaris

The OpenSolaris and Solaris 10 servers have zpool_import installed as a legacy service. On stop, this service executes zpool export poolname on all ZFS pools which do not include a bootable dataset. On start, this service executes zpool import -a.

The zpool_import service leaves ZFS pools in an exported (portable) state when an appliance is stopped. This facilitates moving and copying pools from one application to another as well as modifying pools using the standard 3t shell vol commands, e.g., vol resize, vol copy, etc.

To manage ZFS pools manually, disable this service.

OpenSolaris appliances use zpool version 10 and zfs version 2.

Solaris 10 appliances use zpool version 4 and zfs version 1. To use zfs pools with these appliances, create them from raw volumes rather than through the CLI vol create command. The CLI vol create operation creates the root zfs dataset using zfs version 2 which is not backwards compatible.

Windows

Please see the Windows Appliance Notes for significant details on the operation of Windows appliances under AppLogic.

ALERT! Note that the Windows Server appliances (WIN03X) by default use a random Administrator password for security purposes. If this is not desired, change the password as described in the Windows Appliance Notes.

ALERT! Note that the Windows Server appliances generate a new random password whenever the appliance class name changes. If you wish to disable this behavior, open a Cygwin bash shell on the running appliance and edit the script /appliance/appliance.sh and insert a line exit 0 after the initial comment block.

Related documents

Questions and Comments

IDEA! To post a question or comment on this appliance, visit our forum.


-- PeterNic - 30 Dec 2005

 
Copyright © CA 2005-2011. All Rights Reserved.
%