Monday, 2017-03-13

*** catintheroof has joined #openstack-tricircle00:26
*** catintheroof has quit IRC00:26
*** catintheroof has joined #openstack-tricircle00:26
*** dongfeng has joined #openstack-tricircle00:36
*** dongfeng1 has joined #openstack-tricircle00:37
*** dongfeng1 has quit IRC00:39
*** dongfeng2 has joined #openstack-tricircle00:40
*** dongfeng has quit IRC00:41
*** dongfeng1 has joined #openstack-tricircle00:41
*** dongfeng2 has quit IRC00:44
*** dongfeng1 is now known as dongfeng00:45
*** Kevin_Zheng has joined #openstack-tricircle01:41
*** dongfeng has quit IRC01:46
*** dongfeng has joined #openstack-tricircle01:46
*** joehuang has joined #openstack-tricircle01:50
*** dongfeng has quit IRC01:56
*** dongfeng has joined #openstack-tricircle01:58
*** longxiongqiu has joined #openstack-tricircle02:01
*** catintheroof has quit IRC02:18
joehuangxiuqiong02:32
joehuang,are you online?02:32
*** gongysh has joined #openstack-tricircle02:33
longxiongqiuyes02:41
*** catintheroof has joined #openstack-tricircle02:45
*** catintheroof has quit IRC02:45
*** catintheroof has joined #openstack-tricircle02:45
joehuangfor QoS, asynchrounus job should deal with multiple pod but not only single pod, it only one pod,02:55
joehuangit's not necessary to using async. mechnism if there is only one pod02:56
joehuangupdate_qos_policy(self,ctxt,policy_id,pod_id)02:56
joehuangcreate_qos_policy(self,ctxt,policy_id,pod_id)02:57
longxiongqiuyou mean if we just need deal with only one pod, we don't use async mechinsm?03:00
joehuangtricircle is to deal with multiple OpenStack instacnes, QoS will be associated to the network which may spread into multiple pods, so aysnc mechnism is to deal with multiple pod's processing03:16
joehuangfor single pods, no additional value for tricircle03:16
*** catintheroof has quit IRC03:37
longxiongqiuOk, one qos async job will deal with multiple pods, is it right?03:50
joehuangyes03:51
*** Yipei has joined #openstack-tricircle04:18
*** longxiongqiu has quit IRC04:51
*** longxiongqiu has joined #openstack-tricircle06:17
longxiongqiuUnderstand, i will make some changes06:22
*** dongfeng has quit IRC06:34
*** dongfeng has joined #openstack-tricircle06:34
*** dongfeng has quit IRC06:35
*** longxion_ has joined #openstack-tricircle06:40
*** longxiongqiu has quit IRC06:43
*** dongfeng has joined #openstack-tricircle06:54
*** Yipei_ has joined #openstack-tricircle06:58
*** Yipei has quit IRC07:02
*** longxiongqiu has joined #openstack-tricircle07:12
*** longxion_ has quit IRC07:12
dongfenghello, zhiyuan or joe, are you online? according to the HTTP PUT method, the put request must  have a request body, but for job redo request, we use the PUT method, but it doesn't need request body, all values are unchanged except the job status and job timestamp, but these two could be generated from internal. I plan to add the request body to job request, how do you think?07:12
*** longxion_ has joined #openstack-tricircle07:51
*** longxiongqiu has quit IRC07:55
*** longxiongqiu has joined #openstack-tricircle07:56
joehuanghello, dongfeng, I found that sycn operation should return 201 if succeed07:56
joehuangin creation07:57
dongfengbut job api is async07:57
joehuangit 20207:57
joehuang202 is for asycn creation07:58
dongfengyes, so i returned 20207:58
joehuangok07:58
*** longxio__ has joined #openstack-tricircle07:59
dongfengi have updated it. i dont's modify the request for redo api.07:59
*** longxion_ has quit IRC08:00
*** longxiongqiu has quit IRC08:03
*** longxion_ has joined #openstack-tricircle09:27
*** longxio__ has quit IRC09:31
*** joehuang has quit IRC09:47
*** gongysh has quit IRC10:36
*** longxiongqiu has joined #openstack-tricircle10:49
*** longxio__ has joined #openstack-tricircle10:51
*** longxion_ has quit IRC10:53
*** longxiongqiu has quit IRC10:54
*** gongysh has joined #openstack-tricircle11:19
*** gongysh has quit IRC11:23
*** longxiongqiu has joined #openstack-tricircle11:49
*** longxio__ has quit IRC11:52
*** gongysh has joined #openstack-tricircle12:03
*** longxiongqiu has quit IRC12:15
*** longxiongqiu has joined #openstack-tricircle12:20
*** longxiongqiu has quit IRC13:02
*** Yipei_ has quit IRC13:23
*** longxiongqiu has joined #openstack-tricircle13:30
*** longxiongqiu has quit IRC14:57
*** longxiongqiu has joined #openstack-tricircle14:58
*** gongysh has quit IRC14:59
*** longxiongqiu has quit IRC15:09
*** catintheroof has joined #openstack-tricircle17:25
-openstackstatus- NOTICE: restarting gerrit to address performance problems17:45
*** catinthe_ has joined #openstack-tricircle20:56
*** catintheroof has quit IRC20:58
*** catintheroof has joined #openstack-tricircle21:31
*** catinthe_ has quit IRC21:35
*** catintheroof has quit IRC22:13
*** catintheroof has joined #openstack-tricircle22:14
*** catintheroof has quit IRC22:14
*** catintheroof has joined #openstack-tricircle22:15
*** catintheroof has quit IRC22:40

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