On Dec 12, 2003, at 7:13 AM, Mike Mason wrote:
> Ryan Hunt wrote:
>
>> Well, I can't speak for others, but my needs for the "big WC needs to
>> be shared" scenario is for multiple maintainers to be able to work on
>> and maintain a tree of disk images which can be anywhere from
>> 300MB-2GB each. Because of the size it doesn't make sense to have
>> multiple WC's . I need access to it all of it all of the time
>> because all of the disk images in the WC are going to be live and
>> actively used by potentially as many as 500-1000 users
>> simultaneously.
>
>
> So, as a maintainer, can I simply check out the disk images I wish to
> work on on a particular day? Do I really need to be able to see all of
> those disk images at once? Can you organise the set of disk images
> into different directories, allowing me as a maintainer to just check
> out a subset of those images? Subversion keeps pristine copies of all
> the files in a WC, so for a 200G disk on a workstation you can have
> 100G of files checked out. That's 50 - 300 disk images.
>
If it was just the maintainer that would be fine, but there are users
as well.
> By "live and actively used" does that mean they're going to be in use
> by multiple processes on different machines at the same time?
yep.
> Will that actually work?
yep.
> Are these virtual disks for VMware or something?
some yep.
>
>> In my case NAS snapshots were postulated as an alternative, however,
>> this is not feasible due to the large amount of space this would
>> require, and its inherent inflexibility. The specific features of
>> SVN that are attractive in my situation are: cheap branching and
>> copying, the ability to revert to any revision of a disk image, the
>> ability to rapidly undo changes that were made using svn revert, and
>> the ability to track changes made via the log mechanism.
>
>
> I agree that snapshots are not quite what you want, but I also reckon
> a WC with 500 users is not what you want either. Having binary files
> checked into source control causes problems when multiple people
> change them, because they cannot be merged, so you need some form of
> locking. A single WC as the locking mechanism sounds like overkill
> though!
The disk images are read only for all but the maintainer group of not
more than 5-10 people. The rest just read the files.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 12 17:44:16 2003