Danek, > On Tue, Feb 03, 2009 at 04:15:16PM -0500, Jim Dunham wrote: > >>> Well, we only look at ELF dependencies right now, and as far as I >>> can >>> tell, we're getting all of those right. What we're not getting, >>> because >>> we're not looking, is the service dependencies. svc:/system/nws-ii >>> depends on svc:/system/nws_sv, for instance. >> >> I am confuse by this statement, as I would never expect IPS >> packaging to >> have awareness of SMF service dependencies. > > The packaging itself doesn't, but the publication step, which digs > through > the contents of each package to pull out programmatic dependencies, > could. > Though like I said, we only do that for ELF dependencies currently. > If we > pulled out dependencies by examining service manifests, we would have > gotten all the needed dependencies for this cluster of packages.
Is there an IPS packing developers guide, must like the SRV4 packaging guide? >> Case in point, the AVS packages provided SMF manifests which contain >> specific service dependencies, but these dependencies, and others are >> modified in real-time, based on the output of certain run-time >> utilities, >> like 'clinfo' - display cluster information. AVS is Solaris Cluster >> aware, >> and vice-versa, and if clustering is enabled, it makes sense for >> SMF to >> control service dependencies, in lieu of the old run-level scripts. > > I'm not sure I understand this. You're delivering services which have > dependencies on each other, but are suggesting that we don't pay > attention > to them? Does nws-ii depend on nws_sv or doesn't it? From reading > the > manifest, it does not appear to be an optional dependency. > > Butf SUNWii and SUNWrdc don't depend on SUNWspsv through their > services, > then how do they depend on SUNWspsv at all? The service > dependencies were > the ones you called out when first filing the bug. AVS dependencies are presently fixed, and non-changing. At times in the past, they were modified based on the results of 'clinfo', as a means for AVS and Solaris Cluster's dependencies and milestones to synchronize better at system startup and shutdown time. >> It is my understanding that service dependencies are not being >> checked in >> Solaris / Nevada, > > Of course they are -- by SMF. But if you mean that when building a > package, no automated dependency analysis is being done, you're > probably > right for most of the Solaris consolidations. > >> so where is the added value of doing this within OpenSolaris? > > If it isn't being done for Solaris, and it is being done for > OpenSolaris, > isn't that "added"? Or did you mean to ask "where is the value"? Where is the value for IPS to have awareness of something that SMF already manages? > > > Danek Jim _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
