[Planetlab-devel] tagged VLAN 802.1Q logical subinterface on planetlab slices

[Chris Tracy]

Hi Marc,

>    What version & variant of MyPLC are you using? *By variant I am referring
>    to myplc or myplc-native.

Thanks for the quick response.  I followed the instructions at
https://svn.planet-lab.org/wiki/MyPLCUserGuide, so we are using
myplc-native.

I setup my environment using a command like this: 

./vtest-init-vserver.sh -p linux32 max-myplc
http://build.planet-lab.org/planetlab/f8/planetlab-f8-linux32-4.2-rc24/RPMS/
-- --interface eth0:[IP] --hostname [hostname] &> max-myplc.log &

I then entered the vserver and ran 'yum -y install myplc-native',
configured with 'plc-config-tty', etc..

>    You should upgrade to a new version of MyPLC. I can direct you to
>    this once you answer the above question.

Excellent, I suppose I will need to use a different URL in my vserver
creation command above?  One that points to a newer snapshot?

>    Why do you need to see /proc/net/vlan from inside the vserver?
>    The way we are assuming this is going to work is that a machine
>    will have one or more nodenetwork settings with the appropriate
>    VLAN configuration information as one might find in a
>    /etc/sysconfig/network-scripts/ifcfg-* file. *Specifically for
>    these VLANs we currently assume they will have a static IP
>    address associated with it. * These VLANs could then be made
>    visible across all slices OR they can be made visible within one
>    or more specific slices. *The way the latter works for now is
>    that one needs to add the appropriate IP to the "ip_addresses"
>    attribute associated with a specific sliver (i.e., a slice
>    associated with a specific node). *This is picked up by the
>    nodemanager, which makes the appropriate calls below the covers
>    to make the interface associated with this IP address visible to
>    the sliver.

Yes, I agree that I do not necessarily need to see /proc/net/vlan at
all.  As long as the new slice comes up with an ethX.Y interface, we
should be good to go.

I will work up a little diagram to illustrate exactly what we are
trying to do, I think it will help to explain..  To explain briefly, I
would actually like my planetlab slices to come up with one eth0 that
has the public IP address that will be used to login via SSH, etc.  I
would like to have other interfaces such as eth1.3000 (possibly
several of them) which use private IP addresses (such as a /30).  eth1
of the physical host will be plugged into a dynamic network, which can
provision circuits across a layer 2 infrastructure, similar to how
planetlab can provision slices.

For example, we can perform bookahead/scheduled reservations of
circuits which are provisioned using Ethernet VLANs, which will also
be policed to a certain bandwidth level.  For a video/screencast
demonstration of this, please see:
http://dragon.maxgigapop.net/twiki/bin/view/GENI/GEC3DRAGONDemonstrationMovie

>    Daniel Hokka Zakrisson is the person who has finalized this code
>    (call*[2]pyplnet). *I'd advise that you join our IRC channel (#planetlab)
>    on irc.freenode.net and catch up with daniel_hozac and myself for further
>    details.

Sounds good, I'm there now!

Thanks,
-Chris


>    Cheers,
>    Marc
> 
> References
> 
>    Visible links
>    1. http://groups.geni.net/geni/wiki/Mid-Atlantic%20Crossroads
>    2. http://svn.planet-lab.org/browser/pyplnet

> _______________________________________________
> Devel mailing list
> Devel at lists.planet-lab.org
> https://lists.planet-lab.org/mailman/listinfo/devel


-- 
Chris Tracy
Mid-Atlantic Crossroads (MAX)
Office phone: 301.314.6655
GPG key: 0xB3B9C93D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
Url : http://lists.planet-lab.org/pipermail/devel/attachments/20081215/61b29c12/attachment.bin