Hi Evan,
Evan Layton wrote:
> Hi Folks,
>
> We are in need of your input on requirements for the version
> compatibility work.
>
> Some draft examples of requirements that we're looking at are:
> * Define the versions of the installations we will support
> o 1 to 1 match for live CD and pkg based installs.
Just to clarify, by LiveCD installs, you mean using cpio transfer
mechanism ?
As far as pkg based installs are concerned, how 1:1 match requirement maps
to the existing IPS versioning scheme ? Will it be always assured that this
information can be derived from AI manifest ?
How 1:1 match requirement will affect scalability with respect to number
of AI images
administrator will have to maintain ?
> o possible mismatch for image based installs such as
> replicated images.
> * Define the behavior when a mismatch is detected
> o which do we handle and which do we flag as an error.
When IPS transfer mechanism is used for the installation, I am thinking if
there might be possibility to get rid of this problem or move it to the more
explored area by using similar IPS mechanism we have on running system when
we do the updates.
For now IPS fresh install is one step process - just 'pkg install' packages
listed in AI manifest of the version specified in AI manifest.
The another approach might be to do the fresh install as two step process:
[1] install the system with the same version as booted AI image and do
the all
post install config stuff.
[2] If version specified in AI manifest is newer, use 'pkg image-update'
mechanism to update the installed bits to the required version.
Not sure, if this approach is viable, but it seems that the incompatibility
problem would move to the area being used and explored.
There are issues we would need to check with IPS team, but before starting
that more detailed discussion, I am wondering, if it is even worth to
consider that approach.
Thank you,
Jan
