tools/package/etc/
to directory
tools/package/etc/samples/
Also, removed some comments detailing the handling of the configuration
files.
Change-Id: I4e995cd2af3289b6dbbcbf2d3530628d2b197aba
1. Link Discovery can be turned off completely via configuration
2. PacketService allows applications to hint at table_type when registering for packets
Change-Id: I89f0bbf84dce1b449db5af19868f83503c44f750
(IPv6 Neighbor Discovery related flow mods).
The default configuration is false (disabled).
This fixes ONOS-1146
The configurable parameters are:
tools/package/etc/org.onosproject.provider.host.impl.HostLocationProvider.cfg
- Enable host removal on port/device down events.
(NOTE: not IPv6 related, added for completeness)
hostRemovalEnabled = true
- Enable using IPv6 Neighbor Discovery by the Host Location Provider.
ipv6NeighborDiscovery = false
tools/package/etc/org.onosproject.proxyarp.ProxyArp.cfg
- Enable IPv6 Neighbor Discovery.
ipv6NeighborDiscovery = false
NOTE: The above IPv6-related configuration has drawbacks,
partially because of some PacketService-related side effects.
Currently, we don't support enabling ipv6NeighborDiscovery
in one of the configuration files, and disabling it in another.
Enabling ipv6NeighborDiscovery in one configuration file is
practically equivalent to enabling it in both places.
Change-Id: Ief558697d85c8dcffc8941c575d0bf7d1397d90d
Made Jono's changes to ECM per Madan's suggesion.
Added cell beast.
Re-enabled anti-entropy.
Added ability to push bits through test proxy for faster upload.
Change-Id: I1455d6d443a697d7a3973c88cb81bfdac0e1dd7f
Additional configuration parameters that can be configured in the configuration file (org.onosproject.fwd.ReactiveForwarding.cfg),
that determine application behavior:
- packetOutOfppTable - application will use OFPP_TABLE port in PacketOut message, sending packet back to the OpenFlow pipeline, instead of using switch port
- flowTimeout - configuring reactively installed flow timeout
- flowPriority - configuring reactively installed flow priority
- matchDstMacOnly - reactively installed flows will match only destination MAC address - behavior as legacy L2 switches. This options overrides all other options below.
- matchVlanId - reactively installed flows will match default condition with additionally with VLAN ID field
- matchIpv4Address - reactively installed flows will match default conditions, plus IPv4 address and Protocol field
- matchIpv4Dscp - reactively installed flows will match default condition, IPv4 + with IPv4 DSCP and ECN fields (need matchIPv4Address enabled)
- matchIpv6Address - reactively installed flows will match default condition with IPv6 address and NextHeader field
- matchIpv6FlowLabel - reactively installed flows will match default condition with IPv6 address and IPv6 Flow Label (need matchIPv6Address enabled)
- matchTcpUdpPorts - reactively installed flows will match default condition with IPv4 or IPv6 address and TCP/UDP ports (need matchIPv4Address or matchIPv6Address enabled)
- matchIcmpFields - reactively installed flows will match default condition with IPv4 or IPv6 address and ICMP type and code fields (need matchIPv4Address or matchIPv6Address enabled)
Change-Id: Ieef67a1a12f6341d4de3b07e1226affec66d361a
Added a number of app.xml files for built-in apps.
Added ability to install & activate in one command.
Change-Id: I3fa5fa487ef76d9fe3da4d6dce8045d538cba423
The subsystem no longer returns futures for tracking completion of work.
Notifications are explicitely returned via a call back mechanism. Also, the
subsystem is now asynchronous.
Change-Id: I1a4cef931c24820f9ae9ed9a5398f163f05dfbc9
more flowservice improvements
Change-Id: I5c9c1b6be4b2ebfa523b64f6f52e7634b7d3e05f
more flowservice impl
Change-Id: I05f6774460effb53ced8c36844bcda2f8f6c096f
Manager to store functional (at least i believe it)
Change-Id: I09b04989bd1004c98fe0bafed4c76714b9155d53
flow subsystem functional: need to fix unit tests
Change-Id: I1667f25b91320f625a03e5e1d5e92823184d9de0
flow subsystem functional
Change-Id: I429b3335c16d4fc16f5d55f233dd37c4d1d6111d
finished refactor of flow subsystem
Change-Id: I1899abc6ff6a974a2018d936cc555049c70a6804
fix for null flow provider to use new api
Change-Id: If2fd9bd5baf74d9c61c5c8085cef8bc2d204cbdc
- Added configuration parameters for order of instances.
- got rid of 'flicker' flag since it's redundant.
Reference: ONOS-890
Change-Id: I0217e17f2a55d85e0a1fc8f2b3ea8cb54cb87517
- Number of devices per ONOS instance.
- Number of ports on the devices. This value is global.
The islands created by each instances' providers are joined together
in a chain (circle).
Reference : ONOS-860
Change-Id: I875ad1fbc1d4441869373c25de2ae5b62838e0d4
IPv6 netowrk is advertised.
IPv6 address is used for BGP peering.
Still using IPv4 address for ONOS peering.
*.json files are updated correspondingly.
Change-Id: I8fdac12d2d25b840dcadfb261667a9f98eb9f6be
currently chains null devices together in a linear topology.
The tunable parameters for this provider are:
- flicker = [default false] : flap the links by sending LinkEvents
- eventRate = [default 3000] : time between LinkEvents, in msec
Reference: ONOS-446
Change-Id: I865c1c43c3216d9b64d67bda7c118bb041d5b1c9
New script tutorial_ipv6.py is added.
o Switch OpenFlow version set to OpenFlow 1.3
o IPv6 forwarding is enabled
Change-Id: Ie6840f38f0d09d9afb5b5791d26f7af14c4785d6
If remote bits aren't found, it used to print:
cksum: /tmp/onos-1.1.0.jono.tar.gz: No such file or directory
which may give the impression the install failed.
Fixes ONOS-704.
Change-Id: Ic03f3e546abad1e4dcfb69f61b7766be63c016ef
Setting up bidirectional T-ports in OpticalPathProvisioner
Change-Id: I4e97b2eb53d3d4182aae9c98a227de982f492950
(cherry picked from commit d6843bed27c4b2b4e95984c99de3c54edcefc67f)
- Support for more T ports
- Addresses ONOS-440
Change-Id: Iafbe57b4797f272678696b8b2e46e5a6487e7428
(cherry picked from commit 6aba384469ce820c9e94f0f2991c4a84a691d4f8)
