Sun Microsystems SOLARIS 10 - Manual (Page 33)

Version 3.1-en Solaris 10 Container Guide - 3.1 3. Use Cases Effective: 30/11/2009
3.11. Test systems for developers
Requirement
[ug] Developers need test systems to test their application. Frequently, the interaction of several
computers must be tested as well. Resources for the installation of test systems are usually limited.
Since the developers spend most of their time working on developing, test systems have a low
workload.
• It is possible to share the use of test systems but it increases the time until the test is performed
since systems must be reinstalled or recreated.
• Scheduling conflicts can occur if different developers want to access systems at the same time.
• Backup/restore or installation are usually done by the operating department. The conventional
use pattern of test systems creates a certain amount of overhead here.
Solution
[ug] Developers' test systems are implemented by means of medium-sized computers with zones.
The details:
• Sparse root zones/whole root zones, as needed.
• Data are stored locally.
• Automatic zone creation.
• Automatic system configuration within the zone with sysidcfg.
• Automatic IP address administration.
• The developer becomes application administrator with root access.
• Software to be tested is installed locally.
• Option: Software installation (in part) per mount.
Assessment
[ug] This use case has the following characteristics:
• The operating department must operate far fewer test systems; each new test system therefore
only requires disk space, a separate computer is not needed.
• The creation of test systems can be fully automated; the overhead accrued for the operating
department is therefore much lower.
• Developers can retain several test systems at the same time; only the ones currently in use
must be booted up. A comparison of functionalities in the different versions is possible without
much effort.
• No waiting period (for restore) or coordination (with other tests run on the machine) is required
to perform a test.
26
Figure 17: [dd] Use case: Developer test systems
Global Zone
System
Developer
A
Developer
B
Developer
C
Developer
D
Devel-
oper
E