Darren J Moffat wrote: > James Carlson wrote: >> It should not be the case that there are special things that can be >> done when the system is installed, and that cannot be done at other >> times. In fact, the process of setting up these bits of configuration >> shouldn't be different. (E.g., setting up name services.) > Exactly our thoughts with Caiman. system configuration is system configuration. > sysidkrb5 and kclient being my personal bug about these being different. > > I pushed hard for kclient functionality to be done in sysidkrb5 but I > got out consensused (yeah I know that isn't a word but there wasn't a > vote this was ARC fast-tracks). > > The other thing about sysid is that the bits need to be able to be > configured and unconfigured independently of each other and unless > they really really require a reboot they shouldn't do it. > > So I'm 100% with James here, configuration can be done as part of > install but it must be 100% functional after install too in exactly > the same way. Just to clarify, this is exactly what we intend and are trying to ensure with the Caiman architecture. I probably did not make that point clear. System configuration can be done as part of install but the tool that is being developed for system configuration will the general tool that will be used non-install time system configuration. > > In my definition (and I assume the one James uses) Configuration does > not imply picking which packages to install, only configuring things > in those packages that have been selected for install. This kind of > implies that we should run sysid AFTER install, or at least after > package selection, not before it like we currently do. > Right.. configuration doesn't mean picking packages. That is a totally separate piece of functionality. And as for when to run it, it is likely we will have very minimal configuration stuff to do during the actual 'install' but will allow the user to configure their systems after the bits are laid down on disk.
> One other data point is that I believe this is the model that most if > not all of the products in the JES stack are either doing now or are > moving towards. > We are working with the JES folks, specifically looking at their unified installer for possible use in Caiman. thanks, sarah ****
