New juju-mongodb package

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-12-02 13:01, James Page wrote:
> Morning folks
> 
> so far I have requests for:
> 
> mongo (default shell)
> 
> mongoexport (used in new juju backup plugin)
> 
> mongodump/mongorestore (useful)
> 
> I'm keen we don't bloat out the 'server' package to much - the 
> binaries are quite large due to the requirement to statically link
> v8.
> 
> Which of these is core to the function of juju, and which are
> useful for debugging?  Please also that the mongodb-clients package
> will still be available in universe so you will always be able to
> get any of the client tools that way as well (I'll probably keep
> those packages maintained to the latest point release for the
> released series).

Looking at the juju-backup script, it is intended to use both dump and
export. The export is so that we end up with JSON format for our
"settings" table so we can extract content from there as part of
restore (what credentials were you using, etc).

Are they both really big? If so, we can probably use: mongo --eval
"STUFF" instead of "mongoexport", but that would again presume that we
have a 'mongo' binary available.

I *believe* the data in the mongo dump is just BSON encoded, so it
would be possible to post-filter it with a bson aware tool to get it
into human-consumable form (rather than using mongoexport at backup time).

I guess the question is, how expensive is it to include it? For Juju
core folks the cost of including it is all externality so *we* aren't
particularly motivated to keep our toolset minimal. But if there is a
use case we want to support, we're willing to help.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlKcT7EACgkQJdeBCYSNAAPefwCgoQpVI4z6KJcyhJduazo0UJKZ
O4EAn0/72/0tujz1PGjVcBbFGQTxuiaW
=98tZ
-----END PGP SIGNATURE-----