Wednesday, 2017-04-26

*** timothyb89 has quit IRC01:14
*** timothyb89 has joined #openstack-monasca01:14
*** jayahn has joined #openstack-monasca01:16
*** bobh has quit IRC01:59
*** jayahn has quit IRC02:08
*** zhurong has joined #openstack-monasca02:33
*** bobh has joined #openstack-monasca02:45
*** bobh has quit IRC02:49
*** zhurong has quit IRC03:15
*** zenirc369 has joined #openstack-monasca04:22
*** zhurong has joined #openstack-monasca05:07
*** nadya has joined #openstack-monasca05:15
*** nadya has quit IRC05:21
*** zhurong has quit IRC05:52
*** nadya has joined #openstack-monasca06:14
*** zenirc369 has quit IRC06:16
*** zhurong has joined #openstack-monasca06:25
*** zhurong has quit IRC06:33
*** nadya has quit IRC06:45
*** nadya has joined #openstack-monasca07:18
*** pcaruana has joined #openstack-monasca07:19
*** nadya has quit IRC07:24
*** zhurong has joined #openstack-monasca07:27
*** efoley has joined #openstack-monasca07:39
*** zhurong has quit IRC08:08
*** kei_yama has quit IRC08:41
*** efoley has quit IRC08:46
*** nadya has joined #openstack-monasca09:12
*** zhurong has joined #openstack-monasca09:22
*** zhurong has quit IRC09:37
openstackgerritArtur Basiak proposed openstack/monasca-api master: Set WSGI_MODE to mod_wsgi  https://review.openstack.org/46003009:55
*** nadya has quit IRC10:01
*** efoley has joined #openstack-monasca10:12
*** nadya has joined #openstack-monasca10:32
*** nadya has quit IRC10:37
*** witek has quit IRC10:53
*** nadya has joined #openstack-monasca10:54
*** witek has joined #openstack-monasca11:09
*** efoley has quit IRC11:48
openstackgerritArtur Basiak proposed openstack/monasca-api master: Set WSGI_MODE to mod_wsgi  https://review.openstack.org/46003011:52
*** dtardivel has joined #openstack-monasca12:16
*** efoley has joined #openstack-monasca12:19
*** efoley_ has joined #openstack-monasca12:21
*** efoley has quit IRC12:24
*** tongli has joined #openstack-monasca13:20
*** bobh has joined #openstack-monasca13:42
*** bobh has quit IRC14:01
*** rbrndt has joined #openstack-monasca14:03
*** jayahn has joined #openstack-monasca14:08
*** bobh has joined #openstack-monasca14:27
openstackgerritKaiyan Sheng proposed openstack/monasca-agent master: Add feature to define namespace annotations  https://review.openstack.org/44889514:58
*** tongli has quit IRC15:00
*** rmelero has joined #openstack-monasca15:27
*** tung_doan has joined #openstack-monasca15:36
*** Neptu has joined #openstack-monasca15:39
NeptuHej15:39
Neptuhellow to everyone15:39
rbrndtWelcome15:40
Neptuthanks15:53
Neptulittle cozy place15:54
Neptuanyway is getting late and need get kids going15:55
Neptuwas a good meeting lets talk tomorrow15:55
Neptuwhat is the normal schedule of the channel european time or US time??15:55
rbrndtI'm here US time, not sure what its like before or after that15:55
Neptuhahaha15:55
rbrndt:)15:55
Neptuthen i do not bother to ask you anything before coffe time15:56
rbrndtno worries, I'm not a coffee drinker :D15:56
Neptume neigther15:56
Neptubefore going do you have some benchmarking reports15:57
Neptuto understand a bit what is a normal setup when it comes to api nodes... kafka nodes and influx nodes15:57
rbrndtI do, but not handy. I've been working on other things outside monasca for a while :(15:57
Neptuok15:58
rbrndtI'll put together something for you today though15:58
Neptuno stress i just drafting the whole thing in my head and I need to understand where the bottleneck start15:59
openstackgerritJohannes Grassler proposed openstack/monasca-kibana-plugin master: Use GET for Keystone health check  https://review.openstack.org/46019515:59
rbrndtWe really want something other than influx now that they've gone paid only for clustering16:00
Neptuyes16:00
Neptui mean we are 3, we got an interesting CV today from a python dev16:01
Neptuso this will grow16:01
rbrndtThat sound awesome, we would love to welcome some new people to monasca16:01
Neptui knwo other some banks have tested monasca and they have gone away from it here in stockholm due influx16:02
Neptubut i mean we are all developers here16:02
Neptuso we should be able to put something together16:02
Neptuquickly16:02
rbrndtReally? that's interesting. we don't have a lot of info about monasca outside our sphere in openstack16:03
Neptustill we are building ansible scripts to pop up cluster enviroments on all key components16:03
rbrndtWe had some sensible, but it's long out of date now.16:03
rbrndts/sensible/ansible16:03
Neptuthe idea is to have something to benchmark16:03
Neptuso we are finalizing soon with the script to have x nodes on openstack cluster of kafka zookeper influx and stuff16:04
Neptubut i see a problem with customers in influx not clustering16:04
Neptupeople not like to pay16:04
rbrndtMost of our benchmarks have been on three nodes of each API, Kafka, and Vertica. Influx went closed on clustering before we ramped up testing16:05
*** nadya has quit IRC16:05
rbrndtWe do have some testing on single node influx though16:05
Neptubut vertica is aswell pay licence16:05
*** nadya has joined #openstack-monasca16:05
Neptuyep 900k which looks good16:05
rbrndtyeah, which is why it is slowly phasing out as well16:05
*** nadya has quit IRC16:05
Neptuyep16:05
Neptubut i mean is the beauty of scaling16:06
Neptuso i need to deploy this on large clusters16:06
rbrndtThat has been our strategy16:06
Neptuso scalability is a must16:06
Neptuyep16:06
Neptuim curios about what you said about not compatible datamodel16:07
rbrndtThe simple version is cassandra expects you to search on a single aspect of your data, which doesn't work well for slicing by our dimensions16:07
Neptui will clean my desk before end of the week and will start looking more closely into influx and how stores data16:08
rbrndtthat plus handling the size limits of their expected chunk sizes is a problem16:08
Neptunow im getting into something i donno but influxdb what is the chunck of data size16:08
Neptu??16:08
rbrndtCan't recall the specific number, but influx handles the tags (dimensions) very well, so we haven't had to worry. Cassandra required us to handle some of that ourselvevs16:09
Neptummm16:09
Neptubecause casanda is not metric specific16:09
rbrndtMore or less, yeah16:09
Neptui see the problem16:10
Neptuwell i need to know more about many things before have a clever conversation about that16:10
Neptuso16:10
Neptufirst things first16:10
Neptuah one last thing before go16:11
Neptuyou you have any dummy client that introduces random metrics into the system16:11
Neptuto see it all moving16:11
Neptuand maybe stress it a bit16:11
rbrndtWe do as a matter of fact. let me grab a link16:12
Neptuhave the agent is good but faking the imput at the moment is helpfull16:12
rbrndthttps://github.com/hpcloud-mon/monasca-perf/blob/master/scale_perf/agent_simulator.py16:12
rbrndtthis is set up to simulate a number of agents submitting metrics16:12
Neptuawesome16:12
Neptuexactly what i was looking for16:13
rbrndtit has been modified a bit recently to work for containers, but the basic concept is the same16:13
Neptuhehehe still stuck on vagrant & ansible16:13
Neptuvms are my really still16:14
rbrndtI haven't brought up a devstack in weeks, I'm sure it would fail :/16:14
Neptuit fails yes16:14
Neptufrom 1 month ago16:14
rbrndtIt was fragile all the time16:14
Neptuthe stack command is crazy16:15
Neptuanyone from monasca going to the boston submit?16:15
rbrndtIf it helps, we have a vagrant setup in our monasca-api repo. Perhaps you already found that though16:15
rbrndtRoland, the PTL is planning to be there16:15
Neptuyes i saw it but the provisioner is bash i wrote my own in ansible for my conveninnce16:16
Neptuok my product owner will be there too16:16
rbrndtyeah, devstack is kinda mired in bash16:16
Neptuyep yep16:16
Neptuanyway16:17
Neptui will maybe have to read some docker then16:17
rbrndtwe do have a docker compose that works pretty well16:17
Neptubut the big issue i see is the deployment is gonna be mostly done on openstack vps16:17
Neptuand im not aware you can spin containers16:17
Neptumaybe someone solve that already16:17
rbrndtyeah, openstack is playing catchup on that16:17
*** jayahn has quit IRC16:18
Neptusoon then16:18
Neptuis important to "spin up" the whole cluster at once16:18
Neptuso you can provision all nodes in one go16:18
rbrndtyeah16:18
Neptuim developer and lazy devops16:18
Neptuso my lazy side tells me is a good idea16:19
rbrndtless itime on managing setup = more time on code16:19
Neptuwell i have scripts now to spin a sizeable cluster of kafka and influx16:20
Neptuit does the graphana aswell16:20
Neptumissing the monasca api nodes16:20
Neptusoon i will have an script to rule them all16:20
rbrndtThat would be excellent16:21
Neptuyes the idea is to start decoupling the components from the monasca-devstack install16:21
Neptuso at some point we can replace the components16:22
Neptui think is the clever aproach16:22
Neptubut now im talking too much and i need to get home16:22
Neptuhehehe16:22
rbrndtheh, alright don't let me keep you16:22
Neptunice meeting you16:22
Neptumy pleasure16:22
rbrndtYou as well16:22
tung_doanrbrndt: long time no see. I hope you are still doing well!16:24
*** rbak has quit IRC16:25
tung_doanrbrndt: if you have time pls help me look into this Heat auto-scaling template: https://pastebin.com/x6h35sJr16:25
tung_doanrbrndt: I tried too many times but it seems not to work16:25
rbrndttung_doan, I'd be happy to take e look, though I don't know much about heat16:26
tung_doanrbrndt: btw, i had a blueprint in openstack/tacker which leverage monasca: https://review.openstack.org/#/c/415216/16:26
*** rbak has joined #openstack-monasca16:26
tung_doanrbrndt: np.. I really appreciate your enthusiasm16:29
*** rbak has quit IRC16:30
*** rbak has joined #openstack-monasca16:30
*** jamielennox is now known as jamielennox|away16:31
rbrndtIf i'm reading this right, you have a very narrow window in which nothing should happen16:31
rbrndtbetween 5% and 10%16:32
rbrndttung_doan: what if the behavior that you are seeing which is incorrect?16:35
rbrndts/if/is16:35
tung_doanrbrndt: becasuse i am not in admin domain.. therefore, i used mysql to show alarm infomation16:36
tung_doanrbrndt: in fact, alarm definition, alarm-notification method worked well16:37
tung_doanrbrndt: however, i did not see any metric16:37
rbrndthmm16:38
rbrndtSo, if you query monasca, you don't see any metrics?16:38
tung_doanrbrndt: right16:39
rbrndtThe easiest way to figure out this problem would be to query from the admin perspective, but if you don't have that...16:39
rbrndtYou said you have access to mysql? do you by chance have access to influx as well?16:40
tung_doanrbrndt: not sure what's going wrong here16:40
tung_doanrbrndt: how to access to influx? why we need to do this?16:40
*** rbak_ has joined #openstack-monasca16:40
rbrndtMy first guess is that metrics are all on the admin project and the alarm definition and notification are on a different project16:41
tung_doanrbrndt: good suggestion!!!16:41
tung_doanrbrndt: I had the same feeling16:41
rbrndtIf you don't have access to admin, then influx is the only place to verify that16:41
rbrndtAlternatively, you may want to verify that the resources you are trying to autoscale are on the same project as your alarm definitions16:42
*** rbak has quit IRC16:42
rbrndtJust to clarify, do you see zero metrics in monasca? or just not the ones you need?16:42
*** rbak has joined #openstack-monasca16:43
tung_doanrbrndt: absolutely empty.. i did not see anything in mysql16:43
rbrndtMetrics won't be in mysql, only alarm definitions16:44
tung_doanrbrndt: i already tried many times before16:44
rbrndtbut if you don't see any metrics under the deifnitions/alarms then they aren't arriving16:44
*** rbak__ has joined #openstack-monasca16:44
rbrndtMaybe a good question to ask someone with Heat experience, is 'how are the monasca alarm definitions created?' because if they are all on the admin tenant, then they should have access to all metrics16:45
*** rbak_ has quit IRC16:45
tung_doanrbrndt: I mean this one: https://pastebin.com/SNvG8znE16:46
rbrndtright16:47
tung_doanrbrndt: "alarm_definition" field worked well16:47
tung_doanrbrndt: but "alarm_metric" is empty :(16:47
rbrndtRight, that would imply the alarm hasn't seen any metrics to match yet.16:47
tung_doanrbrndt: +216:47
rbrndtCan you access monasca from its CLI?16:48
*** rbak has quit IRC16:48
tung_doanrbrndt: tried many times before but it seems monasca just works for admin16:48
rbrndtok, so in your setup you don't have another user or something16:49
rbrndtRight...hmm16:49
rbrndtIt's going to be very hard to verify anything without being able to check what metrics exist16:49
tung_doanrbrndt: I suspect that maybe I miss some monasca configuration in Heat template16:50
rbrndtWe know the alarm doesn't see them, but that doesn't rule out a mispelling or anything16:50
rbrndtwith my limited understanding, I don't see anything out of place16:50
rbrndtperhaps it's not getting the scale group right?16:51
rbrndttemplate: avg(cpu.utilization_perc{scale_group=scale_group_id}) > 10 times16:51
rbrndt            116:51
rbrndthow does it fill in that 'scale_group_id'?16:51
tung_doanrbrndt: right.. i stressed VMs many time but scaling-out did not work16:52
tung_doanrbrndt: it will get input from "params: {scale_group_id: SG1}"16:52
tung_doanrbrndt: I think it is just matching metadata, right?16:53
rbrndtAlright, well that's the extent of my knowledge on Heat. I would suggest looking at the alarm definitions (the expressions should be stored in mysql) to make sure that look right16:53
rbrndtOther than that, verifying the metrics are arriving as expected16:53
tung_doanrbrndt: In my test, VMs were also attached the same metadata "SG1"16:54
*** rbak__ has quit IRC16:55
rbrndtI'm not sure off the top of my head how that would translate into our metrics, but I would trust the Heat folks got it working correctly16:55
rbrndtElse, they would be working on it right now16:55
tung_doanrbrndt: you mean that metric is not set in monasca, right?16:55
rbrndtYeah, the metrics may be missing the scale_group dimensions or just not arriving at all16:56
tung_doanrbrndt: it is so weird because no error happends16:56
rbrndtWell, missing metrics doesn't trigger anything in monasca16:56
rbrndtwe allow you to create alarm definitions for things that don't exist16:56
rbrndtNot sure what Heat does for that16:56
tung_doanrbrndt: agree.16:56
tung_doanI will ask Heat folks for more information16:57
tung_doanrbrndt: thanks for your clarification. you help me confirm the problem. thanks16:58
rbrndtLet me know if you have any more questions for me :)16:58
tung_doanrbrndt: great.. really appreciate that. Wish you have a good day :) I might remind you later. thanks16:59
*** kornica has quit IRC17:23
*** pcaruana has quit IRC17:40
*** efoley_ has quit IRC17:56
iurygregoryHello, anyone have any idea on how i would be able to retrive more than 10K of metrics from monasca? I've try monasca measurement-list cpu.percent -2880 --dimensions hostname:computenode4 --merge_metrics --offset 11000 but its not working, without offset i get only 10K but i need more18:00
iurygregoryThe error I get is HTTPException code=500 message={18:00
iurygregory   "title": "The repository was unable to process your request",18:00
iurygregory   "description": "invalid operation: time and *influxql.StringLiteral are not compatible"18:00
iurygregory}18:00
*** nadya has joined #openstack-monasca18:05
*** nadya has quit IRC18:07
openstackgerritKaiyan Sheng proposed openstack/monasca-agent master: Add Dimensions into White List  https://review.openstack.org/45902118:10
*** nadya has joined #openstack-monasca18:25
rbrndtiurygregory: the api has a configured limit of 10,000 to avoid overwhelming the database. If you want to change this, be warned you may see very long query times.18:41
rbrndtAlso, offset is based on time for metric data18:41
iurygregoryrbrndt, tks o/18:41
*** nadya has quit IRC18:43
iurygregoryrbrndt, the limit is set in configuration file?18:48
rbrndtIt should be18:48
*** rbak has joined #openstack-monasca18:55
iurygregorywould be http://git.openstack.org/cgit/openstack/monasca-api/tree/monasca_api/common/repositories/constants.py ?18:59
*** dtardivel has quit IRC19:00
rbrndtThat's the default19:09
rbrndtI apologize, I may have led you astray. It appears the python API does not make that value configurable.19:17
rbrndtiurygregory: the value you found may be the only way to change that limit for the moment19:17
iurygregoryrbrndt, tks o/19:17
*** nicolasbock has joined #openstack-monasca19:20
nicolasbockHi!19:20
nicolasbockHow do I enable the tempest tests for monasca?19:20
nicolasbockI mean, what do I need to add to tempest.conf to enable them?19:21
rbrndtnicolasbock I'm sure I understand your question19:28
rbrndtTempest.conf doesn't define which tests are run, as far as I know19:29
nicolasbockrbrndt, ok19:29
nicolasbockrbrndt, I don't know much about how tempest works19:29
nicolasbockwhich is why I guess my question is a bit confused :)19:29
nicolasbockI would like the monasca tests to run19:29
nicolasbockwhen I run19:29
nicolasbocktempest run --smoke19:29
rbrndtMe either, so hopefully we aren't too far off. I can point you at our devstack setup (which also drives the gate)19:29
nicolasbockok19:29
rbrndthttps://github.com/openstack/monasca-api/blob/master/devstack/post_test_hook.sh19:30
nicolasbockgreat, thanks!19:30
nicolasbockI'll check that out19:30
rbrndtIf you have further questions, I might suggest asking in the infra channel how tempest is meant to be run19:31
nicolasbockok19:31
nicolasbockthat's a good idae19:31
nicolasbockI'll read up on the devstack script first19:31
nicolasbockthanks!19:31
rbrndtnp19:32
*** jamielennox|away is now known as jamielennox19:52
*** rbrndt has quit IRC21:02
*** rbrndt has joined #openstack-monasca21:04
openstackgerritKaiyan Sheng proposed openstack/monasca-agent master: Add feature to report persistent volume capacity  https://review.openstack.org/46031721:14
openstackgerritKaiyan Sheng proposed openstack/monasca-agent master: Add feature to report persistent volume capacity  https://review.openstack.org/46031721:52
openstackgerritTomasz TrÄ™bski proposed openstack/monasca-kibana-plugin master: [WIP] Adjusting to uwsgi deployed keystone  https://review.openstack.org/45926722:01
*** rbak has quit IRC22:15
openstackgerritKaiyan Sheng proposed openstack/monasca-agent master: Add feature to report persistent volume capacity  https://review.openstack.org/46031722:23
*** bobh has quit IRC22:38
*** rbrndt has quit IRC22:52
*** Fdaisuke_ has quit IRC23:36
*** kei_yama has joined #openstack-monasca23:40

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