Matt,
Thanks for doing some more testing. So, short story is, manual provisioning
needs some more work to work with existing providers. The manually
provisioned node thinks it's running an ec2-provider instance. Thus, it
tries to do ec2isms, like querying 169.254.169.254 for instance metadata
Sounds like a cool feature. I tried bootstrapping in aws then adding a
machine supplied by digital ocean. I got an invalid domain error. Any idea
what I was doing wrong?
juju add-machine -v ssh:root@162.243.10.110
2013-09-15 20:06:07 INFO juju.provider.ec2 ec2.go:187 opening environment
amazon
Hi Matt,
It looks like a bug with address resolution. IF you have a DNS entry for
your digital ocean box, please try using that in the ssh:... target.
I'll try and reproduce the issue later - I've logged a bug for now.
Cheers,
Andrew
On Mon, Sep 16, 2013 at 4:59 AM, Matthew Williams
On Tue, Sep 10, 2013 at 2:08 AM, Andrew Wilkins
andrew.wilk...@canonical.com wrote:
$ sudo $(which juju) bootstrap
$ juju status
environment: local
machines:
0:
agent-state: started
agent-version: 1.15.0.1
dns-name: 10.0.3.1
instance-id: localhost
series: raring
As of 1.13.3 you can now do this:
juju add-machine ssh:[user@]host
* Does this user have to be root ? If the user has to be root, do we
have to get into the business of telling people how to adjust their
/etc/ssh/sshd to allow root login ?
* What happens if I do, juju add-machine
