Serverless prototype

[bquenin]

Related to #521

Verification

$ amp pf stop
$ make install
$ ./shrink.sh local
$ amp pf start --local
$ make test

CLI tests

The source code of the amp-demo-function is available here: amp-demo-function

$ docker build -t appcelerator/amp-demo-function examples/functions/demo-function
[...]

$ amp function --help

Usage:  amp function COMMAND

function operations

Aliases:
  function, fn

Options:
      --config string   Config file (default is $HOME/.amp.yaml)
  -h, --help            help for function
      --server string   Server address
  -v, --verbose         Verbose output

Commands:
  create      Create a function
  ls          List functions
  rm          Remove function

 Run 'amp function COMMAND --help' for more information on a command.

$ amp fn create -i appcelerator/amp-demo-function test
[function-id]

$ amp fn ls
ID              Name   Image
[function-id]   test   appcelerator/amp-demo-function   

$ cat Makefile | curl 127.0.0.1:4242/[function-id] --data-binary @-
[The result should be a Capitalized Makefile]

$ amp fn rm [function-id]
[function-id]

$ amp fn ls
ID   Name   Image

[freignat91]

LGTM and tests executed ok

[generalhenry]

It would be nice if you could use [function-ident] in place of [function-id]

I would also prefer fn.local.atomiq.io (or the like) to localhost:4242 (aka add it to the haproxy config)

[generalhenry]

One more small thing, amp function ls should have a -q --quiet options for amp function rm $(amp fn ls -q) cleanups

[bquenin]

@generalhenry You're right about the URL, this is only temporary. It should definitely be something like fn.local.atomiq.io.
I'll make an update regarding the -q.
Regarding function-name vs. function-id, it's just temporary as well, I only built the index by id in etcd.
I'm waiting for feedback on the global approach but all your comments are helpful.
Thanks!

[bquenin]

⚠️ Also, I think we're hitting a bug in Docker causing the container attachment to fail sporadically, causing the function to fail.
For reference, the bug mentioned is moby/moby#29285

[bquenin]

Maybe this issue has an impact as well: moby/moby#29421

[thaJeztah]

@bquenin docker 1.12.5 has been released, which contains moby/moby#29424 to resolve the issue you linked to; https://github.com/docker/docker/releases/tag/v1.12.5

[bquenin]

@thaJeztah thanks for the feedback. Just tested it with 1.12.5 and now it works like a charm!
👊

[subfuzion]

Thanks @thaJeztah. I would imagine this will land shortly in the next 1.13 RC as well then (we're currently on v1.13.0-rc3).

[thaJeztah]

@subfuzion looks like the fix was actually in 1.13.0-rc2 already (see moby/moby#28674); are you having this problem on RC3?

[bquenin]

@thaJeztah I tested on latest stable (1.12.5). Going to check on 1.13.0-rc3.

[thaJeztah]

Perfect! If you have problems on 1.13, please open an issue in the issue tracker 👍

[bquenin]

@thaJeztah Just tested it a thousand times on 1.13.0-rc3, works fine as well! Thanks again

[thaJeztah]

Thanks for testing!

[subfuzion]

@bquenin Very nice! I'm merging this into v0.5.0-rc1 for additional evaluation. 👍

[subfuzion]

@bquenin It looks like there are a few conflicts due to @freignat91 / @ndegory cluster management PR that I just merged into v0.5.0-rc1. Can you work to resolve asap? Thanks!

[bquenin]

@subfuzion Ok, I rebased on the branch v0.5.0-rc1