So if I read this correctly, the only way we can control what package 
versions are used for both the OS and add on packages is through 
maintaining separate repositories ?

Since Sun Mfg installs have a mix and match requirement for add on 
packages we have a modular approach that installs the required OS 
version and then the additional packages, netbeans, SSexp, LDOM etc as 
needed usually by a part number.

I have been searching opensolaris.org for clues on how to do this...

...Les

Dave Miner wrote, On 02/18/09 08:07:
> Sean McGrath wrote:
>> The suituation:
>>   Network boot a machine with AI image osol_0906-106a
>>   Fine, creates the zpool, pulls the pkgs from repo, sets up grub etc..
>>   All nice.
>>
>>   However the latest bits on the IPS repo are snv_107 based.
>>
>>   So all the pkgs pulled with this 106 based AI image are snv_107 ones.
>>   So we end up with a snv_107 based osol installed machine.
>>
>>   The package version can be specified in the manifest like:
>>         <ai_packages>
>>                 
>> <package_name>slim_install at 0.1,5.11-0.106</package_name>           
>> </ai_packages>
>>
>>    (right ?)
>>
>>   but on an AI server which may be installed a few dozen machines at 
>>   any given time and where scripts to create manifests can break :},
>>   theres an amount of work needed to be sure we install with what we 
>> want.
>>     We may want to at any time install AI image $bar and not have 
>> version $foo
>>   installed.
>>     As an enhancement, the AI image could pull packages whose version
>>   matches its own build.  Eg. for osol_0906-106a it'd pull version
>>   0.5.11,5.11-0.106 packages unless otherwise specified in a manifest.
>>
>>   Without this enhancement, the suituation could arise where an older
>>   version of an AI image is used, it creates a zpool, installs the 
>> pkgs etc.
>>   However on rebooting the machine finds its zpool being an older 
>> version,
>>   the grub menu possibly different to what it expects, even perhaps the
>>   boot_archive synced with the AI image's idea of the universe 
>> instead of
>>   the version on disk.
>>
>>   Sound viable ?
>>
>>  Logged this as an RFE:
>>    6724 AI image should perhaps specifiy the pkg versions of any pkgs 
>> it pulls from a repo
>>
>
>
> No, in my opinion that's an undesirable skew from the default behavior 
> that users will get with running "pkg" directly and will lead to even 
> greater confusion in that direction.  If you want a specific branch, 
> you need to specify that branch in the manifest, and I believe we 
> already have a bug about that needing to be supported.
>
> Dave
> _______________________________________________
> caiman-discuss mailing list
> caiman-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss

-- 
Les Wood
Sun Microsystems
Software Integration Engineering
Office: 503-820-3834 x40075

*******************************************************************************

PRIVACY & CONFIDENTIALITY NOTICE: The information contained in this e-mail and 
any attachments is intended for the named recipient(s) only, unless otherwise 
waived in writing by me. It may contain privileged, proprietary and/or 
confidential information. If you are not the intended recipient, you must not 
copy, forward or distribute. If you have received this e-mail in error, please 
notify me immediately.

*******************************************************************************


Reply via email to