Announcing Picasso: OpenStack Functions as a Service
Announcing Picasso: OpenStack Functions as a Service
OpenStack has announced their new functions-as-a-service initiative, Picasso. Take a look at the uses, the architecture, and the roadmap for this new offering.
Join the DZone community and get the full member experience.
Join For FreeLearn how to migrate and modernize stateless applications and run them in a Kubernetes cluster.
We are pleased to announce a new project to enable Functions as a Service (FaaS) on OpenStack — Picasso.
The mission is to provide an API for running FaaS on OpenStack, abstracting away the infrastructure layer while enabling simplicity, efficiency and scalability for both developers and operators.
Picasso can be used to trigger functions from OpenStack services, such as Telemetry (via HTTP callback) or Swift notifications. This means no long running applications, as functions are only executed when called.
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.
Resources
- OpenStack Wiki
- Architecture
- Examples
We’ve created some initial blueprints to show what the future roadmap looks like for the project.
You can try out Picasso now on DevStack by following the quick start guide here. Let us know what you think!
If you’re interested in contributing or just have any questions, please join us on Slack.
Join us in exploring application and infrastructure changes required for running scalable, observable, and portable apps on Kubernetes.
Like This Article? Read More From DZone
Published at DZone with permission of Derek Schultz , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}