File: control

package info (click to toggle)
openoverlayrouter 1.3.0%2Bds1-4
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 4,552 kB
  • sloc: ansic: 42,180; sh: 272; makefile: 268; xml: 11
file content (33 lines) | stat: -rw-r--r-- 1,413 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
Source: openoverlayrouter
Maintainer: Debian IoT Maintainers <debian-iot-maintainers@alioth-lists.debian.net>
Uploaders: Thorsten Alteholz <debian@alteholz.de>
Section: misc
Priority: optional
Build-Depends: debhelper-compat (=13)
	, dh-exec (>=0.2)
	, libzmq3-dev
	, libconfuse-dev
	, libcap2-bin
	, gengetopt
	, libxml2-dev
	, dh-sequence-movetousr
Standards-Version: 4.7.0
Homepage: http://openoverlayrouter.org/
Vcs-Browser: https://salsa.debian.org/debian-iot-team/oor
Vcs-Git: https://salsa.debian.org/debian-iot-team/oor.git
Rules-Requires-Root: no

Package: openoverlayrouter
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}
Description: deploy programmable overlay networks
 The OpenOverlayRouter (OOR) project aims to deliver a flexible and modular
 open-source implementation to deploy programmable overlay networks. It
 leverages on encapsulating overlay-specific packets into underlay-compatible
 packets at the edges of the instantiated overlay and route them over the
 physical underlying infrastructure. In order to do so, it maps overlay
 identifiers to underlay locators and keeps those mappings updated over
 time. In the current version, OOR uses the LISP protocol for the
 control-plane (e.g. mapping retrieval and updating, etc), NETCONF/YANG for
 the management-plane (e.g. overlay identifiers provisioning, etc) and can
 use both LISP and VXLAN-GPE headers for encapsulation.