[Planetlab-devel] RE: Re: Myplc-SFA-OMF binding (Thierry Parmentelat)

Theofilos Pe theofilos_pe at hotmail.com
Mon Feb 7 19:46:16 EST 2011


I greately appreciate your response. My setup goes like this: I have 4 virtual machines in a vserver. Two stand for planetlab nodes, one for myplc and one for omf-aggregator-manager.
omf-aggegator manager has two virtual ethernet interfaces, one for internet and one for the dhcp server. The nodes and myplc have only one for internet. 

myplc is as follows.
On a centos 5.5 I have setup a vserver which runs fedora 8 and this one contains myplc with the following setup:

Fedora release 8 (Werewolf)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx build info
Build build-date: 2010.05.05
Build build-time: 14:10-EDT
Build build-hostname: anakin.cs.princeton.edu
Build build-base: planetlab-f8-i386-4.3-rc18
Build planetlab-distro: planetlab
Build planetlab-tags: planetlab-tags.mk
Build planetlab-tagsid: # $Id: planetlab-tags.mk 16893 2010-01-29 18:18:12Z caglar $
Build target-arch: i386
Build target-distro: Fedora
Build target-distroname: f8
Build target-release: 8
Build target-personality: linux32
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx svn info
                BootCD-SVNPATH := http://svn.planet-lab.org/svn/BootCD/tags/BootCD-4.2-17
           BootManager-SVNPATH := http://svn.planet-lab.org/svn/BootManager/tags/BootManager-4.3-16
           BootstrapFS-SVNPATH := http://svn.planet-lab.org/svn/BootstrapFS/tags/BootstrapFS-1.0-11
               CoDemux-SVNPATH := http://svn.planet-lab.org/svn/CoDemux/tags/CoDemux-0.1-13
DistributedRateLimiting-SVNPATH := http://svn.planet-lab.org/svn/DistributedRateLimiting/trunk
                   Mom-SVNPATH := http://svn.planet-lab.org/svn/Mom/tags/Mom-2.3-2
               Monitor-SVNPATH := http://svn.planet-lab.org/svn//Monitor/tags/Monitor-3.0-30/
                 MyPLC-SVNPATH := http://svn.planet-lab.org/svn/MyPLC/tags/MyPLC-4.3-37
           NodeManager-SVNPATH := http://svn.planet-lab.org/svn/NodeManager/tags/NodeManager-1.8-23
            NodeUpdate-SVNPATH := http://svn.planet-lab.org/svn/NodeUpdate/tags/NodeUpdate-0.5-6
                PLCAPI-SVNPATH := http://svn.planet-lab.org/svn/PLCAPI/tags/PLCAPI-4.3-33
                 PLCRT-SVNPATH := http://svn.planet-lab.org/svn/PLCRT/tags/PLCRT-1.0-11
                PLEWWW-SVNPATH := http://svn.planet-lab.org/svn/PLEWWW/tags/PLEWWW-4.3-41
           PingOfDeath-SVNPATH := http://svn.planet-lab.org/svn/PingOfDeath/tags/PingOfDeath-2.2-1
      VserverReference-SVNPATH := http://svn.planet-lab.org/svn/VserverReference/tags/VserverReference-4.2-16
                 build-SVNPATH := http://svn.planet-lab.org/svn/build/tags/4.3-rc18
                drupal-SVNPATH := http://svn.planet-lab.org/svn/drupal/tags/drupal-4.7-13
           fprobe-ulog-SVNPATH := http://svn.planet-lab.org/svn/fprobe-ulog/tags/fprobe-ulog-1.1.3-0
              iproute2-SVNPATH := http://svn.planet-lab.org/svn/iproute2/tags/iproute2-2.6.16-2
              iptables-SVNPATH := http://svn.planet-lab.org/svn/iptables/tags/iptables-1.3.8-10
             linux-2.6-SVNPATH := http://svn.planet-lab.org/svn/linux-2.6/tags/linux-2.6-22-39
               madwifi-SVNPATH := http://svn.planet-lab.org/svn/madwifi/tags/madwifi-0.9.4-3
            nodeconfig-SVNPATH := http://svn.planet-lab.org/svn/nodeconfig/tags/nodeconfig-4.3-7
            pcucontrol-SVNPATH := http://svn.planet-lab.org/svn/pcucontrol/tags/pcucontrol-1.0-1/
              pf2slice-SVNPATH := http://svn.planet-lab.org/svn/pf2slice/tags/pf2slice-1.0-2
               pl_sshd-SVNPATH := http://svn.planet-lab.org/svn/pl_sshd/tags/pl_sshd-1.0-11
             pyopenssl-SVNPATH := http://svn.planet-lab.org/svn/pyopenssl/tags/pyopenssl-0.9-1
              pypcilib-SVNPATH := http://svn.planet-lab.org/svn/pypcilib/tags/pypcilib-0.2-9
               pyplnet-SVNPATH := http://svn.planet-lab.org/svn/pyplnet/tags/pyplnet-4.3-4
                   sfa-SVNPATH := http://svn.planet-lab.org/svn/sfa/tags/sfa-0.9-10
          util-vserver-SVNPATH := http://svn.planet-lab.org/svn/util-vserver/tags/util-vserver-0.30.215-6
       util-vserver-pl-SVNPATH := http://svn.planet-lab.org/svn/util-vserver-pl/tags/util-vserver-pl-0.3-22
                  vsys-SVNPATH := http://svn.planet-lab.org/svn/vsys/tags/vsys-0.9-4
          vsys-scripts-SVNPATH := http://svn.planet-lab.org/svn/vsys-scripts/tags/vsys-scripts-0.95-14
   www-register-wizard-SVNPATH := http://svn.planet-lab.org/svn/www-register-wizard/tags/www-register-wizard-4.3-1
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx rpm info
DistributedRateLimiting :: version=0.1 release=1.planetlab.2010.05.05
              PLCAPI :: version=4.3 release=33.planetlab
