Feature #2072

Ignore non-reachable Hosts during Startup

Added by S. Wrede almost 6 years ago. Updated about 5 years ago.

Status:ClosedStart date:11/03/2014
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

VDemo can only be started if all hosts in a setup are reachable via ssh logins. It would be really good in larger setups if VDemo would just ignore host that are down, instead of failing to start at all.


Related issues

Related to vdemo - Feature #2071: Survive connection loss Resolved 11/03/2014

History

#1 Updated by S. Wrede almost 6 years ago

#2 Updated by S. Wrede almost 6 years ago

For us, this is really a big problem. What would be needed to add such a behavior to VDemo?

#3 Updated by R. Haschke almost 6 years ago

This feature already exists: the timeout for ssh connections is set to 15s in line 11:

set SSHOPTS "-oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no -oConnectTimeout=15"

So, please be patient ;-)

#4 Updated by S. Wrede almost 6 years ago

  • Status changed from New to Feedback
  • Priority changed from Urgent to Normal

Thanks, Robert, for the quick answer! That's really great! Is this already documented somewhere or should I add it to the Wiki?

Besides: What is the exact semantics of the option? What happens if I start a component on a node that wasn't reachable at VDemo startup time? Would it lazely try to establish its control connections on demand?

#5 Updated by R. Haschke almost 6 years ago

There was still a problem if the host couldn't be resolved at startup time. The feature is not documented - it just works intuitively ;-)
I added an additional measure to fetch broken connections: ssh_commands timeout after 5s now. 167ab63

#6 Updated by R. Haschke almost 6 years ago

You can later on establish connections to new hosts, simply entering the new host name. c5b132c

#7 Updated by R. Haschke about 5 years ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF