Friday, 2017-01-13

*** mpanetta has quit IRC00:30
*** itisha has quit IRC00:32
*** wanghao has joined #openstack-zaqar00:55
*** wanghao has quit IRC01:19
*** wanghao has joined #openstack-zaqar01:19
*** yanyanhu has joined #openstack-zaqar01:37
*** dtrainor has quit IRC01:53
*** yanyanhu has quit IRC01:53
*** yanyanhu has joined #openstack-zaqar01:54
*** dtrainor has joined #openstack-zaqar02:12
*** diga has joined #openstack-zaqar03:15
digaHi All03:16
flwang1diga: hi there03:19
flwang1diga: how can i help?03:19
*** dtrainor has quit IRC03:27
digaflwang1: Hi03:31
flwang1diga: are you going to use or contribute zaqar?03:31
digaflwang1: Zaqar has implemented Falcon API framework correct ?03:31
flwang1diga: yes03:31
digaflwang1: So you use gunicorn or HTTP WSGI ??03:32
digato run Falcon03:32
flwang1you can use uwsgi or mod_wsgi as well03:32
digaokay03:32
digawhat zaqar uses now ?03:33
flwang1diga: in devstack, we're using uwsgi03:33
digaflwang1: ok03:33
flwang1and it's fully depends on the requirements of deployer03:33
digaflwang1: okay03:34
flwang1back to my question03:34
flwang1are you going to deploy zaqar?03:34
flwang1in production, i mean03:34
digaflwang1: what you use for web framework, same WSGI server to run web framework03:34
digaflwang1: I am implementing Falcon for tacker project03:34
flwang1ah, ok03:34
digaflwang1: will need to use zaqar, but that we plan in next release not now03:35
flwang1i don't really understand your last question03:35
flwang1diga: would you mind sending an email to me? flwang@catalyst.net.nz03:35
digaflwang1: back to previous question03:35
digaflwang1: what you use for web framework, same WSGI server to run web framework03:36
flwang1now i have to run to pick up my son :)03:36
digaflwang1: okay03:36
flwang1it's time to off in NZ time :D03:36
diga:) NP03:36
flwang1have a nice weekend, body03:36
digahave a nice weekend you too :)03:36
*** flwang1 has quit IRC03:40
*** wanghao_ has joined #openstack-zaqar03:48
*** wanghao has quit IRC03:50
*** wanghao_ has quit IRC04:37
*** wanghao has joined #openstack-zaqar04:37
*** wanghao_ has joined #openstack-zaqar04:41
*** wanghao has quit IRC04:43
*** wanghao_ has quit IRC04:45
*** wanghao has joined #openstack-zaqar04:45
*** diga has quit IRC05:01
*** wanghao_ has joined #openstack-zaqar05:05
*** wanghao has quit IRC05:08
*** dtrainor has joined #openstack-zaqar05:24
*** dtrainor has quit IRC06:19
*** nadya has joined #openstack-zaqar06:39
*** tesseract has joined #openstack-zaqar07:11
*** wxy has quit IRC07:28
*** kgriffs has quit IRC07:30
*** wxy has joined #openstack-zaqar07:30
*** dhellmann has quit IRC07:30
*** kgriffs has joined #openstack-zaqar07:34
*** dhellmann has joined #openstack-zaqar07:35
*** openstackgerrit has joined #openstack-zaqar07:47
openstackgerritwanghao proposed openstack/zaqar: Subscription Confirmation Support-3  https://review.openstack.org/38947307:47
openstackgerritwanghao proposed openstack/zaqar: Subscription Confirmation Support-3  https://review.openstack.org/38947307:58
*** nadya has quit IRC08:18
*** wanghao_ has quit IRC08:20
*** wanghao has joined #openstack-zaqar08:20
*** wanghao_ has joined #openstack-zaqar09:02
*** nadya has joined #openstack-zaqar09:04
*** wanghao has quit IRC09:05
*** nadya has quit IRC09:29
openstackgerritwanghao proposed openstack/zaqar: Subscription Confirmation Support-3  https://review.openstack.org/38947309:43
*** AAzza has quit IRC09:57
*** AAzza has joined #openstack-zaqar09:58
*** wanghao_ has quit IRC10:01
*** openstackgerrit has quit IRC10:18
*** yanyanhu has quit IRC10:19
*** nadya has joined #openstack-zaqar10:49
*** nadya has quit IRC11:00
*** nadya has joined #openstack-zaqar11:01
*** nadya has quit IRC11:03
*** nadya has joined #openstack-zaqar11:21
*** nadya_ has joined #openstack-zaqar11:40
*** nadya has quit IRC11:41
*** nadya_ has quit IRC11:44
*** nadya has joined #openstack-zaqar11:45
*** nadya has quit IRC12:24
*** nadya has joined #openstack-zaqar13:06
*** rbrady-afk is now known as rbrady14:02
*** dtrainor has joined #openstack-zaqar14:12
*** nadya has quit IRC14:26
*** rbrady has quit IRC15:20
*** rbrady has joined #openstack-zaqar15:44
*** mpanetta has joined #openstack-zaqar16:01
*** pcaruana has joined #openstack-zaqar16:36
*** mpanetta has quit IRC16:46
*** mpanetta has joined #openstack-zaqar16:47
*** nadya has joined #openstack-zaqar16:52
*** nadya has quit IRC16:52
*** dtrainor has quit IRC17:03
*** dtrainor has joined #openstack-zaqar17:44
*** pcaruana has quit IRC18:26
*** nadya has joined #openstack-zaqar18:31
*** nadya has quit IRC18:34
*** pcaruana has joined #openstack-zaqar18:39
*** tesseract has quit IRC18:53
*** openstack has joined #openstack-zaqar18:58
*** pcaruana has quit IRC19:02
*** flwang1 has joined #openstack-zaqar19:31
dtrainoralright, i'm giving up on trying to proxy websockets through apache.  i had concerns about that being the right way about it in the first place.  in fact, the entire tripleo haproxy config needs to be updated, to include frontend/backend instead of bind/server.  this also allows us to use ACLs in haproxy19:37
dtrainorthat being said, i get a new error.  I'm using haproxy to set an acl when the connection is upgraded to a websocket.  The acl works, but then when it hits the backend zaqar websocket transport, I get:  WebSocket connection closed: connection was closed uncleanly (missing port in HTTP Host header '8.43.87.242' and server runs on non-standard port 9000 (wss = False))19:38
dtrainorDoesn't look like zaqar is looking at X-Forwarded-Port either (which I think it should be doing)19:39
*** openstackstatus has quit IRC19:57
*** openstack has joined #openstack-zaqar19:58
*** david-lyle is now known as baling-wire20:00
*** openstackstatus has joined #openstack-zaqar20:00
*** ChanServ sets mode: +v openstackstatus20:00
*** dtrainor has quit IRC20:02
*** dtrainor has joined #openstack-zaqar20:06
*** openstackstatus has quit IRC20:27
*** openstack has joined #openstack-zaqar20:28
*** openstackstatus has joined #openstack-zaqar20:30
*** ChanServ sets mode: +v openstackstatus20:30
dtrainoris autobahn used as the websockets transport that zaqar implements?20:36
vkmcdtrainor, yes20:41
vkmcit uses python autobahn20:41
dtrainorok, thanks.20:42
dtrainori think what i'm seeing is that autobahn is making some less than ideal assumptions about the connection that it receives, instead of looking at headers that a proxy (in this case, both httpd and haproxy) provide20:43
vkmcit's possible dtrainor20:44
vkmcwhich headers are you expecting zaqar to handle?20:45
dtrainorwell, i think autobahn is looking for a host header that includes a port.  my client (browser) is trying to initiate a connection via wss://8.43.87.242:443/zaqar but i'm wanting haproxy or apache to catch this and forward it to a different backend (the zaqar websocket transport itself)20:46
dtrainorwhat i end up with is http://pastebin.test.redhat.com/44597120:49
dtrainorarg.20:49
dtrainorhttps://hastebin.com/raw/funigenito20:49
vkmcall right20:50
thervedtrainor, Have you set external-port?21:02
dtrainori have, yes.  i set it to port 443 since that's the port that the client will be using21:02
therveIt's possible isSecure is not set then?21:04
dtrainorthat would make protocol.py:2935 fail yep21:05
therveProbably because you try to terminate ssl on apache, no?21:06
therveMaybe try to set external-port to 80?21:06
dtrainortechnically haproxy terminates ssl but yes21:06
dtrainori get the same error, but i understand what you meant by testing that21:08
therveI don't think you can terminate ssl in haproxy with websocket?21:09
therveI don't know enough about websocket proxying though21:10
dtrainori don't either, still piecing it together.  but i think wss websockets inside of https may not be a great combination21:10
therveBut it's something along those lines, I'd say21:12
therveWe only support a ws:// URL in zaqar21:12
therveGod knows what happens in your case21:13
dtrainorhaha21:13
*** rbrady is now known as rbrady-afk21:15
dtrainorbased on what i'm able to determine, since the ws connection is technically just http, the websocket gets established using whichever scema - http or https - through the browser, and after https negotiation just like any other data21:15
dtrainorso i am trying to call a backend as ws:// from both apache in haproxy, in my tests21:16
thervedtrainor, Can we see your haproxy config?21:16
dtrainorsure thing - it's messy but you get the jest of it http://pastebin.com/3xFk0Bjz21:18
dtrainori had most recently been playing around with faking the header sent to the backend by haproxy21:18
thervedtrainor, Why did you comment the "http-request set-header Host" ?21:18
therveThat seems it would be the key here21:18
dtrainorbecause the host does not include a port, since the connection was made to https://foo, so just Proto is set21:21
dtrainorif I'm understanding how this is all coming together, properly21:21
therveRIght. I'd force the host to contain the port21:22
dtrainorIn my client configuration I am specifying :443 as the port21:22
dtrainorwhether or not that's required I'm not sure, since I still use a scheme of https21:22
therveI'm just trying to reverse engineer https://github.com/crossbario/autobahn-python/blob/master/autobahn/websocket/protocol.py#L252021:23
dtrainori see21:25
dtrainorthe error i'm seeing is https://github.com/crossbario/autobahn-python/blob/master/autobahn/websocket/protocol.py#L254021:27
therveNot setting external-port may work too21:28
therveAnyway21:28
* therve away21:28
dtrainorthanks for taking a peek!21:30
*** baling-wire is now known as david-lyle22:26
*** mpanetta has quit IRC23:25
*** harlowja has quit IRC23:56

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!