bootcd-planetlab-i386 :: version=4.2 release=17.2010.05.05
         bootmanager :: version=4.3 release=16.planetlab
bootstrapfs-planetlab-i386 :: version=1.0 release=11.2010.05.05
             codemux :: version=0.1 release=13.planetlab
              drupal :: version=4.7 release=13.planetlab
         fprobe-ulog :: version=1.1.3 release=0.planetlab
                ipod :: version=2.2 release=1.planetlab
             iproute :: version=2.6.16 release=2.planetlab
            iptables :: version=1.3.8 release=10.planetlab
              kernel :: version=2.6.22.19 release=vs2.3.0.34.39.planetlab
             madwifi :: version=0.9.4 release=2.6.22.19.3.planetlab
              pl_mom :: version=2.3 release=2.planetlab
             monitor :: version=3.0 release=30.planetlab
               myplc :: version=4.3 release=37.planetlab
          myplc-docs :: version=4.3 release=37.planetlab
          nodeconfig :: version=4.3 release=7.planetlab
         NodeManager :: version=1.8 release=23.planetlab
noderepo-planetlab-i386 :: version=1.0 release=11.2010.05.05
          NodeUpdate :: version=0.5 release=6.planetlab
          pcucontrol :: version=1.0 release=1.planetlab
            pf2slice :: version=1.0 release=2.planetlab
               plcrt :: version=1.0 release=11.planetlab
              plewww :: version=4.3 release=41
           pyOpenSSL :: version=0.9 release=1.planetlab
            pypcilib :: version=0.2 release=9.planetlab
             pyplnet :: version=4.3 release=4.planetlab
       myplc-release :: version=4.3 release=37.planetlab.2010.05.05
                 sfa :: version=0.9 release=10.planetlab
             pl_sshd :: version=1.0 release=11.planetlab
        util-vserver :: version=0.30.215 release=6
     util-vserver-pl :: version=0.3 release=22.planetlab
             vserver :: version=4.2 release=16.2010.05.05
                vsys :: version=0.9 release=4.planetlab
        vsys-scripts :: version=0.95 release=14.planetlab
 www-register-wizard :: version=4.3 release=1.planetlab
              zabbix :: version=3.0 release=1
Fedora release 8 (Werewolf)

In addition to that I have setup a vlan with a vswitch for omf-aggrregator manager, and two physical ethernet interfaces where the wireless routers will be put.

Routers will be assigned ips 10.0.0.x from omf-aggregator manager as recommended in OMF installation-and-Hello-World tutorial.

I have an account at http://www.planet-lab.org/ since I study in NTUA, so I am not sure whether I can check https://www.planet-lab.eu:443/db/nodes/interface.php?id=125 somehow. I would be 
very interested in doing it though as it seems it would be a great help.
Since this project is actually my thesis, I may have to do some (or if I dont stand so lucky- much:P) coding on my own, in order to make the binding, and after wards perform the experiment.

