Downloaded 18 times
![CloudFoundry
transports{[‘websocket’]}
2011/12/14(wed)
Node 3](https://image.slidesharecdn.com/111214nodeconf-111214043921-phpapp02/75/111214-node-conf-1-2048.jpg)
![client_connection.rb
def on_headers_complete(headers)
....
# [kom] Check connection mode(websocket or not)
@is_websocket = (headers[UPGRADE_HEADER] == WEBSOCKET) ? true : false
Router.log.info "@is_websocket : #{@is_websocket}"
....
if (@is_websocket)
host, port = @droplet[:host], @droplet[:port]
@bound_app_conn = EM.connect(host, port, WebsocketConnection, self,
@headers, @droplet)
return
end
....
end](https://image.slidesharecdn.com/111214nodeconf-111214043921-phpapp02/75/111214-node-conf-35-2048.jpg)
Uploaded byKensaku Komatsu
111214 node conf
This document discusses adding WebSocket support to Cloud Foundry. It describes how Cloud Foundry currently uses nginx and a router based on HTTP/1.1. It then proposes modifications to nginx and the router code to support WebSocket by upgrading connections and passing frames between client and app connections. Code snippets from router.rb and a new websocket_connection.rb module are provided as examples.
More Related Content
![[오픈소스컨설팅] 쿠버네티스와 쿠버네티스 on 오픈스택 비교 및 구축 방법](https://cdn.slidesharecdn.com/ss_thumbnails/osck8svsk8sonopenstackkhoj-210310051504-thumbnail.jpg?width=640&height=640&fit=bounds)
![[2018.10.19] Andrew Kong - Tunnel without tunnel (Seminar at OpenStack Korea ...](https://cdn.slidesharecdn.com/ss_thumbnails/tunnelwithouttunnel-181022130534-thumbnail.jpg?width=640&height=640&fit=bounds)
![[오픈소스컨설팅] 프로메테우스 모니터링 살펴보고 구성하기](https://cdn.slidesharecdn.com/ss_thumbnails/oscprometheus-190422050231-thumbnail.jpg?width=640&height=640&fit=bounds)
111214 node conf
- 1. CloudFoundry transports{[‘websocket’]} 2011/12/14(wed) Node 3
- 2. • (@komasshu) • html5 • WebSocket • Google API Expert (HTML5) • Microsoft Valuable Professional (IE)
- 4.
- 5.
- 6. Cloud Foundry ? • VMWare PaaS https://github.com/cloudfoundry
- 7. easy demo just push apps $ vmc push hogehoge http://cloudfoundry.com/
- 8. Heroku • private PaaS • •CloudFoundry PaaS • Active State • AppFog • Joyent
- 9. Architecture of Cloud Foundry http://www.slideshare.net/derekcollison/design-of-cloud-foundry
- 10. • • Cloud Controller • router • DEA • ... • NATS •
- 11. hoge.com 3000 app0 (3000) fuga.com 3001 router hoge.com app1 (3001) DEA register deploy cloud controller push
- 12.
- 13. WebSocket • HTML5 API/Protocol • Web •
- 14. • Web(port=80) VPN • SSL-VPN
- 18.
- 19.
- 20.
- 21.
- 22.
- 23. point : Upgrade RequestHeader (client => server) GET /chat HTTP/1.1 Host: server.example.com Upgrade: websocket Response Header (server => client) HTTP/1.1 101 Switching Protocols Upgrade: websocket Connection: Upgrade Upgrade HTTP WebSocket
- 24. HTTP Compatible • VPN • FW, Proxy • HTTP/1.1 • • Web VPN
- 25. http://www.ericom.com/html5_client_vmware_view.asp http://www.publickey1.jp/blog/11/webhtml5.html
- 26. WebSocket on Cloud Foundry
- 27. CloudFoundry WebSocket orz • why? • nginx 2 • router HTTP/1.1 rails sinatra nginx router node.js DEA
- 28. • nginx •zip Access log HTTPS • router • URL routing URL routing unix domain tcp socket socket rails (tcp socket ) 80/443 sinatra nginx router node.js DEA
- 29. 2 socket.io + transports{‘xhr-polling’}
- 30. WebSocket nginx • Request HTTP (502) • tcp_proxy Patch • https://github.com/yaoweibin/nginx_tcp_proxy_module
- 31. nginx.conf tcp { upstream vcap_router { server unix:/tmp/router.sock; # server 127.0.0.1:2222; # check interval=3000 rise=2 fall=5 timeout=1000; } tcp_nodelay off; server { listen 80; server_name _; proxy_read_timeout 200000; proxy_send_timeout 200000; proxy_pass vcap_router; } }
- 32. WebSocket router • HTTP Request/Response HTTP • WebSocket Frames • HTTP
- 33. dialog of router.rb request Header router request/sec Router on_headers _complete() unix module module node.js nginx domain TCP socket socket ClientConnection AppConnection on_headers _complete() response Header response latency
- 34. WebSocket Upgrade: websocket WebsocketConnection router module TCP socket node.js on_headers AppConnection _complete() on_headers unix module _complete() nginx domain socket ClientConnection module WebsocketConne TCP socket node.js ction WS
- 35. client_connection.rb def on_headers_complete(headers) .... # [kom] Check connection mode(websocket or not) @is_websocket = (headers[UPGRADE_HEADER] == WEBSOCKET) ? true : false Router.log.info "@is_websocket : #{@is_websocket}" .... if (@is_websocket) host, port = @droplet[:host], @droplet[:port] @bound_app_conn = EM.connect(host, port, WebsocketConnection, self, @headers, @droplet) return end .... end
- 36. websocket_connection.rb module WebsocketConnection definitialize client, header, droplet @client, @header, @droplet = client, header, droplet end def connection_completed send_data(@header) end def receive_data(data) @client.send_data(data) end def terminate end orz end
- 38. socket.io + transports{‘websocket’} :)
- 39.
- 40. timeline • cloud foundry •websocket • orz • code reading • ←
- 41. next step • • pull request • brush up
- 42. problem • vps ... Cent OS, 512MB plan • Cloud Foundry • 1GB memory • Ubuntu10.04.2 •
- 43. router ( ∀ ) http://www.slideshare.net/derekcollison/design-of-cloud-foundry
- 44. • NATS • routing
- 45.
- 46.
- 47.
- 48. $ cd bin $./router
- 49. I love BDD Benkyo-kai Driven Development
- 50.