Changes between Version 2 and Version 3 of FeddDesktop

Timestamp:

Jan 21, 2013 10:54:58 PM (11 years ago)

Author:

faber

Comment:

--

FeddDesktop

@@ -37 +37 @@
 Be sure to run these commands as root before attempting to create experiments using the desktop plugin.
 
+Also follow the [FeddConfig#MakingaFedidCertificate instructions for creating a fedid] for this controller.  Save that identity in the configuration directory we create below.  Conventionally, that ID is stored in {{{fedd.pem}}}.
+
 === Configuring the Desktop Controller ===
 
-Create a directory for the data and configuration of the desktop controller.  It does not need to be on a very large file system - a few megs at *most* - but should not be in a temporary directory.  DETER uses {{{/usr/local/etc/fedd}}} for this.  In the configuration directory, create a file similar to [attachment:desktop.conf this one]:
+Create a directory for the data and configuration of the desktop controller.  It does not need to be on a very large file system - a few megs at *most* - but should not be in a temporary directory.  DETER uses {{{/usr/local/etc/fedd}}} for this.  In the configuration directory, create a file similar to [attachment:desktop.conf this one] called {{{desktop.conf}}}:
 
+{{{
+[DEFAULT]
+
+# The directory containing this file
+base: /vim/fedd_desktop
+
+[access]
+
+log_level: debug
+# Saved controller state
+access_state: %(base)s/desktop_access.state
+# saved access info (generated by access_to_abac.py)
+accessdb: %(base)s/desktop_access_map
+# The ABAC database (generated by access_to_abac.py)
+certdir: %(base)s/certs
+# Location of generated scripts and temp data
+localdir: %(base)s/local
+
+auth_type: abac
+auth_dir: %(base)s/abac
+
+# The hostname of the machine we run on
+hostname: vim.isi.edu
+
+# If set the first hop router to DETER (DNS name or IP address)
+# gateway: first_hop.your.domain
+
+# If set the IP address of the interface to use in accessing DETER (Linux only)
+# interface_address 192.168.1.1
+
+[globals]
+# The controllers self-signed identity (X.509 cert)
+cert_file: %(base)s/fedd.pem
+# Port on which to listen
+services: 23235
+# This is a desktop access controller
+access_type: desktop
+}}}
+
+You will want to change {{{base}}} to point to the configuration file, and {{{hostname}}} to be the DNS name of the machine the controller runs on.  If you want to route the experimental traffic through a particular interface, you can use the {{{gateway}}} or {{{interface_address}}} parameters to select the interface to use.  If {{{gateway}}} is set, the interface that routes to that gateway will be used.  If {{{interface_address}}} is set, the interface that has that address assigned will be used.  Currently {{{interface_address}}} only works on Linux machines.
+
+The rest of the defaults are probably acceptable, but they are described in the comments and [FeddConfig#MainConfigurationFilefedd.conf this documentation].
+
+In addition, in the configuration directory create 3 subdirectories:
+
+ * certs - used to hold allocation fedids (if you prefer another name, change the {{{certdir}}} parameter in {{{desktop.conf}}} to point at it)
+ * local - used to hold controller data and the startup and shutdown scripts (if you prefer another name, change the {{{localdir}}} parameter in {{{desktop.conf}}} to point at it)
+ * abac - used to hold ABAC data (if you prefer another name, change the {{{auth_ir}}} parameter in {{{desktop.conf}}} to point at it)
+
+=== Configuring ABAC ===
+
+The simplest configuration of the desktop controller allows a specific DETER user to access it.  To set that up, create a file called {{{desktop_access}}} with a line similar to the following:
+
+{{{
+(fedid:e630047380b1060ce03d19e373b8047bb785031a,<any>,faber)-> access, (access)
+}}}
+
+Change {{{faber}}} to the username of the DETER user you wish to grant access.  If you want multiple users to be able to federate this machine, add additional lines with the same format.  The fedid at the beginning of the line is the fedid of the DETER experiment controller.  This line allows the named DETER users (as validated by the experiment controller) to federate this machine.
+
+To make that operative, use the [FeddABAC#access_to_abac.py access_to_abac.py] command to create the ABAC database:
+
+{{{
+$ access_to_abac.py --cert=fedd.pem --dir=/usr/local/etc/fedd/abac --type=skel --mapfile=desktop_access_map ./desktop_access
+}}}
+
+That command must be run from the configuration directory.  The argument to {{{--dir}}} must be an absolute pathname.
+
+At this point you should be able to start the controller:
+
+{{{
+$ fedd.py --config /usr/local/etc/fedd/desktop.conf
+}}}
+
+== A test experiment ==
+
+This file contains a two node experiment, one node on DETER and the other on your desktop:
+
+{{{
+# simple DETER topology federated to a desktop
+#
+# SERVICE: project_export:deter::project=SAFER
+#
+
+set ns [new Simulator]
+source tb_compat.tcl
+
+set a [$ns node]
+set b [$ns node]
+tb-set-node-testbed $a "deter"
+
+tb-set-node-testbed $b "desktop"
+
+set link0 [ $ns duplex-link $a $b 100Mb 0ms DropTail]
+
+$ns rtproto Static
+$ns run
+
+}}}