Changes between Version 14 and Version 15 of Old/WiMAX/05/01

Timestamp:

Dec 15, 2010, 3:07:53 PM (13 years ago)

Author:

hmussman

Comment:

—

Old/WiMAX/05/01

@@ -353 +353 @@
 [[Image(WiMAX/00:fig 7  121010_ WiMAXSystemOverview.jpg, 100%)]]
 
+Procedure provided by Evan Zhang in Summer, 2010:
+
+= This page contains all the information you need to understand the current OMF lab setting and how it was built =
+
+
+
+== Reference == 
+
+http://omf.mytestbed.net/wiki/omf/Installation_Guide_52
+
+http://omf.mytestbed.net/wiki/omf/Ubuntu_Baseline
+
+
+
+== Related Ticket == 
+
+http://groups.geni.net/syseng/ticket/1004
+
+
+
+== OMF System Architecture with WiMAX Base Station ==
+
+[[Image(omf_gpolab_arch.png)]]
+
+
+
+== Current Lab Setting ==
+
+[[Image(omf_gpolab_internal.png)]]
+
+
+
+== Installation and Test Instructions (You should always look at the reference instruction first,http://omf.mytestbed.net/wiki/omf/Installation_Guide_52) ==
+
+{{{
+Note: The OMF/OML 5.2 software(our current build target, 5.3 is on the way) mainly includes following packages(debian packages): 
+omf-aggmgr-5.2(Aggregate Manager) omf-expctl-5.2(Experiment Controller) omf-resctl-5.2(Resource Controller) oml-server oml-client openfire_3.6.4_all.deb(XMPP server).
+omf-aggmgr-5.2, omf-expctl-5.2, oml-server, openfire_3.6.4_all.deb could either be built on the same machine or dedicated machine for each.
+omf-resctl-5.2 and oml-client should be installed on each experiment node. We choose to build omf-aggmgr-5.2, omf-server, openfire_3.6.4_all.deb in one machine
+(actually VM:herculaneum.gpolab.bbn.com) and omf-expctl-5.2 in another machine(actually VM: drasnia.gpolab.bbn.com).
+For the internal test purpose, we made two kinds of the experiment node: VM nodes and physical nodes. VMs are used for the purpose of quick experiment test(without disk loading).
+Physical nodes are used for testing disk image loading. For the network design, OMF requires that AM, EC and all the nodes are IP connected as control path. And between nodes 
+there should be experiment data path, either through wired, wifi, or wimax. For our current setting, two VM nodes are wired through eth1 as experiment data path. The physical 
+node 3 is a NC10 sumsung netbook which is a wimax enbaled node, so the data path suppose to be through our wimax station. 
+}}}
+ 
+=== Installation of the Aggregate Manager machine(VM) ===
+
+==== Network Setup ====
+
+ * Different from the reference instruction, we also have two interfaces eth0 and eth1 on AM machine. eth0 is control interface with internet accessibility and [[BR]]
+eth1 is used to run our own DHCP server for the disk image loading purpose. Both eth0 and eth1 have fixed IPs and domain names assigned by GPOlab's infrastructure. 
+
+==== Configuring dnsmasq (DHCP, DNS and TFTP server) ====
+
+ * edit /etc/dnsmasq.conf and I add the following lines at the bottom of the file:
+
+{{{
+# Added by Evan for OMF installation
+interface=eth1
+dhcp-range=128.89.91.147,128.89.91.150,12h
+dhcp-option=3,128.89.91.145
+dhcp-option=121,128.89.91.30/32,128.89.91.146     <----- for dhcp assigned IP to ping 128.89.91.30, please refer to http://groups.geni.net/syseng/ticket/1004 for details
+dhcp-option=option:ntp-server,128.89.91.30
+dhcp-boot=net:control,pxelinux.0
+enable-tftp
+tftp-root=/tftpboot
+}}}
+
+ * create a new file /etc/dnsmasq.d/testbed.conf and add your node DHCP details here:
+
+{{{
+dhcp-host=net:control,00:24:54:08:67:68,ini-wimax-dhcp-147,128.89.91.147
+}}}
+
+ * /etc/init.d/dnsmasq restart
+
+==== Set up PXE booting ====
+
+ * Follow the reference instruction and change the related IPs and MACs mentioned in the instruction to ours.
+
+==== Inventory installation ====
+
+ * Follow the reference instruction and manually populate the inventory
+
+{{{
+One testbed info is added to table 'testbeds' with domain name 'sandbox1'
+Three nodes info is added to the inventory (need to update four tables for each node: devices, motherboards, locations, nodes). They are,
+
+node[1,1]: control IP: 128.89.91.31  (vm)
+node[1,2]: control IP: 128.89.91.32  (vm) 
+node[1,3]: control IP: 128.89.91.147 (NC10 physical node)
+
+For more detailed please go to: http://128.89.91.30/phpmyadmin, user:omf, pw:omf
+}}}
+
+
+
+=== Configuring the Aggregate Manager (AM) ===
+
+ * Follow the reference instruction and carefully change the IPs to ours.
+
+ * Test the CMC (Dummy) service with
+
+{{{
+ wget -qO- http://128.89.91.30:5052/cmc/allStatus?domain=sandbox1
+
+<TESTBED_STATUS>
+                <detail>
+                        <node name='n_1_1' x='1' y='1' state='POWERON'/>
+                        <node name='n_1_2' x='1' y='2' state='POWERON'/>
+                        <node name='n_1_3' x='1' y='3' state='POWERON'/>
+                </detail>
+</TESTBED_STATUS>
+}}}
+
+
+=== Installing the Experiment Controller (EC) ===
+
+ * We can not find /etc/omf-expctl-5.2/nodehandler.yaml by following the reference instruction, we need to do,
+
+{{{
+sudo cp /usr/share/doc/omf-expctl-5.2/examples/nodehandler.yaml /etc/omf-expctl-5.2/nodehandler.yaml
+}}}
+
+ * My nodehandler.yaml:
+
+{{{
+---
+:econtroller:  
+  :config:
+    :default:   
+      :domain: 'sandbox1'
+      :repository:
+        :path: ["../repository", "/usr/share/omf-expctl-5.2/repository"]
+
+      :inventory:
+        :url: 'http://128.89.91.30:5052/inventory'
+
+      :web:
+        :host: '129.89.91.31'
+
+      :communicator:
+        :type: 'xmpp'
+        :xmpp:
+          :server: '128.89.91.30'
+          :password: 'gpo2010'
+
+    :debug:
+      :repository:
+        :path: ['../repository']
+      :communicator:
+        :type: 'mock'
+
+}}}
+
+=== Configuring XMPP ===
+
+==== Installing Openfire ====
+
+{{{
+'wget http://www.igniterealtime.org/downloadServlet?filename=openfire/openfire_3.6.4_all.deb' doesn't work, should be
+wget -O openfire_3.6.4_all.deb http://www.igniterealtime.org/downloadServlet?filename=openfire/openfire_3.6.4_all.deb
+
+username: admin, password: gpo2010
+}}}
+
+==== Creating the system nodes ====
+
+{{{
+omf_create_sysnode-5.2 128.89.91.30 128.89.91.31
+omf_create_sysnode-5.2 128.89.91.30 128.89.91.32
+omf_create_sysnode-5.2 128.89.91.30 128.89.91.147
+}}}
+
+
+=== Preparing the experiment nodes ===
+
+ * For VM experiment nodes (which is not mentioned in the reference instruction), the instruction is similar as preparing the baseline disk image. Reference: http://omf.mytestbed.net/wiki/omf/Ubuntu_Baseline   
+
+{{{
+My nodeagent.yaml:
+
+# This is an example configuration for the Resource Controller at NICTA
+#
+# NOTE: use only 'spaces' to indent !
+# ('tab' indents are not supported by the ruby yaml parser used to read this file)
+#
+---
+nodeagent:
+  # Communication settings 
+  comm:
+
+    # How many seconds can we go without a message from the node handler
+    # before we assume we have lost connectivity and need to reset
+    handler_timeout: 40
+  
+    # Number of consecutive handler timeouts before a 'handler lost'
+    # will be declared.
+    timeout_count: 2
+  
+    # Number of seconds to wait between consecutive RETRY requests
+    retry_interval: 3
+  
+    # Number of seconds between consecutive HEARTBEAT messages
+    heartbeat_interval: 10
+  
+    # Pause between resending previous messages
+    resend_interval: 0.1
+  
+    server_port: 9026
+    # local_if: Control Interface used with TCPServer Comm.
+    local_if: eth0
+    xmpp_server: 128.89.91.30
+
+}}}
+
+ * For physical nodes (e.g. NC10 netbooks), we need to load disk image to it. How? We have two ways, 
+
+{{{
+A. Run frisbee server and client manually:
+
+1) Download the target disk image from Winlab. Gautam scped nc10-wimax.ndz to herculaneum.gpolab.bbn.com:/var/lib/omf-images-5.2/nc10-wimax.ndz
+2) Boot NC10 into pxe image. Refer to 'Set up PXE booting' section of this document.
+3) Run frisbee server at AM server(herculaneum): > frisbeed -p 7000 -i 128.89.91.146 -m 128.89.91.147 /var/lib/omf-images-5.2/nc10-wimax.ndz          <------Important: -i option must be specified here
+4) Run frisbee client at NC10(a shell is offered by pxe image): > frisbee -p 7000 -i 128.89.91.147 -m 128.89.91.146 /dev/sda                          <------At both sides -m option IP could be replaced by a muticast IP e.g. 224.0.0.1 
+}}}
+
+{{{
+B. Load disk image through Experiment Controller       
+
+1) Same as A.1)
+2) At Experiment Controller, run: > omf load "[1,3]" nc10-wimax.ndz
+}}}
+
+
+ * After the nodes are up. The Resource Controller will report node's liveness to XMPP server on hourly basis. You can go to http://128.89.91.30:9090/user-summary.jsp (user:admin, pw:gpo2010) to check. 
+
+
+=== Using the testbed ===
+
+At this point, you may want to run a test experiment. We choose to run a modified(get ride of the wireless configuration) hello world experiment with our two VM nodes.
+Based on this page http://omf.mytestbed.net/wiki/omf/Basic_Tutorials_for_Developing_Experiments, we developed our experiment description,
+
+{{{
+ # A) Define the 'source' group, which has the unique node [1,1]
+ #     Nodes in this group will execute the application 'test:proto:udp_sender'
+ #
+ defGroup('source', [1,1]) {|node|
+ 
+   node.prototype("test:proto:udp_sender", {
+     'destinationHost' => '192.168.0.2',
+     'localHost' => '192.168.0.1',
+     'packetSize' => 256, # in Bytes
+     'rate' => 8192 # in bits/sec
+ 
+   })
+ 
+   # mode can be 'adhoc' or 'managed' or 'master'
+# Commented out by Evan for wired test
+   #node.net.w0.mode = "master" 
+ }
+ 
+ #
+ # B)  Define the 'sink' group, which has the unique node [1,2]
+ #     Nodes in this group will execute the application 'test:proto:udp_receiver'
+ #
+ defGroup('sink', [1,2]) {|node|
+ 
+   node.prototype("test:proto:udp_receiver" , {
+     'localHost' => '192.168.0.2'
+   })
+ 
+   # mode can be 'adhoc' or 'managed' or 'master'
+# Commented out by Evan for wired test
+   #node.net.w0.mode = "managed" 
+ }
+ 
+ # 
+ # C)  Configure the wireless interfaces of All the Nodes involved in 
+ #     this experiment
+ #
+
+# Commented out by Evan for wired test
+ #allGroups.net.w0 { |w|
+ allGroups.net.e0 { |w|
+   #w.type = 'g'
+   #w.channel = "6" 
+   #w.essid = "helloworld" 
+   w.ip = "%192.168.0.%y" # the '%' triggers some substitutions
+ }
+ 
+ #
+ # D)  When all the nodes are turned On and the all the applications
+ #     are installed and ready, we can start to perform the experiment
+ #
+ whenAllInstalled() {|node|
+ 
+   wait 30 
+ 
+   allGroups.startApplications
+   wait 20
+ 
+   Experiment.done
+ }
+}}}
+
+You can run the experiment by doing:
+
+{{{
+> omf exec /path/to/hello_wire.rb
+}}}
+
+When I first ran hello_wired.rb experiment, I encountered a error at the resource controller side saying: 
+
+From /var/log/omf-resctl-5.2.log
+{{{
+2010-08-11 11:11:04 DEBUG nodeAgent::EthernetDevice: configure cmd: /sbin/ifconfig exp0 192.168.0.1 netmask 255.255.0.0
+2010-08-11 11:11:04 ERROR nodeAgent::EthernetDevice: While configuring ip with 192.168.0.1 - CMD reply is: ''
+}}}
+
+Then I found out that in source file '/usr/share/omf-resctl-5.2/omf-resctl/omf_agent/agentCommands.rb', there is mapping between net.e0 <--> exp0, 
+
+So I changed it to net.e0 <--> eth1 in order for the experiment description to assign IP to eth1.
+
+Now I can run our first experiment successfully.
+
+
+=== Instrumenting your experiment ===
+
+Basically, you need to insert some code into your application's source code to utilized the measurement library offered by OML. [[BR]]
+Then the measurement data will automatically collected and sent to OML server during the runtime of your experiment.
+
+For more detailed, please refer to: http://omf.mytestbed.net/wiki/omf/UsingOML
 
 == 6.8  OMF/OML Configuration ==