register a user on multiple machines

[Anastasia]

From Cory Johns description in bug # 1657187:

 When automating Juju, you may want to use the same user on multiple machines, such as when a Juju-using app is scaled. Or, for a CI system, you likely want Juju run from within a pristine (containerized) environment, necessitating re-registering the controller for each run. And then of course there's usual dev / debug workflow where you may add and remove controllers multiple times while testing something.

All of these get very tedious if you have to create a new unique user every time.

[John A Meinel (jameinel)]

Is this re-using the same token, generating multiple tokens for your user, or?

Would being able to "juju register IPADDRESS" be sufficient (you can currently juju register DNSNAME"), though you'd need to give a username+password (juju login?) on the second machine.

[Anastasia (anastasia-macmood)]

@Cory Jones,

Could you please clarify what would suit your requirements? An answer to John's questions would be great \o/

[Launchpad Janitor (janitor)]

[Expired for juju because there has been no activity for 60 days.]

[Cory Johns (johnsca)]

I missed this bug being created. John: I don't think I realized you could register an arbitrary controller via its DNS name. That is probably fine for CI applications, since re-using the username and password in that case is acceptable. Being able to register by IP would be a good feature as well, since the CI system might not always have a resolvable name, but I don't think it's as critical.

Perhaps just some better documentation around this feature would be enough.