[openstack-dev] [FaaS] Function as a service in OpenStack
dzimine at stackstorm.com
Sat May 6 19:50:25 UTC 2017
please let me re-surface the discussion,
and propose StackStorm as [a starting point for] a Serverless framework for
StackStorm  is an open source event-driven automation platform, built
around Mistral and adds “before” and “after” - (triggers on events, and
rules that maps triggers to actions) and after (easy to add actions with
auto-generated API) .
It is built for devops automation and often used to automate OpenStack .
Recently, we saw it used as a DIY serverless framework, as it has the parts
of Serverless stack discussed here: “Lambda”, API Gateway, event sources
(not just timers and web hooks but any other events as triggers), and
workflows/Step Functions with Mistral - as workflows become recognizable
part of serverless.
Comparing with OpenWhisk, StackStorm brings the same concepts and
functionality, but does it on OpenStack technology stack: Python, RabbitMQ,
Pecan, eventlets, Oslo config & utils, and a fair amount of same 3rd party
StackStorm is mature (3 years old), heavily used (~3,000 installations /
month), have rich set of existing integrations . StackStorm team has
been a part of OpenStack community and Mistral contributors from the outset.
I hate that this is coming out as a plug, but I’d hate it even more if
there is a match, and we miss it.
Let’s decide on merits. The detailed discussion takes more writing…
How about we use the Boston summit to open the conversation? Here is what
we can do:
1) My talk “Serverless on OpenStack with StackStorm and Mistral” Wed May10
9am can serve as an introduction: https://goo.gl/2ZUJFK
2) Let’s make time at the summit with those who’re interested AND in
Boston, do in-depth technical, architecture, and merits discussion, and
share the findings here.
3) If the community believes the idea worth further consideration, we take
it from there.
If you’re interested to participate, reply here and/or contact me directly.
 StackStorm: https://github.com/StackStorm/st2
 Slides from OpenStack Barcelona where I explained the relations between
Mistral and StackStorm to Mistral community.
 E.g. Cybera, or Symantec:
 Integration points (aka packs) https://exchange.stackstorm.org/
On Sat, May 6, 2017 at 12:25 PM, Dmitri Zimine <dzimine at brocade.com> wrote:
> From: Lingxian Kong <anlin.kong at gmail.com>
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev at lists.openstack.org>
> Date: Wednesday, November 2, 2016 at 6:20 PM
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev at lists.openstack.org>
> Subject: Re: [openstack-dev] [FaaS] Function as a service in OpenStack
> On Thu, Nov 3, 2016 at 10:44 AM, Zane Bitter <zbitter at redhat.com> wrote:
>> This is a really interesting space. There seems to be two main use cases
>> for Lambda that are probably worth talking about separately:
>> The first is for just Lambda alone. You can use it to provide some glue
>> logic between the other AWS services, so you can trigger off various events
>> (e.g. S3 notifications) and write a little bit of conditioning logic that
>> transforms the data and dispatches it to other services (e.g. DynamoDB).
>> This one is particularly interesting to me, and in fact we can support
>> parts of this in OpenStack already because Mistral's functionality is
>> equivalent to something like SWS + parts of Lambda. (Specifically, Mistral
>> can do the data dispatch easily enough, but any data transformation has to
>> be done in YAQL, which is a pretty high bar compared to just writing some
>> code in a language of your choosing.)
> There is still one thing missing in Mistral (maybe it should not be).
> After receieving events from Aodh or Zaqar, what if user just wants to
> trigger some scripts under his/her management, rather than just invoking
> openstack services api? Although actions are pluggable in Mistral, but in
> this case it's definitely not an easy thing as just writing an customized
> action, unless Mistral could include such capatility in its scope which I
> think it too heavy for Mistral to mange such things by itself. So, FaaS
> will be the right answer in this case, and it will also be add-on part to
> empower Mistral to do more things.
>> The second one is Lambda + the API Gateway, which allows you to have web
>> requests act as triggers, so that you can effectively treat it as a PaaS
>> and build an entire web app by stringing together Lambda functions and the
>> various other services (S3, DynamoDB, &c.). On the face of it this sounds
>> to me like a gimmicky way of deploying an unmaintainable mess. Naturally
>> this is the one receiving all of the attention, which shows how much I know
> I also don't think this one is attractive to me, Lambda is especially
> powerful when it's used together with other AWS services(S3,
> DynamoDB, Kinesis Streams, etc).
>> I definitely don't think we should try to reimplement this from scratch
>> in OpenStack. IMHO if we're going to add FaaS capabilities we should re-use
>> some existing project (like OpenWhisk), even if we have to write our own
>> native API over the top of it.
>> The things we'd really want it to do would be:
>> * Authenticate against Keystone,
>> * Provide Keystone credentials for the user-supplied functions it runs to
>> access (probably using Keystone trusts), and
>> * Connect to existing OpenStack sources of events, which hopefully means
>> Zaqar queues
>> Which sounds challenging to integrate with an existing standalone
>> project, though still not as bad as writing an equivalent from scratch.
>> TBH I think the appeal, at least for the FaaS-as-a-PaaS (aka #serverless)
>> crowd, is going to be pretty limited until such time as we have an
>> equivalent of DynamoDB in OpenStack. (i.e. no time soon, since the
>> MagnetoDB project is goneburger.) The idea of FaaS is to make the unit of
>> compute power that you're paying for (a) as fine-grained as possible, and
>> (b) scalable to infinity. Swift provides the same thing for storage
>> (Nova:FaaS::Cinder:Swift). What we don't have is the equivalent for a
>> database, there's only Trove where you're paying for a VM-sized chunk at a
>> minimum and scaling up in units of VM-sized chunks until you reach the
>> limit of how many VMs can communicate with each other and still get any
>> work done. Not many web apps can get by without a database, so that largely
>> negates the purpose to my mind, since the database will likely both
>> dominate costs at the low end and put the upper limit on scale at the high
> Yeah, I agree with you that more things are needed so that FaaS-like
> stuff could be used appropriately and ideally, we can't get everything
> ready on day 1, that's how we do things, from simple to complex, isn't
>>  https://www.openstack.org/videos/video/building-self-healing
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscrib
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev