Github user aledsage commented on the issue:
https://github.com/apache/brooklyn-server/pull/487
@drigodwin interesting. I'm not sure who we should optimise for though,
with the defaults.
The problem is if someone has misconfigured their location. For example,
we'll wait several minutes for sshable before reporting provisioning as
failed. It's annoying that it takes 20 minutes (or whatever) to tell you that
provisioning has failed. If we set `machineCreateAttempts=3` then it will take
60 minutes before it tells you that it's failed.
It's a particular concern because of problems like
https://issues.apache.org/jira/browse/JCLOUDS-1165, which can hit someone using
the defaults in a common cloud (e.g. aws-ec2).
Maybe we compromise with `machineCreateAttempts=2`?
Much longer term, we could try to make the activities view clearer, to show
that it's moved onto attempt number 2 (cc @m4rkmckenna @tbouron). That probably
would require some significant restructuring of the low-level tasks executed
for provisioning though.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
