This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 1411311 - [RFE] Integrate Tap as a Service (TaaS) into RHOSP
Summary: [RFE] Integrate Tap as a Service (TaaS) into RHOSP
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: OSP Team
QA Contact: Toni Freger
URL: https://launchpad.net/tap-as-a-service
Whiteboard:
: 1462796 1571884 1881890 (view as bug list)
Depends On: 1409964
Blocks: 1411434 1476900 epmosp17features, epmosp17rfe 1848015
TreeView+ depends on / blocked
 
Reported: 2017-01-09 12:35 UTC by Bertrand
Modified: 2025-04-20 04:25 UTC (History)
24 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-12-04 14:08:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-2354 0 None None None 2021-11-25 12:49:22 UTC
Red Hat Issue Tracker   OSPRH-5028 0 None None None 2024-12-04 14:07:59 UTC
Red Hat Knowledge Base (Solution) 7009211 0 None None None 2023-04-24 19:35:56 UTC

Internal Links: 1409964

Description Bertrand 2017-01-09 12:35:48 UTC 
Scope / Description:
Nokia would like to have the capability to mirror VM OVS traffic over VLAN to an external tool. An acceptable intermediate step would be to mirror VM OVS traffic to a destination VM over VXLAN. Information about the TaaS project can be found on Launchpad [1] and at the existing git repository[2]. Additional information can be found at [3],[4],[5],[6]

[1] Project Launchpad - https://launchpad.net/tap-as-a-service
[2] Project Git Repository - https://github.com/openstack/tap-as-a-service
[3] Weekly IRC Meeting - http://eavesdrop.openstack.org/ - Tap_as_a_Service_Meeting
[4] IRC - #openstack-neutron @freenode
[5] Tap-as-a-Service (TaaS) - https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/tap-as-a-service-taas-port-monitoring-for-neutron-networks
[6] Slideshare - http://www.slideshare.net/PLUMgrid/tapasaservice-what-you-need-to-know-now

Additional Info:
Partner: Nokia
Contact name: Yossi Boaron
Contact email: yossi.boaron

Red Hat EPM: Bertrand Rault
Contact Email: Brault
Comment 1 Nir Yechiel 2017-03-22 09:11:52 UTC 
Thanks for filing this request. Please note that this is not part of our immediate plans and is not scoped for RHOSP 11 or 12. Please keep this BZ up to date with more details on the use-case.

Thanks,
Nir
Comment 2 Nir Yechiel 2017-03-22 09:13:38 UTC 
Bertrand,

I'd like to use this RFE as a tracker to collect requirements for TaaS. Can you please check with the Nokia team if they are OK with making it a public BZ?

Thanks,
Nir
Comment 3 Bertrand 2017-06-05 07:57:13 UTC 
(In reply to Nir Yechiel from comment #2)
> Bertrand,
> 
> I'd like to use this RFE as a tracker to collect requirements for TaaS. Can
> you please check with the Nokia team if they are OK with making it a public
> BZ?
> 
> Thanks,
> Nir

Hello Nir,

Sorry for the late reply. Nokia is perfectly fine in having that BZ public.


Sincerely,

Bertrand
Comment 4 Nir Yechiel 2017-06-11 09:48:17 UTC 
(In reply to Bertrand from comment #3)
> (In reply to Nir Yechiel from comment #2)
> > Bertrand,
> > 
> > I'd like to use this RFE as a tracker to collect requirements for TaaS. Can
> > you please check with the Nokia team if they are OK with making it a public
> > BZ?
> > 
> > Thanks,
> > Nir
> 
> Hello Nir,
> 
> Sorry for the late reply. Nokia is perfectly fine in having that BZ public.
> 
> 
> Sincerely,
> 
> Bertrand

Thanks a lot. Any idea of an easy way to do it? It looks like I can't simply "clear" the partner field.

Thanks,
Nir
Comment 5 Bertrand 2017-07-09 16:18:45 UTC 
(In reply to Nir Yechiel from comment #4)
> (In reply to Bertrand from comment #3)
> > (In reply to Nir Yechiel from comment #2)
> > > Bertrand,
> > > 
> > > I'd like to use this RFE as a tracker to collect requirements for TaaS. Can
> > > you please check with the Nokia team if they are OK with making it a public
> > > BZ?
> > > 
> > > Thanks,
> > > Nir
> > 
> > Hello Nir,
> > 
> > Sorry for the late reply. Nokia is perfectly fine in having that BZ public.
> > 
> > 
> > Sincerely,
> > 
> > Bertrand
> 
> Thanks a lot. Any idea of an easy way to do it? It looks like I can't simply
> "clear" the partner field.
> 
> Thanks,
> Nir

Hi Nir,

This BZ is already public as far as I can tell as there is no group defined for it. That said I may be missing your point.
Sincerely,

Bertrand
Comment 6 Assaf Muller 2017-07-13 21:13:29 UTC 
*** Bug 1462796 has been marked as a duplicate of this bug. ***
Comment 7 David Peacock 2017-07-17 13:11:14 UTC 
As per Assaf's request on the duplicate 1462796, we have a new customer requiring this in Belgacom.

"I'd like to know if and when the Tap-as-a-Service project would be integrated in RedHat OSP. Feature is very important for insight inside the VNF running on our planned "Telco Cloud"."
Comment 18 Franck Baudin 2018-09-07 16:04:12 UTC 
*** Bug 1571884 has been marked as a duplicate of this bug. ***
Comment 21 Assaf Muller 2020-09-23 12:58:14 UTC 
*** Bug 1881890 has been marked as a duplicate of this bug. ***
Comment 27 Cristian Muresanu 2021-06-29 17:20:40 UTC 
Hi, there seems to be some interest on this. Any ETA ?
Thanks,
Cristian
Comment 28 Shravan Kumar Tiwari 2021-07-14 11:30:48 UTC 
Hi,

One of my customer is also looking TaaS as a feasible option to implement and to explore the possibilities "For the security probes (threat detection)".
Any ETA or input to know if this has some priority in our roadmap?

Thanks,
Shravan
Comment 39 Red Hat Bugzilla 2025-04-20 04:25:02 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.