Hi Rob,
Rob Lagunas wrote:
> Hi Jan,
>
> I was looking at OpenSolaris bug 5451 (No way to permanently target
> specific disk in AI engine manifest) because it represents a major
> barrier to deploying AI as a service to install OpenSolaris in the labs.
>
> Does the AI team have any plans to address this anytime soon?
This issue will not be solved for 2009.06 release
as appropriate research needs to happen, but I agree
with you it is problem which should be considered
to be addressed.
>
> We have several hosts (hundreds) with SAN attached storage and I find
> the root disk is rarely the first disk encountered. I also, find the
> root disk controller number varies from system to system. Because of
> the varying logical disk names on systems, lab staff must first
> confirm the target root disk name and update the manifest (wastes
> time). I don't want to create separate manifests for each client as
> the solution doesn't scale well.
So far two solutions were suggested and captured by following bugs:
7057 desire for being able to specify 'rootdisk' as installation target in AI
manifest
7058 desire for being able to pick up disk as installation target by specifying
volume
name in AI manifest
I am not sure if they might help you to address your case, so I have question -
in your scenario (a lot of machines with SAN attached storage used as target
disks),
might you have any idea how the target disk could be described, so that number
of AI
manifests needed might be minimized (ideally only one will have to be used) ?
Thank you,
Jan
