Johan Hartzenberg wrote: > > > On Thu, Dec 11, 2008 at 2:31 PM, jan damborsky <Jan.Damborsky at sun.com > <mailto:Jan.Damborsky at sun.com>> wrote: > > Both AI (Automated Installation project) and DC (Distribution > Constructor project) > are part of Caiman which is set of projects focused on creating a > new OpenSolaris > installation experience. > > The mission of Automated Installation project is to provide > features to support > completely 'hands off' installation. > > The Distribution Constructor project is building a set of GUI and > command-line > tools allowing users to build an install image from a package > repository. > The distribution constructor tools accept input from the user and > process > a set of repository packages into one or more media images which > can be > utilized to install an OpenSolaris distribution. > > You can find more details about Caiman as well as particular projects > on following pages: > > http://www.opensolaris.org/os/project/caiman/ > http://www.opensolaris.org/os/project/caiman/auto_install/ > http://www.opensolaris.org/os/project/caiman/Constructor/ > > > Wow, that is excellent! From this, can I guess there will be a way to > set up your own in-house package repository from which to deploy > servers, workstations, allowing you to control what versions of OS, > applications, libraries, etc and what configuration details will be > delivered to specific hosts during installation?
It is currently possible to create/setup your own package repository which can be then used as source repository for DC or AI. Please see pages dedicated to Image Packaging System (IPS) project for details: http://www.opensolaris.org/os/project/pkg/documents/Nov2008/ The same machine can serve as both install server and package repository. > > Being an ex onsite Unix administrator I imagine customers would like > to see a way to achieve both of the following two things from a single > "package/install server" > a) Boot up a machine from a disk which automatically finds the > install/package server and then automatically knows what to install, or > b) Boot up a machine from an interactive CD which connects to the > install server and then allows me to select a "profile" to be deployed > onto that system. > > I conclude that this is more or less what is envisioned, and that > network boot options are also included into the pot? At time of being Automated Installer preview supports installation from network on x86 platform (taking advantage of PXE boot). The work on Sparc version is currently in progress. Scenarios you described above are currently not designed/implemented, but definitely will be subjects of further discussions. > > Good work! Thank you very much for your feedback ! Jan > > _J > > -- > Any sufficiently advanced technology is indistinguishable from magic. > Arthur C. Clarke > > My blog: http://initialprogramload.blogspot.com
