Community-Lab introduction: Check-in [38cde6816a]

Overview

Comment:	Use stacked diagrams for testbed architecture and logos, update script.
Downloads:	Tarball \| ZIP archive \| SQL archive
Timelines:	family \| ancestors \| descendants \| both \| fosdem-2014
Files:	files \| file ages \| folders
SHA1:	38cde6816a1663761ba1aab11d74feb733f3c511
User & Date:	ivan on 2014-01-30 12:07:56
Other Links:	manifest \| tags

Context

2014-01-30
12:32		Add slices, slivers and sliver connectivity to testbed architecture diagram. check-in: 6b3bdebd64 user: ivan tags: fosdem-2014
12:07		Use stacked diagrams for testbed architecture and logos, update script. check-in: 38cde6816a user: ivan tags: fosdem-2014
11:50		More small rearrangements to logos in testbed diagram. check-in: 347300a58e user: ivan tags: fosdem-2014

Changes

Hide Diffs Unified Diffs Ignore Whitespace Patch

Modified Makefile from [898a0ad0e5] to [3dc5bf7852].

IMGS = imgs/network-public.png imgs/network-private.png imgs/network-community.png \
	imgs/confine-partners.png imgs/extend-network.png


IMGS_BEAMER = imgs/confine,background.pdf


.PHONY:	clean

all:	slides,lightning.pdf

................................................................................

imgs/confine-partners.png:	logos/confine-partners.svg
	inkscape -z -C -e $@ -w 1024 $<

imgs/extend-network.png:	diagrams/extend-network.svg
	inkscape -z -C -e $@ -w 1024 $<

















clean:
	rm -f $(IMGS) $(IMGS_BEAMER) slides,lightning.pdf slides,lightning.html


|
>
>







 







>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

IMGS = imgs/network-public.png imgs/network-private.png imgs/network-community.png \
	imgs/confine-partners.png imgs/extend-network.png \
	imgs/testbed.png imgs/testbed-cd-rd.png \
	imgs/testbed-logos-node.png imgs/testbed-logos-mgmt.png imgs/testbed-logos-devel.png
IMGS_BEAMER = imgs/confine,background.pdf


.PHONY:	clean

all:	slides,lightning.pdf

................................................................................

imgs/confine-partners.png:	logos/confine-partners.svg
	inkscape -z -C -e $@ -w 1024 $<

imgs/extend-network.png:	diagrams/extend-network.svg
	inkscape -z -C -e $@ -w 1024 $<

imgs/testbed.png:	diagrams/testbed-logos.dia
	dia -e $@ -L testbed -s 1024x $<

imgs/testbed-cd-rd.png:	diagrams/testbed-logos.dia
	dia -e $@ -L testbed,cd-rd -s 1024x $<

imgs/testbed-logos-node.png:	diagrams/testbed-logos.dia
	dia -e $@ -L testbed,cd-rd,logos-node -s 1024x $<

imgs/testbed-logos-mgmt.png:	diagrams/testbed-logos.dia
	dia -e $@ -L testbed,cd-rd,logos-node,logos-mgmt -s 1024x $<

imgs/testbed-logos-devel.png:	diagrams/testbed-logos.dia
	dia -e $@ -L testbed,cd-rd,logos-node,logos-mgmt,logos-devel -s 1024x $<


clean:
	rm -f $(IMGS) $(IMGS_BEAMER) slides,lightning.pdf slides,lightning.html

Modified script,lightning.txt from [2be8593ac1] to [0a81b0f647].

  stations, etc. to be used by the community. *##*
- In a more sophisticated approach, nodes can also be used to implement cloud
  infrastructure provided and managed by the community for the community.
  This is the mission of the Clommunity project. *##*

* Architecture and technologies
** Testbed architecture

- Community-Lab consists of a set of nodes (managed by CN members) that follow
  the configuration in a set of servers (managed by testbed operators).
- All components in the testbed become reachable via a dedicated management
  network implemented as an IPv6 overlay.
- Researchers define experiments (so called slices) in a server.
- Nodes use a REST API to get those definitions from servers and run several
  of them simultaneously as VMs (so called slivers).
- Slivers can access the CN via NAT, natively at the network layer, or in an
  isolated VLAN for routing experiments. *##*

** Technologies

