-
Notifications
You must be signed in to change notification settings - Fork 20
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
client auth requests to api should use pooled request workers #51
Labels
🐞 type/bug
Something isn't working
Comments
wrboyce
added a commit
that referenced
this issue
Apr 17, 2019
* start all services and workers from a unified `open-balena-vpn` systemd service and master process * register as a single service instance in master process and make available to workers * prevent forwarding tunnel requests via proxy workers on the same instance * use pooled request workers for client authentication via api * switch to `eventemitter3` in openvpn management class * update node-tunnel from 2.1.2 to 3.0.0 Connects-to: #47 Connects-to: #48 Connects-to: #49 Connects-to: #50 Connects-to: #51 Change-type: major Signed-off-by: Will Boyce <will@balena.io>
wrboyce
added a commit
that referenced
this issue
Apr 17, 2019
* start all services and workers from a unified `open-balena-vpn` systemd service and master process * register as a single service instance in master process and make available to workers * prevent forwarding tunnel requests via proxy workers on the same instance * use pooled request workers for client authentication via api * switch to `eventemitter3` in openvpn management class * update node-tunnel from 2.1.2 to 3.0.0 Connects-to: #47 Connects-to: #48 Connects-to: #49 Connects-to: #50 Connects-to: #51 Change-type: major Signed-off-by: Will Boyce <will@balena.io>
wrboyce
added a commit
that referenced
this issue
Apr 17, 2019
* start all services and workers from a unified `open-balena-vpn` systemd service and master process * register as a single service instance in master process and make available to workers * prevent forwarding tunnel requests via proxy workers on the same instance * use pooled request workers for client authentication via api * switch to `eventemitter3` in openvpn management class * update node-tunnel from 2.1.2 to 3.0.0 Connects-to: #47 Connects-to: #48 Connects-to: #49 Connects-to: #50 Connects-to: #51 Change-type: major Signed-off-by: Will Boyce <will@balena.io>
wrboyce
added a commit
that referenced
this issue
Apr 17, 2019
* start all services and workers from a unified `open-balena-vpn` systemd service and master process * register as a single service instance in master process and make available to workers * prevent forwarding tunnel requests via proxy workers on the same instance * use pooled request workers for client authentication via api * switch to `eventemitter3` in openvpn management class * Update node-tunnel from 2.1.2 to 3.0.0 * Update pinejs-client-request from 5.1.0 to 6.0.0 Connects-to: #47 Connects-to: #48 Connects-to: #49 Connects-to: #50 Connects-to: #51 Change-type: major Signed-off-by: Will Boyce <will@balena.io>
wrboyce
added a commit
that referenced
this issue
Apr 17, 2019
* start all services and workers from a unified `open-balena-vpn` systemd service and master process * register as a single service instance in master process and make available to workers * prevent forwarding tunnel requests via proxy workers on the same instance * use pooled request workers for client authentication via api * switch to `eventemitter3` in openvpn management class Connects-to: #47 Connects-to: #48 Connects-to: #49 Connects-to: #50 Connects-to: #51 Change-type: major Signed-off-by: Will Boyce <will@balena.io>
wrboyce
added a commit
that referenced
this issue
Apr 17, 2019
* start all services and workers from a unified `open-balena-vpn` systemd service and master process * register as a single service instance in master process and make available to workers * prevent forwarding tunnel requests via proxy workers on the same instance * use pooled request workers for client authentication via api * switch to `eventemitter3` in openvpn management class Connects-to: #47 Connects-to: #48 Connects-to: #49 Connects-to: #50 Connects-to: #51 Change-type: major Signed-off-by: Will Boyce <will@balena.io>
wrboyce
added a commit
that referenced
this issue
Apr 17, 2019
* start all services and workers from a unified `open-balena-vpn` systemd service and master process * register as a single service instance in master process and make available to workers * prevent forwarding tunnel requests via proxy workers on the same instance * use pooled request workers for client authentication via api * switch to `eventemitter3` in openvpn management class Connects-to: #47 Connects-to: #48 Connects-to: #49 Connects-to: #50 Connects-to: #51 Change-type: major Signed-off-by: Will Boyce <will@balena.io>
wrboyce
added a commit
that referenced
this issue
Apr 17, 2019
* start all services and workers from a unified `open-balena-vpn` systemd service and master process * register as a single service instance in master process and make available to workers * prevent forwarding tunnel requests via proxy workers on the same instance * use pooled request workers for client authentication via api * switch to `eventemitter3` in openvpn management class Connects-to: #47 Connects-to: #48 Connects-to: #49 Connects-to: #50 Connects-to: #51 Change-type: major Signed-off-by: Will Boyce <will@balena.io>
wrboyce
added a commit
that referenced
this issue
Apr 19, 2019
* start all services and workers from a unified `open-balena-vpn` systemd service and master process * register as a single service instance in master process and make available to workers * prevent forwarding tunnel requests via proxy workers on the same instance * use pooled request workers for client authentication via api * switch to `eventemitter3` in openvpn management class Connects-to: #47 Connects-to: #48 Connects-to: #49 Connects-to: #50 Connects-to: #51 Change-type: major Signed-off-by: Will Boyce <will@balena.io>
wrboyce
added a commit
that referenced
this issue
Apr 23, 2019
* start all services and workers from a unified `open-balena-vpn` systemd service and master process * register as a single service instance in master process and make available to workers * prevent forwarding tunnel requests via proxy workers on the same instance * use pooled request workers for client authentication via api Connects-to: #47 Connects-to: #48 Connects-to: #50 Connects-to: #51 Change-type: major Signed-off-by: Will Boyce <will@balena.io>
wrboyce
added a commit
that referenced
this issue
Apr 24, 2019
Connects-to: #51 Change-type: patch Signed-off-by: Will Boyce <will@balena.io>
5 tasks
wrboyce
added a commit
that referenced
this issue
Apr 24, 2019
Connects-to: #51 Change-type: patch Signed-off-by: Will Boyce <will@balena.io>
wrboyce
added a commit
that referenced
this issue
Apr 24, 2019
Connects-to: #51 Change-type: patch Signed-off-by: Will Boyce <will@balena.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This will prevent overwhelming the API when we have an influx of client connections (such as following a deploy).
The text was updated successfully, but these errors were encountered: