In working on bug 5209 (http://defect.opensolaris.org/bz/show_bug.cgi?id=5209), I have to solve the problem of applying one or more image specific SMF service profile.
One solution is to allow users to specify the image specific profile(s) to apply in the manifest, similar to what we do today. However, I don't think it is a good approach because image specific SMF service profiles are also configuration files. It goes against the DC's goal of having one single manifest to describe how an image is put together. I suggest replacing the applying of service profile(s) with a series of set-property calls for each of the service in the profile. DC's manifest will be extended to allow users to specify the name of the service, name of the properties to set, and the value for that. (I will send a separate proposal on the exact format if we decided to it). This also works well with incorporating other set-property calls that the mkrepo command calls today into the manifest. If we do this, the functionality of the current mkrepo script can be replaced by calling the manifest-import script from the image, follow by doing svccfg set-property for all the property values specified in the manifest. Your thoughts? --Karen
