Hi David,
David Garcia - ONPIT wrote:
> Hi Jan,
>
> Please see comments inline:
>
> jan damborsky wrote:
>>
>> yes, '-s' is mandatory - it is mentioned later in man page,
>> but it seems to be marked incorrectly in 'usage' section.
>>
>> There is a bug filed for tracking these issues:
>>
>> 5553 required parameters are marked as optional in installadm(1M) man
>> page
>>
>> It seems that the one you noticed is not mentioned in bug report -
>> could you please capture it there ?
>>
> I added a comment in #5553
Thanks !
>
>>
>> Actually, for x86, install service is not bound to the particular
>> image -
>> those are independent.
>>
>> * install image determines the environment used for the installation,
>> * install service provides client with the locations where to ask
>> for installation configuration.
>>
>> For example, you could have bunch of clients you would like
>> to install with 106 and you need to use 106 AI image as
>> installation environment for all of them.
>>
>> But you could have per client requirements where
>> to search for install configuration files.
> I wasn't aware of that. I took a quick look at the man pages and
> couldn't find this documented though. I'll check again later and file
> a bug to capture this.
Looking at the man page, it seems it is a little bit confusing in this
point:
[1] srcimage is marked optional in SYNOPSIS:
...
installadm create-service [-d] [-u][-f bootfile]
[-D DHCPserver] [-n svcname]
[-i dhcp_ip_start] [-c count_of_ipaddr]
[-s srcimage] targetdir
...
[2] SUBCOMMANDS AND OPTIONS section says
...
Publishes the OSInstall service. Only a source image
and a target directory are required for basic setup.
...
-s srcimage
Required: Specifies location of source image to use
for setting up OSInstall service.
...
Note the following specifications:
- As default, both image and service are created.
- If existing service name (svcname) is provided, only
image is created.
- If source image (srcimage) is not provided, and
target directory contains a valid net image, then new
service is created with existing net image.
- One net image can have multiple services.
- Multiple net images can use the same service.
...
Based on this it seems, that 'srcimage' is optional,
but it is not quite clear. Please feel free to file bug for
clarifying this.
>
>
>>
>>> Then shouldn't it be enough to specify the service name when we
>>> create a new client?
>>> Given that a service can't have more than 1 targetdir related to it,
>>> why do we need the option '-t imagepath'?
>>
>> Since install service is not bounded to AI image, you can specify
>> that you would like to use the same install service for clients
>> you would like to install using different AI images. I agree with
>> you that this possibility is not quite obvious, since you probably
>> can't create just AI image without creating new install service.
>>
>> I can see this might be useful for testing purposes (like making
>> sure that different images lead to the same installed bits for
>> regression tests), not sure if there might be other use cases.
>>
> Maybe it would be interesting to implement this as an optional
> argument so by default it'll take the installation configuration from
> the target-dir set in create-service?
Since target dir is not tied to particular install service,
both need to be specified when configuring particular client.
According to installadm(1M) man page, it seems it is possible
to assign more images to one service (I haven't tried):
...
- If source image (srcimage) is not provided, and
target directory contains a valid net image, then new
service is created with existing net image.
- One net image can have multiple services.
- Multiple net images can use the same service.
...
Thanks,
Jan
