[openstack-dev] [tripleo] Zaqar messages standardization

Thomas Herve therve at redhat.com
Thu May 26 10:18:59 UTC 2016


On Thu, May 26, 2016 at 11:48 AM, Jiri Tomasek <jtomasek at redhat.com> wrote:
> On 05/25/2016 08:08 PM, Thomas Herve wrote:

>> Sorry for not responding earlier, but I have some inputs. In Heat we
>> publish events on Zaqar queue, and we defined this format:
>>
>>      {
>>              'timestamp': $timestamp,
>>              'version': '0.1',
>>              'type': 'os.heat.event',
>>              'id': $uuid,
>>              'payload': {
>>                  'XXX
>>              }
>>      }
>
>
> Thanks, it totally makes sense. So when I convert my example to your usage
> it looks like this:
>
> {
>     body: {
>         'timestamp': $timestamp,
>         'type': 'tripleo.validations.v1.run_validation',
>         'id': $uuid,
>         'payload': {
>             execution_id: '123123123',
>             validation_id: '123321'
>             ...
>          }
>     }
> }
>
> I am not sure whether to separate the version from type as it would become
> complicated to reconstruct the workflow name (at least for tripleo
> workflows).
> The most important is the 'type' as that is the key which we'd like to use
> on client to identify what action to take.

Looks great to me, thanks!

-- 
Thomas



More information about the OpenStack-dev mailing list