Add shim for collecting logs

[alexellis]

Signed-off-by: Alex Ellis (OpenFaaS Ltd) alexellis2@gmail.com

Description

Add shim for collecting logs

Motivation and Context

Experimental / WIP

faas-cli store deploy figlet --name f2

sudo journalctl -t openfaas-fn:f2
-- Logs begin at Wed 2020-02-19 21:46:03 GMT, end at Sun 2020-02-23 16:56:42 GMT. --
Feb 23 16:55:56 alexx openfaas-fn:f2[16011]: 2020/02/23 16:55:56 Version: 0.13.0        SHA: fa93655d90d1518b04e7cfca7d7548d7d133a34e
Feb 23 16:55:56 alexx openfaas-fn:f2[16011]: 2020/02/23 16:55:56 Read/write timeout: 5s, 5s. Port: 8080
Feb 23 16:55:56 alexx openfaas-fn:f2[16011]: 2020/02/23 16:55:56 Writing lock-file to: /tmp/.lock
Feb 23 16:55:56 alexx openfaas-fn:f2[16011]: 2020/02/23 16:55:56 Metrics server. Port: 8081
Feb 23 16:56:09 alexx openfaas-fn:f2[16011]: 2020/02/23 16:56:09 Forking fprocess.
Feb 23 16:56:09 alexx openfaas-fn:f2[16011]: 2020/02/23 16:56:09 Wrote 60 Bytes - Duration: 0.006864 seconds

[martindekov]

I see the build fails here:

Server returned unexpected status code: 404 - error finding function figlet.: Get http://faasd-provider:8081/system/function/figlet?namespace=: dial tcp: i/o timeout

Not sure why faas-cli invokes the figlet function with this URL:

http://faasd-provider:8081/system/function/figlet?namespace=

I think this might be related with how the faas-cli invokes functions when no namespace is specified, or how the faasd handles the request. I will try to replicate both suggestions.

[alexellis]

It's a timing issue I think. It's intermittent - so is downloading the CLI (failing often in this project 🤔)

Thanks for looking into it.