1LOGFORWARDER(1) LOGFORWARDER(1)
2
3
4
6 logForwarder - Log item to manage ssh tunnels between log components
7 and tools
8
10 logForwarder - Tools for creating and maintaining ssh tunnels between
11 log components in complex topologies
12
14 logForwarder [options] ...
15
17 logForwarder helps simplifying the maintenance of ssh tunnels between
18 log components and tools, thus improving log scalability and configura‐
19 tion in complex network topologies. The components may be defined in a
20 program to be monitored, they publish messages in the LogCentral. The
21 tools get the messages subscribing to the LogCentral.
22
23 Before starting a log forwarder, you must:
24
25 · launch omniNames on the local and remotes hosts.
26
27 · launch the remote peer only defining its name and network configura‐
28 tion.
29
30 · launch local peer and give him remote peer's name, ssh connection
31 credentials, remote port to use and pass -C option to create the ssh
32 tunnel.
33
34 [Remark: forwarders must be launched before the log tools/components]
35
37 --name [name]
38 String identifying the forwarder
39
40 --peer-name [name]
41 String identifying its peer on the other network
42
43 --ssh-host [host]
44 Host hosting the ssh tunnel
45
46 --ssh-login [login]
47 Login used to establish the ssh connection (default: current
48 user login).
49
50 --ssh-key [/path/to/ssh/key]
51 Path to the ssh key (the private one !) used to establish the
52 ssh connection (default: $HOME/.ssh/id_rsa).
53
54 --remote-port [port]
55 Port listening on the ssh host.
56
57 --remote-host [host]
58 Host to which the connection is made by the tunnel (corresponds
59 to ssh options -L and -R).
60
61 --nb-retry [nb]
62 Number of times that the local forwarder will try to bind itself
63 to the remote forwarder (default: 3).
64
65 --peer-ior [IOR]
66 Pass remote forwarder's IOR. By default, the local forwarder
67 will retrive its peer IOR.
68
70 Here's a simple configuration:
71
72 · We have two domains: net1 and net2, forwarders will be launched on
73 hosts fwd.net1 and fwd.net2.
74
75 · There's no link between hosts fwd.net1 and fwd.net2 but user may
76 access fwd.net2 from fwd.net1 using a ssh connection.
77
78 · We'll name fwd.net1 forwarder Fwd1 and fwd.net2 fowarder Fwd2.
79
80 · One tool lives in fwd.net2 while a component lives on the net1
81 domain.
82
83 Command line for launchind Fwd1
84
85 fwd.net1$ logForwarder --name Fwd1 --peer-name Fwd2 \
86 --ssh-host fwd.net2 --ssh-login dietUser \
87 --ssh-key id rsa net2 --remote-port 50000
88
89 Command line to launch Fwd2
90
91 fwd.net2$ logForwarder --name Fwd2
92
94 The log service uses CORBA as its communication layer. While it's a
95 flexible and robust middleware, it remains hard deploying the log on
96 heterogeneous networks that are not reachable except through ssh tun‐
97 nels. Log forwarders help administrator configuring their grid without
98 manually set-up ssh tunnels which arguably is neither simple nor scal‐
99 able. Log forwarders make it very easy configuring such topologies.
100
102 Copyright
103 (C)2011, GRAAL, INRIA Rhone-Alpes, 46 allee d'Italie, 69364 Lyon cedex
104 07, France all right reserved <diet-dev@ens-lyon.fr>
105
106 License
107 This program is free software: you can redistribute it and/or mod‐ ify
108 it under the terms of the GNU General Public License as pub‐ lished by
109 the Free Software Foundation, either version 3 of the License, or (at
110 your option) any later version. This program is distributed in the hope
111 that it will be useful, but WITHOUT ANY WARRANTY; without even the
112 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR‐
113 POSE. See the GNU General Pub- lic Li‐ cense for more details. You
114 should have received a copy of the GNU General Public License along
115 with this program. If not, see <http://www.gnu.org/licenses/>.
116
118 GRAAL INRIA Rhone-Alpes 46 allee d'Italie 69364 Lyon cedex 07, FRANCE
119 Email: <diet-dev@ens-lyon.fr> WWW: http://graal.ens-lyon.fr/DIET
120
122 omniNames(1), dietForwarder(1), LogCentral(1)
123
125 On some systems, forwarder rules won't work unless you use IP addresses
126 instead of hostnames
127
129 haikel.guemar@sysfera.com, kevin.coulomb@sysfera.com
130
131 License: GPLv3
132
134 DIET developers
135
136
137
138
1390.1 2011-05-11 LOGFORWARDER(1)