Sarah Jelinek wrote:
> Hi Folks,
>
> We have completed the first draft of the Caiman install project
> architecture document and have posted it for review.
>
> You can get it:
> http://www.opensolaris.org/os/community/install/caiman_arch.pdf
>
> Or it is linked off the installation and packaging community page:
> http://www.opensolaris.org/os/community/install/
>
> Please review and send comments to this alias,
> install-discuss at opensolaris.org. We are requesting that comments for
> the first round of reviews be in by December 4, 2006.
>
> Thanks in advance for your participation and input.
>
> Regards,
> sarah
> _______________________________________________
> install-discuss mailing list
> install-discuss at opensolaris.org
> http://opensolaris.org/mailman/listinfo/install-discuss
Sarah,
This is an excellent document. These are my comments.
1. "in-place upgrade" is not supported
There are few comments regarding this topic. Right now "in-place
upgrade" is straight forward. It is almost similar to "initial install".
Are you planning to keep the simplicity when the user choose to do
upgrade with caiman? If you do, this will help the users who rely on
"in-place upgrade" simplicity to get new bits.
2. Page 9: "The process of selecting software is driven by the usage of
the system rather than software bundles. This approach greatly
simplifies the choices presented to the user without assuming a Solaris
centric bias. Thus software selection is based on system usage, i.e.,
desktop, server or server and desktop."
Will there be customization of software? For example if I want
desktop but I don't want staroffice, Can I customize using gui?
3. Why timezone and locale are considered to be essential? Can install
proceed with out them? Is locale is required to determine the locale
packages to be installed on the system?
4. Currently we have a install piece called 'solstart' which is similar
to jumpstart with begin and finish scripts. It is typically used to
install essential patches that comes with the image under
Solaris_XX/Patches directory. Also it is used by SunFire 15000. Solstart
is used interactive installs and jumpstart. Is there any plan in caiman
to allow third party customization scripts to be run before and after
solaris install?
5. Section 2.3 -> item 3: What do you mean by "Must be self re-startable
in the event of failure"? What if it cannot start after failure?
6. Section 4.2-> item 6: "Will provide logging and debugging facility".
What kind of debugging facility you are talking about? It is going to
call a user provided script/program. Are you referring to all the
debugging tools available to the user at that point?
7. Can we attach multiple customization services to be run for a single
install? Also it looks like this is planned only for jumpstart? What
about interactive installs? Also we have a separate script mechanism for
flash. Do you have any plans of making that a customization service?
8. Section 9.1 -> item 5: "Will support full image installations,
advanced deployment installations, and live upgrades". Are you planning
to use jumpstart to do live upgrade? Currently live upgrade uses
pfinstall (which is essentially jumpstart).
9. Section 9.2: We want to simplify installation. I think installation
should be fast and simply install the bits on the system. Any additional
configuration should be done after reboot. Looking at the requirements,
we are adding additional features to installation and will eventually
slow down things and become buggy. I am referring to section 9.2 items
4, 5 and 10.
10. Section 10: Logging service. What will happen to the current logging
mechanisms in jumpstart? Will it be rewritten to use the logging service?
11. Section 11.1: What is CSN format?
12. Section 12.2 -> item 7: "Will support rollback to pre-patch system".
What is the reason behind supporting the rollback? How is it useful for
Jumpstart? It is supposed to be "hands-off". Also do you have any plan
of invoking services by patchpro as part of install/upgrade to do the
patching?
13. Section 13.2: It is nice to have the following requirement: "May be
able to use the same tools that is used for post-install service for
normal re-configurations".
14. Section 13.4: Looking at the "Services Dependent on", the
Orchestrator service will be running after reboot. Will the Orchestrator
service run on the system all the time?
15. Section 14: "Software Repository Service". How does this service
work for media installation with out network? Can the installer provide
another media?
16. Section 15: "Software Selection Service". Can we remove this
feature completely from interactive install? If you look at the current
distribution there are 180 "clusters" and lot of them are not
interesting. Unless we create a supercluster (group of clusters) or show
only clusters that is meaningful to customize, it is going to be mess.
17. Section 16.2 -> Item 3: We may have to detect Veritas File systems also.
Thanks,
Sundar
