Difference between revisions of "Picasso"
m |
|||
| Line 1: | Line 1: | ||
| − | == Picasso | + | == Picasso == |
| − | 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 == | == Projects == | ||
| Line 30: | Line 30: | ||
== Architecture == | == Architecture == | ||
| − | * [https://github.com/iron-io/picasso/blob/master/docs/source/images/picasso_deployment.png High-level] | + | Picasso is comprised of two main components: |
| − | * [https://github.com/iron-io/picasso/blob/master/docs/source/images/intercomponent_architecture.png Inter-component] | + | * 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. | ||
| + | * [https://github.com/iron-io/picasso/blob/master/docs/source/images/picasso_deployment.png High-level architecture] | ||
| + | * [https://github.com/iron-io/picasso/blob/master/docs/source/images/intercomponent_architecture.png Inter-component architecture] | ||
== Getting Started with Picasso == | == Getting Started with Picasso == | ||
Revision as of 04:31, 19 December 2016
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.
- High-level architecture
- Inter-component architecture
Getting Started with Picasso
Instructions for getting started with Picasso using Devstack are available here
