Hi Evan,
On 02/24/10 04:56 PM, Evan Layton wrote: > On 2/24/10 7:29 AM, Jan Damborsky wrote: > >> To ease the transition, maybe we could compare common scenarios - >> how configuration is done in case of jumpstart (by means of >> setup_install_server & add_install_client) and then show how to set >> up AI server for the same scenario by means of installadm(1M) tools. > > I don't think this would really be different from any other package > installation. The installation would include the creation of the > smf service that runs on first reboot which would do the expected > installadm tasks. Based on this it should be possible to show this > as an example. Sorry about the confusion - I had slightly different use case in my mind. In the proposal only client side is covered, so I was not sure if server side is also in scope. I was thinking about administrators who manage jumpstart servers and are used to jumpstart model with respect to configuration of jumpstart clients - we could demonstrate on examples how things change, e.g. with introduction of 'install service' paradigm. For instance, in jumpstart * each client to be installed has to be added by 'add_install_client'. It is not necessary with AI - one install service can serve more clients. * there is a distinction between boot server and install server - 'setup_install_server' allows to set them up separately on different machines. It is different with AI - one machine serves both AI images as well as configuration files, but you additionally need to have IPS server set up which provides bits to be installed. * ... Jan
