On Thu, 2011-05-12 at 22:29 -0700, [email protected] wrote:
> > http://cr.opensolaris.org/~timf/sysrepo-refactor-webrev/
>
> Looks good, Tim. My only comment is that it seems the zoneproxy really
> is a pkg(5) implementation detail rather than something associated with
> zones. As such, it seems both the package that delivers the service and
> the service itself don't belong under "system". My suggestion would be
>
> pkg:/package/pkg/zoneproxy
>
> svc:/application/pkg/zoneproxy
No worries - if we're renaming the service as well, I'd just like to get
consensus. In the gate, we have:
pkg:/package/pkg/system-repository
delivering svc:/application/pkg/system-repository:default
svc:/system/zones-proxyd:default
svc:/system/zones-proxy-client:default
At risk of bikeshedding, I slightly prefer "zones-proxy" over
"zoneproxy", adding a hyphen and making plural since we already have,
eg. "svc:/system/zones-monitoring" and "svc:/system/zones".
Do the service names need to match the binaries involved (which are
zoneproxy-adm, zoneproxy-client and zoneproxyd) in which case I could
also rename those, but wanted to check that was ok before doing so.
Anyway could I propose we have:
pkg:/package/pkg/system-repository
delivering svc:/application/pkg/system-repository:default
pkg:/package/pkg/zones-proxy
delivering svc:/application/pkg/zones-proxyd:default
svc:/application/pkg/zones-proxy-client:default
cheers,
tim
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
