[DONE]
- Restructured to activate or deactivate switching and routing app separately
- Fixed to add or remove host when port is detected or vanished
- Use openstack node service to get integration bridges and data IP
[TODO]
- Remove use of OpenstackPortInfo
- Support installing flow rules for exising VMs
- Call security group update method when port update triggered from OpenStack
Change-Id: Ic0b2ac3f7ab07f0e20c97c6edfdd1928b9767baf
- Shut down openflow meta app before driver test,
was causing port collision issues with openflow server
- Fixed NPE in Network config store
- reordered tests to insure proper sequencing
Change-Id: Ib39330153f543ee960b8631a0dc9246ee4251851
This should fix the problem seen in VirtualBox where you
may have some random interface which is host-only which needs
to have port forwarding set up on it.
Change-Id: Iacdbb129d52529783bdab1c3d768131f6eaf0364
Most notably:
- Added support for onos.py's ONOSCluster controller (it works with
"mn --custom onos.py,bmv2.py --switch onosbmv2 ...")
- Randomly select an open port for the Thrift RPC server
Change-Id: Ifa974741dc4a3693777f01866b1f6203d0e7e75e
1. Supprot handle upper case DELETE and fixed DELETE funcion
2. Fixed `POST` can not work if JSON format is correct
Change-Id: I762cb73ce73a42393264dcace1beaf5cf53492f7
Madan suggested that this might help vs. the pipelined
startup we were doing before, so let's try it.
We will unpack/install all nodes before we start up,
so that we can start the whole cluster at about the same
instant.
Note that this is probably closer to what we'd see in hardware.
The disadvantage is that we don't get a "clean" environment
with each invocation of start().
Change-Id: I0a45984f50e1ef25a7d8a836e46978fdbdff0bd0
We were using eth0 by default before, but this doesn't work if
your default interface isn't eth0.
Fixes port forwarding on Ubuntu 16.04.
Change-Id: I55baed7fd8952a9f6cab364e20e31a0632ddda6d
- optionally specify expected number of intents in "onos-check-intent"
Change-Id: I523a7fd9e1aaa72b441d2428fb9ebb692b07bdd0
- bidrectional vnet link creation (when using ssh)
- optionally specify expected number of intents in "onos-check-intent"
Change-Id: I5c6fe1f269eddeaa70dfec819853d42af59fbd8e
The arp CLI command sends gratuitous ARPs from all hosts - this
makes it easier for ONOS to discover hosts.
Previously checkLog returned None, None if the log file didn't
exist; now we return an empty list, to avoid breaking when we
take the len() of errors or warnings (which was happening before)
and to avoid having to check for None, None, which didn't seem to
add a lot of value to justify its complexity.
Change-Id: I84847fcf70525c82ac037d8a84cf40d21ab2a106
We check for:
- process exits
- log ERRORs
- log WARNings
- low memory
Also added a "status" CLI command to check for exits
and errors.
Change-Id: I6e65fe49619e338f1827fc616ca52a82de7ba470
This doesn't seem quite right, because it doesn't match
a supposedly legal use case where you omit the output file
and list the node IP addresses. However, it's better than
what we have now, which simply ignores the output file name.
Intended to help with ONOS-4667
Change-Id: Ib46195e7b829bc4d304c4dd51138b73acd4f1501
We really don't need the OCx variables, but for now at
least we are unsetting the ones that are incorrect and
calling onos-gen-partitions with the explicit IP
addresses.
Change-Id: I8bd3d69bee4857e00070288b586255455c9c8adf