Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RA-1 RA-2] Chaining of multiple VNFs #1019

Closed
sukhdevkapur opened this issue Feb 2, 2020 · 6 comments
Closed

[RA-1 RA-2] Chaining of multiple VNFs #1019

sukhdevkapur opened this issue Feb 2, 2020 · 6 comments
Labels
Projects

Comments

@sukhdevkapur
Copy link
Collaborator

During Prague meeting, we discussed the following:

  1. OpenStack SFC API is not actively supported and may not be deployable
  2. Shall we beef up work in the OpenStack Community to address this APIs?
  3. Most of the SDNs solve this and most of the operators used SDN based solutions - so, do nothing and used SDN and make SDN a part of RA1 and RA2
  4. Work with OpenStack community to adopt SDN apis as neutron extension - this was considered preferred solution. Perhaps we should discuss this in the CNTT TSC

This issue applies to RA2 as well. However, NSM (Network Service Mesh) could address this in RA2. Should we consider including NSM in RA2? - Again a discussion that needs to be taken to the CNTT TSC

@sukhdevkapur sukhdevkapur added this to the Backlog milestone Feb 2, 2020
@fkautz
Copy link
Collaborator

fkautz commented Feb 2, 2020

I'm happy to help advise to work out if NSM is a good fit and subsequent design decisions if such a thing is desired.

@tomkivlin
Copy link
Collaborator

Comments from RA2 meeting 6th Feb 2020:
@ASawwaf @fkautz both made the point that NSM and service chaining needs collaboration between the workstreams. As per original comment, handle in TSC as part of wider SDN/Programmable Fabric discussions (#960, #1037). All further discussions are part of RM Core WS.

@rabi-abdel rabi-abdel added this to To do in RA1 via automation Feb 6, 2020
@rabi-abdel rabi-abdel added RA 1 and removed RA 1 Dev labels Feb 6, 2020
@rabi-abdel rabi-abdel added this to To do in old-RA2 via automation Feb 6, 2020
@rabi-abdel rabi-abdel added RA 2 and removed RA 2 Dev labels Feb 6, 2020
@rabiabdel rabiabdel changed the title Chaining of multiple VNFs [RA-1 RA-2] Chaining of multiple VNFs Feb 11, 2020
@pgoyal01 pgoyal01 added the Archive Archive Item label Feb 11, 2020
@project-bot project-bot bot moved this from To do to Archive in RA1 Feb 11, 2020
@project-bot project-bot bot moved this from To do to Archive in old-RA2 Feb 11, 2020
@pgoyal01 pgoyal01 removed the Archive Archive Item label Feb 11, 2020
@rabi-abdel rabi-abdel removed this from the Backlog milestone Feb 11, 2020
@rabi-abdel rabi-abdel added this to the M3 (Freeze Contributions) milestone Feb 25, 2020
@project-bot project-bot bot moved this from Archive to Backlog in RA1 Apr 30, 2020
@sukhdevkapur
Copy link
Collaborator Author

We will be discussing and addressing this in the Networking Focus Group. Based upon the outcome of decision, this issue will addressed appropriately.

@pgoyal01 pgoyal01 added Baraque and removed Backlog labels May 11, 2020
@pgoyal01 pgoyal01 moved this from Backlog to To do in RA1 May 11, 2020
@rabi-abdel rabi-abdel removed this from the M3 (Freeze Contributions) milestone May 15, 2020
@project-bot project-bot bot moved this from To do to Backlog in RA1 May 15, 2020
@pgoyal01
Copy link
Collaborator

Closing #1080 as a duplicate of this issue.

@pgoyal01
Copy link
Collaborator

As moved to RM, closing this issue as per Metering of July 27, 2020.

RA1 automation moved this from Backlog to Done Jul 27, 2020
@ulikleber
Copy link
Collaborator

Do we have an issue number in RM, that is used to follow up?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
RA1
  
Done
Development

No branches or pull requests

6 participants