Tuesday, 2016-06-28

*** marcin1234 has joined #openstack-telemetry00:01
marcin1234how can I increase Gnocchi batching for "measures" ?00:01
stevellemarcin1234: I believe it is the batch_size option in the [collector] section of ceilometer.conf00:07
marcin1234I will try that00:13
*** g3ek has quit IRC00:16
*** diogogmt has quit IRC00:17
*** g3ek has joined #openstack-telemetry00:17
*** julim has joined #openstack-telemetry00:26
marcin1234guys any idea why with Gnocchi 2.1.3 I would be getting resource type instance does not exist err in Ceilometer collector log? I checked indeed resource type does not exist in the mysql table only generic00:32
*** rwsu has joined #openstack-telemetry00:39
stevellemarcin1234: you need to run the migrations with --create-legacy-resource-types00:40
stevellehttps://github.com/openstack/gnocchi/commit/b1b7c1730bff0875089399dc66469d05d1ce5ba600:40
stevellethat's any 2.1+00:41
marcin1234ah00:46
marcin1234thx stevelle00:46
*** jwcroppe has quit IRC00:48
marcin1234you are talking about running gnocchi-upgrade --create-legacy-resource-types ?00:49
marcin1234yes you are00:51
stevellegl, gotta run00:52
*** julim has quit IRC00:52
stevellelooks like you got it00:52
*** thorst_ has joined #openstack-telemetry00:52
*** cheneydc has joined #openstack-telemetry00:55
*** jwcroppe has joined #openstack-telemetry00:57
*** thorst_ has quit IRC00:57
*** thorst_ has joined #openstack-telemetry00:58
*** thorst_ has quit IRC01:06
*** rcernin has quit IRC01:11
*** khushbu has joined #openstack-telemetry01:14
*** thorst_ has joined #openstack-telemetry01:39
*** khushbu has quit IRC01:40
*** thorst_ has quit IRC01:40
*** thorst_ has joined #openstack-telemetry01:41
*** thorst_ has quit IRC01:50
*** thorst_ has joined #openstack-telemetry02:19
*** thorst_ has quit IRC02:21
*** thorst_ has joined #openstack-telemetry02:22
*** khushbu has joined #openstack-telemetry02:22
*** thorst_ has quit IRC02:30
*** chlong has quit IRC02:37
*** g3ek has quit IRC02:37
*** g3ek has joined #openstack-telemetry02:38
*** khushbu has quit IRC02:45
*** chlong has joined #openstack-telemetry02:49
*** sheel has joined #openstack-telemetry03:07
*** khushbu has joined #openstack-telemetry03:07
*** jwcroppe has quit IRC03:22
*** thorst_ has joined #openstack-telemetry03:28
openstackgerritliusheng proposed openstack/ceilometer: Add a tool to clean the legacy alarm tables  https://review.openstack.org/31239903:32
*** thorst_ has quit IRC03:35
*** links has joined #openstack-telemetry03:50
flwangliusheng: hi04:05
flwanglast time you told me there is no project id info in alarm, so as the receiver of the notifier, how can i know which the project the alarm belongs to?04:06
*** zqfan has joined #openstack-telemetry04:33
*** thorst_ has joined #openstack-telemetry04:33
*** thorst_ has quit IRC04:41
*** rcernin has joined #openstack-telemetry04:47
*** g3ek has quit IRC04:56
*** g3ek has joined #openstack-telemetry05:03
*** _nadya_ has joined #openstack-telemetry05:08
*** M00nr41n has quit IRC05:13
*** _nadya_ has quit IRC05:32
*** rcernin has quit IRC05:37
*** thorst_ has joined #openstack-telemetry05:38
*** tomoiaga has joined #openstack-telemetry05:40
*** g3ek has quit IRC05:45
*** thorst_ has quit IRC05:47
*** g3ek- has joined #openstack-telemetry05:47
*** g3ek- is now known as g3ek05:47
liushengflwang: there is no project id in the alarm notification message, but if you need the alarm's project id, you can show the alarm detals by alarm id.06:03
*** M00nr41n has joined #openstack-telemetry06:07
*** rcernin has joined #openstack-telemetry06:10
*** _nadya_ has joined #openstack-telemetry06:16
*** khushbu__ has joined #openstack-telemetry06:28
*** khushbu has quit IRC06:28
*** davidlenwell has quit IRC06:30
*** p01nt3r75 has quit IRC06:31
*** davidlenwell has joined #openstack-telemetry06:40
openstackgerritMehdi Abaakouk (sileht) proposed openstack/gnocchi: Add grenade plugin  https://review.openstack.org/30632906:42
*** thorst_ has joined #openstack-telemetry06:44
*** pcaruana has joined #openstack-telemetry06:46
*** khushbu has joined #openstack-telemetry06:49
*** thorst_ has quit IRC06:51
*** khushbu__ has quit IRC06:52
*** cheneydc has quit IRC06:53
*** yprokule has joined #openstack-telemetry06:57
*** _nadya_ has quit IRC06:58
*** tesseract- has joined #openstack-telemetry06:59
*** g3ek has quit IRC07:14
*** amoralej|off is now known as amoralej07:15
*** khushbu has quit IRC07:18
*** g3ek has joined #openstack-telemetry07:23
openstackgerritMehdi Abaakouk (sileht) proposed openstack/gnocchi: DNM: gate check  https://review.openstack.org/33480907:25
openstackgerritMehdi Abaakouk (sileht) proposed openstack/gnocchi: Add grenade plugin  https://review.openstack.org/30632907:31
*** belmoreira has joined #openstack-telemetry07:35
openstackgerritMehdi Abaakouk (sileht) proposed openstack/ceilometer: move out oslo.service  https://review.openstack.org/31193407:36
openstackgerritMehdi Abaakouk (sileht) proposed openstack/ceilometer: pollsters: Remove eventlet timers  https://review.openstack.org/30933107:36
openstackgerritChangBo Guo(gcb) proposed openstack/ceilometer: Config: no need to set default=None  https://review.openstack.org/33481507:46
*** thorst_ has joined #openstack-telemetry07:48
*** diogogmt has joined #openstack-telemetry07:53
*** eglynn has joined #openstack-telemetry07:55
*** shardy_afk is now known as shardy07:55
*** thorst_ has quit IRC07:56
*** g3ek has quit IRC08:04
*** khushbu_ has joined #openstack-telemetry08:06
*** khushbu_ has quit IRC08:10
*** g3ek has joined #openstack-telemetry08:11
openstackgerritDarren Hague proposed openstack/ceilometermiddleware: Add ability to hand off event sending to a queue processed by a background thread so  as not to block swift proxy  https://review.openstack.org/33457108:24
*** khushbu has joined #openstack-telemetry08:27
*** _nadya_ has joined #openstack-telemetry08:31
*** _nadya_ has quit IRC08:38
*** khushbu has quit IRC08:42
*** yassine has joined #openstack-telemetry08:44
openstackgerritAayush Rajoria proposed openstack/aodh: Don't manually invoke pip. Use the devstack function instead.  https://review.openstack.org/32983408:45
*** g3ek has quit IRC08:53
*** thorst_ has joined #openstack-telemetry08:53
*** g3ek has joined #openstack-telemetry08:55
*** ljxiash has joined #openstack-telemetry09:00
*** liamji has joined #openstack-telemetry09:00
*** thorst_ has quit IRC09:01
*** nicolasbock has joined #openstack-telemetry09:08
*** nicolasbock_ has joined #openstack-telemetry09:09
*** nicolasbock has quit IRC09:12
openstackgerritChangBo Guo(gcb) proposed openstack/ceilometer: test: Fix wrong override value of config option interface  https://review.openstack.org/33488409:46
*** ljxiash has quit IRC09:57
*** ljxiash has joined #openstack-telemetry09:57
*** thorst_ has joined #openstack-telemetry10:00
*** ljxiash_ has joined #openstack-telemetry10:01
*** ljxiash has quit IRC10:02
*** ljxiash_ has quit IRC10:05
*** thorst_ has quit IRC10:06
*** _nadya_ has joined #openstack-telemetry10:24
*** p01nt3r75 has joined #openstack-telemetry10:27
*** _nadya__ has joined #openstack-telemetry10:33
*** _nadya_ has quit IRC10:33
*** yassine has quit IRC10:57
*** ljxiash has joined #openstack-telemetry11:12
*** ljxiash has quit IRC11:14
*** ljxiash has joined #openstack-telemetry11:14
*** peristeri has joined #openstack-telemetry11:17
*** g3ek has quit IRC11:19
*** g3ek has joined #openstack-telemetry11:25
*** thorst_ has joined #openstack-telemetry11:26
*** gordc has joined #openstack-telemetry11:30
jd__is our gate broken?11:41
jd__pretty sure I059a12b1b920f703f28aca0e2f352714118dee97 broke our gate11:44
jd__coolio11:44
*** gordc has quit IRC11:45
*** khushbu_ has joined #openstack-telemetry11:45
*** yassine has joined #openstack-telemetry11:55
*** khushbu_ has quit IRC11:58
silehtjd__, oh I was looking for this thx!12:02
*** g3ek has quit IRC12:07
*** amoralej is now known as amoralej|lunch12:09
jd__sileht: yeah I don't understand curl enough12:11
jd__or bash12:11
*** gordc has joined #openstack-telemetry12:12
*** g3ek has joined #openstack-telemetry12:13
openstackgerritIldiko Vancsa proposed openstack/aodh: Add install-guide for aodh  https://review.openstack.org/33004812:13
*** khushbu has joined #openstack-telemetry12:14
*** diogogmt has quit IRC12:21
*** liamji has quit IRC12:22
*** diogogmt has joined #openstack-telemetry12:22
silehtjd__, something in stable branches have broken my grenade works, before my vacation, it was failling at stopping metricd after tempest tests, now it fails to start old keystone version due to requirement issues...12:26
silehtjd__, http://logs.openstack.org/29/306329/29/check/gate-gnocchi-grenade-dsvm-functional-file-mysql-1.x/9f14fa7/logs/old/screen-key-a.txt.gz#_2016-06-28_07_56_12_79412:26
jd__sileht: I've spent the last months fixing stable/mitaka and stable/liberty branches12:26
jd__-s12:26
jd__I spend my time fixing things12:26
jd__what requires oslo.utils >=3.11?12:27
jd__probably a upper cap missing from global-req12:27
silehtjd__, Got it, Gnocchi 2.1.X is installed instead of 1.3 ...12:30
jd__ah…12:31
*** diogogmt has quit IRC12:34
openstackgerritIldiko Vancsa proposed openstack/aodh: Add install-guide for aodh  https://review.openstack.org/33004812:35
*** liusheng has quit IRC12:35
*** liusheng has joined #openstack-telemetry12:36
openstackgerritJulien Danjou proposed openstack/ceilometer: devstack: do not wait using the full URL  https://review.openstack.org/33499412:38
*** links has quit IRC12:40
*** amoralej|lunch is now known as amoralej12:47
*** links has joined #openstack-telemetry12:53
*** khushbu has quit IRC12:55
silehtjd__, hum that looks like a pip bug ...12:56
silehtjd__, :12:56
sileht2016-06-28 07:48:03.305 | Requirement already satisfied (use --upgrade to upgrade): oslo.utils>=3.3.0 in /usr/local/lib/python2.7/dist-packages (from gnocchi==2.1.1.dev160)12:56
sileht2016-06-28 07:48:03.323 | Collecting oslo.middleware>=3.11.0 (from gnocchi==2.1.1.dev160)12:56
sileht2016-06-28 07:48:03.383 |   Downloading http://mirror.dfw.rax.openstack.org/pypi/packages/e9/17/e8193e20735f94859774c6af8b444a3ab127af32eb7a9900d522920eb82d/oslo.middleware-3.13.0-py2.py3-none-any.whl (52kB)12:56
silehtjd__, gnocchi requires oslo.utils>=3.3.0 and oslo.middleware-3.13 oàslo.utils>=3.11.012:56
silehtjd__, but pip thinks 3.3 is fine for both ...12:56
sileht*3.8.0*12:57
openstackgerritMehdi Abaakouk (sileht) proposed openstack/gnocchi: Add grenade plugin  https://review.openstack.org/30632912:58
openstackgerritMehdi Abaakouk (sileht) proposed openstack/gnocchi: metricd: use Cotyledon lib  https://review.openstack.org/31174412:58
openstackgerritMehdi Abaakouk (sileht) proposed openstack/gnocchi: devstack: Fix requirement typo  https://review.openstack.org/33500712:58
silehtjd__, I just reproduce with my local pip ....13:00
silehtjd__, virtualenv venv; venv/bin/pip install oslo.utils===3.8.0; venv/bin/pip install -e gnocchi[test,file,mysql,keystonmiddleware]13:01
silehtjd__, and oslo.utils is not upgraded ...13:01
*** M00nr41n has quit IRC13:05
*** yprokule_ has joined #openstack-telemetry13:12
*** yprokule has quit IRC13:13
*** diogogmt has joined #openstack-telemetry13:15
gordcwhat do you think of shrinking the split size from 14400 to 1440? or something smaller than 14400.13:27
*** liamji has joined #openstack-telemetry13:30
*** Tamayo has joined #openstack-telemetry13:32
openstackgerritMehdi Abaakouk (sileht) proposed openstack/gnocchi: Add grenade plugin  https://review.openstack.org/30632913:34
*** rbak has joined #openstack-telemetry13:41
jd__sileht: isn't there a upper cap requirements with -r passed to pip?13:47
silehtjd__, nop13:47
*** r-mibu has quit IRC13:48
silehtjd__, you can reproduce with: virtualenv venv; venv/bin/pip install oslo.utils===3.8.0; venv/bin/pip install -e gnocchi; venv/bin/pip freeze | grep -e oslo.utils -e oslo.middleware13:48
*** r-mibu has joined #openstack-telemetry13:48
silehtjd__, oslo.utils is not upgraded even oslo.middleware-3.14 requires oslo.utils>=3.11.013:49
*** pradk has joined #openstack-telemetry13:50
silehtjd__, that why some peoples use the constraint file, no upgrade issue, but their always use obsolete libs13:51
jd__sileht: really looks like a pip bug…13:53
*** KrishR has joined #openstack-telemetry13:54
jd__sileht: if you pass -U to pip that seems to solve it13:54
jd__but that might just be by luck13:54
silehtjd__, yeah I have used that as workaround13:55
*** ametts has joined #openstack-telemetry13:57
silehtjd__, I wonder why pypi doesn't provide a file with all versions availables and all requirements like any other packages systems13:59
jd__sileht: or let's just use dpkg? :P14:00
silehtjd__, ahaha14:00
openstackgerritJulien Danjou proposed openstack/ceilometer: devstack: do not wait for service to start  https://review.openstack.org/33499414:17
*** M00nr41n has joined #openstack-telemetry14:27
*** g3ek has quit IRC14:28
*** g3ek has joined #openstack-telemetry14:31
*** diogogmt has quit IRC14:32
*** diogogmt has joined #openstack-telemetry14:32
*** tomoiaga has quit IRC14:36
*** links has quit IRC14:38
*** john5223 has quit IRC14:43
*** john5223 has joined #openstack-telemetry14:43
openstackgerritJulien Danjou proposed openstack/ceilometer: collector: use an intermediate proxy class for event dispatcher  https://review.openstack.org/31743114:46
*** yprokule1 has joined #openstack-telemetry14:46
*** krotscheck_dcm is now known as krotscheck14:48
*** yprokule_ has quit IRC14:48
*** thumpba has joined #openstack-telemetry14:49
jd__sileht: don't forget to add panko to your list of projects to review ;)14:52
jd__gordc: too14:52
silehtyeah I need to update my dashboard14:53
gordcwe need more devs/reviewers :(14:53
jd__I know gordc14:54
gordcjd__: sileht: i'm playing around with decrease how many points we store per split... it seems performance drops quite a bit when the obj gets larger.14:54
gordcbased on the 14400 value righ tnow14:55
jd__14400 too big?14:55
jd__even with lz4? we need delta compression again14:55
gordcyeah, let me show you quick graph on normal 1 worker test14:57
gordcjust need to find it14:57
*** Tamayo has quit IRC14:57
silehtjd__, we need to create a box first14:57
gordci've been doing maths on delta compression or something similar... it's quite a bit slower to compute delta but not sure if it's better or worse tradeoff.14:58
silehtjd__, something like this: http://cdn1.tnwcdn.com/wp-content/blogs.dir/1/files/2016/05/pied-piper-box.png15:00
silehtjd__, it's perfect to store a delta comrpession algorythm15:00
jd__rofl15:00
gordclol15:00
jd__gordc: I think it's worth the data storage gain15:04
gordcjd__: https://docs.google.com/presentation/d/1eHZDcgN9QJk8uEo4V-tGhthpq7aOp_m1kncBFWLwwQI/edit?usp=sharing slide2215:07
jd__https://review.openstack.org/#/c/334994/ this should fix the Telemetry gate15:07
gordcit's actually worse in real life (the degradation).15:07
jd__gordc: rewrite slower than write in Ceph? lol?15:08
jd__gordc: but that has no relation with delta compression right?15:08
*** M00nr41n has quit IRC15:08
gordcmost of the other stuff is just how i (tried to) stabilise ceph15:08
gordcjd__: rewrite means reading existing object, and then writing full (what happens now)15:09
jd__ha15:09
jd__1 second for 100 points which should be 2 KB with no compression?15:10
jd__or is it 100*100 points?15:10
*** M00nr41n has joined #openstack-telemetry15:10
gordcwhatever number in axes is a group of 10015:10
jd__hm15:11
gordcso right now the compression with lz4 really only puts us down to 10B/ point15:11
jd__ok so that's 1 second for 10K points so 200 Kb with no compression15:11
gordcsomething like that15:12
jd__delta + lz4 goes down 9 B on average15:12
jd__down to 1 B on best case scenario IIRC15:12
gordcthat test is a bit dumber, the test is realy just reading obj, adding (timestamp, value) tuple, and writing15:12
jd__ 0.05 byte on best case sorry15:13
jd__9 bytes is worst case, not average15:13
gordcthat's the delta case right?15:13
jd__delta+lz415:13
jd__that's why I think it's really worth it15:14
gordcright. currently the format is {values: {time:value, time:value, etc...}}15:14
*** M00nr41n has quit IRC15:14
jd__even if we need to micro-optimize it later to be faster (think: C)15:14
gordcthat's about 10B with lz4, i think that graph has it closer to 18B15:15
jd__yes, no compression is 16 B / point + 20% overhead15:15
jd__so 19 B vs 0.05 B15:15
jd__:-D15:15
gordcif i run it in real life with with current master, you'll notice it start to drop pretty hard with 20k metrics... ie starts around 1-2seconds/metric and is around 8s/metric near the larger end.15:17
gordcalthough i'm not entirely sure where the split is happening...15:17
*** g3ek has quit IRC15:18
gordc0.05B is if you have all zeros i'm guessing15:18
jd__gordc: likely15:19
jd__but it goes down very low if you have discret value that are very close15:19
jd__worst case is totally random :)15:19
gordci was thinking we don't need to even store delta, just the value and let the position in file dictate the time.15:20
*** g3ek has joined #openstack-telemetry15:20
gordcit's roughly 5bytes float+delimiter.15:20
*** M00nr41n has joined #openstack-telemetry15:20
jd__so just put 0 to fill the file?15:21
gordcyeah.15:21
jd__unless you want to use sparse files, but that would not be possible for most backends I think15:21
gordcright. it may be worse for swift when obj size is small.15:22
jd__this is what the delta compression does gordc, it only applies to timestamps15:22
gordcwe'd probably need to move serialize methods into each of the backends.15:22
jd__the values are compressed only by lz415:22
gordcright. the delta compression does that but doesn't allow us to append. the padded format allows append but is probably more inefficient in serialising.15:24
*** M00nr41n has quit IRC15:24
gordci think the biggest two things right now are number of iops needed and degradation based on object size.15:25
jd__gordc: so open question15:26
jd__because I know you are going to work on that optimization etc15:26
jd__and I'm glad you do15:27
jd__I'm not sure that having backported https://review.openstack.org/#/c/333367/ is going to help you in the future and is really clean15:27
jd__WDYT?15:27
jd__we're in the middle of things right now, and I would really like to clear things out15:28
gordcwas thinking same thing :) was debating whether to revert the compression and let us decide what we want to do next.15:28
gordci don't really have a strong idea which path to go right now. i'm open to options.15:28
*** M00nr41n has joined #openstack-telemetry15:29
gordci'm currently just etsting how long it would take to serialise/deserialise into float+delimiter15:29
jd__i'm open to letting you find the best option15:29
jd__let's use that failure as a good opportunity to do better?15:30
gordcagreed15:30
jd__so I can revert the patch in stable/2.1 and we can experiment15:30
gordcsounds good to me.15:30
gordchold off on a release off master as well then? to avoid releasing the compression there.15:31
*** belmoreira has quit IRC15:31
jd__gordc: I'm gonna revert there too15:31
gordci'm guessing you folks don't have time / opporunity to look at this?15:32
jd__so we can have 2.215:32
gordcjd__: kk15:32
jd__and then we'll do 3.0 with your new fancy stuff whatever that is15:32
openstackgerritJulien Danjou proposed openstack/gnocchi: Revert "carbonara: compress all TimeSerie classes using LZ4"  https://review.openstack.org/33509215:33
jd__gordc: ^^^15:33
jd__gordc: now you have the future in your hans ^^15:33
jd__hands15:33
jd__and I keep fixing the gates lol15:33
gordcyou're making a huge mistake ;)15:34
jd__that won't be the last15:37
*** _nadya__ has quit IRC15:39
*** jmccarthy has joined #openstack-telemetry15:44
*** jmccarthy has left #openstack-telemetry15:46
jd__gordc: FYI https://bugs.launchpad.net/ceilometer/+bug/159698815:47
openstackLaunchpad bug 1596988 in Ceilometer "ElasticSearch functional tests fail" [Critical,Triaged]15:47
jd__not sure you still care though15:47
openstackgerritJulien Danjou proposed openstack/panko: devstack: do not wait for service  https://review.openstack.org/33510715:55
openstackgerritJulien Danjou proposed openstack/panko: tox: rename elastic search targets  https://review.openstack.org/33510815:55
*** tesseract- has quit IRC15:56
openstackgerritMehdi Abaakouk (sileht) proposed openstack/gnocchi: Add grenade plugin  https://review.openstack.org/30632915:58
*** vishwanathj has joined #openstack-telemetry16:02
*** g3ek has quit IRC16:04
*** ljxiash has quit IRC16:05
*** g3ek has joined #openstack-telemetry16:07
*** yassine has quit IRC16:27
openstackgerritMerged openstack/ceilometer: devstack: do not wait for service to start  https://review.openstack.org/33499416:31
*** khushbu has joined #openstack-telemetry16:32
*** zqfan has quit IRC16:33
*** p01nt3r75 has quit IRC16:34
*** _nadya_ has joined #openstack-telemetry16:40
*** permalac has joined #openstack-telemetry16:43
*** _nadya_ has quit IRC16:45
*** permalac_ has quit IRC16:45
gordcjd__: not really. :( i'm hoping someone else takes care of it... preferably someone that uses it. we use events but not elasticserach16:46
*** pcaruana has quit IRC16:49
*** rcernin has quit IRC16:51
*** g3ek has quit IRC16:52
*** g3ek has joined #openstack-telemetry16:55
*** vishwanathj has quit IRC17:02
*** yprokule1 has quit IRC17:12
*** hoonetorg has quit IRC17:19
*** julim has joined #openstack-telemetry17:30
jd__gordc: ok, then we'll see17:30
*** flwang1 has joined #openstack-telemetry17:35
flwang1gordc: ping re aodh notifier17:35
*** rcernin has joined #openstack-telemetry17:45
*** rbak_ has joined #openstack-telemetry17:57
*** diogogmt has quit IRC17:58
*** rbak has quit IRC17:59
*** diogogmt has joined #openstack-telemetry18:00
*** liamji has quit IRC18:02
gordcflwang1: whatsup?18:06
flwang1gordc: i'm working on an enhancement for the aodh zaqar driver18:07
flwang1so i'm trying to figure out how to setup the dev  env :)18:08
flwang1so where is the config option to set aodh's notifier as zaqar? in ceilometer's pipeline.yaml?18:08
*** _nadya_ has joined #openstack-telemetry18:08
gordcflwang1: it would be an alarm_action... i don't know exactly how the zaqar one works but for normal webhook you specify http(s)://url to trigger when an alarm happens18:10
flwang1gordc: ah, got it18:10
gordci imagine it'd be zaqar://something18:11
gordcpradk: ^18:11
gordcsince you implemented it :)18:11
pradkgordc, looking18:12
pradkflwang1, yea you just specific zaqar:// with subscriber and topics18:13
pradkflwang1, something like:18:13
pradk'zaqar://?topic=critical&subscriber=mailto:foo@example.com&ttl=7200'18:14
flwang1pradk: cool, i'm trying to add a support for zaqar's pre-signed queue18:14
pradkcool18:14
flwang1so for that way, aodh can send notification to tenant user's queue instead of the queue created by aodh's service user18:14
flwang1with that way, user know the queue name18:14
flwang1and the benefit is user can create subscription in zaqar as well18:15
flwang1if the subscription need some complicated data18:15
pradkflwang1, cool, yea i remember we discussed this while back18:15
*** diogogmt has quit IRC18:16
flwang1pradk: yep, the idea is when user create alarm, he may need input something like this  'zaqar://?topic=critical&subscriber=mailto:foo@example.com&ttl=7200&queue_name=myqueue&project_id=xxx&signature=xxx&paths=xxx&expires=xxx&methods=xxx'18:17
flwang1and with those addition info(signature, expires...) aodh can create a zaqar client with a different auth way(signed-url), and then with that client, user can post messages to the queue user inputed18:19
flwang1does that make sense?18:19
pradkflwang1, understood, i'm not sure if we should limit by queue .. but yea auth part makes sense18:20
pradkflwang1, so this would be optional i assume? as in default would still work as usual18:21
pradkfor backward compatibility18:22
*** liusheng has quit IRC18:24
*** liusheng has joined #openstack-telemetry18:24
*** pcaruana has joined #openstack-telemetry18:25
*** diogogmt has joined #openstack-telemetry18:28
flwang1pradk: yes, for sure18:29
flwang1it's optional18:29
flwang1the default way still work18:29
*** PsionTheory has joined #openstack-telemetry18:29
flwang1the idea is18:30
flwang1we would like to support it to trigger mistral18:30
flwang1recently we added a mistral notification driver and which need a complicated options for subscription18:30
flwang1which aodh can't do that for now18:30
flwang1so we're trying to provide another way so that user can define subscriptions in zaqar but still get alarms from aodh18:31
flwang1btw, are you guys aware of any production deployment of aodh for auto scaling?18:32
flwang1what's the general purpose of aodh deployment for now?18:32
pradki dont have data around prod deployments for aodh  .. may gordc has some info18:34
flwang1pradk: ok, no problem18:36
flwang1pradk: btw, what's the simplest metric i should try to test the notifier?18:36
flwang1i mean how to set an alarm to make the test easy?18:36
gordcwe use aodh internally (well ceilometer alarms since it's based on older code) i don't know exact use cases18:37
*** PsionTheory has quit IRC18:39
flwang1gordc: got, thanks.18:40
flwang1i'm trying to propose a breakout session about aodh+zaqar+mistral+heat for autoscaling18:40
flwang1or just aodh+ zaqar + heat or senlin18:40
gordcsounds cool. although you can already go straight from aodh+heat. never used any of the other projects tbh18:41
stevelleflwang1: you have my interest, I want to get good autoscaling18:41
*** jwcroppe has joined #openstack-telemetry18:42
*** davidlenwell has quit IRC18:42
*** amoralej is now known as amoralej|lunch18:42
*** amoralej|lunch is now known as amoralej|off18:43
*** khushbu has quit IRC18:43
stevelleflwang1: do you have any user stories / use cases / write up of what autoscaling capability you want to deliver?18:46
*** davidlenwell has joined #openstack-telemetry18:52
flwang1gordc: yep, i know. aodh+ heat works18:55
flwang1but seems not too much people use it18:55
*** sheel has quit IRC18:55
flwang1and after google, you won't see too much info about openstack autoscaling18:56
flwang1that's a pity18:56
flwang1stevelle: not yet, i'm working on that18:57
flwang1stevelle: we can talk more about that18:57
flwang1stevelle: the quick way is joining my proposal so that we can work out a solution together18:57
flwang1i'm sure there should be a queue between aodh and heat or senlin18:58
flwang1especially given autoscaling won't be heat's interest18:58
flwang1stevelle: the basic idea is i want to leverage the workflow of mistral19:02
stevelleflwang1: that scares me a bit if the use case is to create a need for mistral, or appears that way19:08
flwang1not 'create a need' :)19:09
flwang1like i mentioned above, we can even don't use mistral at here19:09
flwang1but i still believe a queue between aodh and heat(senlin) makes sense19:10
flwang1for example, pls correct me if i'm wrong19:10
flwang1now can aodh trigger many different targets with one alarm?19:11
stevelleI don't know an answer for that right now, since the compound/composite alarms changes :)19:11
flwang1for example, when there is an alarm like cpu usage >90%, i want to notify admin by email and trigger a heat stack update and a mistral workflow19:12
flwang1or something like that19:12
flwang1that's my init thought19:13
flwang1stevelle: welcome to debate it to make it clear :)19:13
flwang1stevelle: what do you mean 'compound/composite alarms changes'?19:14
stevelleflwang1: I have time tonight to look at this and think about it more but I believe that is a good use case by itself. It would be valuable to build up a solution and maybe a summit talk for this.19:16
flwang1stevelle: awesome, if you are interested in, you can ping me at zaqar channel and we can talk more19:17
flwang1now i'm doing something test/demo based on this idea19:17
flwang1and again, the basic idea is using a message broker between those services/components to get a better auto scaling19:18
stevelleflwang1: at the root, multiple actions on alarm trigger is a valuable use case19:18
flwang1stevelle: yes for sure19:18
flwang1you know, some times, the auto scaling is not a simple pattern like if A do B19:19
flwang1it's most like if A then Check B or check C then do D or do E or .....19:19
flwang1heat is not good at that19:20
flwang1and we(zaqar) is planning to add the retry for notification19:21
flwang1which is another gap for aodh+heat way19:21
flwang1so those are some very rough ideas19:21
flwang1if we can write them down and figure out some detailed user cases, it would be great19:22
flwang1i always believe auto scaling is one of critical user case of cloud19:22
flwang1unfortunately, we didn't see enough effort in this domain19:23
flwang1my 0.0219:23
openstackgerritMerged openstack/gnocchi: Revert "carbonara: compress all TimeSerie classes using LZ4"  https://review.openstack.org/33509219:28
*** ametts has quit IRC19:40
*** flwang1 has quit IRC19:49
*** hoonetorg has joined #openstack-telemetry19:54
*** ametts has joined #openstack-telemetry19:56
*** peristeri has quit IRC19:57
*** g3ek has quit IRC20:02
*** g3ek has joined #openstack-telemetry20:03
*** _nadya_ has quit IRC20:43
*** thumpba has quit IRC20:45
*** g3ek has quit IRC20:48
*** ametts has quit IRC20:49
*** g3ek has joined #openstack-telemetry20:50
*** harlowja has quit IRC21:19
*** julian1_ has joined #openstack-telemetry21:28
*** g3ek has quit IRC21:36
*** thorst_ has quit IRC21:37
*** julian1_ has quit IRC21:37
*** g3ek has joined #openstack-telemetry21:37
*** julian1_ has joined #openstack-telemetry21:37
*** thorst_ has joined #openstack-telemetry21:37
*** thorst__ has joined #openstack-telemetry21:40
*** thorst_ has quit IRC21:42
*** thorst__ has quit IRC21:44
*** flwang1 has joined #openstack-telemetry21:59
*** thorst_ has joined #openstack-telemetry22:00
*** davidlenwell has quit IRC22:02
*** rbak_ has quit IRC22:04
*** davidlenwell has joined #openstack-telemetry22:11
*** harlowja has joined #openstack-telemetry22:16
*** harlowja has quit IRC22:23
*** g3ek has quit IRC22:24
*** g3ek has joined #openstack-telemetry22:29
*** gordc has quit IRC22:38
*** KrishR has quit IRC22:47
*** pradk has quit IRC22:53
openstackgerritgordon chung proposed openstack/gnocchi: simplify model loading  https://review.openstack.org/33524822:58
marcin1234anyone familiar with WARNING requests.packages.urllib3.connectionpool [-] Connection pool is full, discarding connection in metricd logs?23:00
openstackgerritgordon chung proposed openstack/gnocchi: simplify model loading  https://review.openstack.org/33524823:00
*** rcernin has quit IRC23:03
*** thorst_ has quit IRC23:06
*** g3ek has quit IRC23:06
*** thorst has joined #openstack-telemetry23:07
*** g3ek has joined #openstack-telemetry23:11
*** harlowja has joined #openstack-telemetry23:12
*** thorst has quit IRC23:15
*** khushbu_ has joined #openstack-telemetry23:56

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