Gitiles
Code Review Sign In
gerrit.onosproject.org / onos / e48f73b2a0431e2a72a4ed32c037763e76aff32c
commite48f73b2a0431e2a72a4ed32c037763e76aff32c[log] [tgz]
authorEsin Karaman <esin.karaman@netsia.com>Tue Mar 05 13:49:02 2019 +0000
committerPier Luigi Ventre <pier@opennetworking.org>Wed Jun 19 16:35:20 2019 +0000
tree7d9713bd5834beed7b050f0b2166b6af6ea9281a
parent8484ad15cb0e9c19257a592de6ab65e50fa9c494 [diff]
ONOS-7944 McastHandler of SegmentRouting considers only dual-homed sinks,
not the sinks that are not tied with any host.

However, one of addSinks method of MulticastRouteService of mcast
application allows adding connect points each of which is a standalone
sink. In a scenario where all connect points are used as different sinks,
processSinksToBeAdded method in McastHandler service does not return
a true list of sinks to be added;

In overall,all connect points which are associated with HostId.NONE must
be added as different sinks. In the current situation, just one of them
is selected and added.

Change-Id: I3d4eb1ff865aca4f2fe85011a6a390374028a081
(cherry picked from commit d222b5cd3d2e9f53fbf9810c565f9b82739d0154)
1 file changed
tree: 7d9713bd5834beed7b050f0b2166b6af6ea9281a
  1. .buckconfig
  2. .dockerignore
  3. .gitignore
  4. .gitreview
  5. BUCK
  6. Dockerfile
  7. Jenkinsfile
  8. LICENSE.txt
  9. README.md
  10. apps/
  11. buck-tools/
  12. bucklets/
  13. cli/
  14. core/
  15. docs/
  16. drivers/
  17. features/
  18. incubator/
  19. lib/
  20. models/
  21. modules.bzl
  22. modules.defs
  23. onos.defs
  24. pipelines/
  25. pom.xml
  26. protocols/
  27. providers/
  28. tools/
  29. utils/
  30. web/
README.md

ONOS : Open Network Operating System

What is ONOS?

ONOS is a new SDN network operating system designed for high availability, performance, scale-out.

Top-Level Features

  • High availability through clustering and distributed state management.
  • Scalability through clustering and sharding of network device control.
  • Performance that is good for a first release, and which has an architecture that will continue to support improvements.
  • Northbound abstractions for a global network view, network graph, and application intents.
  • Pluggable southbound for support of OpenFlow and new or legacy protocols.
  • Graphical user interface to view multi-layer topologies and inspect elements of the topology.
  • REST API for access to Northbound abstractions as well as CLI commands.
  • CLI for debugging.
  • Support for both proactive and reactive flow setup.
  • SDN-IP application to support interworking with traditional IP networks controlled by distributed routing protocols such as BGP.
  • IP-Optical use case demonstration.

Checkout our website and our tools