Hi Alta,
I have looked at
"Migrating from Solaris Custom JumpStart to OpenSolaris Automated Installer"
main page. Please see my comments below.
Thank you,
Jan
***************************************
"Reset the Root Password on the Client"
"To reset the root password after a JumpStart installation, use the
root_password keyword in a sysidcfg(4) file."
I might recommend to use different word instead of 'reset',
perhaps 'configure', since I think 'reset' evokes impression
of setting to default/initial value instead of customized one.
***************************************
"For Automated Installer, reset the root password and define new users ..."
->
"For Automated Installer, configure the root password and define new
user ..."
Current System Configuration manifest supports only one user account.
***************************************
"Rules Keywords and Criteria Manifest Directives"
It seems that the table does not capture AI criteria correctly,
in particular, AI currently supports:
arch - reflects output of `uname -m`, e.g. sun4u
cpu - reflects output of `uname -p`, e.g. sparc
platform - reflects output of `uname -i`, e.g. i86pc
Based on this, following AI criteria are equivalent to jumpstart rules
keywords:
jumpstart AI criteria
.........................
arch cpu
karch arch
model platform
***************************************
"Profile Keywords and AI Manifest Directives"
In entry 'boot_device c0t0d0s0 update' following
piece of AI manifest is listed as equivalent:
<ai_target_device>
<target_device_name>c0t0d0s0</target_device_name>
</ai_target_device>
However, <target_device_name> accepts only disk name,
not slice name. We can perhaps use following AI manifest
as an replacement:
<ai_target_device>
<target_device_name>
c0t0d0
</target_device_name>
<target_device_install_slice_number>
0
</target_device_install_slice_number>
</ai_target_device>
* Also, 'update' portion of 'boot_device' jumpstart keyword is only
applicable for Sparc. For x86, 'preserve' has always to be used, since
there is no way to change the boot device for x86. Thus, the behavior
is the same for both jumpstart as well as AI.
* 'usedisk' jumpstart keyword can only contain ctd device name. Since
AI provides much more in that area, I would recommend to mention this.
For more information about what <ai_target_device> allows, please see
http://hub.opensolaris.org/bin/view/Project+caiman/Heads+upFlag+day+for+bugs+5451%2C7057%2C7058
***************************************
"Converting a Profile File to an AI Manifest"
In SC manifest, I might recommend to add configuration of 'hostname':
...
<propval name="hostname" type="astring" value="opensolaris"/>
...
***************************************
"Sample JumpStart Rules File"
In jumpstart rules file, I believe it should be:
arch i86pc
->
arch i386
or
arch i86pc
->
karch i86pc
Criteria part in the first AI manifest:
<ai_criteria name="ARCH">
<value>Sparc</value>
</ai_criteria>
->
<ai_criteria name="cpu">
<value>Sparc</value>
</ai_criteria>
***************************************
On 05/ 7/10 12:32 AM, Alta Elstad wrote:
Installers,
We would like to get your comments on some Automated Installer and
JumpStart how-to documentation. This documentation is intended to help you
migrate from JumpStart to Automated Installer. This set of documentation
references the AI guide, but it is more than that. We have tried to
document the entire process around automated install, including setting up
a DHCP server, setting up a local repository, creating an SMF service to do
post-install tasks, etc.
Do you use JumpStart now? Have you tried AI? Specific examples of how you
use AI, or how you use JumpStart so that we can provide specific migration
examples to AI, would be very much appreciated. We would love to get
example JumpStart begin and finish scripts so that we can work on specific
AI solutions for those. We have general descriptions now, but it would be
great to be able to say, "If you did this in your JumpStart begin|finish
script, do it this way in AI."
You can send comments to this alias, or you can comment directly on the
wiki pages.
Please send questions and comments by Friday, May 14.
The set starts here:
Migrating from Solaris Custom JumpStart to OpenSolaris Automated Installer
http://wikis.sun.com/display/OpenSolarisInfo/Solaris+JumpStart+to+OpenSolaris+Automated+Installation
and continues on these pages - click the arrow near the top of the above
page to get to these links or follow the child pages links at the bottom of
the page:
* Automated Installer Use Cases
o Create a Local OpenSolaris Package Repository
o Oracle Solaris DHCP for AI
o ISC DHCP for AI
o Set Up an AI Install Server
o Install OpenSolaris on a Single System
o Upgrade the OpenSolaris OS
o Automated Installer Manifests
+ Editing Automated Installer Manifest Files
o Create a First Boot Service To Run After Automated Installer
Install
o What Software Will Automated Installer Install?
o Which Target Will Automated Installer Install?
o Automated Installer Use Case for OpenSolaris 2010.05
* Installing Solaris 10 Using JumpStart on an OpenSolaris Server
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
