There's been some discussion in the past of this idea.. that bootstrap should poll and wait for the instance to come up before it returns. I agree with this, but the concern of others was that users would think juju was slow when in actuality EC2, ubuntu mirrors, or the slowness of the install on bare metal would all contribute to the process taking a long time.
One way to combat this misconception would be to instrument more stages of the process. So we could poll the provider to see if the machine state is known yet, and make it clear in the messages.. "Waiting for machine to be provisioned by [maas|ec2|etc]" makes it clear that juju is at a point where it can't do anything else.
There's been some discussion in the past of this idea.. that bootstrap should poll and wait for the instance to come up before it returns. I agree with this, but the concern of others was that users would think juju was slow when in actuality EC2, ubuntu mirrors, or the slowness of the install on bare metal would all contribute to the process taking a long time.
One way to combat this misconception would be to instrument more stages of the process. So we could poll the provider to see if the machine state is known yet, and make it clear in the messages.. "Waiting for machine to be provisioned by [maas|ec2|etc]" makes it clear that juju is at a point where it can't do anything else.