Hi, This issue came up when I wrote the manifest for SunDS at my workplace.
SMF instances must either be "named" at import via the <instance name=...> tag or it can be a default instance. Can SMF be extended to support delivery of "unnamed" service instances? A typical example will be for SunDS where the user will create an LDAP instance. The instance name is not known at the point of installation. If SunDS wants to do SMF, the manifest has to be generated and imported at the creation of the LDAP instance. Alternatively, we can support something like: <instance name = "*" ...> and supply a start/stop method that takes in instance_name as an arguement. We can then do: svcadm enable ldap-server:newinstance without having to import a new service instance. This should benefit any services that supports creation of instances. -- Just me, Wire ...
