Hi Sarah, thank you for looking at this !
I have captured the outcome on System Configuration Project pages (in section Automated Installer): http://hub.opensolaris.org/bin/view/Project+caiman/System+Configuration+Project Thanks again ! Jan On 02/22/10 09:18 PM, Sarah Jelinek wrote: > Hi Jan, > > Your proposal makes sense to me. I have no additional comments other > than that. > > thanks, > sarah > **** > > On 02/16/10 05:47 AM, Jan Damborsky wrote: >> Hi, >> >> thank you all who provided valuable feedback with respect to >> how format of System Configuration manifest should look like. >> >> Please see below for design draft which contains proposal >> for common format of System Configuration manifest used >> to configure target system installed by means of Automated >> Installer. >> >> Document does not address how System Configuration manifest >> will be embedded within AI manifest - this problem is to >> be addressed by DC/AI manifest rework effort. >> >> If possible, please provide your comments before COB Friday >> February 19th. >> >> Thank you, >> Jan >> >> >> Background >> ---------- >> >> For purposes of Automated Installer, configuration of system >> to be installed will be specified in form of set of configuration >> parameters provided in System Configuration Manifest. >> >> Requirements >> ------------ >> >> * Set of supported configuration parameters should be extensible >> without need to modify the installer >> * allow to syntactically and semantically validate the manifest >> if needed >> * allow to dynamically determine selected configuration parameters >> on client side >> >> Constraints >> ----------- >> Automated Installer will configure target system by >> applying SMF profile defining set of SMF properties carrying >> information about desired system configuration. >> Configuration will take effect during first boot when SMF >> properties will be processed by related SMF services. >> >> Solution >> -------- >> Since all system configuration parameters will be in form of >> SMF properties and system configuration will be carried out by >> applying appropriate SMF profile to the installed system, >> it is being proposed that format of SC manifest matches SMF >> profile to be applied to the installed system. >> >> That will allow: >> >> * Automated Installer to directly use System Configuration >> manifest as SMF profile to be applied to target system >> when feasible. >> Minimum interaction would be needed - e.g. manifest >> would be only syntactically validated. >> >> * to introduce support for new configuration parameters >> without need to accommodate the installer >> >> * if desired, to involve Automated Installer (by designing >> necessary plug-ins) in processing System Configuration >> manifest for purposes of >> - semantic validation >> - dynamic modification of desired configuration parameters >> >> Based on this assumption, System Configuration manifest will >> have following characteristics: >> >> * it will be provided in form of one XML DTD document >> containing all system configuration parameters >> * it will validate against following schema: >> /usr/share/lib/xml/dtd/service_bundle.xml >> * all system configuration properties will be in format >> of SMF properties for one of SMF services delivered to >> target system during installation process >> >> Example >> ------- >> >> See [1] for example showing System Configuration manifest >> defining networking configuration (setting static IP and DNS >> as naming service). >> >> References: >> [1] Format of networking part of system configuration (networking SMF >> profile) >> http://hub.opensolaris.org/bin/download/Project+caiman/System+Configuration+Project/networksmfprofile.xml >> >> >> >> >> Related links: >> System Configuration Project pages >> http://hub.opensolaris.org/bin/view/Project+caiman/System+Configuration+Project >> >> >> >> >> _______________________________________________ >> caiman-discuss mailing list >> caiman-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >>
