On 01/09/13 16:38, Tim Foster wrote:
On 01/10/13 02:58 AM, Liane Praza wrote:
On 1/8/13 10:56 PM, Tim Foster wrote:
In order for a user to run this service, the minimum they have to do is:
# pkgrepo create /some/repodir
# chown -R pkg5srv /some/repodir
# svccfg -s mirror setprop config/repository = /some/repodir
# svccfg -s mirror refresh
Quick question on these setup steps... by default, could a standard location
be used for the repo, and have the directory delivered by the system rather
than setup by the user? That is, I'd think 99% of the use cases will be to
configure a repo to be used by the install server and future updates to mirror
the Oracle repos. It'd be good if the default usage would involve the fewest
numbers of steps to make that happen. The directory is one such step... there
may be others too that we could help with.
That's a good idea. Given the potential size of the repositories
created, we really need these repositories to separate from the current
boot environment.
We could do that by delivering
/var/.migrate/pkg/repositories/
which would then appear as /var/share/pkg/repositories. The only
slightly odd thing here, would be that /var/share/pkg doesn't bear any
relation to /var/pkg (so deviating from the pattern established by other
contents of /var/share/ so far)
We could have the method script attempt to create the repository if it
doesn't already exist, say using '/var/share/pkg/repositories/default'
as the default repository name; other suggestions are welcome -
'default' here matches the SMF instance name, and doesn't attempt to
describe the contents, which could change anyway if the user modifies
the 'config/origins' property.
In that case to run a mirror, all the user needs to do is:
# svcadm enable mirror
which would be neat.
The only downside I can think of against using off-BE storage, is if we
were to rev the repository format incompatibly, we could have different
BEs potentially being unable to read the repository contents, but this
seems unlikely.
I think that does seem unlikely, and the upside of keeping this out of
BE's is pretty large.
Did you consider making this a separate dataset, rather than just a
directory? Or do we want to discourage the idea of replicating further
using zfs send/recv?
The one odd part of /var/share is that sharing the repo over NFS is
reasonable and that would slightly argue for something under /export
instead, but in principle I can't come up with a reason to discourage
sharing of things under /var/share.
Dave
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
