Caiman Version Compatibility

Problem Statement:

• Currently installing a client where the booted image doesn't match the OS bits being installed the installation behavior will be unexpected and have undefined results.
  - Further, the user is given no information on why the installation may have failed because the failure is not handled gracefully or logged. - Additionally both the user and the installer application have no insight into where or why we failed. - It is also possible that the installation may succeed however the resultant installation status is undefined and we can not guarantee that it is correct.

The following are the places where we have the potential for incompatibilities:

• Architecture, SPARC or X86/64 (for image or archive based install).
• OS version the client is booted to
• installer version
• The type of install image we are using. For example Package based, archive(cpio, etc) based or image (replicated or recovery image) based.
• OS version being installed
• manifest and schema versioning to make sure they match. (This is part of Jack's XML parsing work)

Meeting Notes:
6/10 meeting
5/27/09 & 5/28/09 meetings
5/20/09 Meeting
5/14/09 Meeting

More Thoughts and Ideas

Information for draft proposal

Functional spec for Installer Versioning