Hi Alta,
As I'm less technically aware of JS, my comments/feedback focus on what
"perception" I get about AI as a result of the top-level document. I
will take a look at the use cases page next (are there any other
specific pages that you'd like me to look at, bearing in mind my lack of
knowledge of JS and that AI is the area of install I'm least familiar
with?).
General: Most of the descriptions of AI functionality are 2-3 times
longer than the descriptions of the AI equivalent. This makes it sound
like AI is far more complicated than it is (or will be, in cases where
enhancements are coming), even though the descriptions are generally
valuable. In some cases, deferring some of the details of AI to the
sub-pages would make sense; in others, a slightly longer explanation of
the JS equivalent would help (in particular, highlighting why the JS
equivalent is more difficult, where applicable).
Installation configurations: The reference to XML in "Automated
Installer uses XML AI manifest files" seems to be a bit wordy at this
stage. The internal format of the files aren't under discussion in this
section, so is there a reason to call it out? Additionally, the fact
that the AI overview is 3 times longer than the JS overview makes AI
seem far more complicated. I'd perhaps recommend simply providing an
overview of the 3 files (AI manifest, SC manifest, and criteria
manifest) and provide one-liners describing their purpose - leave the
details for elsewhere.
Test Install: Again, the fact that the description of the JS pfinstall
fits on one line, and the AI equivalent takes 7 lines to describe, gives
me the wrong impression. In this case, I'd suggest expanding on how
difficult it seems to be to actually use pfinstall[1]. (Also this
section title reads to me like "Text Install" but that's probably just a
symptom of having spent so much time on that project...)
Upgrade Systems: Again, expand the JS section. "To upgrade systems using
JumpStart, you have create a separate(?) profile, and run JumpStart all
over again."
Install Third Party Software: Perhaps this section could be "installing
additional software". Then highlight how installing additional IPS based
packages is trivial. The explanation on how to install SVR4 packages is
fine, though it could be shortened to "to install SVR4 packages as part
of an AI installation, create a first reboot SMF service that installs
the packages, and install that SMF service as part of the AI install by
supplying it in an IPS package" (or something like that).
- Keith
[1] The steps given in this link make it seem difficult:
http://docs.sun.com/app/docs/doc/817-5506/6mkv6ki7h?a=view
On 05/ 6/10 03:32 PM, 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
