Changes between Version 16 and Version 17 of OldFeddAbout

Timestamp:

Jul 16, 2012 6:21:34 PM (12 years ago)

Author:

faber

Comment:

--

OldFeddAbout

@@ -434 +434 @@
 
 By splitting this function out, we intend to allow different installations of `fedd` to provide different interconnection and service tunneling function.  Currently the [FeddDownload DETER fedkit] is the only federation kit in use, and `fedd` defaults its startcmd options for use with it.
+
+The federation kit has 2 roles
+
+ * Configuring experiment nodes to use [FeddAbout#ExperimentServices services], such as shared file systems.
+ * Configuring portal nodes to connect experiments
+
+== Fedkit on Experiment Nodes ==
+
+On experiment nodes, the fedkit starts dynamic routing, and optionally configures user accounts and samba filesystems if they are in use.  The system expects the following software to be available:
+
+ * quagga routing system (an old gated installation will also work)
+ * samba-client
+ * smbfs
  
+Those are the linux package names; equivalent FreeBSD packages will also work.  For software to be available is for it to be either installed or accessible using {{{yum}}} or {{{apt-get}}}.  DETER nodes have a local repository for that purpose.
+
+The fedkit is installed in {{{/usr/local/federation}}} and when run places a log in {{{/tmp/federate}}}.
+
+Services are initialized based on the contents of {{{/usr/local/federation/etc/client.conf}}}.  Possible values include:
+
+ '''!ControlGateway'''::
+  The DNS name (or IP address) of the node that will forward services
+ '''Hide''':
+  Do nat add this node to the node's view of the experiment.  Used for [FeddMulti multi-party experiments].
+ '''!PortalAlias'''::
+  A name that will be mapped to the same IP address as the control gateway.  SEER in particular expects nodes with certain functions to have certain names.
+ '''!ProjectUser'''::
+  The local user under which to mount shared project directories
+ '''!ProjectName'''::
+  Project name to derive shared project directories from
+ '''Service'''::
+  a string naming the [FeddAbout#ExperimentServices services] to initialize.
+ '''SMBShare'''::
+  The name of the share to mount
+
+
+
+== Fedkit on Portal Nodes ==
+
+On portal nodes the fedkit uses ssh to interconnect the segments and bridges traffic at layer 2.  If the portal node is a Linux image it needs to have the {{{bridge-tools}}} package available.  Like the fedkit on experiment nodes, it will attempt to load that software from repositories if it is not present.
+
+The fedkit configures the portal based on the contents of a configuration file containing the following parameters:
+
+ '''active'''::
+  a boolean.  If true this portal will initiate ssh connections to its peer.
+ '''nat_partner'''::
+  a boolean.  If true the fedkit's peer is behind a network address translator.  Not used yet.
+ '''tunnelip'''::
+  a boolean.  If true use the DETER system for binding external addresses.
+ '''peer'''::
+  a string.  A list of DNS names or IP addresses.  Usually this is one value, the DNS name of the peer, but passive ends of NATted portals may use a list of addresses to establish routing.
+ '''ssh_pubkey'''::
+  a string.  A file in which the access controller has placed the ssh key shared by this portal and its peer.  These are nonce keys discarded after the experiment ends.
+ '''ssh_privkey'''::
+  a string.  A file in which the access controller has placed the ssh key shared by this portal and its peer.  These are nonce keys discarded after the experiment ends.
+
+The passive portal node establishes routing connectivity to the active end, reconfigures the local sshd to allow link layer forwarding and to allow the active end to remotely configure it, and waits.  The active end connects through ssh, establishes a link layer forwarding tunnel and bridges that to the experimental interface.  It also forwards ports to connect experiment services.
 
 = Interfaces to fedd =