Tuesday, 2016-04-19

openstackgerritchenying proposed openstack/smaug: Add fullstack test to smaug  https://review.openstack.org/30699601:53
openstackgerritsmile-luobin proposed openstack/smaug: The resource graph walker listener  https://review.openstack.org/28757202:51
openstackgerritchenying proposed openstack/smaug: Add name property to protectable instances model  https://review.openstack.org/30208603:18
openstackgerritsmile-luobin proposed openstack/smaug: Implement HeatTemplate for restore  https://review.openstack.org/30754903:37
openstackgerritxiangxinyong proposed openstack/smaug-dashboard: [Checkpoints] Submit index view function  https://review.openstack.org/30757106:18
openstackgerritchenying proposed openstack/smaug: Add show protectables instance endpoint  https://review.openstack.org/30214406:19
openstackgerritxiangxinyong proposed openstack/smaug-dashboard: [Checkpoints] Submit index view function  https://review.openstack.org/30757206:22
*** yinweiishere has quit IRC06:22
*** yinweiishere has joined #openstack-smaug06:23
*** yuval has joined #openstack-smaug06:38
*** yuval is now known as Guest6063506:38
*** Guest60635 has quit IRC06:38
*** yuval_ has joined #openstack-smaug06:39
*** yuval_ is now known as yuval06:40
openstackgerritchenying proposed openstack/smaug: Add a field parameters to resource plans  https://review.openstack.org/30273006:47
*** saggi has joined #openstack-smaug08:34
chenzengyuval:are you there? how are you?08:38
chenzengyuval:if you have time, please review my patche:https://review.openstack.org/#/c/282263/, i hope it can be merged this week. thanks.08:41
openstackgerritsmile-luobin proposed openstack/smaug: Enable lease checking for checkpoint  https://review.openstack.org/29922811:49
openstackgerritxiangxinyong proposed openstack/smaug-dashboard: [Operation Logs] Submit index view function  https://review.openstack.org/30772911:52
openstackgerritchenying proposed openstack/python-smaugclient: Add a field parameters to resource plans  https://review.openstack.org/30773611:58
openstackgerritsmile-luobin proposed openstack/smaug: Store ResourceGraph and Plan in checkpoint  https://review.openstack.org/30773712:00
yuvalping yinweiishere yinwei_computer12:28
*** zengchen has joined #openstack-smaug13:51
*** chenying_ has joined #openstack-smaug13:55
zengchenyuval:are you there?13:56
*** yinweimac has joined #openstack-smaug13:57
*** xiangxinyong456 has joined #openstack-smaug13:58
yuvalzengchen: yes13:59
*** pzchen has joined #openstack-smaug14:00
*** zhonghua-lee has joined #openstack-smaug14:00
zengcheni have seen you comments. thanks.14:01
yuval:)14:01
zengchenbut i think we have not reached an agreements about the logs.14:01
zengchenWhy should write log before sending it to thread pool. Because we don't want to lose the operations which are still in the queue when the Operation Engine service crashes. we will resume them when the service restarts14:02
yuvallet discuss that after the meeting?14:02
yuval(in #openstack-meeting)14:02
zengchenok14:03
zengchenyuval:can we discuss about the logs now?14:10
yuvalin the meeting channel or here?14:10
yuvalzengchen: ?14:11
zengchenhere14:11
yuvalone second14:11
zengchenok14:11
yuvalitem in meeting is important14:11
zengchenok14:11
*** pzchen has quit IRC14:22
*** pzchen has joined #openstack-smaug14:40
zengchenyuval:can we talk now?14:48
yuvalyes14:48
zengchenWhy should write log before sending it to thread pool. Because we don't want to lose the operations which are still in the queue when the Operation Engine service crashes. we will resume them when the service restarts14:49
zengchenthe logs are used to resume the operations.14:49
zengchenwe can not ignore any operations.14:50
yuvalI agree that we need to update the scheduled operation log to 'started' only when the actual operation has begun14:52
yuvalBut I think executors is not the right place for it14:53
*** yinweimac has quit IRC14:54
zengchenwe have only two component, one is trigger, the other is executor.14:54
yuvalmaybe we can create the log when the scheduled operation is created, with a state of 'waiting for run' (or something like that), and have the operation itself update to 'started' when the it begins14:54
yuvalAll: you can join the Trello board: https://trello.com/invite/b/Sudr4fKT/826e3dcffc7259b1447d4ecc448c1a45/smaug14:56
zengcheni think it is a litle complex. when the operation is triggered, one log is generated.14:57
zengcheni think the design now is more clear.14:57
yuvalI take back what I said. If we create a log when the scheduled operation is registerd, once it is triggered, we will have to create another one. not good.14:59
*** dell_ has joined #openstack-smaug15:01
xiangxinyongyuval: i join it15:01
xiangxinyongyuval: the trello15:01
yuvalxiangxinyong: great :)15:01
*** dell_ is now known as zengchenn15:02
yuvalzengchen: here is another idea15:03
zengchennyuval:yes15:04
*** zengchen has quit IRC15:04
yuvalzengchenn: 1 sec15:04
zengchennyuval:ok15:04
yuvalhow about creating the log in the beginning of the Operation.execute method?15:05
yuvalOperation.execute will be something like:15:05
yuval1. create log15:06
yuval2. call self._execute (which every operation implements)15:06
yuval3. set log as finished15:06
yuval-----15:06
zengchennwe have stored the operations in the queue, so there is the risk to lose the operation if we don't write log first.15:08
yuvalI'll be back in a few minutes15:08
*** chenying_ has quit IRC15:09
yuval(about 10-15)15:09
*** yuval has quit IRC15:09
*** xiangxinyong456 has quit IRC15:09
zengchennyuval:sorry, i will go to sleep. if you have any good ideas, please leave message to me. thanks.15:12
*** zengchenn has quit IRC15:12
*** yuval has joined #openstack-smaug15:25
yuvalping ChanServ15:25
yuvalping chenzeng15:25
yuvalping chenzeng15:26
*** yuval has quit IRC15:28
*** pzchen has quit IRC15:29

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