bootstrap doesn't work if Dial takes more than 5 seconds

[Roger Peppe]

The waitSSH function used for the initial connection to the bootstrap
instance uses a 5 second timeout when dialling it.

This means that if the dial legitimately takes more than five
seconds (in my case it takes 15, even when the instance is up)
we will never succeed in connecting.

I don't believe we should time out the dial at all.

[John A Meinel (jameinel)]

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

On 2013-12-06 22:32, Roger Peppe wrote:
> Public bug reported:
>
> The waitSSH function used for the initial connection to the
> bootstrap instance uses a 5 second timeout when dialling it.
>
> This means that if the dial legitimately takes more than five
> seconds (in my case it takes 15, even when the instance is up) we
> will never succeed in connecting.
>
> I don't believe we should time out the dial at all.
>
> ** Affects: juju-core Importance: High Status: New
>

Given bug #1258240, I think we actually do want to timeout the dial
and then go lookup to see if the IP address to connect to has changed.

So the idea of being able to tweak it on a user level, and maybe
default to a 'long enough for most people' is reasonable.

Though note, setting it to 30s will actually default to slowing down
bootstrap notifications for HP users because we *expect* to see only
the private address before we end up seeing the public address. (And
any cloud where we have to set a floating IP.)

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

iEUEARECAAYFAlKlqIoACgkQJdeBCYSNAANBKgCXSzIWAQxDeMpqEJ+qz0Rb5UxP
IwCgxC2L6qnzG1Tz4K/fErACoenQR0E=
=ev9P
-----END PGP SIGNATURE-----