Oracle Solaris 10 branded zones –
Oracle Solaris 10 Zones provide an Oracle Solaris 10 environment on Oracle
Solaris 11. You can migrate an Oracle Solaris 10 system or zone to a solaris10 zone on an Oracle Solaris 11
system in the following ways:
- Create a zone archive and use the archive to create an s10zone on the Oracle Solaris 11 system. See Transitioning an Oracle Solaris 10 Instance to an Oracle Solaris 11 System.
- Detach the zone from the Oracle Solaris 10 system and attach the zone on the Oracle Solaris 11 zone. The zone is halted and detached from its current host. The zonepath is moved to the target host, where it is attached. See About Detaching and Attaching the solaris10 Zone in Oracle Solaris Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management.
The zonep2vchk tool
identifies issues that could affect the migration, and creates zone
configuration output for the target zone.
Oracle Solaris 11 installation support
– You can specify the configuration and installation of non-global zones as
part of an AI client installation. Non-global zones are installed and
configured on the first reboot after the global zone is installed. See Chapter
12, Installing and Configuring Zones, in Installing Oracle Solaris 11
Systems.
Whole root zones only – Oracle Solaris
Zones are whole-root type only, but you can configure your zones in a more
flexible way, such as when disk space is limited or if you prefer a read-only
zone root configuration. By default, zone boot environments are compressed.
Legacy branded zones – The following
legacy branded zone features are only supported in Oracle Solaris 10 releases:
·
Linux brand (lx)
·
Oracle Solaris 8 Containers (solaris8)
·
Oracle Solaris 9 Containers (solaris9)
Exclusive IP zones by default –
Exclusive-IP zones enable you to assign a separate IP stack per zone. Each zone
has the flexibility to configure IP within that stack completely separate to
other zones. Administrators can easily observe network traffic, per zone, and
apply individual network resources. However, in previous versions of Oracle
Solaris this was dependent on the number of physical NICs an administrator had
per system. The addition of network virtualization provides administrators
enhanced flexibility with regard to managing zones, without the restrictions of
physical network hardware. Newly created zones in Oracle Solaris 11 will be
exclusive-IP zones with a VNIC, net0,
whose underlying lower link is automatically selected at boot time. See Chapter 10,
Managing Oracle Solaris Releases in a Virtual Environment.
Network virtualization for zones –
Oracle Solaris 11 network virtualization features can be applied to a zone by
creating a virtual NIC (VNIC) for the zone and applying bandwidth limits and
traffic flows to the zone's assigned VNIC. The VNIC is created when the zone
boots and deleted when the zone halts, and will be created within the
non-global zone's datalink namespace. This feature allows you to provision a
zone without having to learn the details of network configuration and topology.
If you want to assign a preexisting datalink to an exclusive-IP zone, you can
still do so during the zone configuration.
For example, create a virtual NIC, limit the SPEED of the VNIC, create an
address for it, and then assign it to zone.
#
dladm create-vnic -l net0 -p maxbw=600 vnic0
#
ipadm create-addr -T static -a local=x.x.x.x/24 vnic0/v4static
zonecfg:s11zone>
set ip-type=exclusive
zonecfg:s11zone>
add net
zonecfg:s11zone:net>
set physical=vnic0
zonecfg:s11zone:net>
end
The ip-type
value for the zone can either be shared
or exclusive:
The ip-type=exclusive
value means that you are dedicating a datalink, which can be a virtual (VNIC)
for exclusive use by the zone. This strategy brings some of the network stack
management benefits to the zone. Historically, this hasn't been practical if a
system has many zones, but only a maximum of 4 network interfaces.
Exclusive IP is now the recommended ip-type
for zones. The set physical
value identifies the system's network interface cards that is assigned to the
zone. Using an ip-type of
exclusive allows the zone to manage its IP stack directly.
If ip-type=shared
was identified in the above example, you would have to specify an IP address
and other resources.
NFS server support in non-global zones
– You can share file systems in a non-global zones by using the NFS protocol.
The SMB (CIFS) sharing protocol is not currently available in a non-global
zone.
Zone monitoring – System resources
that are consumed by non-global zones can be monitored by using the zonestat command.
Oracle
Solaris 10 Branded Zones Preparation
Prepare for migrating a Oracle
Solaris 10 OS instance or zone to your Oracle Solaris 11 system.
Confirm that your Oracle Solaris 10 instance or zone is
running the Oracle Solaris 10 9/10 release, which is the minimum OS
requirement.
Copy the Oracle Solaris 11 /usr/sbin/zonep2vchk
script to any location within the Oracle Solaris 10 system. Run this
script to determine if any issues would prevent the Oracle Solaris 10 zone
or instance from running successfully on a Oracle Solaris 11 system.
Keep in
mind that this script is only for system migration purposes.
- Enable the Oracle Solaris 10 package and patch tools.
To use the
Oracle Solaris 10 package and patch tools in your Oracle Solaris 10 zones,
install the following patches on your source Oracle Solaris 10 system before
the image is created.
- 119254-75, 119534-24, 140914-02 (SPARC platforms)
- 119255-75, 119535-24 and 140915-02 (x86 platforms)
The
physical to virtual (P2V) process works without the patches, but the package
and patch tools do not work properly within the Oracle Solaris 10 zones.
Transitioning
an Oracle Solaris 10 Instance to an Oracle Solaris 11 System
You can transition your Oracle
Solaris 10 environment to a non-global zone on an Oracle Solaris 11 system by
creating a zone archive and migrating the zone archive to an Oracle Solaris 11
system. The following steps describe this process.
- Install the Oracle Solaris 10 zone package on your Oracle Solaris 11 system. For example:
s11sysB#
pkg install system/zones/brand/brand-solaris10
- Copy the zonep2vchk script from your Oracle Solaris 11 system to the Oracle Solaris 10 instance or system to identify any issues that might prevent the instance from running as a solaris10 zone.
3. s10sys#
./zonep2vchk
4. --Executing
Version: 1.0.5-11-15652
5.
6. - Source System: tardis
7. Solaris Version: Oracle Solaris 10 8/11
s10s_u10wos_17b SPARC
8. Solaris Kernel: 5.10 Generic_147440-01
9. Platform: sun4u SUNW,Sun-Fire-V440
10.
11. - Target System:
12. Solaris_Version: Solaris 10
13. Zone Brand: native (default)
14. IP type: shared
15.
16.--Executing
basic checks
17..
.
- Create a ZFS file system that will contain the flash archive of the Oracle Solaris 10 system instance, if necessary.
Then,
create a NFS share of the ZFS file system on your Oracle Solaris 11 system. For
example:
s11sysB#
zfs create pond/s10archive
s11sysB#
zfs set share=name=s10share,path=/pond/s10archive,prot=nfs,root=s10sysA
pond/s10archive
name=s10share,path=/pond/s10archive,prot=nfs,sec=sys,root=s10sysA
s11sysB#
zfs set sharenfs=on pond/s10archive
- Select an Oracle Solaris 10 instance, which could be a virtual environment or a global zone on a Solaris 10 system. Note the Oracle Solaris 10 system's hostid.
20.s10sysA# hostid
8439b629
- Create an archive of the Oracle Solaris 10 instance that you would like to migrate to a non-global zone on the Oracle Solaris 11 system.
s10sysA#
flarcreate -S -n s10sysA -L cpio /net/s11sysB/pond/s10archive/s10.flar
- Create a ZFS file system for the Oracle Solaris 10 zone.
23.s11sysB# zfs
create -o mountpoint=/zones pond/zones
s11sysB#
chmod 700 /zones
- Create the non-global zone for the Oracle Solaris 10 instance.
25.s11sysB# zonecfg
-z s10zone
26.s10zone:
No such zone configured
27.Use
'create' to begin configuring a new zone.
28.zonecfg:s10zone>
create -t SYSsolaris10
29.zonecfg:s10zone>
set zonepath=/zones/s10zone
30.zonecfg:s10zone>
set ip-type=exclusive
31.zonecfg:s10zone>
add anet
32.zonecfg:s10zone:net>
set lower-link=auto
33.zonecfg:s10zone:net>
end
34.zonecfg:s10zone>
set hostid=8439b629
35.zonecfg:s10zone>
verify
36.zonecfg:s10zone>
commit
zonecfg:s10zone>
exit
- Install the Oracle Solaris 10 non-global zone.
38.s11sysB# zoneadm
-z s10zone install -u -a /pond/s10archive/s10.flar
39.A ZFS file
system has been created for this zone.
40.Progress
being logged to /var/log/zones/zoneadm.20110921T135935Z.s10zone.install
41. Installing: This may take several
minutes...
42.
Postprocess: Updating the image to run within a zone
43. Postprocess: Migrating data
44. from:
pond/zones/s10zone/rpool/ROOT/zbe-0
45. to: pond/zones/s10zone/rpool/export
46..
47..
.
- Boot the Oracle Solaris 10 zone.
#
zoneadm -z s10zone boot
- Configure the Oracle Solaris 10 non-global zone.
50.s11sysB# zlogin
-C s10zone
51.[Connected
to zone 's10zone' console]
52..
53..
54..
55.s10zone
console login: root
56.Password: xxxxxxxx
57.# cat
/etc/release
58. Oracle Solaris 10 8/11
s10s_u10wos_17b SPARC
59. Copyright (c) 1983, 2011, Oracle and/or its
affiliates. All rights reserved.
60. Assembled 23 August
2011
61.# uname
-a
62.SunOS
supernova 5.10 Generic_Virtual sun4v sparc SUNW,Sun-Fire-T1000
63.# zfs
list
64.NAME USED AVAIL
REFER MOUNTPOINT
65.rpool 4.53G 52.2G
106K /rpool
66.rpool/ROOT 4.53G
52.2G 31K legacy
67.rpool/ROOT/zbe-0 4.53G
52.2G 4.53G /
68.rpool/export 63K
52.2G 32K /export
rpool/export/home 31K
52.2G 31K /export/home