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

Placement of VNF in lower level Service Platform #1

Open
DarioValocchi opened this issue Jul 12, 2017 · 2 comments
Open

Placement of VNF in lower level Service Platform #1

DarioValocchi opened this issue Jul 12, 2017 · 2 comments

Comments

@DarioValocchi
Copy link

How does the Lower SP places the VNFs? Does the placement SSM get deployed in Sp-Red as well?

@DarioValocchi
Copy link
Author

More precisely, placement is an open issue more in general. We need:

  • A SP placement plugin, or better an SSM, that deployes one VNF in the first PoP and a second VNF in the lower level SP.
  • Maybe it's enough to have the a default placement plugin on the lower level SP (it will have just one PoP)

@tsoenen @mpeuster @hadik3r

@PhilipEardley
Copy link

I think that:

  • the upper SP's placement function (*) decides that (let's assume the NS involves VNF-1 & VNF-2) it is not best placed to implement VNF-2 (either it can't do it, or it knows it's better to do it in the remote PoP)
  • the lower SP's placement function decides where to place VNF-2
    (*) placement function or SSM - where the different functionality lies is a bit fuzzy to me
    In the Pilot, we can do whatever's easiest. For instance, the placement functions could have a built-in decision (default option), so effectively not have to decide each time.

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

No branches or pull requests

2 participants