- Nodes are connected via Ethernet to normal community devices.
- Nodes are moderately powerful computers running OpenWrt with a control
  daemon written in Lua.  Slivers are implemented as Linux containers.  We are
  working on safe node upgrade using kexec.

- The GUI and REST API in servers are implemented as Django applications.
- The IPv6 overlay used for the management network is a tinc mesh VPN.
- We use Git, Redmine, Jenkins and our Virtual CONFINE Tesbed (VCT) package
  for development and testing. *##*

* Collaborations
- CONFINE actively collaborates to the development of several Free software
  projects: the OpenWrt router distro, the BMX6 and OLSR mesh routing
  protocols, the DLEP protocol for collecting link characteristics, the NodeDB








>
|
|


|
|
|




>
|
<
|
|
>

|

  stations, etc. to be used by the community. *##*
- In a more sophisticated approach, nodes can also be used to implement cloud
  infrastructure provided and managed by the community for the community.
  This is the mission of the Clommunity project. *##*

* Architecture and technologies
** Testbed architecture
- How does the Community-Lab testbed work?
- It consists of a set of nodes (managed by CN members) that follow the
  configuration in a set of servers (managed by testbed operators).
- All components in the testbed become reachable via a dedicated management
  network implemented as an IPv6 overlay.
- Then researchers define experiments (the so called slices) in a server.
- And nodes use a REST API to get those definitions from servers and run
  several of them simultaneously as VMs (the so called slivers).
- Slivers can access the CN via NAT, natively at the network layer, or in an
  isolated VLAN for routing experiments. *##*

** Technologies
- Nodes are moderately powerful computers (like this barebone computer)
  connected via Ethernet to normal community devices (i.e. routers). *##*

- Nodes run OpenWrt with a control daemon written in Lua.  Slivers are
  implemented as light Linux containers.  We are working on safe node upgrade
  using kexec. *##*
- The GUI and REST API in servers are implemented as Django applications.
- The IPv6 overlay used for the management network is a tinc mesh VPN. *##*
- We use Git, Redmine, Jenkins and our Virtual CONFINE Tesbed (VCT) package
  for development and testing. *##*

* Collaborations
- CONFINE actively collaborates to the development of several Free software
  projects: the OpenWrt router distro, the BMX6 and OLSR mesh routing
  protocols, the DLEP protocol for collecting link characteristics, the NodeDB

Modified slides,lightning.txt from [9f954ade3b] to [2819b0bc48].


# Community-Lab as community infrastructure

- Extend CNs (with Community-Lab nodes and links)
- Community-Lab for hosting services
- [Clommunity](http://clommunity-project.eu/): community clouds

# Architecture and technologies

<!--- testbed architecture diagram --->
- Testbed
    - Nodes, servers, management network
    - Researchers, slices and slivers
    - Sliver connectivity: NAT, native L3, isolated L2
<!--- overlay CD and RD pictures --->
<!--- overlay logos on top of diagram --->
- Nodes: OpenWrt, Lua, LXC, kexec
- Servers: Django
- Management network: tinc
- Software development: Git, Redmine, Jenkins, VCT







# Collaborations

- [OpenWrt](https://openwrt.org/)
- [BMX6](http://bmx6.net/)
- [OLSR](http://olsr.org/)
- [DLEP](https://datatracker.ietf.org/doc/draft-ietf-manet-dlep/)








|
|
|
|
|
|
|
|
|
|
|
|
|
>
>
>
>
>
>


# Community-Lab as community infrastructure

- Extend CNs (with Community-Lab nodes and links)
- Community-Lab for hosting services
- [Clommunity](http://clommunity-project.eu/): community clouds

# Architecture and technologies (1/5)

![CONFINE testbed architecture](imgs/testbed.png)

# Architecture and technologies (2/5)

![CONFINE testbed architecture](imgs/testbed-cd-rd.png)

# Architecture and technologies (3/5)

![CONFINE testbed architecture](imgs/testbed-logos-node.png)

# Architecture and technologies (4/5)

![CONFINE testbed architecture](imgs/testbed-logos-mgmt.png)

# Architecture and technologies (5/5)

![CONFINE testbed architecture](imgs/testbed-logos-devel.png)

# Collaborations

- [OpenWrt](https://openwrt.org/)
- [BMX6](http://bmx6.net/)
- [OLSR](http://olsr.org/)
- [DLEP](https://datatracker.ietf.org/doc/draft-ietf-manet-dlep/)