Wednesday, 2016-11-23

openstackgerritPrudhvi Rao Shedimbi proposed openstack/watcher: Implemented wacther decision engine config module  https://review.openstack.org/40100600:53
*** diga has quit IRC02:21
*** thorst has joined #openstack-watcher02:32
*** thorst has joined #openstack-watcher02:33
openstackgerritMerged openstack/puppet-watcher: Remove rabbitmq connection parameters  https://review.openstack.org/39524402:33
*** thorst has quit IRC02:40
*** thorst has joined #openstack-watcher02:41
*** thorst has quit IRC02:45
*** thorst has joined #openstack-watcher03:09
openstackgerritRong Han proposed openstack/watcher: Remove redundan lines.  https://review.openstack.org/40105003:14
openstackgerritRong Han proposed openstack/watcher: Solve some spelling mistakes.  https://review.openstack.org/39940203:23
*** jwcroppe has joined #openstack-watcher03:23
*** jwcroppe has quit IRC03:24
*** jwcroppe has joined #openstack-watcher03:24
*** jwcroppe has quit IRC03:24
*** jwcroppe has joined #openstack-watcher03:25
*** thorst has joined #openstack-watcher03:36
*** thorst has quit IRC03:37
openstackgerritbailin.zhang proposed openstack/watcher-specs: Fix a spelling error  https://review.openstack.org/40107206:09
*** michaelgugino has quit IRC06:23
*** Yumeng has joined #openstack-watcher06:31
*** Yumeng has quit IRC07:04
openstackgerritRong Han proposed openstack/watcher-specs: Support Description For Dynamic Action  https://review.openstack.org/40111107:50
*** diga has joined #openstack-watcher08:17
*** dtardivel has joined #openstack-watcher08:41
*** alexchadin has joined #openstack-watcher08:51
openstackgerritAlexander Chadin proposed openstack/watcher: Add periods input parameter  https://review.openstack.org/39953908:55
openstackgerritMerged openstack/watcher: Remove redundan lines.  https://review.openstack.org/40105008:58
openstackgerritMerged openstack/watcher: Solve some spelling mistakes.  https://review.openstack.org/39940208:58
acabothi guys, weekly meeting will start in 2 min on #openstack-meeting-408:59
openstackgerritMerged openstack/watcher: Fix inconsistent descriptions in docstring in action_plan.py  https://review.openstack.org/39984608:59
openstackgerritRong Han proposed openstack/watcher-specs: Support Description For Dynamic Action  https://review.openstack.org/40111109:00
*** diga has quit IRC09:02
alexchadindtardivel: hi!09:04
dtardivelhi alexchadin09:05
dtardivelwe are on meeting :)09:05
dtardivelcan you join us ?09:05
alexchadindtardivel: already09:06
dtardivelyep I see it :)09:07
*** diga has joined #openstack-watcher09:12
*** befreax has joined #openstack-watcher09:14
*** befreax is now known as tmetsch09:14
openstackgerritMerged openstack/watcher: Fix the wrong ref for 'Compute node'  https://review.openstack.org/39867309:41
*** diga_ has joined #openstack-watcher09:41
openstackgerritMerged openstack/watcher: Fix some typos in action.py & action_plan.py & audit.py  https://review.openstack.org/39893809:41
*** diga has quit IRC09:42
openstackgerritMerged openstack/python-watcherclient: Updated from global requirements  https://review.openstack.org/39862009:46
alexchadindtardivel: can we discuss planner improvements?09:47
dtardivelyep09:50
*** tmetsch is now known as befreax09:50
alexchadinAs you said here, disabling compute node is not linked action to the migration since we still can migrate instances after node is disabled https://review.openstack.org/#/c/385871/2/specs/ocata/approved/planner-storage-action-plan.rst@4009:52
alexchadinbut I agree, that we need mechanism to support 2 or more parents09:53
alexchadinin the future, since we don't have such type of action that will have some requirements09:53
alexchadinwe can store parents as list in database (json or jsonb in PostgreSQL, for example)09:54
dtardivelyes I think so09:56
*** alexchadin has quit IRC09:57
*** alexchad_ has joined #openstack-watcher09:57
alexchad_dtardivel: sorry for disconnecting09:57
alexchad_dtardivel: "yes I think so" - is it your last message?09:58
dtardivelyep09:58
alexchad_dtardivel: great:)09:59
dtardivelcan you add in your spec the new fields of actions ?10:02
dtardivelbased from https://github.com/openstack/watcher/blob/master/watcher/objects/action.py#L4410:03
dtardivelI did not understand why you said both BP should be merged together10:04
alexchad_dtardivel: you mean to remove first_action_id?10:04
alexchad_dtardivel: how will applier work without changes if we remove next fields also?10:05
alexchad_field*10:05
dtardivelIf in the first one, you update the Action data model, by introducing a new 'parents' field and you rewrite the planner algorithm to take into account this new way to store an action in Db, we should have no impact in the applier (the action plan built by the planner should be similar as before)10:08
dtardivelin other words, in db we will have new model, by but from Applier point of view, we will have same data structure with 'next' pointer. This is the proposal from vincentfrancoise to be able to split this BP in two parts.10:10
dtardivelso the new planner job will be to translate 'parents' link to 'next' links10:12
dtardiveli'm not familiar with this part of code.10:12
dtardivelDoes it make sense from your point of view ?10:13
alexchad_dtardivel: I'm exploring this part of code10:13
alexchad_dtardivel: give me a sec:)10:13
dtardivelyou have time for reflexion10:14
dtardivelIt's just a input10:14
dtardivelThe first part of the work will concern only the data model and the planner. The second part will concern the applier and the graph modelisation (and you can see from my previous comments that there will be lot of use cases to cover)10:17
dtardiveltake time to think about vincentfrancoise proposal :)10:17
alexchad_dtardivel: well, we have almost done our work with the first part10:17
alexchad_dtardivel: ok, I agree10:25
dtardivelIf you agree with our proposal, could you rewrite your pseudo code and the list of work items as well10:26
alexchad_https://github.com/openstack/watcher/blob/master/watcher/applier/default.py#L6010:26
alexchad_here we get list of actions10:26
dtardiveland also define exactly the scope of this spec :)10:26
alexchad_and we don't use 'next' field in applier10:26
dtardiveloh oh I see10:28
dtardivelin fact 'next' is used only by planner to built of ordered list of actions, named action plan.10:30
dtardivelSo if we remove 'next' and add 'parents' fielf, the action plan new algo should take into account the new field 'parents' to built the ordered action list. in our first implementation, 'parents' will have only a  unique action uuid10:32
dtardivelare you agree ?10:33
dtardivels/to built of/to build an10:33
*** pkoniszewski has quit IRC10:35
*** alexchad_ has quit IRC10:37
*** alexchadin has joined #openstack-watcher10:37
dtardivelhummm I read the code is 'next' field realy useful for now ?10:39
*** alexchadin has quit IRC10:42
*** pkoniszewski has joined #openstack-watcher10:44
*** danpawlik has joined #openstack-watcher10:54
openstackgerritOpenStack Proposal Bot proposed openstack/watcher: Updated from global requirements  https://review.openstack.org/40115211:05
*** diga_ has quit IRC11:48
*** exploreshaifali has joined #openstack-watcher11:50
*** openstackgerrit has quit IRC12:03
*** openstackgerrit has joined #openstack-watcher12:03
*** shaifali has joined #openstack-watcher12:12
*** exploreshaifali has quit IRC12:12
*** alexchadin has joined #openstack-watcher12:41
alexchadindtardivel: ping12:42
dtardivelalexchadin: pong13:14
alexchadinseems that 'next' field is used only in API13:14
alexchadinright?13:14
dtardivelyes. but I will need to clarify with jed5613:14
dtardivelI think the applier is not well implemented. It is confused for me now. For me the goal of the planner will be to build a graph of actions (the simple graph will be a linked chain of actions for now).13:17
dtardivelThe goal of the applier should be to to convert the action graph to something readable by the workflow engine used, i.e. taskflow for our default implementation .13:18
dtardivelright ?13:18
alexchadinright13:25
alexchadinso planner only creates linked list now13:25
alexchadinand save it to DB13:26
dtardivelI'm discussing with jed56. He implemented this part a long time ago.13:32
*** lamt has joined #openstack-watcher13:39
dtardivelalexchadin: jed56 confirm to me that this is a bug on applier side. it shoudl take into account 'next' field to find the next action.13:43
alexchadinwow13:43
dtardivelSo you're right, applier should be impected as well in the first bp13:43
alexchadinwell13:44
dtardivelso forget what I wrote later13:44
alexchadinSo we have to implement storage improvements and changes to applier13:45
dtardivelplanner will build a list of action (the action plan) chained by the 'parents' field. And applier should be able to handle 'parents' field to create task for engine workflow (taskflow). And we will limit the first bp to simple chained list used for now. right ?13:46
alexchadinhm13:47
alexchadinok13:48
*** alexchadin has quit IRC13:50
*** shaifali_ has joined #openstack-watcher13:53
*** shaifali has quit IRC13:57
*** thorst has joined #openstack-watcher14:08
*** thorst has quit IRC14:19
*** shaifali has joined #openstack-watcher14:22
*** thorst has joined #openstack-watcher14:22
*** shaifali_ has quit IRC14:25
*** thorst has quit IRC14:31
*** shaifali_ has joined #openstack-watcher14:35
*** shaifali has quit IRC14:37
*** shaifali_ has quit IRC15:00
*** thorst has joined #openstack-watcher15:05
sballe_can I get some +2 on https://review.openstack.org/#/c/397411/10? dtardivel15:11
sballe_acabot: ^^15:11
sballe_thx tp everybody who reviewed15:12
*** thorst has quit IRC15:12
*** thorst has joined #openstack-watcher15:16
*** thorst has quit IRC15:20
acabotsballe_ : I plan to review it tomorrow15:29
sballe_thx15:30
sballe_4am is just too early for me to attend the IRC meeting.15:30
sballe_I will read the minutes15:30
sballe_acabot:15:30
acabotno pb15:31
sballe_acabot: I should have the remaing two docs done really quickly now. I just didn;t want to have 3 docs in flight which would end up haveing similar comments across them15:40
acabotsballe_ : ok great15:44
sballe_All: pshedimb is looking for for reviews on https://review.openstack.org/#/c/400367/315:45
acabotdtardivel will review https://review.openstack.org/#/q/topic:bp/centralise-config-opts15:47
sballe_thx. pshedimb decided to commit smaller peices instead of all the code in one commit. Does that works for you or do you want it all in one commit?15:49
acabotno no please split the code15:50
sballe_ok good. that what he did15:50
*** thorst has joined #openstack-watcher16:38
*** thorst has quit IRC16:39
*** thorst has joined #openstack-watcher17:06
*** thorst_ has joined #openstack-watcher17:07
*** thorst has quit IRC17:11
*** thorst_ has quit IRC17:11
openstackgerritPrudhvi Rao Shedimbi proposed openstack/watcher: Implemented api config module  https://review.openstack.org/40036717:16
openstackgerritPrudhvi Rao Shedimbi proposed openstack/watcher: Implemented applier config module  https://review.openstack.org/40096917:17
openstackgerritPrudhvi Rao Shedimbi proposed openstack/watcher: Implemented wacther decision engine config module  https://review.openstack.org/40100617:17
pshedimbthanks sballe_ acabot17:17
pshedimbpushed in a few config options yest and will push in a few more today.17:18
openstackgerritPrudhvi Rao Shedimbi proposed openstack/watcher: Implemented api config module  https://review.openstack.org/40036717:24
openstackgerritPrudhvi Rao Shedimbi proposed openstack/watcher: Implemented applier config module  https://review.openstack.org/40096917:25
openstackgerritPrudhvi Rao Shedimbi proposed openstack/watcher: Implemented wacther decision engine config module  https://review.openstack.org/40100617:26
*** befreax has quit IRC18:53
*** dtardivel has quit IRC19:24
*** wootehfoot has joined #openstack-watcher21:15
*** thorst_ has joined #openstack-watcher21:47
*** thorst_ has quit IRC22:20
*** wootehfoot has quit IRC23:26
*** lamt has quit IRC23:43

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