Thanks for the ideas David & Danek,
On 12/14/12 07:18 AM, Danek Duvall wrote:
david.co...@oracle.com wrote:
How about simply application/pkg/depot? Or if we think we might
envision other "depot" services (for example, for cleanup) maybe
application/pkg/depot/server?
I'm fine with application/pkg/depot, though
svc:/application/pkg/depot/server might be confusing when we also have
svc:/application/pkg/server
[ but it also clashes with nfs/server, ldap/server, install/server,
dhcp/server, so perhaps that's not really a worry ]
I'm inclined in this way as well -- you're not really introducing a new
thing, just existing functionality built on top of a different platform.
It's not clear to me that the name of the thing should change at all
because of this.
The difference is the way configuration is performed. With the
apache-based depot running, you can svcadm enable/disable the different
pkg/server instances that contribute to its configuration, and have
those appear/disappear from the Apache server.
The httpd.worker processes are all managed by a single SMF instance, so
here svcs -p says:
STATE STIME FMRI
online 8:53:23 svc:/application/pkg/http-depot:default
8:53:21 6292 httpd.worker
8:53:21 6294 httpd.worker
8:53:21 6295 httpd.worker
8:53:21 6296 httpd.worker
8:53:21 6297 httpd.worker
8:53:22 6319 httpd.worker
Would it be possible, for instance, to simply use pkg/server as we do now,
and simply have a configuration switch that toggles between the use of
cherrypy and apache? If that's not unreasonable, then perhaps we should
design towards it.
I really only want one Apache instance running on the system (at least
for this service)
If I were to allow the first svc:/application/pkg/server instance manage
the Apache processes, and subsequent instances of pkg/server contribute
to its configuration, what happens when I disable that first pkg/server
instance? I'd need to kill those Apache processes, then choose one of
the remaining pkg/server instances as the 'leader' and start Apache
there, and I think that'd be difficult to do gracefully (but am of
course open to suggestions)
The separate SMF services make for a nice administration interface in my
view: configuration items that are specific to a given repository, like
pkg/inst_root and (eventually) SSL keys/certs, get set on the pkg/server
instances, things that are common to all, like which port the server
runs on gets set on the http-depot service.
cheers,
tim
_______________________________________________
pkg-discuss mailing list
pkg-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
