This month I am deploying MongoDB infrastructure for
package "repositories" @rpm5.org.
The intent with infrastructure deployment is to establish conventions
for MongoDB schema (particular identifiers) and to establish a
"real world" store so that client-side tools can be attempted,
and reliability/performance issues can be seen.
Two MongoDB collections that I will be prototyping specific to package
management are
1) an "everything" store with all *.rpm package metadata
(much like what is currently at sophie.zarb.org)
2) a repo-md store with the usual primary/filelists/other metadata.
The prototyping work will initially be based on Mandriva Cooker and
perhaps Unity Linux, which are of course irrelevant to a RHEL based
add-on repository like RPMForge.
However, I most definitely will be adding RPMForge metadata into a MongoDB
store as I proceed.
If there is interest at RPMForge in using MongoDB as an alternative to
traditional mirroring of "repository" metadata, I will adjust my priorities
accordingly, and attempt to host an RPMForge MongoDB containing package metdata
sooner rather than when a round 'tuit is found.
Any interest?
73 de Jeff
_______________________________________________
users mailing list
[email protected]
http://lists.rpmforge.net/mailman/listinfo/users
