Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

Hi. A colleague and i have been experimenting and prototyping an implementation for listening for ampq notifications and kicking off mistral workflows as a mistral service. This is for a use case that is different than discussed here, but seems like it might be useful to this use case as

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

> On 12 Nov 2015, at 00:11, Clint Byrum wrote: > > Excerpts from Zane Bitter's message of 2015-11-11 09:43:43 -0800: >> 1. Keystone (or some Rabbit->Zaqar proxy service reading notifications >> from Keystone) sends "new federated user" notification out via Zaqar. >> 2.

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

On 11/11/15 13:11, Clint Byrum wrote: Excerpts from Zane Bitter's message of 2015-11-11 09:43:43 -0800: 1. Keystone (or some Rabbit->Zaqar proxy service reading notifications from Keystone) sends "new federated user" notification out via Zaqar. 2. Mistral picks up the message and checks policy

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

Excerpts from Renat Akhmerov's message of 2015-11-12 07:52:42 -0800: > > > On 12 Nov 2015, at 00:11, Clint Byrum wrote: > > > > Excerpts from Zane Bitter's message of 2015-11-11 09:43:43 -0800: > >> 1. Keystone (or some Rabbit->Zaqar proxy service reading notifications > >>

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

questions) Subject: Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation On 11/11/15 13:11, Clint Byrum wrote: > Excerpts from Zane Bitter's message of 2015-11-11 09:43:43 -0800: >> 1. Keystone (or some Rabbit->Zaqar proxy service reading n

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

On 10/11/15 11:32, Adam Young wrote: On 11/10/2015 10:28 AM, Renat Akhmerov wrote: On 09 Nov 2015, at 20:43, Adam Young wrote: On 11/06/2015 06:28 PM, Tim Hinrichs wrote: Congress allows users to write a policy that executes an action under certain conditions. The

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

: Zane Bitter [zbit...@redhat.com] Sent: Wednesday, November 11, 2015 9:43 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation On 10/11/15 11:32, Adam Young wrote: > On 11/10/2015 10:28 AM, Renat Akhme

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

Excerpts from Zane Bitter's message of 2015-11-11 09:43:43 -0800: > 1. Keystone (or some Rabbit->Zaqar proxy service reading notifications > from Keystone) sends "new federated user" notification out via Zaqar. > 2. Mistral picks up the message and checks policy to see what should be > done. >

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

Excerpts from Wed, Nov 11, 2015 at 10:14 AM Clint Byrum wrote: > > But as Renat mentioned, the part about triggering Mistral workflows from > > a message does not yet exist. As Tim pointed out, Congress could be a > > solution to that (listening for a message and then starting

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

On 11/10/2015 10:28 AM, Renat Akhmerov wrote: On 09 Nov 2015, at 20:43, Adam Young wrote: On 11/06/2015 06:28 PM, Tim Hinrichs wrote: Congress allows users to write a policy that executes an action under certain conditions. The conditions can be based on any data