Previous Topic: LINUX5, LINUX64: Generic Linux ServersNext Topic: Dynamic Catalog


OSOL, OSOL64, SOL10: Generic Solaris Servers

OSOL, OSOL64, SOL10: Generic Solaris Servers

At a Glance

Catalog

System

Category

Generic

User volumes

no

Min. memory

384 MB

OS

Solaris

Constraints

no

Functional Overview

OSOL, OSOL64, and SOL10 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:

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

Name

Latest Version

OS

Notes

OSOL

1.0.9-1

OpenSolaris build 2008.11

 

OSOL64

1.1.9-1

OpenSolaris build 2008.11

 

SOL10

1.0.4

Solaris 10 build GA

This appliance is currently not distributed with CA 3Tera AppLogic. Contact Technical Support for more information.

Boundary

Resources

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 Servers

Resource

Minimum

Maximum

Default

CPU

0.5

16

0.5

Memory

384 MB

32 GB

512MB

Bandwidth

1 Mbps

2 Gbps

100 Mbps

Terminials

TerminalsName

Diriction

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.

Notes:

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

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

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 data set. 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, for example, vol resize, vol copy, and so on.

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 data set using zfs version 2 which is not backwards compatible.

Open source and 3rd party software used inside of the appliance

OSOL and OSOL64 uses the following 3rd party/open source packages in addition to any open source and 3rd party packages included as part of their base install of OpenSolaris build 2008.11.

Software

Version

Modified

License

Notes

osol-0811.iso

0811

No

opensolaris

OpenSolaris only

SUNWexpect

5.43-0.101

No

GPLv2

N/A

SUNWgccruntime

3.4.3-0.101

No

GPLv2

N/A

SUNWgcc

3.4.3-0.101

No

GPLv2

N/A