Difference between revisions of "Picasso"
m (→Getting Started with Picasso) |
m (→Getting Started with Picasso) |
||
Line 43: | Line 43: | ||
== Getting Started with Picasso == | == Getting Started with Picasso == | ||
− | Instructions for getting started with Picasso using Devstack are available [https://github.com/iron-io/picasso/blob/master/devstack/README.md | + | Instructions for getting started with Picasso using Devstack are available [https://github.com/iron-io/picasso/blob/master/devstack/README.md here] |
== Examples == | == Examples == | ||
* [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] |
Revision as of 20:04, 3 January 2017
Contents
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/iron-io/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.
Getting Started with Picasso
Instructions for getting started with Picasso using Devstack are available here