2019-04-19 19:49:59 +00:00

2019-03-24 20:35:35 +00:00

2017-01-18 10:30:41 -07:00

2019-03-24 20:35:35 +00:00

2016-12-07 00:01:44 +02:00

2016-12-13 09:59:50 +02:00

2016-12-07 00:01:44 +02:00

2016-12-13 01:31:51 +02:00

2016-12-13 03:48:30 +02:00

2019-04-19 19:49:59 +00:00

2016-11-28 14:56:50 +02:00

2016-12-07 00:01:44 +02:00

2016-12-14 11:39:50 -07:00

2016-11-14 17:57:27 +02:00

2017-01-23 14:48:28 -07:00

2016-12-14 22:59:22 +02:00

2017-01-18 11:15:58 +02:00

2016-12-14 12:39:29 +02:00

2017-03-02 16:29:04 +08:00

2016-12-15 23:45:05 -07:00

2016-12-15 15:33:50 -07:00

Functions-as-a-Service (FaaS) on OpenStack

Mission

Picasso aims to provide an API abstraction layer for Functions-as-a-Service (FaaS) on OpenStack.

What is FaaS?

Functions as a service is a new paradigm in computing that enables simplicity, efficiency and scalability for both developers and operators. It's important to distinguish the two, because the benefits differ:

Benefits for developers

The main benefits that most people refer to are on the developer side and they include:

No servers to manage -- you just upload your code and the platform deals with the infrastructure
Super simple coding -- no more monoliths! Just simple little bits of code
Pay by the milliseconds your code is executing -- unlike a typical application that runs 24/7, and you're paying 24/7, functions only run when needed

Since you'll be running IronFunctions yourself, the paying part may not apply, but it does apply to cost savings on your infrastructure bills as you'll read below.

Benefits for operators

If you will be operating IronFunctions, then the benefits are different, but related.

Extremely efficient use of resources
- Unlike an app/API/microservice that consumes resources 24/7 whether they are in use or not, functions are time sliced across your infrastructure and only consume resources while they are actually doing something
Easy to manage and scale
- Single system for code written in any language or any technology
- Single system to monitor
- Scaling is the same for all functions, you don't scale each app independently
- Scaling is simply adding more IronFunctions nodes

System requirements

Operating system: Linux/MacOS
Python version: 3.5 or greater
Database: MySQL 5.7 or greater

Quick-start guide

Install DevStack with IronFunctions enabled
Clone the Picasso source

Create a Python3.5 virtualenv

Install Picasso dependencies

Install Picasso

Install MySQL if you haven't already, and create a new database for functions

Migrations

Once all dependencies are installed it is necessary to run database migrations. First, set the following environment variable:

Then use alembic to apply the migrations

Starting the Picasso API server

The following are the minimum required options to start the Picasso API service:

Building and Running Picasso in Docker

Install Docker engine if you haven't already.

From the Picasso repo, build a Docker image using the following commands:

To start the container, pass in the required env vars with --env-file or by entering all required values in -e <KEY>=<VALUE> format to the docker run command.

Example Dockerfile.env

Once the container is started, check if the service in running. In your web browser navigate to:

or using the CLI:

API docs

API docs are discoverable via Swagger. Just launch the Picasso API and browse to:

Picasso provides private and public functions

Using the Picasso API, it is possible to create two type of functions - private and public.

Private functions are defined as functions that belong to a specific OpenStack project, and the execution of the function requires passing in authorization headers.
Public functions belong to a specific OpenStack project ID, but do not require any authorization headers to execute, allowing the function to be shared with anyone.

Private and public functions are handled by different URL handlers:

See OpenStack alarming example for more details.

Testing Picasso

See Testing.md

Support

Join us on Slack!