Jan Damborsky wrote: > Keith Mitchell wrote: >> All, >> >> In some discussions I had today, the issue came up of post-install >> customization of the VM Constructor image. Current design flow limits >> our customization options to installation of custom packages - the >> user can install packages A, B, and C, but they can't specify other >> parameters such as network settings, user groups, etc. >> >> How can we support post-install non-package customizations? Could >> this be done via SMF enhanced profile work? Using DC finalizer >> scripts (into the AI image, prior to VM install)? In some other >> manner? To make the VM constructor robust, I think we'll want more >> than just the basics of package selection and VM settings. > > With respect to customization of created VM image, I am thinking if > there might be another level of customization based on the scope of > the project. > > Is it assumed that all customization will be done when image is > constructed or will it be allowed to do some customization steps > when VM image is used as a 'template' which might be instantiated/ > deployed later on more than one guest system ?
Good question. Based on the initial conversation about this it appears that the VMC team is relying on eSMF which is an install time thing to configure the 'system' in the VM. Which means it will be baked in to the .ovf file that is eventually exported. If this isn't what we want the user experience to be we need to look at this more and understand the requirements. thanks, sarah **** > For instance, we might want to customize IP address/hostname/root > password for each virtual machine created VM image will be deployed on. > > Thank you, > Jan > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
