On Mon 15 Dec 2008 at 02:36PM, Shawn Walker wrote:
> One of the things that has bothered me for a while now, is the fact that
> the depot and the repository share the same root directory.
>
> Example:
>
> /export/repo
...
>
> I think it would be better for a lot of reasons if this information
> separated.
>
> Any thoughts?
I'm not sure without knowing the reasons! How much and in what way do
you want to separate things? And how does this intersect with the
"scratch area"? For example, I would not like to see the current
contents of /export/repo spread out across the filesystems, into /etc,
/var, and so forth. Keep in mind that changing this will cause a very
large flag day in which the format of the depot directory for all our
depots will have to change simultaneously with the depot code. Or
you'll need to add a versioning scheme and give us a transition period.
One thing which is nice about our current setup for deployers is that
we can work with a depot in terms of a single directory (and hence, a
single zfs dataset provided to us by release engineering).
Of course, cfg_cache is something we're having to tweak locally, and
so that makes our deployment a lot more complex and more error prone.
Another high level goal is that I'd like to have as much of the repo
data be read-only as much of the time as possible for security and data
management reasons. This is made harder due to search engine DB changes
(so the search db needs rebuilding) and the cfg_cache needing to be
tweaked.
So, I guess I'm not upset about the current layout assuming we get
RFEs 2701 and 5211 taken care of. So I'm wondering if this is worth it?
I guess I need those reasons to really have a better sense, it isn't
obvious (yet) to me.
-dp
--
Daniel Price - Solaris Kernel Engineering - [email protected] - blogs.sun.com/dp
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
