juju-restore requires mongodb-clients

[Horacio Durán]

juju-restore plugin performs a couple of operations on the db that require mongo client which is part of mongodb-clients, currently we are triggering an install of that package from inside the restore plugin. The proper solution would be to have mongodb-clients as a dependency of juju-core or have mongo binary included in /usr/lib/juju/bin

[John A Meinel (jameinel)]

I actually don't think using "mongo" is the correct fix here. We already have all the code we need inside of juju-core, we shouldn't depend on a separate client library in order to write stuff to the database.

We *definitely* don't want mongodb-clients as a dependency for juju-core (juju-core is the client package, not what we install on the remote machine).

Instead, we should have a "jujud restore" as a command that we can invoke from remote (like we do 'jujud bootstrap-state" today). Long term it can take over everything that we need to do during restore, potentially even connecting to all the other agents and updating their configuration to point to itself. (We now have an SSH Identity that should allow an API server to SSH to all machines and run commands there.)

[Anastasia (anastasia-macmood)]

Without mongodb-client, we cannot log into database, we cannot get db dumps, etc. It is not just restore that needs it.

[Curtis Hovey (sinzui)]

This is essentially fixed by juju-mongodb3.2 and juju-mongo-tools3.2. The client and the tools are installed on the controller.