> This is the general idea; then the interface should come up as part of the usual boot process---->would you be kind enough to explain this a bit more? Meaning that I will manage the interfaces 
as real interfaces inside myplc? 

Thank you in advance for your help!
----------------------------------------------------------
> 
> Message: 1
> Date: Mon, 7 Feb 2011 14:55:53 +0100
> From: Thierry Parmentelat <thierry.parmentelat at inria.fr>
> Subject: Re: [Planetlab-devel] Myplc-SFA-OMF binding
> To: PlanetLab Development <devel at planet-lab.org>
> Message-ID: <C5AFCD22-BFF8-4BF9-91BB-A6E4500AB937 at inria.fr>
> Content-Type: text/plain; charset="us-ascii"
> 
> Hi Theofilos
> 
> As far as the support for wireless goes:
> we don't have much of a documentation at this point
> the basic idea is rather simple: assuming that you'd want to have a wired interface for management, plus one wireless interface for exps.:
> 
> you would create a secondary interface, attach it to the node in question, and then set tags to configure the wireless network
> the tags to use are the ones listed in this file below
> http://git.onelab.eu/?p=plcapi.git;a=blob;f=PLC/Accessors/Accessors_wireless.py;hb=HEAD
> the set of supported tags very closely matches what is supported by the initscripts system under fedora
> 
> Alternatively, ou can probe these tags through the API, e.g.:
> >>> [tt['tagname'] for tt in GetTagTypes({'category':'*wifi*'})]
> [u'mode', u'sens', u'iwconfig', u'key', u'channel', u'securitymode', u'iwpriv', u'freq', u'rate', u'key3', u'key2', u'key1', u'nw', u'key4', u'essid']
> 
> If you have an ccount on PLE you can see how this is done for a real node
> https://www.planet-lab.eu:443/db/nodes/interface.php?id=125
> (this one just selects its ESSID; we've chosen to implement access policy as a MACaddress-based filters in the access point)
> 
> ====
> This is the general idea; then the interface should come up as part of the usual boot process, and the slices hould be able to use it as well. Of course if anything goes wrong the first thing to check is whether the interface has been correctly brought up, i.e. whether it can be accessed from the root context.
> 
> ===
> However, I just checked the whole thing on this node wlab02.pl.sophia.inria.fr
> Turns out that I just upgraded it to f14, and it looks like things don't work as smoothy as they should, at least with f14
> 
> I'm willing to spend some time checking all this, and fixing stuff as need be; 
> What is your target environment ? You're saying that you already have a deployed myplc, what flavour are you running on the nodes ?
> I mean, which combination of fedoradistro & planetlabditro ( & architecture) are we talking about ?
> I'm asking b/c we used to have code that relied on patching /etc/modprobe.conf, and that seems to have been deprecated, so a change is needed in our code; but if you're lucky maybe you can live without it ...
> 
> 
> -- Thierry
> 
> 
> On Feb 5, 2011, at 9:15 PM, Theofilos Pe wrote:
> 
> > Hello to you all! I have installed myplc and successfully booted two nodes. I plan to setup a wireless testbed using omf with two wireless nodes. The purpose of my experiment is to use SFA in order to give a user a slice which consists of wireless nodes+planetlab slivers. The main idea comes from this:
> > 
> > http://mytestbed.net/wiki/1/OMFManagementPlanetLab
> > 
> > I would like the user and/or the myplc nodes to be able to interact with the wireless network.  Could anyone point me in a brief steps method I should follow in order to implement this binding? Thank you in advance for your help!
> > 
> > Theofilos
> > _______________________________________________
> > Devel mailing list
> > Devel at lists.planet-lab.org
> > https://lists.planet-lab.org/mailman/listinfo/devel
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.planet-lab.org/pipermail/devel/attachments/20110207/94d213a1/attachment-0001.html
> 
> ------------------------------
> 
> _______________________________________________
> Devel mailing list
> Devel at lists.planet-lab.org
> https://lists.planet-lab.org/mailman/listinfo/devel
> 
> 
> End of Devel Digest, Vol 82, Issue 4
> ************************************
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.planet-lab.org/pipermail/devel/attachments/20110208/843f6109/attachment-0001.html


More information about the Devel mailing list