Friday, 2019-08-16

*** ricolin has joined #heat00:58
*** mhen has quit IRC01:13
*** spsurya has joined #heat01:14
*** ramishra has joined #heat01:51
*** ramishra has quit IRC03:30
*** ramishra has joined #heat03:39
*** skramaja has joined #heat04:41
*** zaneb has quit IRC05:04
*** zbitter has joined #heat05:04
*** e0ne has joined #heat05:13
*** e0ne has quit IRC05:27
*** jtomasek has joined #heat05:36
*** zhurong has joined #heat06:12
openstackgerritlidong proposed openstack/heat master: Firewall creation failed due to "INACTIVE"  https://review.opendev.org/67638406:29
*** mhen has joined #heat06:34
mhenhello, can somebody tell me how Heat aggregates the events for stacks?06:34
mhenis it simply polling the APIs (Nova, Cinder etc.) in a regular interval and recording the states of individual resources?06:35
ramishramhen: those are heat events and not polled from other services, we keep a event log in the database and write to it at different times in the process of resource actions07:20
ramishraif you're talking about heat events api07:22
*** jtomasek has quit IRC07:25
mhenramishra, thanks, yes I'm talking about this API07:28
mhenhow does Heat determine the state of resources if it is not polling the other APIs?07:28
ramishrayes it does api calls for getting the status of the async resource operations, if that's what you mean07:31
mhenwhat I'm wondering is, let's say a Nova server resource transitions between multiple states A > B > C in the process of a task on that resource, how is Heat made aware of each transition?07:40
ramishraWe don't keep track of all nova server states, we've basically have four states(status) for heat resources INIT, IN_PROGRESS, COMPLETE, FAILED, we translate nova server states to heat resource states07:45
ramishrahttps://github.com/openstack/heat/blob/master/heat/engine/resource.py#L969-L986 we keep polling for the status (check_*_complete method diff for every resource), if there is an error we mark it as FAILED07:47
ramishrahttps://github.com/openstack/heat/blob/master/heat/engine/resources/openstack/nova/server.py#L890-L896 for nova server create07:48
ramishrahttps://docs.openstack.org/heat/latest/developing_guides/pluginguide.html#life-cycle-handler-methods should help you understand the lifecycle07:49
mhenramishra, I see now. That has been most helpful, thanks a lot!07:51
*** e0ne has joined #heat07:52
ramishrajust a correction there are 3 statuses (IN_PROGRESS, COMPLETE, FAILED) INIT is an action  like CREATE/UPDATE/DELETE not an status07:53
mhenramishra, alright, thanks for the clarification :)08:01
*** ivve has joined #heat08:07
openstackgerritJens Harbott (frickler) proposed openstack/heat master: Stop requiring an identity admin endpoint  https://review.opendev.org/67577810:34
*** jtomasek has joined #heat11:03
*** gfidente has joined #heat11:04
*** skramaja has quit IRC12:03
*** zbitter is now known as zaneb13:23
*** zaneb has quit IRC13:55
*** hjensas has quit IRC13:56
*** cliffparsons has quit IRC14:10
*** bnemec is now known as beekneemech14:48
*** ivve has quit IRC14:57
*** ramishra has quit IRC15:14
*** e0ne has quit IRC15:58
*** bnemec has joined #heat16:19
*** beekneemech has quit IRC16:19
*** bnemec is now known as beekneemech16:20
*** beekneemech has quit IRC16:32
*** bnemec has joined #heat16:35
*** bnemec has quit IRC16:44
*** bnemec has joined #heat16:45
*** gfidente has quit IRC16:48
*** ivve has joined #heat16:49
*** ivve has quit IRC16:49
*** bnemec has quit IRC17:02
*** bnemec has joined #heat17:03
*** ivve has joined #heat17:09
*** bnemec has quit IRC17:14
*** bnemec has joined #heat17:15
*** bnemec has quit IRC17:31
*** bnemec has joined #heat17:34
*** bnemec has quit IRC17:40
*** bnemec has joined #heat17:42
*** jtomasek has quit IRC17:53
*** ivve has quit IRC18:07
*** ricolin has quit IRC18:24
*** zaneb has joined #heat18:29
*** jcoufal has joined #heat18:39
*** jcoufal has quit IRC19:01
*** bnemec is now known as beekneemech20:14
*** spsurya has quit IRC22:23

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!