Hey Tyson,
I think we need to generally consider moving the large code blobs to an
object store (getting the code blogs into couch attachment as a first step
is in this PR [1]).
That said, I think you'd either need to deploy a couchdb instance or
upgrade your plan to a dedicated instance.
-r
details details ...
Will help along the way
Yay !! OpenWhisk Go!
On Sat, Feb 10, 2018 at 10:57 AM Rodric Rabbah wrote:
> > One problem I see is the /run running on port 8080 there will be a port
> conflict.
>
> Michele said "exec", so the initial proxy will replace itself
> One problem I see is the /run running on port 8080 there will be a port
conflict.
Michele said "exec", so the initial proxy will replace itself with a new
proxy and the compiled function.
Should avoid port conflict. A wrinkle I see is terminating the /init
connection held by the invoker (so
I forgot to mention the use case were the user uploads source code .go
action the /init will compiled it for them and then run the executable
Like Rodric said also the whole proxy can be all golang and no python
involved.
— Carlos
On Sat, Feb 10, 2018 at 10:47 AM Carlos Santana
Hi Michele
I’m not super familiar with go, but I think it goes inline with what we do
with.
So If I understand correctly your proposal is for the use case that user
provide and precompiled the executable.
One approach is for the web server that implements /init on port 8080 to
run the go
Reads well thought out and I don't see any immediate issues. Please go for it
(no pun intended)!
Cheers,
Markus
Thanks for the excellent write up. TL;DR (if I may): implement the proxy in Go.
Go! It of course make a lot more sense this way and the advantage of the proxy
and function in the same language are self evident.
-t
# How Go Action are currently implemented
Currently, Go Action are implemented using the generic docker support.
I investigated the implementation and I found there is a python based server,
listening for /init and /run requests. The /init will collect an executable and
place in the current