Reed Allman 2ebc9c7480 hybrid mergy (#581)
* so it begins

* add clarification to /dequeue, change response to list to future proof

* Specify that runner endpoints are also under /v1

* Add a flag to choose operation mode (node type).

This is specified using the `FN_NODE_TYPE` environment variable. The
default is the existing behaviour, where the server supports all
operations (full API plus asynchronous and synchronous runners).

The additional modes are:
* API - the full API is available, but no functions are executed by the
  node. Async calls are placed into a message queue, and synchronous
  calls are not supported (invoking them results in an API error).
* Runner - only the invocation/route API is present. Asynchronous and
  synchronous invocation requests are supported, but asynchronous
  requests are placed onto the message queue, so might be handled by
  another runner.

* Add agent type and checks on Submit

* Sketch of a factored out data access abstraction for api/runner agents

* Fix tests, adding node/agent types to constructors

* Add tests for full, API, and runner server modes.

* Added atomic UpdateCall to datastore

* adds in server side endpoints

* Made ServerNodeType public because tests use it

* Made ServerNodeType public because tests use it

* fix test build

* add hybrid runner client

pretty simple go api client that covers surface area needed for hybrid,
returning structs from models that the agent can use directly. not exactly
sure where to put this, so put it in `/clients/hybrid` but maybe we should
make `/api/runner/client` or something and shove it in there. want to get
integration tests set up and use the real endpoints next and then wrap this up
in the DataAccessLayer stuff.

* gracefully handles errors from fn
* handles backoff & retry on 500s
* will add to existing spans for debuggo action

* minor fixes

* meh
2017-12-11 10:43:19 -08:00
2017-12-11 10:43:19 -08:00
2017-12-11 10:43:19 -08:00
2017-12-11 10:43:19 -08:00
2017-12-05 08:22:03 -08:00
2017-12-07 14:15:54 +00:00
2017-12-11 10:43:19 -08:00
2017-12-06 10:45:27 -08:00
2017-11-29 17:50:24 -08:00
2017-11-29 17:50:24 -08:00
2017-05-18 18:59:34 +00:00
2017-11-17 15:59:36 +00:00
2017-12-05 08:22:03 -08:00
2017-12-06 10:45:27 -08:00
2017-12-06 10:45:27 -08:00
2017-10-06 08:42:33 -07:00
2017-05-18 18:59:34 +00:00
2017-12-05 08:22:03 -08:00
2017-11-29 17:50:24 -08:00
2017-11-18 07:09:43 -08:00
2017-11-28 11:21:39 -06:00

Fn Project

CircleCI GoDoc Go Report Card

Fn is an event-driven, open source, functions-as-a-service compute platform that you can run anywhere. Some of its key features:

  • Open Source
  • Native Docker: use any Docker container as your Function
  • Supports all languages
  • Run anywhere
    • Public, private and hybrid cloud
    • Import Lambda functions and run them anywhere
  • Easy to use for developers
  • Easy to manage for operators
  • Written in Go
  • Simple yet powerful extensibility

The fastest way to experience Fn is to follow the quickstart below, or you can jump right to our full documentation, API Docs, or his us up in our Slack Community!

Quickstart

Pre-requisites

  • Docker 17.05 or later installed and running
  • A Docker Hub account (Docker Hub) (or other Docker-compliant registry)
  • Log Docker into your Docker Hub account: docker login

Install CLI tool

The command line tool isn't required, but it sure makes things a lot easier. There are a few options to install it:

1. Homebrew - MacOS

If you're on a Mac and use Homebrew, this one is for you:

brew install fn

2. Shell script

This one works on Linux and MacOS (partially on Windows):

curl -LSs https://raw.githubusercontent.com/fnproject/cli/master/install | sh

This will download a shell script and execute it. If the script asks for a password, that is because it invokes sudo.

3. Download the bin

Head over to our releases and download it.

Run Fn Server

Now fire up an Fn server:

fn start

This will start Fn in single server mode, using an embedded database and message queue. You can find all the configuration options here. If you are on Windows, check here. If you are on a Linux system where the SELinux security policy is set to "Enforcing", such as Oracle Linux 7, check here.

Your First Function

Functions are small but powerful blocks of code that generally do one simple thing. Forget about monoliths when using functions, just focus on the task that you want the function to perform.

First, create an empty directory called hello and cd into it.

The following is a simple Go program that outputs a string to STDOUT. Copy and paste the code below into a file called func.go.

package main

import (
  "fmt"
)

func main() {
  fmt.Println("Hello from Fn!")
}

Now run the following CLI commands:

# Initialize your function
# This detects your runtime from the code above and creates a func.yaml
fn init

# Set your Docker Hub username
export FN_REGISTRY=<DOCKERHUB_USERNAME>

# Test your function
# This will run inside a container exactly how it will on the server
fn run

# Deploy your functions to the Fn server (default localhost:8080)
# This will create a route to your function as well
fn deploy --app myapp

Now you can call your function:

curl http://localhost:8080/r/myapp/hello
# or:
fn call myapp /hello

Or in a browser: http://localhost:8080/r/myapp/hello

That's it! You just deployed your first function and called it. To update your function you can update your code and run fn deploy myapp again.

User Interface

We also have an open source graphical user interface for Fn. It's very easy to use, simply run the command below:

docker run --rm -it --link fnserver:api -p 4000:4000 -e "FN_API_URL=http://api:8080" fnproject/ui

For more information, see: https://github.com/fnproject/ui

Learn More

Get Help

Get Involved

Stay Informed

Description
The container native, cloud agnostic serverless platform.
Readme Apache-2.0 170 MiB
Languages
Go 97.4%
Shell 1.2%
Ruby 0.5%
Makefile 0.4%
Dockerfile 0.4%
Other 0.1%