Wednesday, 2016-09-07

*** thorst has quit IRC00:08
*** thorst has joined #openstack-watcher00:09
*** thorst has quit IRC00:17
openstackgerritDigambar proposed openstack/watcher-specs: automatic triggering audit
*** thorst has joined #openstack-watcher01:14
*** thorst has quit IRC01:16
*** thorst has joined #openstack-watcher01:16
*** thorst has quit IRC01:32
*** diga has quit IRC01:39
*** thorst has joined #openstack-watcher02:24
*** thorst has quit IRC02:29
*** thorst has joined #openstack-watcher02:48
*** thorst has quit IRC02:48
*** thorst has joined #openstack-watcher02:48
*** thorst has quit IRC04:43
*** thorst has joined #openstack-watcher04:45
*** thorst has quit IRC04:50
*** thorst has joined #openstack-watcher04:56
*** thorst has quit IRC05:00
*** openstackgerrit has quit IRC05:18
*** openstackgerrit has joined #openstack-watcher05:18
*** thorst has joined #openstack-watcher05:28
*** thorst has quit IRC05:29
*** thorst has joined #openstack-watcher05:32
*** thorst has quit IRC06:26
*** thorst has joined #openstack-watcher06:28
*** thorst has quit IRC06:28
*** thorst has joined #openstack-watcher07:00
*** thorst has quit IRC07:06
*** vincentfrancoise has joined #openstack-watcher07:34
*** thorst has joined #openstack-watcher07:36
*** thorst has joined #openstack-watcher08:01
*** thorst_ has joined #openstack-watcher08:10
*** thorst__ has joined #openstack-watcher08:10
openstackgerritVincent Françoise proposed openstack/watcher: Fixed flaky test due to notification issues
*** thorst has quit IRC08:12
*** thorst_ has quit IRC08:14
openstackgerritTomasz Kaczynski proposed openstack/watcher: Add documentation for Scoring Module
*** aspiers has joined #openstack-watcher08:23
*** thorst__ has quit IRC08:32
*** openstackgerrit has quit IRC08:34
*** openstackgerrit has joined #openstack-watcher08:34
*** thorst has joined #openstack-watcher08:34
*** thorst has quit IRC08:35
*** thorst has joined #openstack-watcher08:46
*** thorst has quit IRC08:49
*** diga has joined #openstack-watcher08:52
*** jimbaker has quit IRC09:01
digaacabot: Hi09:01
*** jimbaker has joined #openstack-watcher09:05
*** jimbaker has quit IRC09:05
*** jimbaker has joined #openstack-watcher09:05
vincentfrancoisediga: hi09:28
vincentfrancoisediga: I started reviewing your spec09:40
digavincentfrancoise: Hi09:46
digavincentfrancoise: Thx. Are we having meeting now ?09:46
digaor it is postponed ?09:47
vincentfrancoiseno I think it's at 14:00UTC09:47
vincentfrancoiseI am the one that will implement the watcher-notifications-ovo you are referring to in your blueprint09:48
digavincentfrancoise: okay09:48
vincentfrancoiseand so I was looking at the notification payloads you have put09:48
digaPlease check that, I just used those notifications payload what is used for contineous Audit09:49
vincentfrancoiseand it doesn't match the structure I intend to use although it's not official yet09:49
digaThat's fine, we can change it later on09:50
digaThis is just a reference I have put in there09:50
vincentfrancoiseYeah I see09:50
digaOnce your patch is up, I can update it09:51
vincentfrancoiseis there any reason for you to use notifications / event-driven logic instead of calling the RPC interface as in ?09:52
vincentfrancoiseIMHO, that would be simpler to do it like that09:53
vincentfrancoisediga: still here?09:59
*** thorst has joined #openstack-watcher10:00
*** thorst has quit IRC10:04
*** hanrong has left #openstack-watcher10:46
*** thorst has joined #openstack-watcher10:48
digavincentfrancoise: Hi11:00
sballe_gzhai: are you here?11:00
acabotdiga : vincentfrancoise is at lunch now, he will be back in an hout11:01
digaacabot: okay11:01
digaacabot: Hi, how are you ?11:01
acabotdiga : good thx and you ?11:03
digaacabot: Good!11:04
digaacabot: I have pushed updated patch for automatic_triggering11:04
digaacabot: take a look at it once you get time11:04
acabotyes I saw that vincent and alex already sent their comments11:05
acabotI will do it before the weekly meeting11:05
acabotsballe_ : do you know if gzhai has confirmed the meeting ?11:10
sballe_yes and I met with him last night and reconfirmed11:10
acabotgzhai : please ping me if you join the channel11:26
*** gzhai has joined #openstack-watcher11:34
acabotgzhai : hi11:36
acabothow are you ?11:36
acabotso whats going on on the test infra ?11:37
gzhaitest team installed base system.11:37
gzhaimonasca/watcher/ceilosca need extra work11:38
acabotdo you know which version of Watcher they install ?11:39
gzhaiI list all the related project. But any other install docs would be helpfule11:39
gzhaiI gave the ansible-watcher project, so I think he will install trunk version11:40
acabotany other install docs would be helpfull ? which one ?11:40
gzhaisballe_: are you there?11:40
acabotshe is taking care of her kids going to school11:41
acabotshe will be back in an hour11:41
gzhaiacabot: I have the access to the machines including KVM/PDU.11:43
acabotok so can you start using PKB ?11:45
acabotstarts VM on the infra11:45
acabotyou have to update the yaml file11:45
acabotdo you see what I mean ?11:45
gzhaiNot reproduce my last state. My environment crashed.11:46
acabotok if it can help we can give you a valid yaml file for PKB11:48
acabotwe need to know 2 things :11:48
acabotname of your compute nodes11:48
acabotname of the image you will use for basic testing (can be cirros or ubuntu or anything else)11:49
gzhaiwhere is the yaml file? I didn't see it when try it.11:53
*** alexchadin has joined #openstack-watcher11:54
acabotlet me check11:55
openstackgerritAntoine Cabot proposed openstack/watcher-specs: Add Ocata entry for specifications
acabotdid you use ?12:01
*** alexchadin has quit IRC12:04
*** alexchadin has joined #openstack-watcher12:05
*** acabot has quit IRC12:05
*** acabot has joined #openstack-watcher12:07
acabotsorry gzhai12:07
acabotdid you use to run PKB ?12:07
acabotok I just checked with dtardivel12:30
acabotthis version is the original PKB version12:30
acabotnot the one we have modified12:30
acabothe will push it in a private repo on docker hub12:31
acabotcould you create an account on ?12:31
acabotand give your login so that I can  add it to the repo12:32
gzhaiacabot: 1 min12:34
acabot"edwinzhai" does not exist12:39
*** diga has quit IRC12:40
acabotcan you log in docker hub ?12:40
acabotok can you access ?12:46
acabotnow you just need to run docker login on your pc12:47
acabotalexchadin : are you there ?12:51
alexchadinacabot: hi12:51
acabotI'm on
acabotand I dont really understand why we use int for host aggregates12:51
alexchadinCause we take ids from them12:52
alexchadinnot names12:52
acabotso you mean we dont use UUIDs for host_aggregates in Nova ?12:52
alexchadinthere is no uuids for host aggregates in nova12:52
vincentfrancoisealexchadin: could we use names?12:53
alexchadinvincentfrancoise: I don't think it is good idea cause nova operates ids in their API regarding host aggregates12:54
vincentfrancoisealexchadin: it's just that it might be a bit more user friendly this way12:55
alexchadinvincentfrancoise: I understand, but I'm not sure that names are uniques12:56
vincentfrancoiseand they seem to have a 'unique' constraint on them so that's why I'm asking12:56
vincentfrancoiseI just tried from horizon and I couldn't create a second one12:56
vincentfrancoisehere is the error message: The name "test" is already used by another host aggregate.12:56
*** thorst has joined #openstack-watcher12:57
alexchadinhm. There is no unique flag on Aggregate model in models.py12:57
vincentfrancoisebut if you prefer IDs only, that's fine by me12:57
vincentfrancoiseok so let's keep it simple with IDs only then12:57
alexchadinI think, we can use names in future12:58
vincentfrancoiseagree, put it in the alternatives section then please ;)12:58
alexchadinWe can extend our schema if we need so12:58
alexchadinvincentfrancoise: where?:)12:59
acabotalexchadin : I think you can add it into "other deployer impact"13:00
acabotstating that it would be easier to manager strings for host aggregates in the future13:00
alexchadinacabot: ah, ok13:01
*** jwcroppe has joined #openstack-watcher13:01
openstackgerritAlexander Chadin proposed openstack/watcher-specs: Change host aggregates id type to integer
alexchadinacabot, vincentfrancoise - take a look13:06
alexchadinvincentfrancoise: about watcherclient13:09
vincentfrancoisealexchadin: about the YAML format thing?13:09
alexchadinvincentfrancoise: yeap, json is a subset of yaml13:10
gzhaisballe_: online?13:10
alexchadinNote JSON is a subset of YAML 1.2. The JSON produced by this module’s default settings (in particular, the default separators value) is also a subset of YAML 1.0 and 1.1. This module can thus also be used as a YAML serializer.13:11
acabotgzhai : did you manage to do a docker pull bcom/pkb-easyvirt ?13:12
vincentfrancoisealexchadin: oh I didn't know that, but my point is: should we add the new PyYAML dependency?13:13
alexchadinvincentfrancoise: this is good format that is used in some other projects like Rally13:14
vincentfrancoisealexchadin: that's really an open question, I am just wondering13:14
alexchadinvincentfrancoise: I think it could be good to support it13:14
alexchadinvincentfrancoise: Ceilometer is also using it13:14
vincentfrancoiseok then13:15
gzhaiacabot: failed with git clone
acabotgzhai : there is no git clone to do here13:16
vincentfrancoisealexchadin: also, can you add a quick example in your help text?13:16
acabotgzhai : you just have to run "docker pull bcom/pkb-easyvirt"13:16
vincentfrancoisealexchadin: in either json or yaml actually13:16
gzhaiJust followed new README.13:17
alexchadinvincentfrancoise: in docs?13:17
vincentfrancoisealexchadin: no, in
acabotgzhai : you dont need to build the container image, its already available on docker hub13:18
acabotgzhai : just pull it13:18
alexchadinvincentfrancoise: wouldn't it be redundantly to add example of json or yaml to help section?13:19
gzhaiacabot: Error: image bcom/pkb-easyvirt:latest not found13:20
alexchadinvincentfrancoise: we can provide some examples in some folder named like watcher-examples13:20
gzhaiacabot: watcher/pkb is there as before.13:20
vincentfrancoisealexchadin: it's just that we should give all needed information on how to use the option so the operator doesn't have to search in the docs to know the structure of the JSON/YAML to be passed13:21
acabotgzhai : did you run "docker login" already ?13:22
sballe_hi I am back13:23
alexchadinvincentfrancoise: ok, should it be like "JSON example: [{'host_aggregates': {...}}, {'availability_zones': {...}}]"?13:24
alexchadinhello sballe_ :)13:24
sballe_alexchadin: hi :-)13:24
vincentfrancoisealexchadin: yeap13:24
alexchadinvincentfrancoise: ok, no problem13:25
vincentfrancoisealexchadin: thanks :)13:25
gzhaiacabot: works now:)13:25
acabotgzhai : thats great !13:25
acabotdid you copy paste the lines on into your .bashrc file .13:26
gzhaishould we start discussion for the test?13:26
acabotsballe_ gzhai : sure we can13:27
gzhaiacabot: I'm doing it now as last time.13:27
sballe_I thought you guys had done that already13:27
gzhaithis is the shared doc13:28
acabotgzhai : ok you will have to update parameters to fit your platform13:28
sballe_acabot: gzhai and I went over it yesterday. please drive the conversation now so we make sure we are all on the same page13:28
gzhaiacabot: in the pkb?13:28
acabotso I tried to have a complete view of test env in one slide13:29
acabotgzhai : in your .bashrc, you will have to update things like --openstack_auth_url=''13:29
acabotbecause its our own conf :-)13:30
acabotyou should replace it with your keystone IP13:30
gzhaiI know13:30
acabotwhen you will have all your parameters set, just run "pkb" command and it should run13:30
gzhailast time, I run it on the same OS machine.13:31
acabotdtardivel will update doc asap because you will need to edit the file "--benchmarks_conf_file='scn-rennes_1.yaml'13:31
gzhaiit will create one VM and run the specified benchmark?13:31
*** dtardivel has joined #openstack-watcher13:32
acabotthe yaml file look like that
acabotin this yaml file you can see that we have 2 compute nodes13:33
acabotsorry 4 compute nodes13:34
acabotand on each compute node we start 1 VM13:34
acabot2 cirros & 1 ubuntu13:35
acabot2 ubuntu sorry13:35
acabotand in ubuntu VMs, we start the command "stress"13:35
acabotwith params to load CPU13:35
acabotis that clear for you ?13:35
acabotdtardivel just updated the doc on
openstackgerritMerged openstack/watcher-specs: Add Ocata entry for specifications
gzhaiso the # of vm on one node is fixed13:37
gzhaiin the yaml file13:37
acabotgzhai : yes you can specify it in the "vm_count: 1" param13:38
acabotif you want to have 10 VMs on one host, just set vm_count: 1013:38
gzhainode_srv001_cirros: is the compute node name, can it be IP?13:39
gzhaiwhat else do I need in the VM image? like ssh key?13:39
dtardivelgzhai: I don't think so13:39
dtardivelgzhai: Please wait for, I will checked quickly13:40
dtardivelgzhai: Please wait for, I will check quickly13:40
acabotghzai : does the slide helps you to understand the test bed ?13:42
acabotgzhai : do you have any question regarding steps ?13:42
openstackgerritMerged openstack/watcher-specs: Change host aggregates id type to integer
gzhaiacabot: no at this point.13:43
dtardivelgzhai: So no, zone is the hostname of your compute node. Please have a look on horizon (dashboard hypervisors, tab 'Compute Host') to get them13:44
acabotgzhai : we will probably provide a script to handle watcher logs & GMR13:44
gzhaidtardivel: docker run -d --name pkb bcom/pkb, shouldn't be pkb-easyvirt?14:02
*** michaelgugino has joined #openstack-watcher14:07
openstackgerritAlexander Chadin proposed openstack/watcher: Use parameters instead of config for workload stabilization
*** tri2sing has joined #openstack-watcher14:18
openstackgerritMerged openstack/watcher: Add documentation for Scoring Module
*** danpawlik1 has quit IRC14:20
*** danpawlik1 has joined #openstack-watcher14:42
gzhaiafter running pkb, it just shows one uuid.14:54
acabotand if you do docker logs -f pkb14:55
gzhaiERROR    Unknown command line flag 'benchmarks_conf_file'. Did you mean: benchmark_config_file?14:56
gzhaisome cmd line error14:56
gzhaiI suspect the VM is not started.15:00
dtardivelcan you return output of #docker images please ?15:00
dtardivelI think you are using an obsolete pkb container image15:01
dtardivelgzhai: sorry, command is 'docker images'15:02
gzhaiI have both of them15:05
dtardivelgzhai: please check also, after running the command 'pkb' that your use the correct image (named bcom/pkb-easyvirt): # docker ps15:05
gzhaithe doc is out of date, but I use pkb-easyvirt15:06
dtardivelCan you run pkb again and just after docker p15:07
*** danpawlik1 has quit IRC15:07
dtardivelgzhai: docker ps15:07
gzhai  still uses docker run bcom/pkb15:07
dtardivelI synched the doc 30mn ago here:
dtardivelDid you update your .bashrc file ?15:07
gzhaidocker ps shows nothing.15:08
dtardivelDid you source again this file ?15:08
gzhaias all container exit15:08
dtardivelgzhai: Can I check your pkb() function from your .bashrc file ?15:09
dtardivelgzhai: you must run your container with a shared volume pointing to your local scenario directory.15:14
dtardivelcurrently, your pkb container can not access to your yaml file15:15
dtardivelgzhai: Do not forget -v option in docker run command15:16
*** tamilhce has joined #openstack-watcher15:17
alexchadinvincentfrancoise: ping15:18
vincentfrancoisealexchadin: I'm here15:19
alexchadinvincentfrancoise: don't you know how to indent lines in watcherclient help section?15:19
vincentfrancoisealexchadin: good question :p15:20
alexchadinvincentfrancoise: I got this:
vincentfrancoisealexchadin: \n doesn't work?15:20
alexchadinjust tried15:20
gzhaidtardivel: same result15:22
vincentfrancoisealexchadin: have you tried putting it in the descrption instead of help? (see
*** gzhai has quit IRC15:25
alexchadin__init__() got an unexpected keyword argument 'description'15:25
vincentfrancoisealexchadin: I guess you have to change the formatter_class somehow to make it work15:25
alexchadinvincentfrancoise: will take a look15:26
alexchadinvincentfrancoise: which one do we have now?15:26
vincentfrancoisealexchadin: see
vincentfrancoisealexchadin: the default one is HelpFormatter15:27
*** michaelgugino has quit IRC15:34
*** tamilhce has quit IRC15:43
alexchadinacabot: do we have a RoadMap?15:50
acabotalexchadin : yes its called Launchpad :-)15:51
acabotalexchadin : more seriously, what do you need ?15:52
alexchadinMy colleague just asked me about Watcher RoadMap, how we plan work on watcher15:53
alexchadinI answered him, that we have BP and having discussions about them on meetings15:54
acabotI think the best way to know what we are planning to do next is to look at
acabotunfortunately we are ending a cycle now and I plan to fix priorities for Ocata next week15:56
acabotaccording to our last mid-cycle15:56
alexchadinacabot: great!15:56
acabotpriorities will be confirmed in Barcelona15:56
*** thorst has quit IRC16:24
*** thorst has joined #openstack-watcher16:24
*** thorst has quit IRC16:32
*** alexchadin has quit IRC16:51
*** vincentfrancoise has quit IRC17:00
*** thorst has joined #openstack-watcher17:29
*** thorst has quit IRC17:38
*** harlowja has quit IRC17:46
*** harlowja has joined #openstack-watcher17:49
*** michaelgugino has joined #openstack-watcher18:30
*** thorst has joined #openstack-watcher18:39
*** thorst has quit IRC18:43
*** thorst has joined #openstack-watcher19:39
*** dtardivel has quit IRC19:47
*** thorst has quit IRC19:48
*** openstackgerrit has quit IRC20:04
*** openstackgerrit has joined #openstack-watcher20:04
*** tri2sing has quit IRC20:12
*** thorst has joined #openstack-watcher20:35
*** thorst has quit IRC20:42
*** michaelgugino has quit IRC21:23
*** thorst has joined #openstack-watcher21:40
*** thorst has quit IRC21:48
*** thorst has joined #openstack-watcher22:48
*** thorst has quit IRC22:53
*** harlowja has quit IRC23:03
*** gzhai has joined #openstack-watcher23:13
*** gzhai has quit IRC23:32
openstackgerritJoe Cropper proposed openstack/watcher-specs: Limit concurrent actions invoked by Watcher
*** thorst has joined #openstack-watcher23:50
*** thorst has quit IRC23:58

Generated by 2.14.0 by Marius Gedminas - find it at!