By ckamps on Nov 12, 2009
Since build 126 of OpenSolaris was recently released, it was time to update my Automated Install (AI) server and to verify that the reduced installation profile I had tested using build 125 was still working properly. Overall, the process was straightforward and trouble free.
Updating the reduced OpenSolaris installation took very little time because only 78 MB was needed to update the 200 or so packages installed on my AI server. This is a key benefit of using a reduced installation of an OS: you can dramatically reduce update overhead by downloading and applying updates for only those packages that matter to your particular application. It's also a testament to the pkg(5) system in that it is able to bring down only updated files rather than being forced to always download complete packages.[Read More]
Just over 7 minutes to install a text-oriented, headless server OpenSolaris system from scratch?
This is the next installment in my effort to establish an
efficient development and test environment for experimental OpenSolaris
base installation profiles. In this entry I address how to hook a
heavily reduced form of the OpenSolaris development package repository
into an Automated Installer environment to produce text-oriented, headless server installs of OpenSolaris.
In this post I explain how I've used the pkg(5) system's content retrieval client, pkgrecv(1),
to establish a reduced form of the OpenSolaris development package
repository on a local system for the purpose of optimizing my Automated
Installer (AI)-based installations.
In my recent post on Initial Experiments with Base Install Profiles,
I described how I am using the OpenSolaris Automated Installer and
VirtualBox to experiment with heavily reduced or minimized
installations of OpenSolaris. Use of a local copy of a repository will
dramatically increase the speed of installing these heavily reduced
This post is a follow-on to the entry describing how to set up an OpenSolaris Automated Installer (AI) environment using the JeOS prototype and VirtualBox. In this entry I describe how to use a custom AI manifest representing an experimental base installation profile to install a greatly reduced or minimized form of OpenSolaris in a VirtualBox virtual machine - just ~90 or so packages and an installed footprint of ~570 MB. The resulting installations are text-oriented, headless server installations containing only enough features to enable developers to add more packages and customize the environment to suit their specific needs.
A slightly modified form of the AI manifest can be
used to realize similarly reduced installations in other system
virtualization and bare metal environments.
Experimenting with base installation profiles is part of the OpenSolaris JeOS project's effort to help define a formal base installation profile for OpenSolaris.[Read More]
Given the popularity of system or server virtualization products and technologies including VMware, Xen, Sun xVM VirtualBox, etc. in addition to Sun's upcoming xVM Server product, partners, prospects and customers often ask whether Sun supports the deployment of our middleware on these environments. Historically, we've provided inconsistent answers to this question. Fortunately, Sun recently released an official support statement to help address this issue.
Updated March 9, 2009
This article describes the results of the first of several experiments intended to demonstrate how projects' build environments can be enhanced to deliver pkg(5)-based distributions. In this article we address the first stage of an experiment based on the popular OpenDS project.
Update: As of late 2009, building the pkg(5) form of delivering
OpenDS is available in the official OpenDS source tree and is
documented on the OpenDS wiki. After satisfying a couple of
dependencies, you can
build the packages and download bundle image straight from the official
OpenDS source. See the document Build and Use OpenDS in pkg(5) Format for details.