)]}'
{
  "log": [
    {
      "commit": "b8ae330cd3c65808044d344b24f0917b312c4fb9",
      "tree": "092dd842454bb360f81a38ecfa5b283c5d173427",
      "parents": [
        "ef20ef7de9fe52931e7a5ce07b8228e87f7f52b6"
      ],
      "author": {
        "name": "Avneesh Sachdev",
        "email": "avneesh@sproute.com",
        "time": "Thu Jul 14 09:59:30 2016 -0700"
      },
      "committer": {
        "name": "Paul Jakma",
        "email": "paul.jakma@hpe.com",
        "time": "Tue Sep 13 10:36:42 2016 +0100"
      },
      "message": "Use only the ISC license for .proto files.\n\nSimplify licensing for protobuf files based on discussion on the\nquagga-dev mailing list.\n\nPreviously, users could choose between the GPL and the ISC license.\n\nSigned-off-by: Avneesh Sachdev \u003cavneesh@sproute.com\u003e\nSigned-off-by: Avneesh Sachdev \u003cavneesh@sproute.com\u003e\n"
    },
    {
      "commit": "ef20ef7de9fe52931e7a5ce07b8228e87f7f52b6",
      "tree": "b9aabfbf06546079bcddee105fd8be7e3fadc6f6",
      "parents": [
        "b2624487659d8148ca253147fd7e63560a439c8b"
      ],
      "author": {
        "name": "Avneesh Sachdev",
        "email": "avneesh@sproute.com",
        "time": "Mon Apr 04 10:54:57 2016 -0700"
      },
      "committer": {
        "name": "Paul Jakma",
        "email": "paul.jakma@hpe.com",
        "time": "Tue Sep 13 10:36:42 2016 +0100"
      },
      "message": "fpm: Add protobuf support for FPM.\n\nCode that allows a client to convey routes to a Forwarding Plane\nManager component using protobuf instead of netlink..\n\n  * fpm/fpm.proto\n\n    Protobuf definitions pertaining to the Forwarding Plane Manager.\n    In particular, this file defines the AddRoute and DeleteRoute\n    messages.\n\n  * fpm/fpm.h\n\n    Tweak FPM message header definition to also allow messages to be\n    encoded in protobuf format.\n\n  * fpm/{fpm_pb.h,.gitignore,.Makefile.am}\n\n    Add the fpm_pb library, which contains code for interfacing with\n    the FPM using protobuf.\n\n  * configure.ac\n\n    Generate fpm/Makefile.\n\n  * Makefile.am\n\n    Add fpm subdirectory to build.\n\n  * common.am\n\n    Add flags to be used by clients of the fpm_pb library.\n\nSigned-off-by: Avneesh Sachdev \u003cavneesh@sproute.com\u003e\n"
    },
    {
      "commit": "d869dbd03b4d75d512552d07ed8fbe0807272a9c",
      "tree": "2ade0de7288c4dd3fc68232708346881fd1a59fa",
      "parents": [
        "9da9a61e2f8afb61aa31c17fb810169290bf96ee"
      ],
      "author": {
        "name": "Udaya Shankara KS",
        "email": "shankara.k.s.u@gmail.com",
        "time": "Thu Feb 11 21:42:29 2016 +0530"
      },
      "committer": {
        "name": "Paul Jakma",
        "email": "paul@quagga.net",
        "time": "Wed Jul 20 12:58:32 2016 +0100"
      },
      "message": "zebra: Enable fpm module to connect to remote fpm server\n\nFPM aims to provide cross platform mechanism to support the scenario\nwhere the router has forwarding path distinct fromt the kernel.Commonly\nHardware based fast path.Hence it is non-configurable paramter.This\nlimits us to use funcationality to update FIB information to remote\nhosts, like SDN controller.\n\nThis implementation provides the CLI to configure remote hosts and port\ninformation of remote fpm controller.Otherwise default fpm server will\nbe localhost and default fpm port will be well know port 2620.\n\n* zebra_fpm.c: added fpm_server paramter to zfpm_global_t handler.\n    Implemented CLI for configuring the fpm server and no fpm\n    command to revert back to default configuration.\n\n* zserv.c: Install zebra node to write fpm configuration info\n   on console/config file.\n\nFurther documentation supplied:\n-------------------------------\n\n               ZEBRA : CLI CONFIGURATION FOR FPM MODULE\n         \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\n1. INTRODUCTION\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n   1.1 scope\n\n     This memo discusses the configuration option for zebra to update\n     FIB information to local and remote modules.\n     This will also helps to address the issue associated with CORD project.\n     https://jira.onosproject.org/browse/CORD-411\n\n2. REFERENCE\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n  Quagga version 99.24+ ( main branch committed on 29-sep-2015)\n\n3. PROBLEM DESCRIPTION\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\n    Once FPM is enabled, Quagga periodically tries to initiate fpm\nconnection to localhost:2620.  These values are non configurable in\nexisting implementation.  There is no CLI available to configure\n\"host:port\".  hence limits us to use it for hardware based fast path\nmodules only.\n\n4. PROPOSED CHANGES\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nFollowing changes are done to the quagga code\n   a) Added new CLI to configure \"host address : port\".\n      The CLI format\n      \u003cconf t\u003e\n           $ fpm connection ip \u003cipv4 address\u003e port \u003ctcp port num\u003e\n\n      and no fpm command to revert back to default\n      \u003cconf t\u003e\n           $ no fpm connection ip \u003cipv4 address\u003e port \u003ctcp port num\u003e\n\n   b) Allowed values are ipv4 address and tcp port range \u003c1-65535\u003e\n\n   c) FPM initialization code has been enhanced to pick the \"host\n      address : port\" values from zebra.conf.  if not found then\n      default values as localhost:2620 will be used.  and updated the\n      information on to config file on write config command\n\n5. FILES MODIFIED\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n  1) fpm/fpm.h :\n     a) Added MACRO to represent network order loopback ip\n\n  2) zebra/zebra_fpm.h :\n\n     a) introduced fpm_server variable in zfpm_glob_t handler to hold\n        the remote fpm server address\n\n     b) Hooked \u0027fpm_remote_ip_cmd\u0027 and \u0027no_fpm_remote_ip_cmd\u0027 at CONFIG\n        node to configure remote fpm detail and to revert back to\n        default respectively\n\n  3) zebra/zserv.c :\n     a) Hooked \u0027config_write_fpm\u0027 callback function, at ZEBRA_NODE to\n        display the fpm connection details on console on entering\n        command\n\n         $ show running_config\n        and to write to configuration file on entering command\n         $ write config\n\n6. TESTING DETAILS\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\n   6.1. default behavior\n\n          In default configuration FPM will attempt to connect to\n          localhost:2620\n\n   6.2. update fpm info\n        a) Using CLI command user can configure fpm host:port details\n           and can be able to write to config file(zebra.conf) using\n           write config command.  this parameters has no\n           dependency/impact on other parameters of config file\n\n        b) show running-config/write config will display the fpm\n           information if configured.  and will not display any\n           information related to fpm for default configuration\n\n        c) these configured information will be stored to config file.\n           only on write config command.\n\n   6.3 loading from config file\n        a) zebra attempts to connect to fpm server if fpm parameter\n           found in config file.else connects to default parameters.\n\n        b) if fpm connection drops, fpm will periodically attempts to\n           connect to remote server.\n\n        c) if fpm connections already established. then newly\n           configured fpm parameters will not disconnect the existing\n           connection.  new connection to the different fpm server will\n           happen only after existing connection closes by either of\n           the end.\n"
    },
    {
      "commit": "443b993777e3e86fceb988f647d1c5b57661a182",
      "tree": "49e929ef6339feea5bd8b634381f753dd71fa79a",
      "parents": [
        "04f7dd64dfa0f339208f0d4833276b7684ee3343"
      ],
      "author": {
        "name": "Avneesh Sachdev",
        "email": "avneesh@opensourcerouting.org",
        "time": "Tue Nov 13 22:48:58 2012 +0000"
      },
      "committer": {
        "name": "David Lamparter",
        "email": "equinox@opensourcerouting.org",
        "time": "Fri Nov 30 21:41:17 2012 +0100"
      },
      "message": "fpm: Add public header for Forwarding Plane Manager\n\nThe Forwarding Plane Manager (FPM) is an optional component that may\nbe used in scenarios where the router has a forwarding path that is\ndistinct from the kernel, commonly a hardware-based fast path. It is\nresponsible for programming forwarding information (such as routes and\nnexthops) in the fast path.\n\nIn Quagga, the Routing Information Base is maintained in the \u0027zebra\u0027\ninfrastructure daemon. Routing protocols communicate their best routes\nto zebra, and zebra computes the best route across protocols for each\nprefix. This latter information comprises the bulk of the Forwarding\nInformation Base.\n\nThe new header file added by this patch, \u0027fpm/fpm.h\u0027, defines a\npoint-to-point interface using which zebra can update the FPM about\nchanges in routes. The communication takes place over a stream\nsocket. The FPM listens on a well-known TCP port, and zebra initiates\nthe connection.\n\nAll messages sent over the connection start with a short \u0027FPM header\u0027.\nIn the case of route add/delete messages, the header is followed by a\nnetlink message. Zebra should send a complete copy of the forwarding\ntable(s) to the FPM, including routes that it may have picked up from\nthe kernel.\n\nThe FPM interface uses replace semantics. That is, if a \u0027route add\u0027\nmessage for a prefix is followed by another \u0027route add\u0027 message, the\ninformation in the second message is complete by itself, and replaces\nthe information sent in the first message.\n\nIf the connection to the FPM goes down for some reason, the client\n(zebra) should send the FPM a complete copy of the forwarding table(s)\nwhen it reconnects.\n\nSigned-off-by: Avneesh Sachdev \u003cavneesh@opensourcerouting.org\u003e\nSigned-off-by: David Lamparter \u003cequinox@opensourcerouting.org\u003e\n"
    }
  ]
}