Hi Chetan, this is fantastic... I followed your instructions here as is even though I noticed the gw PR was merged already and in theory I should be able to drop the image override.
the system came up cleanly, and as relayed on Slack, I think it would be useful to hoist the messages that gw is ready up to where the system checks are first printed so they aren't lost in all the output that follows which for the most part, users should be able to ignore. i tried creating an API as documented in [2] but hit a snag. The controller received this request from the gateway: [#tid_bEVIJzQ...] GET //localhost:3233/api/v1/web/guest/default/hello.json but this doesn't match any routes in the controller and the API returns with a 404. The prefix "//localhost:3233/" needs to be omitted, I'm not yet sure where it's coming from. I suspect you'll know right away. These are the logs from the gw for the failed request: ==> /var/log/api-gateway/access.log <== 172.17.0.1 - remote_user="-" [29/Jul/2019:14:50:45 +0000] request_method="GET" request_uri="/api/23bc46b1-71f6-4ed5-8c54-816aa4f8c502/hello/world" request_protocol="HTTP/1.1" status=404 bbs=96 rl=130 rt=0.008 hr="-" ua="curl/7.54.0" xfwdf="-" upadd="192.168.65.2:3233" upstat=404 uprt=0.007 tenantId="23bc46b1-71f6-4ed5-8c54-816aa4f8c502" tenantNamespace="23bc46b1-71f6-4ed5-8c54-816aa4f8c502" tenantInstance="" requestHeaders="" requestBody="" responseHeaders="" responseBody="" apiId="8a68d0a9-a024-4411-9233-7ba1d9099b1a" apiKey="-" analyticsUri="/hello/world" reqid="zvL6RbV0qtiZ0BakfDGudINV8Gzv1Ocl" ==> /var/log/api-gateway/gateway_error.log <== 2019/07/29 14:50:45 [info] 35#0: *21 client 172.17.0.1 closed keepalive connection 2019/07/29 14:50:48 Executing sync cmd: echo '' sync stdout | '' 2019/07/29 14:50:48 done -r On Mon, Jul 29, 2019 at 7:53 AM Chetan Mehrotra <chetan.mehro...@gmail.com> wrote: > Hi Team, > > As discussed in last Tech Interchange call support is now being added > to launch the Api Gateway with Standalone Server [1]. With this it > should be possible to direct new OpenWhisk users to use the Standalone > server to try out various features provided by OpenWhisk > > So far tests look fine and would now like to seek some feedback from > community on this feature. For this it would be helpful if you can try > out a beta build and see if it works as expected > > # Fetch custom docker build of apigateway which has > apache/incubator-openwhisk-apigateway#347 fixed > $ docker pull chetanmeh/apigateway > > # Download the openwhisk-standalone jar > $ wget > https://github.com/chetanmeh/incubator-openwhisk/releases/download/0.11/openwhisk-standalone.jar > $ java -Dwhisk.standalone.api-gateway.image=chetanmeh/apigateway -jar > openwhisk-standalone.jar --api-gw > > Post this you can use the steps as mentioned in [2] to check out the > gateway support. > > Please share any feedback on #4571 or this mail thread > > Chetan Mehrotra > [1] https://github.com/apache/incubator-openwhisk/pull/4571 > [2] > https://github.com/apache/incubator-openwhisk/blob/master/docs/apigateway.md >
