Hi Dave, I have the following comments/questions about the updated version. Some of the questions might apply to the previous version as well, but I just thought of them today. :-)
Provisioning section ---------------------------------------- 1) "-s <package-spec>" is used here in the create-service command... Later, in the "update" section and the man page, "-s <srcimage>" is used instead, it would be good to be consistent all over the document. 2) "... If this capability is not desired the user can merely delete the any-i386 service using "installadm delete-service". As there are implementation limitations on the size of the menu that pxegrub can load, a SMF property (global_menu) is created on each service, with its value set to "true". If a service should be excluded from the any-i386 menu, the administrator can set this property to "false" using the "installadm set" command, which was included in the original AI design but has not yet been implemented..." Which "installadm set" command? I don't see any in the man page. 3) create-service command allows one to specify an alternate package name. To me, that means, people can just use it to install any package. Is there any changes needed in installadm to validate that all the files downloaded actually comprised of a "valid" AI image? Or do we assume that people know what they are doing? Update section -------------------------- 1) Users are allowed to specify a FMRI or URI for -s in this case. Since this operation is meant for "update", and people can specify anything in the FMRI or URI, even a different package name than what is currently there. The image might be greatly altered if people do that. Does the update-service command prevent that from happening? installadm.1m man page: ------------------------------------------- 1) for the description of -s in create-service, I think the "If..." sentence is not complete. 2) for update-service, there's no description for valid values of -s. I think it is important to point out that the acceptable values for -s in this case is different than the acceptable values for -s in create-service. 3) the -s option for create-service allows one to use an ISO file. Should there be some sort of warning printed out to tell people that the resulting image can not be updated? If so, it would be good to display that in example 1 of the man page. Other question --------------------------------- Despite the earlier discussion, I am still not very clear about how default-<arch> and any-<arch> work in terms of how it determines which service a client will use in the new AI image management scenario. I came to my understanding below from the "provisioning" section's description of the DHCP configuration changes, and the description of "installadm create-service" in the man page. Let me summary my understanding of how things will work in the following example. Please confirm or correct my understanding. 1) On a x86 system without any AI service, I do create-service. This will create the first AI service. It will have a unique name and it will be automatically be aliased to default-x86. 2) Now, I boot a client, the grub menu will have 2 entries. The "default-x86" entry, which is the default, and the "any-x86" entry. If I select the "any-x86" entry now, it will list the 1 single AI service that's currently available. 3) Add 2 other AI service on the server, named svc2 and svc3, not aliasing them to default-x86 at this time. 4) I boot a client now, the first AI service I setup will be booted, because that's the default. If I select "any-x86", 3 entries will be displayed, and I will be able to select which entry to boot. 5) Now, I alias svc3 to be default-x86. 6) If I boot a client now, svc3 will be booted. 7) I delete svc3. 8) If I boot a client now, it will error out, because the default-x86 entry is selected, and it doesn't map to anything??? Thanks, --Karen On 02/19/10 15:43, Dave Miner wrote: > Thanks for the comments on the revised image management spec. I've > published a revision that captures the discussion; of particular note > are links to an updated man page and diffs against the existing page. > > http://hub.opensolaris.org/bin/view/Project+caiman/AI+Image+Management > > Dave > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
