Hi Sue,
Thanks for the fast feedback!
On Wed, 2009-05-20 at 11:31 -0700, Susan Sohn wrote:
> The -d option was removed from create-service as it was non-functional. There
> currently is no concept of default service, but this is being looked at as
> part
> of the services redesign efforts. Currently, the service is associated with
> the
> boot image so the client isn't discovering install services.
Ok - in the services resdesign efforts, do you know whether the
"install_media" and "install_service" guest boot options are likely to
go away any time soon?
It sounds like I should make the requirement for 'install_service',
passed to the installing guest's kernel boot options by virt-install
optional. I would also issue a warning if that option was missing
however.
- does that make sense?
cheers
tim
> Sue
>
>
> On 05/20/09 05:12, Tim Foster wrote:
> > Hi there,
> >
> > A question came up during another code review of the AI support in
> > virt-install[1]
> >
> > The installadm man page talks of a -d option to "create-client" that
> > allows one to specify the default install service on a network, but I
> > see that this option isn't accepted anymore by installadm.
> >
> > Is there still the concept of a default install service, or is it the
> > case now that clients always discover all services and match on the
> > criteria specified in the manifest (and in the case of identical
> > manifests, how does the client determine which service to use?)
> >
> > - I'm trying to determine whether always specifying the boot argument
> > "-B install_service=<foo>" should be required or not when bringing up
> > the guest.
> >
> > cheers,
> > tim
> >
> >
> > [1] this time, for the ongoing 3.3 port of xVM, we decided not to
> > putback the changes I wrote for the 3.1-based code.
> >
> > _______________________________________________
> > caiman-discuss mailing list
> > caiman-discuss at opensolaris.org
> > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>
