-
Notifications
You must be signed in to change notification settings - Fork 712
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
Probe plugins should be able to add controls. #1022
Comments
I plan on doing this as part of #554. Maybe get a chance next week. |
@alban @tomwilkie okay BUT Can you please call the "bad network" mode "comcast"? |
We've added plugins in 0.14, but they don't have the ability to respond to control requests yet. We're probably not going to add it in 0.15 unless the feedback on plugins is very strong. But its a candidate for 0.16. |
This isn't something I am in a desperate hurry for, but I do want to say On Tue, Apr 19, 2016, 22:19 Tom Wilkie [email protected] wrote:
|
/cc @alepuccetti |
In the traffic control plugin, we add controls from the plugin into the container details view. |
Yes, but it's closed by #1837 |
I would like to have control plugins in Weave Scope so users could do more actions on containers from the Scope UI. See also #554 for similar ideas on probe plugins.
My use case is to simulate bad network in containers with the netem queuing discipline. I would like users to be able to configure latency, bandwidth, percentage packet drop on egress and ingress for each connection. The Scope UI would take care of sending the commands to the right node and the actual work of configuring the traffic control rules could be delegated to a control plugin.
I started to write a daemon that receives commands on D-Bus to configure the traffic control rules:
https://github.com/kinvolk/tcd
A traffic control plugin for Scope could either send the D-Bus commands to tcd, or just include the golang code to do the job.
The text was updated successfully, but these errors were encountered: