Open Stack

Derek,

I think Serverless is a great idea.  I had considered starting a new project in October around Serverless.  During my analysis I of course saw iron.io’s work and OpenWhisk.  I thought OpenWhisk would be a better community to join as it was open.  Iron.io and OpenWhisk should join forces!  That may be challenging, as OpenWhisk is an apache project and OpenStack doesn’t have Scala infrastructure for a language choice.

If you do plan to enter the big tent with this code base, I’d have a read of:
https://github.com/openstack/governance/blob/master/reference/new-projects-requirements.rst

Best wishes for success for OpenWhisk+Iron.io!,
-steve

From: Derek Schultz <schultz.derek at gmail.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Date: Tuesday, December 20, 2016 at 11:27 AM
To: "openstack-dev at lists.openstack.org" <openstack-dev at lists.openstack.org>
Subject: [openstack-dev] [picasso] Picasso (FaaS) project release!


Hi all,

I’m very pleased to announce a new project, Picasso[1][2] - Functions as a Service (FaaS).

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<https://github.com/iron-io/functions>, an open-source Serverless/FaaS platform based on Docker.

Resources

  *   Wiki

     *   https://wiki.openstack.org/wiki/Picasso

  *   Architecture

     *   Picasso deployment architecture<https://raw.githubusercontent.com/iron-io/picasso/master/docs/source/images/picasso_deployment.png>
     *   Picasso/IronFunctions inter-component architecture<https://raw.githubusercontent.com/iron-io/picasso/master/docs/source/images/intercomponent_architecture.png>

  *   Examples

     *   Triggering functions from Telemetry and Aodh<https://github.com/iron-io/picasso/blob/master/examples/openstack-alarms/README.md>
     *   Application that queries Nova for a list of running servers<https://github.com/iron-io/picasso/tree/master/examples/openstack-app>



We’ve created some initial blueprints<https://blueprints.launchpad.net/picasso> 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<https://github.com/iron-io/picasso/blob/master/README.md#quick-start-guide>. Let us know what you think!

If you’re interested in contributing or just have any questions, please join us on Slack at open-iron.slack.com<http://open-iron.slack.com/>.



[1] https://launchpad.net/picasso

[2] https://launchpad.net/python-picassoclient



Regards,

Derek Schultz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161221/261712d0/attachment.html>