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

Open google doc issue 25: RSpec routing and aggregation #34

Open
wvdemeer opened this issue May 15, 2014 · 0 comments
Open

Open google doc issue 25: RSpec routing and aggregation #34

wvdemeer opened this issue May 15, 2014 · 0 comments

Comments

@wvdemeer
Copy link

Below is a literal copy of google doc issue 25:

  1. RSpec routing and aggregation -- proposal on github, just a slight impact on RSpec ?

Jordan: The current document specifies that an AM can be a proxy to several AMs. This was refered to a Slice Manager (SM) component in the OpenSFA architecture. This poses several issues that we might then need to solve : the proxy AM has to know the different RSpecs, to translate them or aggregate them (potentially losing some information, having incompatibilities, etc.). Also, how to route properly a request RSpec to the origin AMs, without loops, splitting it, translating it, etc should then be documented.
Note: AM of AMs if proposed in GENI but to the best of our knowledge has not been implemented.

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

1 participant