[openstack-dev] [Heat][Zaqar] Integration plan moving forward
Flavio Percoco
flavio at redhat.com
Fri Sep 19 09:37:08 UTC 2014
On 09/18/2014 11:51 AM, Angus Salkeld wrote:
>
> On 18/09/2014 7:11 PM, "Flavio Percoco" <flavio at redhat.com
> <mailto:flavio at redhat.com>> wrote:
>>
>> Greetings,
>>
>> If I recall correctly, Heat was planning to adopt Zaqar regardless of
>> the result of the graduation attempt (please correct me if I'm wrong).
>> Based on this assumption, I'd like to start working on a plan forward to
>> make this integration happen.
>>
>> So far, these are the use cases I've collected from past discussions:
>>
>> * Notify heat user before an action is taken, and after - Heat may want
>> to wait for a response before proceeding - notifications not
>> necessarily needed and signed read-only queues might help, but not
>> necessary
>> * For integrating with user's tools
>> * Monitoring
>> * Control surface
>> * Config management tools
>> * Does not require notifications and/or read-only/signed queue
> endpoints
>> *[These may be helpful, but were not brought up in the discussion]
>> * Subscribe to an aggregate feed of interesting events from other
>> open-stack components (such as Nova)
>> * Heat is often deployed in a different place than other
>> components and doesn't have access to the AMQP bus
>> * Large deployments consist of multiple AMQP brokers, and there
>> doesn't seem to be a nice way to aggregate all those events [need to
>> confirm]
>> * Push metadata updates to os-collect-config agent running in
>> servers, instead of having them poll Heat
>>
>>
>> Few questions that I think we should start from:
>>
>> - Does the above list cover Heat's needs?
>> - Which of the use cases listed above should be addressed first?
>
> IMHO it would be great to simply replace the event store we have
> currently, so that the user can get a stream of progress messages during
> the deployment.
Could you point me to the right piece of code and/or documentation so I
can understand better what it does and where do you want it to go?
Thanks for the feedback,
Flavio
--
@flaper87
Flavio Percoco
More information about the OpenStack-dev
mailing list