Open Stack

On 10/03/17 21:34, Clint Byrum wrote:
>> (BTW I proposed a workaround for Magnum/Kuryr at the PTG by using a
>> pre-signed Zaqar URL with a subscription triggering a Mistral workflow,
>> and I've started working on a POC.)
>>
> What triggers the boot to kick over the bucket full of golf balls
> though?

It's inside the workflow definition but seriously, I'll be glad when 
people stop making these kinds of comments.

I'm the first person to say that ideally I think we should only need to 
involve Zaqar when the cloud needs to talk to the application, and that 
the application should have the credentials it needs to talk to the 
cloud directly using its APIs.

Notwithstanding that, every application is a special snowflake and there 
a plenty of reasons for applications to want to plug in their own logic 
between cloud services. Mistral is the obvious way to do that. It'd be 
nice to think we could get to a point of talking about two OpenStack 
services integrating with each other using the exact same public APIs 
that they provide to applications and people would just assume that it 
works (or raise bugs) instead of breaking out the Rube Goldberg jokes.

FWIW in AWS it's routine for SNS notifications of events in the cloud to 
trigger Lambda functions that can then make API calls: 
http://docs.aws.amazon.com/lambda/latest/dg/invoking-lambda-function.html#supported-event-source-sns

- ZB