Our current configuration in production is 2 x Sun T2000 (8 core, 32GB RAM), each running: 1 x Cluster manager in its own Solaris 10 zone 2 x Portal nodes (both members of the single cluster) each in their own Solaris 10 zone
Can we create a new Solaris 10 zone (at each site) on the same hardware, install portal in it and run it as an additional member of the cluster, without extra cost.
Q: Can we create a new Solaris 10 zone (at each site) on the same hardware
A: The customer is able to create zones in Solaris 10. The limitations of the zone is similar to any virtualisation technique in that the zone is using disk, cpu, network and devices. If the hardware can handle the increased load this is a potential option.
Review the current hardware’s performance, capacity and growth characteristics. Review again with the additional zone and the expected workloads.
The zone capability is an implementation of operating system level virtualization technology provided in Solaris 10.
Q: install portal in it and run it as an additional member of the cluster,
A: The T2000 server supports zones via Solaris 10. Each zone can operates as a separate instance within a global zone. WebSphere Portal v6.0.0.x is supported in a non global zone..> link
Inland Revenue are able to deploy WebSphere Portal in the proposed deployment.
Solaris Containers (including Solaris Zones ) is an implementation of operating system-level virtualization technology first made available in 2005 as part of Solaris 10 .
A Solaris Container is the combination of system resource controls and the boundary separation provided by zones . Zones act as completely isolated virtual servers within a single operating system instance. By consolidating multiple sets of application services onto one system and by placing each into isolated virtual server containers, system administrators can reduce cost and provide all the same protections of separate machines on a single machine.
A Solaris Zone is a partitioned virtual OS environment working in a Solaris OS space.
There are two types of Solaris Zones: Global Zones and Non-Global Zones.
Global Zone is the traditional OS environment and is where Solaris OS is installed. All system operations such as installations, startups and shut-downs are done in the Global Zone. However the 8000+ Non-Global Zone entities work as virtual Solaris OS environments within the Global Zone.
Only Disk and Network interfaces defined in the Global Zone can be used in the Non-Global Zones. Definition can only be done in the Global Zone. Non-Global Zones are more simply referred to as Zones.
If you have experience with Solaris OS configuration and operation, it is easy to construct and operate Zones. Your configuration tasks remain familiar as most OS parameters including Timezone succeed from Solaris OS to each Zone. Network configurations such as Host names and IP addresses must be configured in each Zone. Plus, to ensure the system security at Zone level, root privileges are placed in each Zone so that each Zone can be managed as an independent system. System startup and shut-down control is performed in the Global-Zone by the zoneadm(1M) command.
Each Zone has a dedicated directory under the Global Zone's file system. Zone installation then constructs a dedicated directory. In the global Zone, access to all files or directories under each dedicated Zone directory is permitted. But in each Zone, files or directories not included in the dedicated Zone directory can't be accessed. Directories in Global Zone can be mounted to a Zone's dedicated directory . You can also choose the access mode to the mounted directories, enabling either read-only or read-write.