Wednesday, 2016-10-12

*** Yumeng has quit IRC00:09
*** hvprash has quit IRC00:13
*** thorst has joined #openstack-watcher01:04
*** thorst has quit IRC01:22
*** Kevin_Zheng has joined #openstack-watcher01:33
*** thorst has joined #openstack-watcher01:58
*** Guest50630 has quit IRC02:03
*** thorst has quit IRC02:03
*** zigo has joined #openstack-watcher02:05
*** zigo is now known as Guest5942702:06
*** yuanying has quit IRC02:48
*** yuanying has joined #openstack-watcher02:58
*** yuanying has quit IRC03:02
*** odyssey4me has quit IRC03:14
*** odyssey4me has joined #openstack-watcher03:15
*** yuanying has joined #openstack-watcher03:30
*** yuanying has quit IRC03:33
*** licanwei has joined #openstack-watcher03:35
*** yuanying has joined #openstack-watcher03:36
*** yuanying has quit IRC03:45
*** yuanying has joined #openstack-watcher03:49
*** hvprash has joined #openstack-watcher04:02
*** gabor_antal_ has joined #openstack-watcher05:35
*** gabor_antal has quit IRC05:37
*** dtardivel has joined #openstack-watcher07:07
*** vincentfrancoise has joined #openstack-watcher07:23
*** Guest59427 is now known as zigo07:33
*** acabot has joined #openstack-watcher07:37
*** alexchadin has joined #openstack-watcher07:55
*** Yumeng has joined #openstack-watcher08:06
*** alexchad_ has joined #openstack-watcher08:15
*** alexchadin has quit IRC08:18
*** befreax has joined #openstack-watcher08:48
*** befreax is now known as tmetsch08:49
*** alexchad_ has quit IRC09:01
*** alexchadin has joined #openstack-watcher09:02
acabotweekly meeting starts on #openstack-meeting-409:03
*** alexchad_ has joined #openstack-watcher09:05
*** alexchad_ is now known as alexchadin_09:05
vincentfrancoisealexchadin: hi09:06
*** alexchadin has quit IRC09:06
vincentfrancoisealexchadin: just as an FYI, I'll try to merge your service BP before EOD since it already has a +209:07
alexchadin_vincentfrancoise: nice to hear:)09:10
alexchadin_jed56: ping09:37
*** alexchadin_ is now known as alexchadin09:46
jed56alexchadin: hi10:05
alexchadinjed56: how are you?:)10:05
jed56very well and you ?10:07
alexchadinI'm fine10:08
alexchadinI think that we need to save action weights, maybe rename it to the priorities10:09
jed56I have to go sorry10:09
jed56Where do you want to store the priorities ?10:10
alexchadinwe can store it in the action table10:10
*** alexchadin has quit IRC10:23
*** alexchadin has joined #openstack-watcher11:38
*** thorst has joined #openstack-watcher11:47
vincentfrancoisehi alexchadin11:55
alexchadinhi vincentfrancoise11:55
vincentfrancoisejed56 is busy but kind of followed the debate11:56
vincentfrancoisealexchadin: so I'll try to answer your questions ;)11:56
alexchadinI think, that we don't need next field (action table) anymore11:57
vincentfrancoiseI was wondering: why you were willing to store the weights?11:57
alexchadinwhat if some strategy would want to set to one of migration action weight 2?11:58
vincentfrancoiseso your problem is more about being able to select a specific planner for a specific strategy right?11:59
vincentfrancoiseand pass some parameters down to it11:59
alexchadintake a look12:00
alexchadinthis is part of proposed changes12:00
vincentfrancoisedo not forget that the weight-based planner is only one of the possible implementations for a planner12:02
vincentfrancoiseso the problem I see with the priority is that it is too specific12:03
alexchadintoo specific? can you describe what you mean?12:04
vincentfrancoiseso first off, I would argue that planner parameters should be put into some parameters sub structure like we do between the audit and the strategy12:04
vincentfrancoiseby specific I mean that you already assume that we will be using the default planner even though it might not be the case12:05
*** tmetsch has quit IRC12:06
alexchadinok, we can leave weights to load them from conf12:07
vincentfrancoiseI agree, it's easier for now12:07
alexchadinthen we still need map between action types and weight12:07
vincentfrancoiseand it's not really necessary for you to complete this blueprint12:08
alexchadinis it ok?12:08
vincentfrancoisethat mapping already exist I think12:08
alexchadinyes, it is exist:)12:08
vincentfrancoiseso yeah it should stay12:09
alexchadinI propose to name it priorities12:09
alexchadinit makes more sense12:09
vincentfrancoisethe parameters thing is probably a different blueprint that we will probably want in the future12:09
vincentfrancoiseit's already renamed as priority in the code so yeah12:10
alexchadinHave you seen changes in workflow?12:11
alexchadinI mean, the diagram12:11
vincentfrancoiseyeah but let me re-read it so I make sure I understand it12:11
openstackgerritMerged openstack/watcher: Stop adding ServiceAvailable group option
openstackgerritMerged openstack/watcher: Updated from global requirements
vincentfrancoisejust to make sure I understand the "node" field you want to introduce: what defines the node name you will put in it?12:14
vincentfrancoiseI mean, what does it refer to?12:14
alexchadinIt may comes from source_node for migration type or resource_id for change_node_state12:16
alexchadinThis is the node the action is related to12:16
vincentfrancoiseyeah but where do you create the node you refer to and how does it get its name?12:17
alexchadinWe add value to the node column (action table) at the planner layer12:19
alexchadinthis is just compute node12:20
vincentfrancoiseso it's not a graph node12:20
vincentfrancoiseit's a compute node12:20
vincentfrancoiseok so that was not clear at all for me12:21
alexchadinseems need to rename Node to ComputeNode12:21
vincentfrancoiseyeah but my problem will be the following then?12:22
vincentfrancoisewhat do we do in the future we we deal with, say, a storage model or a network model?12:22
vincentfrancoisewe cannot hardcode a compute_node field in the action table12:22
alexchadinI meant to change Node in the Graph the ComputeNode12:23
alexchadinto the*12:24
alexchadinBTW, any actions we do related to the resources, that are placed on one of the nodes, compute or network or storage12:25
vincentfrancoiseok, let me try to explain how I understand it to see if that's what you meant12:26
vincentfrancoiseThe action table will not contain a "next" field anymore12:26
vincentfrancoiseinstead we add a "node" field12:26
vincentfrancoisewhich will reference the parent action (via its resource_id or its UUID/ID ?)12:27
alexchadinIt will just contain Node Name12:27
alexchadinfor example, compute112:28
vincentfrancoiseIMHO, it's better to reference it via a nullable foreign key on another action.12:28
vincentfrancoiseso the Main Flow's top-level action will have no "node" set12:30
vincentfrancoisebut all the subsequent actions will have something in it12:30
vincentfrancoisewhat do you think?12:31
alexchadinyou want to reference actions to each other?12:32
alexchadinthen where we will store Node Name?:)12:33
alexchadinlet me think12:36
vincentfrancoiselet me think about it too12:37
dtardivelalexchadin: While talking with vincentfrancoise, could you have a quick look on and set +2/+1 if it's ok for you. Thx ;)12:38
alexchadindtardivel: oh, great commit!12:38
dtardivelalexchadin: validated on my devstack !!!12:39
alexchadindtardivel: Need to create sticker: Trust me, it works on devstack12:39
vincentfrancoisealexchadin: hahaha12:39
*** alexchadin has quit IRC12:42
*** alexchadin has joined #openstack-watcher12:42
openstackgerritMerged openstack/watcher: Added composite unique name constraints
openstackgerritMerged openstack/python-watcherclient: Add service support
alexchadinNeed to rebase:)12:49
openstackgerritAlexander Chadin proposed openstack/watcher: Add service supervisor
openstackgerritAlexander Chadin proposed openstack/watcher: Add service object to the watcher_db_schema
alexchadinvincentfrancoise: We can get actions by node name and order them respecting the priorities.13:01
alexchadinvincentfrancoise: It will be done in workflow engine13:02
alexchadinvincentfrancoise: then we don't need to reference them to each other13:02
*** alexchadin has quit IRC13:12
openstackgerritMerged openstack/watcher: Add service supervisor
*** michaelgugino has joined #openstack-watcher14:17
*** brunograz has joined #openstack-watcher14:43
*** jimbaker has joined #openstack-watcher15:20
acabotbrunograz : hello Bruno15:25
brunograzHi acabot15:25
acabotbrunograz : we will soon merge a template to write doc strategy in Watcher
brunograzacabot: we have been disconnected to IRC for a while :) - Apols for that15:26
acabotbrunograz : no pb15:26
acabotbrunograz : would it be possible that you update the doc for vm_workload_consolidation according to this template ?15:27
brunograzOk, I see now. we will have a look on this and revert back to you15:27
brunograzis there any deadline for this?15:27
acabotI'd really like to have a clear doc for each strategy available in Watcher before the summit in 2 weeks15:28
brunograzacabot: we will try to make it by then ;)15:28
acabotbefore end of next week if possible, I think its pretty straightforward if you know the strategy15:28
acabotthanks a lot15:28
acabotbrunograz : will you attend the summit ?15:30
brunograznps - and sorry again for being a bit disconnected15:30
brunograzacabot:  yes - myself and Sean will attend15:30
acabotok great15:30
brunograzbut we are not sure if we can make it for the fishbowl session15:31
acabotbrunograz : if you plan to attend watcher sessions, here is the agenda
brunograzoh great15:31
brunograzthanks :)15:32
*** thorst is now known as thorst_afk16:04
*** thorst_afk is now known as thorst17:14
*** michaelgugino has quit IRC17:14
*** michaelgugino has joined #openstack-watcher17:28
*** dtardivel has quit IRC18:34
*** Kevin_Zheng has quit IRC18:59
*** Kevin_Zheng has joined #openstack-watcher19:02
openstackgerritPrashanth Hari proposed openstack/watcher-specs: Define grammar for workload characterization
*** hvprash_ has joined #openstack-watcher19:45
*** hvprash_ has quit IRC19:50
*** thorst has quit IRC21:05
*** thorst has joined #openstack-watcher21:11
*** brunograz_ has joined #openstack-watcher21:12
*** thorst has quit IRC21:16
*** zigo_ has joined #openstack-watcher21:17
*** odyssey4me_ has joined #openstack-watcher21:17
*** odyssey4me has quit IRC21:18
*** odyssey4me_ is now known as odyssey4me21:18
*** brunograz has quit IRC21:19
*** licanwei has quit IRC21:19
*** zigo has quit IRC21:19
*** mestery has quit IRC21:23
*** kamtamtun has quit IRC21:23
*** tkaczynski has quit IRC21:23
*** jimbaker has quit IRC21:24
*** mestery has joined #openstack-watcher21:28
*** kamtamtun has joined #openstack-watcher21:28
*** tkaczynski has joined #openstack-watcher21:28
*** zigo_ is now known as zigo21:28
*** michaelgugino has quit IRC21:31
*** thorst has joined #openstack-watcher21:45
*** thorst has quit IRC21:49
*** thorst has joined #openstack-watcher21:55
*** thorst has quit IRC22:00
*** jimbaker has joined #openstack-watcher22:49
*** jimbaker has quit IRC23:00
*** jimbaker has joined #openstack-watcher23:15

Generated by 2.14.0 by Marius Gedminas - find it at!