3 ms·
In case someone is looking for a way to run and deploy this to a public cloud (in my case Azure), there is an extant pull request here that will set up a dynami
by rcarmo 9y ago
In case someone is looking for a way to run and deploy this to a public cloud (in my case Azure), there is an extant pull request here that will set up a dynamically resizable Swarm cluster:
https://github.com/get-faas/labs-azure-scaling-template/pull/1 https://github.com/get-faas/labs-azure-scaling-template/pull...
This allows the FaaS runtime to dynamically allocate more Swarm nodes based on CPU load (indirectly, using Azure VM scale sets).
I've been meaning to see how I could tie in Azure Container Instances to FaaS, but currently lack the time (and to do that it would need to cleanly separate the admin UI from function endpoints, something that wasn't implemented yet a few weeks ago).
- alexellisuk 9y agoFunction endpoints take a route of /function or /async-function and all administration is via /system/functions route and the UI is hosted at /ui - so you have all the separation in place. There's an open issue for ACI - would be great if you wanted to contribute to the project. https://github.com/alexellis/faas/issues/117 https://github.com/alexellis/faas/issues/117
- rcarmo 9y agoI meant separating the admin UI completely, into its own process/container and IP/port, distinct from the reverse proxy. Route separation just means I can DoS the admin UI by invoking functions repeatedly - which will eventually happen even with "production" loads.