Difference between revisions of "Picasso"
m (→Getting Started with Picasso) |
(→Picasso) |
||
| Line 7: | Line 7: | ||
{| border="1" cellpadding="2" | {| border="1" cellpadding="2" | ||
| Source code | | Source code | ||
| − | | https://github.com/ | + | | https://github.com/openstack/picasso |
|- | |- | ||
| Bug tracker | | Bug tracker | ||
Revision as of 20:45, 10 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
