- 09 Mar, 2016 13 commits
-
-
By making all flow rule installation triggered by HOST event. Also removed unnecessary host annotation. Change-Id: Ib6d230f2fbbac4ad7d66628d7465e69450ef1a26
Hyunsun Moon authored -
- now implements proper resizing and scrolling. Change-Id: Ideabb86ed3db44ed1827de15e49216d107053189
Simon Hunt authored -
- OVSDB client has changed to update br-int even if there's br-int already in device - So OpenstackNode modified only the leader node to performs node bootstrap Change-Id: Ie01843ca8ab36ec61b58e80ce20c0c8c31ff8273
Daniel Park authored -
Might be useful to refresh data plane with most recent status of Neutron and VMs by flushing all existing rules and pushing network config again And also removed read configuration during activation since leadership service does not work as expected during app activation Change-Id: Ia22fe02d25a61126f3e6df59fc5ad4d065f89f18
Hyunsun Moon authored
- 08 Mar, 2016 27 commits
-
-
- Implements floatingIp REST interfaces & event handler - Implements rulePopulate method for floatingIp handler - Fixes minor logics - Changes app structure - exports configuration - Implements case issue. when openstack deletes vm w/o deassociating floatingIp, openstack doesn`t send floatingIp deassociation event. Change-Id: If4d8ac3fecfed1957d84139f94ae31f593a9097b
Kyuhwi Choi authored -
… agr string for revision fix Change-Id: Id9d596512f35b54f6359d361402bcd0180b71678
Vidyashree Rama authored -
- Remove ONOS keyword from application title - Capitalize each keyword in application title - Make it consistent to use App, Provider and Driver in application title - Add right category name for each application - Add missing application title and category - Make application category comment more descriptive Change-Id: Ib886b4a4293c38bd546a4107b20569f1bd7031a7
Jian Li authored -
- Update br-int rather than do nothing if it already exists - Make only the leader performs node bootstrap - Check mastership on HOST event not flow rule populator - Install/uninstall flow rules for vSG always from master, or the rules stay in PENDING_ADDED state Change-Id: I4bd5cf6f84bf36f2617288b2d843435819c76ba8
Hyunsun Moon authored -
…, but for two different subject classes are encountered. Change-Id: I4de7f6e22bdf038dff91630f4cf576d9c38e9807
Thomas Vachuska authored -
And update existing node if newly added node has the same hostname with existing node. Change-Id: Ifebbf4129df4f742e16b9a25be619dd90e0745ff
Hyunsun Moon authored -
- Implement Openstack FloatingIP REST call json parser Change-Id: I6123bc13eea00a973bdec3ff5503949b25ebceca
musonous authored -
Edge case fix in group store where extraneous group buckets are updated so the group can be reused Bug fix for broadcast group in OF-DPA as there can only be one l2flood group per vlan Group operation failure codes are now reported by the provider to the core Group ids are displayed in hex in a couple of places Change-Id: Ib48d21aa96e0400b77999a1b45839c28f678e524Saurav Das authored -
- Process Icmp packet sent from Host to external network for OpenstackGateway Node - Process Arp packet sent from physical router to gateway Change-Id: Ifcde71a9ca10180682811c9e1bcf58f991b36443
Daniel Park authored -
1. Invoke karaf script in all cases (upstart, initd/systemd) This means that onos-service now blocks, which means we need to change onos.initd to run it in the background. Otherwise, we could use karaf/bin/start This should fix ONOS-4117 2. Use service onos {start/status/etc.} for upstart/init/systemd onos-install should not invoke the new init.d script directly; instead it should use service onos {cmd, which should work if service is available on upstart, init.d, and systemd-based distributions. This should fix ONOS-4124 3. In onos.initd, check if ONOS is running. This makes it easier to see what is going on, and it also avoids attempting to start ONOS if it's already running. Change-Id: I0152fd7fdcb079b25531442315d0bd69e6c7653dBob Lantz authored
