-
Notifications
You must be signed in to change notification settings - Fork 51
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
Expose enqueue action action to NetKAT layer #481
Comments
I think I would do the following:
The plugin architecture is still being baked, but you could be an early -N On Tue, Mar 29, 2016 at 4:45 PM, Shrutarshi Basu notifications@github.com
|
@jnfoster I've just noticed the commit 5e1fe76 by @craig-riecke and I was wondering if the situation changed. Is the Enqueue action still not exposed? In case it is still not exposed, could you point to an example backend plugin in order to aid the implementation of the approach suggested by @jnfoster. |
Hi Luca, Yes! Here is the OF 1.0 plugin: I am on sabbatical as of next week so I can also have a go at this... -N |
Hi Nate, thanks for the reply! I am not really fluent in OCaml, so if you'll implement this feature I will return the favor by issuing a pull request integrating enqueue actions in pyretic. Thanks again, |
Hi Nate, any update on this? Thanks a lot, |
Sorry not yet. |
@basus did you find any way to implement that? |
I haven't used the queues for a while and I'm not sure what the state of the plugin architecture is. However, it looks like the OpenFlow backend does support |
I've been trying to port the Merlin codebase to use the current Frenetic code. Merlin makes use of the queues extensively. There seems to OpenFlow-level support for queues in the codebase, but this isn't presented to the NetKAT layer. One way would be to extend the NetKAT
location
type with aQueue of queueId * portId
constructor and then push that down through the compiler.I can make the required changes to a branch, unless someone has a better way of going about it.
The text was updated successfully, but these errors were encountered: