Jump to: navigation, search

Difference between revisions of "Picasso"

(Picasso)
Line 48: Line 48:
  
 
* [https://github.com/iron-io/picasso/blob/master/examples/openstack-alarms/README.md Alarm event triggers from Telemetry and Aodh]
 
* [https://github.com/iron-io/picasso/blob/master/examples/openstack-alarms/README.md Alarm event triggers from Telemetry and Aodh]
 +
 +
== Demo/Screencasts ==
 +
* [https://www.youtube.com/watch?v=qIM-ciBnsfQ Latest]

Revision as of 20:54, 11 January 2017

Picasso

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

Projects

Picasso

Source code https://github.com/openstack/picasso
Bug tracker https://bugs.launchpad.net/picasso
Blueprints https://blueprints.launchpad.net/picasso

Python Picasso Client

Source code https://github.com/iron-io/python-picassoclient
Bug tracker https://bugs.launchpad.net/python-picassoclient
Blueprints https://blueprints.launchpad.net/python-picassoclient

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

Demo/Screencasts