Difference between revisions of "Picasso"
(→Architecture) |
|||
| Line 37: | Line 37: | ||
| − | [https://raw.githubusercontent.com/ | + | [https://raw.githubusercontent.com/openstack/picasso/master/docs/source/images/picasso_deployment.png High-level] |
| − | [https://raw.githubusercontent.com/ | + | [https://raw.githubusercontent.com/openstack/picasso/master/docs/source/images/intercomponent_architecture.png Inter-component] |
== Getting Started with Picasso == | == Getting Started with Picasso == | ||
Revision as of 00:36, 18 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/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.
Getting Started with Picasso
Instructions for getting started with Picasso using Devstack are available here
