On 04/ 1/10 01:40 PM, Erik Lafever wrote:
----- [email protected] wrote:
> ----- [email protected] wrote:
>
>> On 03/31/10 07:21 PM, Alok Aggarwal wrote:
>>>
>>> On Wed, 31 Mar 2010, Erik Lafever wrote:
>>>
>>>> Thanks Alok,
>>>>
>>>> That is the file that I was looking for. Should DC
> "depend" on
>> that
>>>> package? Is there any reason the xml is not included in
> the
>>>> distribution-
>>>> constructor package?
>>>
>>> The manifest is really an AI manifest so I'm not sure
>>> if it should be included in the DC package.
>>>
>>> The fact that VMC depends on it may mean that we need to
> deliver
>>> the manifest as part of some other common package (which
>>> one, I'm note sure). Feel free to file a defect.
>>>
>>> Alok
>>> _______________________________________________
>>> caiman-discuss mailing list
>>> [email protected]
>>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>>
>>
>> The ability for VMC to support a user specified AI client
> manifest
>> was
>> tracked by bug 13272.
>>
>> VMC does not depend on the AI manifest, it's optional. It is
> only
>> needed
>> if the user does not want to use the default manifest built
> into
>> the AI
>> image.
>>
>> VMC currently requires the user to have an AI image. VMC will
> not
>> automatically generate the image. The default AI client
> manifest
>> can
>> also be accessed from the AI image by lofi mounting the
> image.
>>
>> Since the user is required to supply the AI image and/or an
>> optional
>> manifest I don't see any reason to have DC depend on the
>> install/auto-install/auto-install-common package.
>>
>> Joe
>> _______________________________________________
>> caiman-discuss mailing list
>> [email protected]
>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>
>
> The problem I had was that I built an AI image that used
> http://ipkg.sfbay.sun.com
> for the publisher. When I use that image to build a Virtual
> Machine, the default.xml
> manifest gets pulled in and points to
> http://pkg.opensolaris.org/release. Then we
> wait for the build to finish and it wont boot. Did a miss a step
> somewhere?
>
> Thanks,
> Erik
The publisher was http://ipkg.sfbay/dev not http://ipkg.sfbay.sun.com
-Erik
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
Hey Eric,
There are 2 different manifests involved.
One, an "AI Distro Constructor manifest", is used to instruct DC how to
build an AI Image.
The other, an "AI Client manifest", is used to instruct AI how to
install a client.
Both of these manifests have an entry for where IPS packages should be
pulled from.
When you used the DC to build your AI image you modified an "AI DC
manifest", instructing DC to pull packages from http://ipkg.sfbay/dev.
One of the things that gets built into an AI image is a default "AI
Client Manifest". When AI is used to do an install the user can specify
a different "AI Client Manifest".
VMC has an option to allow for a user specified "AI Client Manifest".
Hope this helps.
Joe
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
