Picasso

Picasso
Picasso provides an OpenStack API for Functions as a service, abstracting away the infrastructure layer while enabling simplicity, efficiency, and scalability for both developers and operators.

Architecture
Picasso is comprised of two main components:
 * Picasso API
 * The Picasso API server uses Keystone authentication and authorization through its middleware.
 * IronFunctions
 * Picasso leverages the backend container engine provided by IronFunctions, an open-source Serverless/FaaS platform based on Docker.

High-level

Inter-component

Getting Started with Picasso
Instructions for getting started with Picasso using Devstack are available here

Examples

 * Alarm event triggers from Telemetry and Aodh

Demo/Screencasts

 * Latest

Roadmap

 * Picasso features are tracked in launchpad blueprints
 * Ideas needing blueprints:
 * Magnum integration
 * Features for IronFunctions:
 * Support for RabbitMQ as backend message queue
 * Support for MySQL as backend database

IRC Meetings

 * Biweekly on Tuesday at 1700 UTC in #openstack-meeting
 * Check Picasso Meetings for more details

Contact Us

 * Use IRC channel for regular discussions: #openstack-functions
 * Use [Picasso] tag for Picasso emails on OpenStack Mailing Lists