Information Technology Reference
In-Depth Information
In addition to virtual analogues of physical network devices, OpenSolaris
provides the ability to constrain the amount of network bandwidth used by a
Container. You can set a bandwidth limit for each network interface—even vir-
tual ones.
GZ#
dladm set-linkprop -p maxbw=50m vn_cl1
GZ#
dladm set-linkprop -p maxbw=50m vn_cl2
GZ#
dladm show-linkprop -p maxbw
LINK PROPERTY PERM VALUE DEFAULT POSSIBLE
bge0 maxbw rw -- -- --
vn_srvr maxbw rw -- -- --
vn_router maxbw rw -- -- --
vn_cl1 maxbw rw 50m -- --
vn_cl2 maxbw rw 50m -- --
Containers provide all of the strengths of the OSV model:
Compute efficiency.
Containers have almost zero overhead, giving them
an advantage over hypervisors, which use CPU cycles for I/O transactions,
and over-partitioning, which leaves CPU cycles unused even when another
workload could use those resources.
■
Storage efficiency.
A Container can use as little as 100 MB of disk space
and as little as 40 MB of RAM.
■
Hardware independence.
Containers do not depend on any hardware
features and do not have any code specific to one instruction set. They are
currently supported on x86/x64 and SPARC architectures, with ports of
OpenSolaris to other CPU types under way.
■
Observability.
The kernel controls access to all information regarding its
Containers, so tools such as DTrace can simultaneously view internal details
of multiple Containers and their processes.
■
In addition, Containers have advantages over other forms of OSV:
Solaris 8 Containers and Solaris 9 Containers allow you to run all of the
software from an older system on a system running Solaris 10.
■
Search WWH ::
Custom Search