Thursday, 2017-03-02

*** _cjones_ has quit IRC00:21
*** _cjones_ has joined #openstack-telemetry00:22
*** _cjones_ has quit IRC00:26
*** thorst has joined #openstack-telemetry00:31
*** thorst has quit IRC00:36
*** thorst has joined #openstack-telemetry00:41
*** gongysh has joined #openstack-telemetry00:45
*** ppiela has quit IRC00:45
*** gongysh has quit IRC00:49
*** iceyao has joined #openstack-telemetry00:50
*** iceyao has quit IRC00:54
*** thorst has quit IRC01:01
*** catintheroof has joined #openstack-telemetry01:04
*** sanfern has quit IRC01:36
*** iceyao has joined #openstack-telemetry01:43
*** catintheroof has quit IRC02:01
flwangjd_: any luck you're around?02:31
flwangor any core member of telemetry team around?02:31
flwangi have a question about panko02:31
flwangabout the publisher02:31
flwangi can see only a database.py under panko/publisher02:32
flwangbut i can see many publisher driver under ceilometer/publisher/02:32
flwangare they 'same' publisher?02:32
*** rbak has joined #openstack-telemetry02:40
*** sanfern has joined #openstack-telemetry02:50
openstackgerritHanxi Liu proposed openstack/ceilometer master: Support loading multiple meter definition files  https://review.openstack.org/42959002:54
*** rbak has quit IRC02:59
*** gongysh has joined #openstack-telemetry03:04
*** dave-mccowan has joined #openstack-telemetry03:06
*** links has joined #openstack-telemetry03:08
*** gongysh has quit IRC03:16
*** thorst has joined #openstack-telemetry03:50
*** thorst has quit IRC03:50
*** rcernin has quit IRC03:50
*** sudipto has joined #openstack-telemetry04:10
*** sudipto_ has joined #openstack-telemetry04:10
*** dave-mccowan has quit IRC04:16
*** Gautam has joined #openstack-telemetry04:29
*** sudipto_ has quit IRC04:30
*** sudipto has quit IRC04:30
*** thorst has joined #openstack-telemetry04:32
*** thorst has quit IRC04:32
*** iceyao has quit IRC04:32
*** nadya has joined #openstack-telemetry04:51
*** nadya has quit IRC04:52
*** thorst has joined #openstack-telemetry05:03
*** iceyao has joined #openstack-telemetry05:13
*** thorst has quit IRC05:16
*** iceyao has quit IRC05:18
*** iceyao has joined #openstack-telemetry05:18
*** adriant_ has quit IRC05:20
*** Jack_Iv has joined #openstack-telemetry05:46
*** narasimha_SV has joined #openstack-telemetry06:27
*** Jack_Iv has quit IRC06:41
*** Jack_Iv has joined #openstack-telemetry06:42
*** Jack_Iv_ has joined #openstack-telemetry06:46
*** Jack_Iv has quit IRC06:47
*** zhurong has joined #openstack-telemetry06:48
*** zhurong has quit IRC06:53
*** sudipto has joined #openstack-telemetry06:56
*** sudipto_ has joined #openstack-telemetry06:56
*** sudipto_ has quit IRC07:00
*** sudipto has quit IRC07:00
*** rcernin has joined #openstack-telemetry07:17
*** tesseract has joined #openstack-telemetry07:18
*** iceyao has quit IRC07:21
*** Jack_Iv_ has quit IRC07:33
*** Jack_Iv has joined #openstack-telemetry07:34
*** Jack_Iv has quit IRC07:35
*** Jack_Iv has joined #openstack-telemetry07:35
*** gongysh has joined #openstack-telemetry07:41
*** iceyao has joined #openstack-telemetry07:45
*** nadya has joined #openstack-telemetry07:45
*** yprokule has joined #openstack-telemetry07:50
*** lhx__ has joined #openstack-telemetry07:55
*** Jack_Iv has quit IRC08:00
*** Jack_Iv has joined #openstack-telemetry08:01
jd_flwang: yes08:01
*** shardy has joined #openstack-telemetry08:04
*** Jack_Iv has quit IRC08:06
openstackgerritHanxi Liu proposed openstack/ceilometer master: Support loading multiple meter definition files  https://review.openstack.org/42959008:12
*** pcaruana has joined #openstack-telemetry08:13
jd_sileht: so has nova fixed our gate? lol08:20
silehtjd_, maybe I haven't check yet08:21
jd_i still see failure but i did not dig08:22
silehtjd_, no more nova ERROR at least08:22
*** yprokule_ has joined #openstack-telemetry08:22
jd_ok cool08:22
silehtjd_, some are failling due to pscygo2 lib issue08:22
jd_hm and tooz?08:24
jd_recheck should be enough08:24
*** yprokule has quit IRC08:24
*** yprokule_ is now known as yprokule08:24
silehtjd_, yes08:24
silehtjd_, the integration job that fail is maybe due to the oslo.messaging threading issue08:26
silehtjd_, I will ask a release of oslo.messaging for pike with the fix08:26
*** danpawlik has left #openstack-telemetry08:27
jd_wtf is that http://logs.openstack.org/23/439823/1/check/gate-ceilometer-dsvm-tempest-plugin-mongodb-ubuntu-xenial/0238a02/console.html#_2017-03-01_22_11_37_89198908:27
jd_it's in the ocata branch https://review.openstack.org/#/c/43982308:28
jd_sileht: is this your copy of tempest we need to cherry pick?08:28
* sileht trows tempest by the windows, following by a dinosaur on top on it, to ensure it does not survive08:29
*** Jack_Iv has joined #openstack-telemetry08:31
silehtjd_, I will backport https://review.openstack.org/#/c/431698/08:40
silehtjd_, https://review.openstack.org/44021208:43
silehtthe openstackstatus bot is dead ?08:43
silehtwakeup openstackgerrit08:43
*** sshnaidm|off is now known as sshnaidm08:46
*** yprokule_ has joined #openstack-telemetry09:03
*** shardy has quit IRC09:04
*** shardy has joined #openstack-telemetry09:04
*** yprokule has quit IRC09:04
*** yprokule_ is now known as yprokule09:04
*** eglynn has joined #openstack-telemetry09:11
*** amoralej|off is now known as amoralej09:13
*** thorst has joined #openstack-telemetry09:13
*** thorst has quit IRC09:18
*** nadya has quit IRC10:01
*** gongysh has quit IRC10:27
openstackgerritHanxi Liu proposed openstack/ceilometer master: Support loading multiple meter definition files  https://review.openstack.org/42959010:28
*** links has quit IRC10:31
*** cdent has joined #openstack-telemetry10:33
*** iceyao has quit IRC10:39
jd_sileht: looks like integration gate is really broken10:39
jd_gtg10:39
*** nadya has joined #openstack-telemetry10:40
*** sanfern has quit IRC10:44
*** links has joined #openstack-telemetry10:48
openstackgerritMehdi Abaakouk (sileht) proposed openstack/ceilometer master: prepare future tempest breakage  https://review.openstack.org/43941410:49
openstackgerritMehdi Abaakouk (sileht) proposed openstack/ceilometer master: Don't run ceilometer-upgrade on unconfigured db  https://review.openstack.org/43962710:49
*** sanfern has joined #openstack-telemetry10:54
*** Gautam_ has joined #openstack-telemetry10:57
*** shardy has quit IRC11:00
*** Gautam_ has quit IRC11:00
*** Gautam_ has joined #openstack-telemetry11:00
*** Gautam has quit IRC11:01
*** shardy has joined #openstack-telemetry11:01
*** Gautam has joined #openstack-telemetry11:01
*** Gautam has quit IRC11:05
openstackgerritMehdi Abaakouk (sileht) proposed openstack/ceilometer master: prepare future tempest breakage  https://review.openstack.org/43941411:07
openstackgerritMehdi Abaakouk (sileht) proposed openstack/ceilometer master: Don't run ceilometer-upgrade on unconfigured db  https://review.openstack.org/43962711:07
*** Jack_Iv has quit IRC11:13
*** Jack_Iv has joined #openstack-telemetry11:13
*** thorst has joined #openstack-telemetry11:14
*** sanfern has quit IRC11:15
*** nadya_ has joined #openstack-telemetry11:18
*** nadya has quit IRC11:18
*** Jack_Iv has quit IRC11:18
*** thorst has quit IRC11:19
*** Gautam has joined #openstack-telemetry11:30
*** Gautam has quit IRC11:34
*** eglynn has quit IRC11:43
lhx__seems issue related to oslo.messaging, but not sure11:46
*** links has quit IRC11:51
*** yassine has quit IRC11:52
*** yassine has joined #openstack-telemetry11:58
*** narasimha_SV has quit IRC12:02
*** links has joined #openstack-telemetry12:04
*** gkadam has joined #openstack-telemetry12:13
*** shardy is now known as shardy_lunch12:21
*** thorst has joined #openstack-telemetry12:45
*** gkadam has quit IRC12:46
*** catintheroof has joined #openstack-telemetry12:56
*** shardy_lunch is now known as shardy12:58
*** sanfern has joined #openstack-telemetry13:02
*** zhangguoqing has joined #openstack-telemetry13:05
*** nadya_ has quit IRC13:08
*** Gautam has joined #openstack-telemetry13:09
*** lhx__ has quit IRC13:18
jd_what how?13:19
jd_sileht: clue?13:19
silehtjd_, a link ?13:21
jd_sileht: https://review.openstack.org/#/c/439156/213:21
jd_all integration jobs are dead13:21
silehtjd_, Looks like nova returns an empty server list...d13:22
jd_sileht: indeed, but why …13:22
jd_is there really no server running?13:22
silehtjd_, the devstack patch yesterday should have fixed this13:22
jd_is this a plot against telemetry?13:23
silehtjd_, yes because gnocchi have the metrics and heat checks creation of resources and it returns OK13:23
silehtjd_, even "openstack server list" is empty...13:24
jd_is CloudStack still a thing? asking for a friend13:24
openstackgerritMehdi Abaakouk (sileht) proposed openstack/ceilometer master: DNM: test  https://review.openstack.org/44055413:30
*** cdent has quit IRC13:31
*** gordc has joined #openstack-telemetry13:33
silehtjd_, openstack server list is empty, but openstack server show XXXX works ...13:35
*** chlong_ has joined #openstack-telemetry13:40
jd_sileht: hilarious13:49
silehtjd_, I'm writting a ML mail13:50
jd_sigh13:50
silehtjd_, I think their break something with policies or something13:50
silehtjd_, because we are the only project that create instances as admin13:50
silehtjd_, and the policy is perhaps confused13:50
*** aolwas has quit IRC13:51
silehtjd_, if https://review.openstack.org/440554 pass, that will confirm my though13:51
jd_ok13:52
jd_fingers crossed13:52
silehtjd_, I have seen some patches about converting policy yaml files in code13:52
silehtperhaps related, we will see13:53
*** lhx__ has joined #openstack-telemetry13:53
* sileht just quits nova 'git log', after seeing 'Merge "vomiting"'13:56
jd_LOL13:59
*** nadya has joined #openstack-telemetry14:02
*** cdent has joined #openstack-telemetry14:03
openstackgerritRico Lin proposed openstack/python-pankoclient master: [Fix gate]Update test requirement  https://review.openstack.org/44057414:06
*** Jack_Iv has joined #openstack-telemetry14:07
*** fguillot has joined #openstack-telemetry14:12
*** links has quit IRC14:12
silehtjd_, funny DEBUG message:14:15
silehtnova.osapi_compute.wsgi.server [req-e44f5adf-519c-4b52-ad8a-845cd5a0f30a admin admin] (11780) timed out ('104.130.199.12', 32778) process_request /usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py:72414:15
jd_did you plug your hard drive to the software?14:15
silehtit occurs when we list instances with gabbi14:16
silehtwhile we have :14:16
sileht(11780) accepted ('104.130.199.12', 32778) server /usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py:86814:16
silehtwhen the instances are list via Ceilometer pollsters14:16
cdentsileht: is that gabbi with wsgi-intercept or live?14:17
*** nadya has quit IRC14:20
silehtcdent, live14:20
cdentI guess I should have known that since you're talking to nova there.14:21
* cdent needs to wake up14:21
silehthttps://github.com/openstack/ceilometer/blob/master/ceilometer/tests/integration/gabbi/gabbits-live/autoscaling.yaml14:21
* jd_ slaps cdent 14:22
jd_always glad to help14:22
cdentow! I have a very sunburnt face.14:22
jd_too much beach14:22
cdentyeah, too much beach with too much wind so I didn't realize I was roasting14:22
openstackgerritBéla Vancsics proposed openstack/ceilometer master: Remove unused variable  https://review.openstack.org/43947114:23
*** ppiela has joined #openstack-telemetry14:26
openstackgerritBéla Vancsics proposed openstack/ceilometer master: Remove unused parameter  https://review.openstack.org/43946914:32
EmilienMI just noticed tripleo jobs don't run anymore in telemetry project14:33
EmilienMsomeone removed them?14:33
EmilienMI think I found why, I'm working on it14:34
*** jmlowe has quit IRC14:46
silehtjd_, in fact the call works:14:55
silehthttp://logs.openstack.org/56/439156/2/check/gate-telemetry-dsvm-integration-gnocchi-ubuntu-xenial/d4a6c69/logs/screen-n-api.txt.gz#_2017-03-02_09_16_25_64714:55
silehtand some minutes later it doesn't:14:55
silehthttp://logs.openstack.org/56/439156/2/check/gate-telemetry-dsvm-integration-gnocchi-ubuntu-xenial/d4a6c69/logs/screen-n-api.txt.gz#_2017-03-02_09_16_44_34914:55
silehtlen 323 is when the list is empty14:56
jd_sileht: -_-14:58
jd_sileht: the database has been erased in the meantime :P14:58
silehtjd_, we delete an instance14:59
silehtjd_, I see only one deletion on nova-compute, so we don't erase everything :)14:59
jd_a good old DELETE with a missing WHERE :P14:59
silehtahah14:59
*** jmlowe has joined #openstack-telemetry15:17
*** Gautam has quit IRC15:20
*** rbak has joined #openstack-telemetry15:21
*** dave-mccowan has joined #openstack-telemetry15:26
*** cdent has quit IRC15:27
silehtjd_, nova cores are looking around a global var called CELLS for our issue15:28
*** zhangguoqing has quit IRC15:28
* sileht opens the pop corn15:28
silehtnova have 7 years and their still don't get why global are wrong...15:29
jd_lol15:31
jd_you still need parents at 715:31
silehtlol15:31
silehtjd_, the good new is mriedem is working hard for us, thx to him15:35
jd_yeah i'm glad they're taking that seriously :)15:36
silehtjd_, the issue around using global seems to be confirmed: https://bugs.launchpad.net/nova/+bug/1669473/comments/115:44
openstackLaunchpad bug 1669473 in OpenStack Compute (nova) "openstack server list returns an empty list" [Undecided,New]15:44
silehtjd_, they have to add more debug to nova to continue, unfortunatly15:44
*** nicodemus_ has joined #openstack-telemetry15:45
jd_:(15:45
nicodemus_hello15:45
jd_hi nicodemus_15:45
nicodemus_I have a question regarding a feature we're thinking here, and wanted to ask you guys to see what you think15:46
nicodemus_If I add custom metadata to a certain instance, how can that be updated in the resource in an automatic fashion?15:48
sileht2615:48
silehtoups15:48
silehtjd_, concurrency 101, doesn't lock to protect concurency update of global: https://github.com/openstack/nova/blob/master/nova/compute/api.py#L2524-L252815:51
silehtdoesn't/don't use15:51
silehtjd_, one more nova bug root cause discover by telemetry \o/15:53
nicodemus_To elaborate: now we can create out custom resource types, and then map our custom metadata in gnocchi_resources.yaml. If tomorrow a sample contains some new extra metadata, unless we update by hand the resource-type add it on gnocchi_resources.yaml that extra metadata is ignored. Is there any way/any plan to allow adding this new metadata dynamically?15:55
*** cdent has joined #openstack-telemetry15:57
gordcnicodemus_: i don't think we want that. seems you want document storage capabilities if you want to blindly capture metadata... i don't think that's gnocchi's usecase15:58
gordc(my opinion)15:58
*** rcernin has quit IRC15:59
*** yprokule has quit IRC16:00
*** chlong_ has quit IRC16:01
*** joadavis_ has joined #openstack-telemetry16:01
*** chlong__ has joined #openstack-telemetry16:01
*** sergio_ has joined #openstack-telemetry16:01
*** sergio_ is now known as Guest1759616:01
gordcjd_: sileht: was there a reason we made 'delete metric' async?16:04
nicodemus_gordc: our thinking behind my inquiry is that maybe some instances have extra metadata, for example each project adds tags to instances like the type of application its running16:07
nicodemus_later on, a user wishes to aggregate metrics from all instances that are running eg. a database, for that we need to use the tag16:08
silehtgordc, why not :p16:09
nicodemus_as it is now, we should update the resource-type and edit the gnocchi_Resources.yaml by hand16:09
gordcsileht: :)16:09
silehtgordc, releasing the lock and compute another metric16:09
gordcsileht: i want to move this code somewhere esle https://github.com/openstack/gnocchi/blob/master/gnocchi/storage/_carbonara.py#L440-L45416:10
nicodemus_that is nowadays a normal behavior, something that can be done in gnocchi (and we are doing it currently)16:10
gordcnicodemus_: yeah, so it seems like you want somethin like how we capture server_group right now. it's a user_metadata field that may be added to nova instances by heat16:11
*** nadya has joined #openstack-telemetry16:11
openstackgerritMehdi Abaakouk (sileht) proposed openstack/gnocchi master: Nova testing  https://review.openstack.org/44065716:11
gordcnicodemus_: my hesitation is once you start allowing free capturing of all metadata, people will just stop being explicit about what they capture because it's easier, and then they run into issue of db is now too big because it's capturing a lot of noise.16:12
*** rbak_ has joined #openstack-telemetry16:12
*** rbak has quit IRC16:12
gordcit's not the only issue but it was one of the issues why old legacy ceilometer grew to be an issue.16:13
nicodemus_what we wonder now is if that could be automatic, like allowing a certain limit of extra keys but those extra keys to be added "automatically" to the resource_type and not having to be something fixed and/or something that requires manual intervention16:13
nicodemus_yeah, allowing anyone to add any amount of extra keys is overkill16:13
nicodemus_but perhaps adding some configuration option in order to limit the amount of extra keys16:14
gordcnicodemus_: possibly. but then you have scenario where you have no idea which keys will get accepted... just that whatever keys are accepted were the first x16:15
nicodemus_gordc, you think that's something undesirable? Because if you want to control specifically what metadata to allow, you can always put extra_keys=false ans just accept the metadata defined in gnocchi_resources.yaml16:17
silehtgordc, go ahead16:17
nicodemus_we're thinking this as a way to allow some extra (let's say "random") metadata without needing to update everything by hand16:18
gordcnicodemus_:  i think it's not safe if you have a limit... you won't really know what metadata you're capturing unless you are explicit.16:21
gordcnicodemus_: understood that it's easier... i don't think it's safe though. *shrugs*16:22
*** nadya has quit IRC16:22
gordcif the limit is too small, you might not get what you want. if too big, your db is collecting junk... i don't know. it's too difficult for me to think about :)16:24
nicodemus_gordc, that's the thing. The metadata that I care is all explicit in gnocchi_resources.yaml. The extra metadata is giving the user the possibility to add some tags16:26
nicodemus_the possibility and the responsibility of managing his or her extra keys, so if the user knows that it has a 5 extra keys limit, if he added 6 and is missing one, he or she has to remove some old key for the new one to show up16:27
gordcnicodemus_: so you'd put metadata you want in gnocchi_resources.yaml? you just don't want to update the resource-type manually?16:28
nicodemus_and then he or she could later group the resources by whatever criteria they want16:28
gordcif you remove one from gnocchi_resources.yaml, does that mean it'd get deleted from resource-type?16:29
jd_sileht: I am going to ask that we merge Telemetry and QA then16:30
silehtjd_, I will add a new mandatory pep8 checks '/global.*/' -> failure16:31
jd_gordc: yeah it's async on purpose, why?16:32
jd_sileht: cfg.CONF? :p16:32
gordcjd_:  i want to move this https://github.com/openstack/gnocchi/blob/master/gnocchi/storage/_carbonara.py#L440-L45416:32
jd_nicodemus_: you can have "metadata" if you just accept to add a string(256) as a field as not ever do any query with it… then sure16:33
gordcbecause if we create multiple bucket, i might know which bucket they will be in.16:33
jd_gordc: nicodemus_ : however i think a nice feature would be to have ceilometer change/create the resource types in Gnocchi by reading what's in gnocchi_resources.yaml :)16:34
nicodemus_the idea is to have a resource-type with 10 metadata items that are all explicit in gnocchi_resources.yaml, metadata items that we need and we define as required=true in the resource-type. Besides that, if a user wishes to add some other type of metadata (let's say app_type) to the instances on his project (because he later wants to get all metrics from the apache webservers), that extra metadata will be ignored as it is16:34
nicodemus_. For that metadata to appear in the resource, we need to add it by hand to the gnocchi_Resources.yaml and to the resource-type.16:34
gordcjd_: does the resource-type delete attributes when removed from gnocchi_resources?16:34
jd_gordc: I'm not following what the problem is :( can you give me an example?16:35
jd_gordc: well it does not and that's the operator to do it :p16:35
gordcjd_: which problem? metadata or buckets? )16:35
jd_gordc: buckets lol16:35
jd_nicodemus_: well then just add an extra "metadata" field and let the user put whatever it wants, now?16:35
gordc:)16:35
jd_s/now/no/16:35
jd_this channel is almost always silent and suddenly there are 3 conversations at the same time16:36
jd_get a schedule ffs16:36
jd_:P16:36
nicodemus_jd_, heheh sorry about that16:36
nicodemus_jd_, yeah16:36
gordcjd_: in the code i linked, if the metric is removed from indexer, i cannot figure out which bucket the metric's unprocessed measures are in.16:37
nicodemus_but it happening without having to alter it by hand16:37
jd_gordc: it's not removed from the indexer, it's "marked for removal" so you just have to hash the metric id to get the bucket, no?16:37
gordcif i move the code to delete unprocessed measures when metric is removed from indexer, it might keep getting scheduled until cleanup process runs16:38
gordcyes, but the cleanup process is different from scheduler process.16:38
gordcso in theory, it could cleanup, and then schedule unprocessed16:38
jd_oh you can do that to I don't think it's a problem16:39
nicodemus_suddenly a user ads a key-value to an instance, ceilometer picks it up and produces a sample with this extra key-value. the dispatcher sees that extra_keys=true in the config and extra_leys_limit=10 is not reached yet, the dispatcher updates the resource-type with the new metadata (with required=false) and pushes it16:39
nicodemus_does that make any sense?16:39
gordcjd_: yeah, that's what i was thinking. i guess there's an issue if cleanup doesn't run for a long time, then we might have a bunch of unprocessed measures that keep getting scheduled and skipped.16:40
jd_gordc: I think this code predates the metricd job partitinong we have right now16:40
jd_gordc: yeah, I don't think it's nor will be a big deal16:40
gordcjd_: kk, i'll move it and we can fix it if someone asks 'wtf'.16:41
jd_nicodemus_: as long as these keys/values are stored in a single field, I don't see a problem even right now16:41
jd_nicodemus_: the problem is if you want to create a custom field on resource type for each key key…16:41
jd_nicodemus_: you'd even need different resource types16:41
*** jd_ has left #openstack-telemetry16:42
*** jd_ has joined #openstack-telemetry16:42
jd_gordc: 👍16:42
*** pcaruana has quit IRC16:42
nicodemus_jd_, yeah, we'd imagine creating the "instance" resource-type for project A, a separate "instance" resource-type for project B and so on16:45
nicodemus_so that each project has its own extra-keys not shared with snother resource-type for another project16:45
jd_this does not sound like a good design16:45
jd_I think what'd be more interesting nicodemus_ is to explain why in the first place you want to do that, i.e. what the root problem is, what do you want to solve16:46
jd_which is at least is not clear to me right now :)16:46
jd_so what are theses key/values metadata for?16:47
*** _cjones_ has joined #openstack-telemetry16:49
*** _cjones_ has quit IRC16:49
nicodemus_jd_, the scenario we're thinking is the following: you have two different openstack deployments independent from one another. The user from deploy A launches each instance with "app_type" metadata (that is not defined in gnocchi_resources.yaml nor in the resource_type. The user from deploy B launches instances with some other, different metadata (let's say "day of the week" just to say something).16:50
*** _cjones_ has joined #openstack-telemetry16:50
nicodemus_each customer makes use of their extended attributes for whatever reason, and user A wishes to get all metrics from resources that have app_type=webserver16:51
nicodemus_next week, user A suddenly wishes to add another key, let's say "distro" that refers to ubuntu/centos/slack/etc16:52
nicodemus_each of these extended attributes /extra keys, we would need to add to the resource-type and to the gnocchi_resources.yaml file16:52
*** jmlowe has quit IRC16:53
nicodemus_I think in this scenario, it would be better just to alow user A to define whatever extra key he wants, and simply accept it from gnocchi's side16:53
nicodemus_with a configurable limit16:53
jd_you again describes a solution but not the problem you want to solve :)16:53
jd_I still don't know why you need these key/values16:53
*** jmlowe has joined #openstack-telemetry16:54
jd_*what* are you trying to solve? :)16:54
jd_now *how*16:54
nicodemus_the user needs it. The user wishes to see all metrics from webservers16:54
jd_so the user has to store a list of server that are webservers ;)16:55
nicodemus_how can he get all webservers? by grouping together all resources that have the "webservers" app_type key/value in the resource16:55
jd_nicodemus_: how can the user identify a "webserver" in Nova?16:57
nicodemus_because the instance has a tag added by the user when he launched it16:57
nicodemus_if not, suppose the user is using some other cloud provider that is not openstack-based and he wishes to push metrics to gnocchi16:59
openstackgerritgordon chung proposed openstack/gnocchi master: delete unprocessed measures on expunge  https://review.openstack.org/44068817:00
openstackgerritDarren Hague proposed openstack/ceilometer master: Enable Basic and certificate authentication for http publisher & dispatcher targets  https://review.openstack.org/44070417:07
openstackgerritJulien Danjou proposed openstack/gnocchi master: carbonara: remove misleading comment  https://review.openstack.org/44070717:09
jd_nicodemus_: so nova has server tag? I should look into that17:09
jd_nicodemus_: ok so Nova tags are just keys, not keys/values, right?17:11
nicodemus_jd_, yes17:11
nicodemus_perhaps I misspoke when I said key/value17:11
nicodemus_its just tags17:12
jd_yeah it's a bit different indeed17:12
jd_because the list of tag can be translated to e.g. "webserver,production,foobar"17:12
*** dave-mcc_ has joined #openstack-telemetry17:12
jd_so then you can store that as a string in Gnocchi and use it for requesting the resources17:12
jd_you use store ",webserver,production,foobar," and then do a search with "like %,webserver,%" for example17:13
*** dave-mccowan has quit IRC17:13
jd_and it works :)17:13
nicodemus_but each tag should be translated to a separate metadata item in the resource, if not... how can we aggregate the resources?17:14
jd_POST /v1/aggregation/resource/instance/metric/cpu.util with body: {"like": {"%,webserver,%"}}17:15
jd_IIUC what you want17:15
jd_POST /v1/aggregation/resource/instance/metric/cpu.util with body: {"like": {"tags": {"%,webserver,%"}}}17:15
*** dave-mccowan has joined #openstack-telemetry17:15
jd_sorry :)17:15
jd_we could also have something more robust with a type "array of string" but that would only work with PostgreSQL unfortunately17:16
jd_and I know many folks like this good ol' MySQL17:16
nicodemus_jd_, me for example :)17:16
*** dave-mcc_ has quit IRC17:17
jd_yeah so forget about that, you sneaky little MySQL user!17:17
jd_:P17:17
jd_but the like trick should work17:17
jd_how does that sound?17:17
jd_this could be implemented upstream in Ceilometer I think17:18
jd_if Nova gives us the list of tags, we can add it to gnocchi_resources.yaml17:18
nicodemus_that could work... though if those were only tags, there'd be no group_by17:23
*** nadya has joined #openstack-telemetry17:23
nicodemus_I mean, the resource will have a collection of tags, but I cannot know from all those tags which one is the app_type, which tag is the production_status, etc17:23
jd_nicodemus_: ah right17:23
*** aolwas has joined #openstack-telemetry17:23
*** lhx__ has quit IRC17:27
jd_nicodemus_: it's really an interesting challenge but it gets down to be limited by MySQL TBH17:36
*** tesseract has quit IRC17:52
nicodemus_jd_, ok... we'll think it through a bit more17:52
nicodemus_thanks jd_ & gordc !17:52
*** rbak_ has quit IRC17:58
catintheroofjd_: to use gnocchi file backend, do i have some special "pip" requirement ?18:19
stevellenicodemus_: is that really how tags should work anyway?18:20
nicodemus_stevelle, the use cases we've been discussing included such considerations18:21
*** nadya has quit IRC18:21
*** shardy has quit IRC18:21
nicodemus_meaning what would happen if one day we start gathering samples from a source where the resources should contain its tags or associated key/values18:22
stevelleI would assume tags would be named so you don't need labels or keys to them e.g. tags="credits_app,is_production,financial_group"18:22
stevelleso just having support for tags would do it18:22
stevellethat said, I have to also wonder what gnocchi should do when tags change on a resource18:24
stevellelast writer wins would probably be good enough, but should validate18:25
stevelletags behave different from key/value, maybe implement as a different case?18:26
*** amoralej is now known as amoralej|off18:44
nicodemus_stevelle, got sidetracked. The tags case shouldn't be difficul, because I can allow on all resource_types n extra metadata called "tags", and in there I can write the list of all tags the resource has associated18:54
nicodemus_difficul/difficult18:54
nicodemus_a different story would be if I wanted to add each tag as a key/value18:55
*** _cjones_ has quit IRC19:01
*** _cjones_ has joined #openstack-telemetry19:01
*** _cjones_ has quit IRC19:06
*** ddyer2 has quit IRC19:06
*** thorst has quit IRC19:09
*** thorst has joined #openstack-telemetry19:10
*** ddyer has joined #openstack-telemetry19:11
openstackgerritMatt Riedemann proposed openstack/gnocchi master: Nova testing  https://review.openstack.org/44065719:11
*** thorst has quit IRC19:14
*** sshnaidm is now known as sshnaidm|off19:16
*** cdent has quit IRC19:36
*** rbak_ has joined #openstack-telemetry19:47
openstackgerritgordon chung proposed openstack/gnocchi master: delete unprocessed measures on expunge  https://review.openstack.org/44068819:51
*** rbak_ has quit IRC20:04
*** yassine has quit IRC20:06
*** narasimha_SV has joined #openstack-telemetry20:15
narasimha_SVi am using ceilometer collectd plugin20:15
narasimha_SVas collectd starts I am getting metrics like this20:16
narasimha_SVhttp://paste.openstack.org/show/601182/20:16
narasimha_SVit is missing resource id20:16
narasimha_SVis this the way it is expected ?20:16
nicodemus_jd_, gordc, as a follow-up to our earlier talk: I was checking the key/value vs tag approach, and be it amazon, openstack and even azure you can add key/values to an instance (not simply a tag)20:25
nicodemus_I was also looking at some history and found this oldie: https://bugs.launchpad.net/gnocchi/+bug/151362320:27
openstackLaunchpad bug 1513623 in Gnocchi "dynamic metadata on gnocchi resources" [Wishlist,Fix released] - Assigned to Mehdi Abaakouk (sileht)20:27
*** narasimha_SV has quit IRC20:28
nicodemus_our idea behind that one bug was to replicate what ceilometer did with mongodb, allowing the gnocchi dispatcher to update a certain resource-type when the sample has more key/values than the ones in gnocchi_resources.yaml20:30
gordcnicodemus_: i wasn't reading what you/jd_ were typing earlier.20:33
gordcnicodemus_: i'm pretty sure the 'dynamic' part of that bug was being allowed to modify resource type after creation. now to make gnocchi arbitrarily create attributes.20:34
*** thorst has joined #openstack-telemetry20:35
gordci'll be honest, i'm probably not going to add your request since i've my concerns (and i don't need it personally).20:36
gordccould you not create a script/service that adds it to the resource using existing methods? so when you add a k/v to instance, it'll add manually trigger add in gnocchi?20:37
nicodemus_gordc, in short: I wanted to discuss this possibility with you and see if you considered something worthy to add upstream. My guess is we could do some hacking on the dispatcher so that this happens without manual intervention20:38
flwanggordc: jd_: question  for panko20:39
flwang(15:31:42) flwang: i have a question about panko20:39
flwang(15:31:51) flwang: about the publisher20:39
flwang(15:32:11) flwang: i can see only a database.py under panko/publisher20:39
flwang(15:32:26) flwang: but i can see many publisher driver under ceilometer/publisher/20:39
flwang(15:32:45) flwang: are they 'same' publisher?20:39
gordcbrb, i have to make a call.20:39
*** narasimha_SV has joined #openstack-telemetry20:47
gordcnicodemus_: yeah, i think it's better to have something trigger an attribute add... instead of just creating some super ability in gnocchi itself.20:48
gordcnicodemus_: maybe the other folks have different opinion20:48
narasimha_SVhttp://paste.openstack.org/show/601182/ will collectd-ceilometer-plugin metrics are expected as this20:48
narasimha_SVbecause resource_id is missing here20:48
gordcflwang: sort of. the publisher in panko is basically ceilometer publish to panko db20:49
gordcthe other publishers in ceilometer have nothign to do with panko (ie. notifier) so that's why you don't see it in panko20:50
gordcnarasimha_SV: https://julien.danjou.info/blog/2017/gnocchi-collectd-setup20:50
nicodemus_gordc, I believe gnocchi does have the super ability that allows through the API to update a resource-type... the extra lines of code should be in ceilometer (more specifically in the dispatcher)20:51
gordcwell you can add it yes. but you have to explicitly add attributes.20:52
nicodemus_I'll dig a little into it, I hope it's not that hard20:52
gordci'll let you find out if its hard or not :)20:53
*** yassine has joined #openstack-telemetry20:54
nicodemus_thanks gordc ! If I return crying some days later, it proved too hard for my skills :)20:54
gordclol best of luck20:54
nicodemus_ty20:54
*** yassine has quit IRC20:58
*** adriant has joined #openstack-telemetry20:59
*** gordc has quit IRC21:05
*** Guest17596 has quit IRC21:07
*** gordc has joined #openstack-telemetry21:09
*** gordc has quit IRC21:09
*** tlian has joined #openstack-telemetry21:20
*** yassine has joined #openstack-telemetry21:21
*** narasimha_SV has quit IRC21:27
*** yassine has quit IRC21:28
*** tlian has quit IRC21:29
openstackgerritEmilien Macchi proposed openstack/ceilometer master: CI test - never merge  https://review.openstack.org/44082021:36
catintheroofjd_: to use gnocchi file backend, do i have some special "pip" requirement ?21:37
*** nicodemus_ has quit IRC21:40
*** yassine has joined #openstack-telemetry21:43
*** dave-mccowan has quit IRC21:44
*** yassine has quit IRC21:44
*** gordc has joined #openstack-telemetry21:46
*** Jack_Iv has quit IRC21:50
*** Jack_Iv has joined #openstack-telemetry21:51
*** jmlowe has quit IRC21:52
jd_gordc: well the problem with nicodemus thing is also the perf IMHO… key/value in SQL…21:53
gordcjd_: yeah, that's also why i'm not doing it :)21:54
*** anteaya has quit IRC21:54
jd_i like that tag idea but it won't scale21:54
*** Jack_Iv has quit IRC21:55
* gordc didn't read what you folks were talking about21:56
*** fguillot has quit IRC22:05
*** anteaya has joined #openstack-telemetry22:07
*** thorst has quit IRC22:08
*** jmlowe has joined #openstack-telemetry22:11
*** thorst has joined #openstack-telemetry22:36
*** catintheroof has quit IRC22:40
*** thorst has quit IRC22:41
*** gordc has quit IRC23:11
*** thorst has joined #openstack-telemetry23:17
*** oomichi has quit IRC23:18
*** thorst has quit IRC23:19
*** oomichi has joined #openstack-telemetry23:21
*** yassine has joined #openstack-telemetry23:40
*** Jack_Iv has joined #openstack-telemetry23:52
*** _cjones_ has joined #openstack-telemetry23:55
*** _cjones_ has quit IRC23:55
*** _cjones_ has joined #openstack-telemetry23:55
*** Jack_Iv has quit IRC23:57
*** yassine has quit IRC23:59

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