Part 3: Glassfish V3 Pet Catalog sample DEMO in VM Template - SW Installation
By natiku on Dec 20, 2009
In this example I will DEMOnstrate creation of Evaluation type Virtual Appliance / VM Template which will leveradge OpenSolaris 200906 JeOS prototype and just in Dec/09 released Glassfish v3, Java EE 6 and Netbeans 6.8 with simple Java EE 6 demo. This entry is part of Virtual Appliances & OVF workshop.
New Glassfish V3 introduce an unique network repository based modular structure, so we can more easily create really simple initial DEMO setup which user can extend by installation more samples right from Glassfish V3 repository or from Netbeans GUI.
Step 2: Add layered software
Now we will install and configure layered software (web containers and/or applications that you want to expose through the template). Create default users.
Step 2a: Bundled vs UnBundled SW installation
Bundled software is part of OS installation , UnBundled is installed interdependently from OS installation.
For our Developer oriented DEMO like Virtual Appliances / VM Templates we will use a UnBundled installation ,
because we can put SW installation to separate ZFS filesystem and developer can easily to snapshot or clone it.
UnBundled SW , also called layered SW, depend on SW installed OS, but there is no direct dependencies check on
this type of installation, so dependencies need to be checked manually.
UnBundled SW distributions are ofter backed by dedicated SW repository , we need to be sure repository related license
allow redistribution and in repository have miced FOSS/Commercial SW then we will not install commercial SW with limited
distribution and /or with limited evaluation time.
Step 2b: Using UnBundled SW Installation for our DEMO
For Glassfish V3 we will use Community edition, for MySQL we will use a WebStack installation.
Both this UnBundled distribution use a GUI based tool for Update Center image management, but JeOS is CLI only
environment, we will provide samples how to manage image with CLI, in case then developers want to work in GUI, they will
need to install minimal X/GUI libs environment, see:
For check for OS install level dependencies we can use samples in
Step 2c: OpenSolaris is dual arch (32bit and 64bit) environment
Opposite to Linux , OpenSolaris is dual arch (32bit and 64bit) environment, because some Virtualization Platforms are still 32bit or
32bit execution is fallback execution profile, when there are issues with COU build-in Hardware Assisted virtualization support.
Ideally will by if we can support both 32bit and 64bit OpenSolaris boot modes.
Step 2d: Creating a dedicated ZFS fs for UnBundled installation
1. User osol have home under dedicated export ZFS fs
osol@osol-jeos:~$ zfs list | grep export rpool/export 68K 6.31G 20K /export rpool/export/home 48K 6.31G 20K /export/home rpool/export/home/osol 28K 6.31G 28K /export/home/osol
2. Create a dedicated unbundled ZFS fs under osol home
osol@osol-jeos:~$ pfexec zfs create rpool/export/home/osol/unbundled osol@osol-jeos:~$ pfexec zfs set mountpoint=/export/home/osol/unbundled rpool/export/home/osol/unbundled osol@osol-jeos:~$ pfexec chown osol:staff /export/home/osol/unbundled
3. Check ZFS used space before SW installation
osol@osol-jeos:~$ pfexec zfs list NAME USED AVAIL REFER MOUNTPOINT rpool 1.51G 6.31G 83.5K /rpool rpool/ROOT 646M 6.31G 19K legacy rpool/ROOT/opensolaris 646M 6.31G 646M / rpool/dump 384M 6.31G 384M - rpool/export 89K 6.31G 20K /export rpool/export/home 69K 6.31G 20K /export/home rpool/export/home/osol 49K 6.31G 30K /export/home/osol rpool/export/home/osol/unbundled 19K 6.31G 19K /export/home/osol/unbundled rpool/swap 512M 6.81G 20K - osol@osol-jeos:~$ pfexec df -h Filesystem Size Used Avail Use% Mounted on rpool 6.4G 84K 6.4G 1% /rpool rpool/ROOT/opensolaris 7.0G 647M 6.4G 10% / rpool/export 6.4G 20K 6.4G 1% /export rpool/export/home 6.4G 20K 6.4G 1% /export/home rpool/export/home/osol 6.4G 30K 6.4G 1% /export/home/osol rpool/export/home/osol/unbundled 6.4G 19K 6.4G 1% /export/home/osol/unbundled
Step 2b: Install and configure MySQL
1. Check ZFS used space before SW installation
root@osol-jeos:~$ zfs list NAME USED AVAIL REFER MOUNTPOINT rpool 1.51G 6.31G 83.5K /rpool rpool/ROOT 646M 6.31G 19K legacy rpool/ROOT/opensolaris 646M 6.31G 646M / rpool/dump 384M 6.31G 384M - rpool/export 68K 6.31G 20K /export rpool/export/home 48K 6.31G 20K /export/home rpool/export/home/osol 28K 6.31G 28K /export/home/osol rpool/swap 512M 6.81G 20K - root@osol-jeos:~$ df -h Filesystem Size Used Avail Use% Mounted on rpool/ROOT/opensolaris 7.0G 647M 6.4G 10% / swap 1.1G 228K 1.1G 1% /etc/svc/volatile swap 1.1G 4.0K 1.1G 1% /tmp swap 1.1G 28K 1.1G 1% /var/run rpool/export 6.4G 20K 6.4G 1% /export rpool/export/home 6.4G 20K 6.4G 1% /export/home rpool/export/home/osol 6.4G 28K 6.4G 1% /export/home/osol rpool 6.4G 84K 6.4G 1% /rpool