https://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732014-11-03T16:28:16ZOpen Source Collaboration Platformvdemo - Feature #2072: Ignore non-reachable Hosts during Startuphttps://code.cor-lab.de/issues/2072?journal_id=61202014-11-03T16:28:16ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<ul><li><strong>Related to</strong> <i><a href="/issues/2071" class="issue tracker-2 status-3 priority-4 priority-default closed">Feature #2071</a>: Survive connection loss </i> added</li></ul> vdemo - Feature #2072: Ignore non-reachable Hosts during Startuphttps://code.cor-lab.de/issues/2072?journal_id=61222014-11-03T16:29:04ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<ul></ul><p>For us, this is really a big problem. What would be needed to add such a behavior to VDemo?</p> vdemo - Feature #2072: Ignore non-reachable Hosts during Startuphttps://code.cor-lab.de/issues/2072?journal_id=61252014-11-03T23:28:33ZR. Haschkerhaschke@techfak.uni-bielefeld.de
<ul></ul><p>This feature already exists: the timeout for ssh connections is set to 15s in line 11:</p>
<p>set SSHOPTS "-oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no -oConnectTimeout=15"</p>
<p>So, please be patient ;-)</p> vdemo - Feature #2072: Ignore non-reachable Hosts during Startuphttps://code.cor-lab.de/issues/2072?journal_id=61272014-11-04T08:37:36ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>Priority</strong> changed from <i>Urgent</i> to <i>Normal</i></li></ul><p>Thanks, Robert, for the quick answer! That's really great! Is this already documented somewhere or should I add it to the Wiki?</p>
<p>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?</p> vdemo - Feature #2072: Ignore non-reachable Hosts during Startuphttps://code.cor-lab.de/issues/2072?journal_id=61292014-11-04T09:04:30ZR. Haschkerhaschke@techfak.uni-bielefeld.de
<ul></ul><p>There was still a problem if the host couldn't be resolved at startup time. The feature is not documented - it just works intuitively ;-)<br />I added an additional measure to fetch broken connections: ssh_commands timeout after 5s now. <a href="https://code.cor-lab.de/projects/vdemo/repository/revisions/167ab63249d792eec85027c06a81a0056332dc0f" class="changeset" title="timeout on ssh_commands (when connection is not established or broken)">167ab63</a></p> vdemo - Feature #2072: Ignore non-reachable Hosts during Startuphttps://code.cor-lab.de/issues/2072?journal_id=61302014-11-04T09:06:50ZR. Haschkerhaschke@techfak.uni-bielefeld.de
<ul></ul><p>You can later on establish connections to new hosts, simply entering the new host name. <a href="https://code.cor-lab.de/projects/vdemo/repository/revisions/c5b132cd05273a50e8d8899b47eeb4e68cd1ce52" class="changeset" title="reestablish master connection if necessary">c5b132c</a></p> vdemo - Feature #2072: Ignore non-reachable Hosts during Startuphttps://code.cor-lab.de/issues/2072?journal_id=74432015-08-28T18:32:15ZR. Haschkerhaschke@techfak.uni-bielefeld.de
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li></ul>