We've just released faucet 1.7.6 which is a fairly incremental release over
1.7.5, however we're happy to note our continuing upward trend of test
coverage, we are hoping to hit the 90% mark shortly.
If you're upgrading to 1.7.6 from 1.6.x please read the release notes first:
Please review the faucet installation documentation for a list of the
different methods of installing faucet:
Highlights for this release include:
- Test coverage increase (83%)
- Docker test suite always uses Ubuntu 16.04
- Prioritize route gateways over host routes, for nexthop resolution.
I am currently in the process of using Faucet for one my use cases, which
requires both faucet's ACLs and to push reactive flows. In our use case the
reactive flows will be more frequent therefore we are integrating with NATS
which will listen to incoming messages and will transmit the messages
through the open flow channel.
There are two ways to implement this:
1) Implement a Unix socket listener in the faucet which will basically
listen to all incoming messages and will push it as a reactive flow to the
switch. Furthermore, we are intending to implement NATS as an adapter to
the faucet. – These changes need to be maintained in the faucet repo.
2) Create a separate Ryu application and pass it along with faucet’s
"--ryu-app" parameter, This app will listen to NATs messages and will use
Ryu app's dpset reference and will push the flow rules directly to the
switch. This way reactive flows will be handled through a separate
application. – This needs to be maintained by us.
Please let me know what will be the best way to carry forth?.