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.)
** Changed in: juju-core
Importance: Undecided => High
** Changed in: juju-core
Status: New => Triaged
** Tags added: backup-restore tech-debt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1317896
Title:
juju-restore requires mongodb-clients
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1317896/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
