752fb029fa
In the current implementation, when the TaaS API (tap-service, tap-flow) call completes, the status of result is returned. [1] In order to adopt an asynchronous model, the 'status' field is needed in the API. The following code adds the status field in the API. In the first step, the status is set to 'ACTIVE' by default. [1]: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html Depends-On: Ie6b3811e41a94721679c9178cdd5119bdad8208d Change-Id: Ib8e4ad15e5b4272ac7f8800f72d7f2c003db798e
Tap as a Service
Tap-as-a-Service (TaaS) is an extension to the OpenStack network service (Neutron). It provides remote port mirroring capability for tenant virtual networks.
Port mirroring involves sending a copy of packets entering and/or leaving one port to another port, which is usually different from the original destinations of the packets being mirrored.
This service has been primarily designed to help tenants (or the cloud administrator) debug complex virtual networks and gain visibility into their VMs, by monitoring the network traffic associated with them. TaaS honors tenant boundaries and its mirror sessions are capable of spanning across multiple compute and network nodes. It serves as an essential infrastructure component that can be utilized for supplying data to a variety of network analytics and security applications (e.g. IDS).
- Free software: Apache license
- API Reference: https://github.com/openstack/tap-as-a-service/blob/master/API_REFERENCE.rst
- Source: https://git.openstack.org/cgit/openstack/tap-as-a-service
- Bugs: https://bugs.launchpad.net/tap-as-a-service
For installing Tap-as-a-Service with Devstack please read the INSTALL.rst file