| *** matsuhashi has joined #openstack-ceilometer | 00:23 | |
| *** _nadya_ has quit IRC | 00:25 | |
| *** shakayumi has joined #openstack-ceilometer | 00:31 | |
| *** shakayumi has quit IRC | 00:31 | |
| *** shakayumi has joined #openstack-ceilometer | 00:32 | |
| *** nati_uen_ has quit IRC | 00:32 | |
| *** nati_ueno has joined #openstack-ceilometer | 00:33 | |
| *** lcostantino has quit IRC | 00:35 | |
| *** nati_ueno has quit IRC | 00:38 | |
| *** nati_ueno has joined #openstack-ceilometer | 00:39 | |
| *** shakayumi has quit IRC | 00:45 | |
| *** ddieterly has joined #openstack-ceilometer | 00:46 | |
| *** nati_ueno has quit IRC | 00:47 | |
| *** nati_ueno has joined #openstack-ceilometer | 00:48 | |
| *** fnaval has quit IRC | 00:57 | |
| *** fnaval has joined #openstack-ceilometer | 00:57 | |
| *** fnaval has quit IRC | 01:01 | |
| *** fnaval has joined #openstack-ceilometer | 01:03 | |
| *** _nadya_ has joined #openstack-ceilometer | 01:04 | |
| *** _cjones_ has quit IRC | 01:09 | |
| *** _cjones_ has joined #openstack-ceilometer | 01:09 | |
| *** `jpg has quit IRC | 01:13 | |
| *** _cjones_ has quit IRC | 01:14 | |
| *** nati_uen_ has joined #openstack-ceilometer | 01:18 | |
| *** nati_ueno has quit IRC | 01:22 | |
| *** nosnos has joined #openstack-ceilometer | 01:38 | |
| *** nati_uen_ has quit IRC | 01:39 | |
| *** nati_ueno has joined #openstack-ceilometer | 01:39 | |
| *** caynan has joined #openstack-ceilometer | 01:42 | |
| *** _nadya__ has joined #openstack-ceilometer | 01:49 | |
| *** _nadya_ has quit IRC | 01:50 | |
| *** r3pl4y has joined #openstack-ceilometer | 01:52 | |
| *** _nadya__ has quit IRC | 01:53 | |
| openstackgerrit | liusheng proposed a change to openstack/ceilometer: Fix notification for NotImplemented record_events https://review.openstack.org/97669 | 01:53 |
|---|---|---|
| openstackgerrit | liusheng proposed a change to openstack/ceilometer: Fix notification for NotImplemented record_events https://review.openstack.org/97669 | 01:56 |
| openstackgerrit | liusheng proposed a change to openstack/ceilometer: Check unsupported query filters of listing events https://review.openstack.org/96653 | 02:06 |
| *** _nadya_ has joined #openstack-ceilometer | 02:17 | |
| openstackgerrit | Mauro Stettler proposed a change to openstack/ceilometer: Corrects a flaw in the treatment of swift endpoints https://review.openstack.org/97474 | 02:19 |
| *** `jpg has joined #openstack-ceilometer | 02:20 | |
| *** harlowja is now known as harlowja_away | 02:42 | |
| *** fnaval has quit IRC | 02:44 | |
| openstackgerrit | liusheng proposed a change to openstack/python-ceilometerclient: Provide explicit help string of resource-metadata https://review.openstack.org/97674 | 02:55 |
| openstackgerrit | liusheng proposed a change to openstack/python-ceilometerclient: Provide explicit help string of resource-metadata https://review.openstack.org/97674 | 03:05 |
| openstackgerrit | liusheng proposed a change to openstack/python-ceilometerclient: Provide explicit help string of resource-metadata https://review.openstack.org/97674 | 03:06 |
| *** changbl has joined #openstack-ceilometer | 03:08 | |
| *** rwsu has quit IRC | 03:10 | |
| openstackgerrit | liusheng proposed a change to openstack/ceilometer: Fix the notification of floatingip association https://review.openstack.org/97413 | 03:21 |
| *** nosnos has quit IRC | 03:29 | |
| *** fnaval has joined #openstack-ceilometer | 03:30 | |
| *** matsuhashi has quit IRC | 03:31 | |
| openstackgerrit | ZhiQiang Fan proposed a change to openstack/ceilometer: set debug to true in api test https://review.openstack.org/97099 | 03:31 |
| openstackgerrit | liusheng proposed a change to openstack/ceilometer: Improve the timestamp validation of ceilometer API https://review.openstack.org/92786 | 03:32 |
| *** Longgeek has joined #openstack-ceilometer | 03:33 | |
| *** ddieterly has quit IRC | 03:46 | |
| *** ddieterly has joined #openstack-ceilometer | 03:47 | |
| *** skelpter has joined #openstack-ceilometer | 03:52 | |
| openstackgerrit | Mauro Stettler proposed a change to openstack/ceilometer: Corrects a flaw in the treatment of swift endpoints https://review.openstack.org/97474 | 03:52 |
| *** `jpg has quit IRC | 04:05 | |
| *** fnaval has quit IRC | 04:19 | |
| *** matsuhashi has joined #openstack-ceilometer | 04:25 | |
| *** nosnos has joined #openstack-ceilometer | 04:26 | |
| *** r3pl4y has quit IRC | 04:37 | |
| *** psharma has joined #openstack-ceilometer | 04:39 | |
| *** `jpg has joined #openstack-ceilometer | 04:54 | |
| *** nati_ueno has quit IRC | 04:55 | |
| *** Longgeek has quit IRC | 04:56 | |
| *** nati_uen_ has joined #openstack-ceilometer | 04:57 | |
| *** nati_uen_ has quit IRC | 04:57 | |
| *** Longgeek has joined #openstack-ceilometer | 05:01 | |
| *** ildikov has quit IRC | 05:04 | |
| *** shakamunyi has joined #openstack-ceilometer | 05:04 | |
| *** underyx is now known as Underyx|off | 05:12 | |
| *** ildikov has joined #openstack-ceilometer | 05:35 | |
| *** alexpilotti has joined #openstack-ceilometer | 05:39 | |
| *** skelpter has left #openstack-ceilometer | 05:48 | |
| *** _nadya_ has quit IRC | 05:49 | |
| *** alexpilotti has quit IRC | 05:54 | |
| *** eglynn_ has joined #openstack-ceilometer | 05:56 | |
| *** r3pl4y has joined #openstack-ceilometer | 06:00 | |
| *** alexpilotti has joined #openstack-ceilometer | 06:01 | |
| openstackgerrit | OpenStack Proposal Bot proposed a change to openstack/ceilometer: Imported Translations from Transifex https://review.openstack.org/88506 | 06:01 |
| *** `jpg has quit IRC | 06:03 | |
| *** nati_ueno has joined #openstack-ceilometer | 06:10 | |
| eglynn_ | DinaBelova: o/ | 06:16 |
| *** r3pl4y has quit IRC | 06:16 | |
| *** _nadya_ has joined #openstack-ceilometer | 06:16 | |
| eglynn_ | DinaBelova: FYI I brought up that capabilities API versus static test-excluding config conumdrum with mtreinish last night | 06:17 |
| *** r3pl4y has joined #openstack-ceilometer | 06:17 | |
| eglynn_ | ... at the project/release status meeting, then spilled over to #openstack-qa | 06:17 |
| eglynn_ | http://eavesdrop.openstack.org/irclogs/%23openstack-qa/%23openstack-qa.2014-06-03.log | 06:17 |
| eglynn_ | ... search for "eglynn has joined #openstack-qa" | 06:17 |
| eglynn_ | ... his PoV is slightly clearer to me now | 06:19 |
| eglynn_ | ... tho' there is a lack of consistency across the tempest-against-public-cloud-X versus tempest-in-the-gate cases | 06:19 |
| *** r3pl4y has quit IRC | 06:21 | |
| *** r3pl4y has joined #openstack-ceilometer | 06:22 | |
| openstackgerrit | Mauro Stettler proposed a change to openstack/ceilometer: Corrects a flaw in the treatment of swift endpoints https://review.openstack.org/97474 | 06:25 |
| *** Ruetobas has quit IRC | 06:25 | |
| *** nati_ueno has quit IRC | 06:28 | |
| *** Ruetobas has joined #openstack-ceilometer | 06:31 | |
| *** Ruetobas has quit IRC | 06:35 | |
| *** Ruetobas has joined #openstack-ceilometer | 06:35 | |
| *** cdent has joined #openstack-ceilometer | 06:37 | |
| *** lsmola has quit IRC | 06:40 | |
| *** cdent has quit IRC | 06:46 | |
| *** alexpilotti has quit IRC | 06:59 | |
| *** _nadya_ has quit IRC | 07:04 | |
| *** Underyx|off is now known as underyx | 07:04 | |
| *** r3pl4y has quit IRC | 07:09 | |
| *** idegtiarov has joined #openstack-ceilometer | 07:10 | |
| *** r3pl4y has joined #openstack-ceilometer | 07:11 | |
| *** matsuhashi has quit IRC | 07:17 | |
| *** matsuhashi has joined #openstack-ceilometer | 07:18 | |
| *** eglynn_ is now known as eglynn-afk | 07:21 | |
| openstackgerrit | liusheng proposed a change to openstack/ceilometer: Fix notification for NotImplemented record_events https://review.openstack.org/97669 | 07:29 |
| *** _nadya_ has joined #openstack-ceilometer | 07:30 | |
| *** Alexei_987 has quit IRC | 07:33 | |
| openstackgerrit | Mehdi Abaakouk proposed a change to openstack/ceilometer: Iterates swift response earlier to get the correct status https://review.openstack.org/97702 | 07:40 |
| *** renlt has joined #openstack-ceilometer | 07:46 | |
| *** eglynn-afk is now known as eglynn_ | 07:47 | |
| *** r3pl4y has quit IRC | 07:49 | |
| *** r3pl4y has joined #openstack-ceilometer | 07:51 | |
| *** nacim has quit IRC | 07:58 | |
| *** nacim has joined #openstack-ceilometer | 07:58 | |
| *** r3pl4y has quit IRC | 08:00 | |
| *** r3pl4y has joined #openstack-ceilometer | 08:01 | |
| *** `jpg has joined #openstack-ceilometer | 08:06 | |
| *** r3pl4y has quit IRC | 08:07 | |
| *** nacim has quit IRC | 08:07 | |
| *** nacim has joined #openstack-ceilometer | 08:09 | |
| *** r3pl4y has joined #openstack-ceilometer | 08:09 | |
| *** shakamunyi has quit IRC | 08:10 | |
| *** idegtiarov has quit IRC | 08:15 | |
| *** idegtiarov has joined #openstack-ceilometer | 08:17 | |
| ildikov | sileht: hi. are you around? | 08:21 |
| sileht | ildikov, o/ | 08:25 |
| *** Longgeek has quit IRC | 08:27 | |
| *** Longgeek has joined #openstack-ceilometer | 08:28 | |
| *** Longgeek has quit IRC | 08:29 | |
| *** Longgeek has joined #openstack-ceilometer | 08:30 | |
| *** r0j4z0 has quit IRC | 08:30 | |
| *** safchain has joined #openstack-ceilometer | 08:31 | |
| *** Alexei_987 has joined #openstack-ceilometer | 08:33 | |
| ildikov | sileht: you made the oslo.messaging swap, so I thought that maybe you have some answers for my questions | 08:34 |
| ildikov | sileht: I'm working on fixing the doc generation errors and warnings | 08:35 |
| *** IvanBerezovskiy1 has joined #openstack-ceilometer | 08:35 | |
| *** _nadya_ has quit IRC | 08:35 | |
| * sileht listens | 08:35 | |
| *** _nadya_ has joined #openstack-ceilometer | 08:35 | |
| ildikov | sileht: dhellmann fixed the autoindex for source code dodc generation | 08:35 |
| ildikov | sileht: so the doc generation now works, but it failed with some imports | 08:36 |
| ildikov | sileht: so I started to investigate a bit and I found the for instance the ceilometer.openstack.common.notifier code was removed | 08:36 |
| ildikov | sileht: but there are still imports that refer to that code | 08:36 |
| ildikov | sileht: there is a similar import which would call nova.openstack.common.notifier.api, but it was deleted also from nova | 08:37 |
| ildikov | sileht: https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/nova_notifier.py#L23 | 08:38 |
| ildikov | sileht: https://github.com/openstack/ceilometer/blob/master/ceilometer/openstack/common/middleware/notifier.py | 08:38 |
| ildikov | sileht: https://github.com/openstack/ceilometer/blob/master/ceilometer/openstack/common/log_handler.py#L19 | 08:38 |
| ildikov | sileht: so this is the big story | 08:38 |
| ildikov | sileht: my plan is to clean up a bit, the question is how to do this clean up | 08:39 |
| sileht | ildikov, I see | 08:39 |
| ildikov | sileht: I hope that you know better these parts of the code than me | 08:39 |
| sileht | ildikov, each items have a different story | 08:39 |
| sileht | for https://github.com/openstack/ceilometer/blob/master/ceilometer/openstack/common/log_handler.py#L19 | 08:39 |
| sileht | code must be update to handle oslo.messaging or old rpc code (not only old code) | 08:40 |
| sileht | for https://github.com/openstack/ceilometer/blob/master/ceilometer/openstack/common/middleware/notifier.py I guess it can be removed from ceilometer ? | 08:40 |
| sileht | and for https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/nova_notifier.py#L23 I think this code looks currently broken | 08:41 |
| ildikov | I think so too, I just needed a second opinion :) | 08:41 |
| ildikov | I thought about this last one too that it could be deleted | 08:41 |
| *** hoangdo has joined #openstack-ceilometer | 08:41 | |
| *** matsuhashi has quit IRC | 08:42 | |
| ildikov | so the question is in this last case that can it be fixed or it should be rewritten according to the changes? | 08:43 |
| hoangdo | hello everyone | 08:43 |
| sileht | ildikov, for the last one it's needed to get compute sample one last time before a instance is deleted | 08:44 |
| sileht | ildikov, the good way to fix it, is to improve the instance.delete notification in nova, but this is a huge work | 08:44 |
| sileht | ildikov, the quick fix is to use the new nova notifier code | 08:45 |
| hoangdo | we would like to dev a plugin: getting info from a software running on VMs (more specific: rabbitmq) instead of general info like CPU, RAM, Network, etc. I wonder is it the right way to do with Ceilometer | 08:45 |
| *** caynan has quit IRC | 08:47 | |
| ildikov | sileht: a-ha, so this module is to get that last sample and this could be done by using the new nove notifier code? | 08:47 |
| *** ildikov has quit IRC | 08:48 | |
| *** changbl has quit IRC | 08:48 | |
| *** openstackgerrit has quit IRC | 08:48 | |
| *** IvanBerezovskiy1 has quit IRC | 08:48 | |
| *** ityaptin has quit IRC | 08:48 | |
| *** liusheng has quit IRC | 08:48 | |
| *** ityaptin has joined #openstack-ceilometer | 08:48 | |
| eglynn_ | hoangdo: we don't have any facility currently to gather metrics from applications/services running *within* the VM | 08:48 |
| *** IvanBerezovskiy has joined #openstack-ceilometer | 08:48 | |
| *** changbl has joined #openstack-ceilometer | 08:49 | |
| *** ildikov has joined #openstack-ceilometer | 08:49 | |
| *** IvanBerezovskiy has left #openstack-ceilometer | 08:49 | |
| *** IvanBerezovskiy has joined #openstack-ceilometer | 08:49 | |
| ildikov | sileht: what is missing from that Nova notif? | 08:49 |
| *** liusheng has joined #openstack-ceilometer | 08:49 | |
| *** openstackgerrit has joined #openstack-ceilometer | 08:49 | |
| *** matsuhashi has joined #openstack-ceilometer | 08:50 | |
| eglynn_ | hoangdo: ... instead all metrics are gathered from the outside-in (by polling the hypervisor layer) | 08:50 |
| openstackgerrit | Alexei Kornienko proposed a change to openstack/ceilometer: Refactor tests to remove direct access to test DBManagers https://review.openstack.org/95613 | 08:51 |
| eglynn_ | hoangdo: ... gathering metrics instead from the inside-out would present some issues | 08:51 |
| hoangdo | eglynn_: so it's impossible? We want Heat to scale not on CPU or RAM but on message broker queue. Do you have any suggestion | 08:52 |
| eglynn_ | hoangdo: ... for example if the approach required an agent to be installed inside the VM, this would require propogating credentials so that the agent can POST datapoints to the ceilometer-api | 08:52 |
| sileht | ildikov, some note I have made, the last time I have tracked this issue: https://wiki.openstack.org/wiki/Ceilometer/blueprints/remove-ceilometer-nova-notifier | 08:52 |
| eglynn_ | hoangdo: ... not impossible, but v. awkward to do if these data can't be surfaced from *outside* the VM | 08:52 |
| eglynn_ | hoangdo: ... that's one of the main reasons heat want to use ceilo for alarming (on CPU util) to drive autoscaling | 08:53 |
| ildikov | sileht: thanks | 08:53 |
| eglynn_ | hoangdo: ... as the original heat approach required installing a heat cfn-push-stats agent in the VM | 08:53 |
| ildikov | sileht: it's for the third, nova_notifier item, right? | 08:54 |
| ildikov | sileht: for the second, we both think it could be deleted | 08:54 |
| sileht | ildikov, yes | 08:55 |
| sileht | ildikov, and yes | 08:55 |
| hoangdo | eglynn_: well I understand it's very strange to use an "inside" agent. But that's what we really need now. For example, in our case, we monitor the Message Broker queues, if some queue is full, we don't need to scale the Message Broker node, but we scale the "Handler" nodes which receive/process data from that queue. | 08:57 |
| hoangdo | eglynn_: I don't know what is the best practice for this | 08:57 |
| ildikov | sileht: and for the first, log_handler one, it should now support oslo.messaging and rpc too? | 08:58 |
| eglynn_ | hoangdo: can that data not be surfaced outside the VM? | 08:59 |
| hoangdo | eglynn_: I guessed no. | 09:00 |
| sileht | ildikov, it should support both, at least until K | 09:00 |
| eglynn_ | hoangdo: ... in that case, you'd need to figure out some way of (a) ensuring the agent is installed on-VM and (b) propogating credentials to that agent | 09:00 |
| ildikov | sileht: thanks for the good news :) | 09:00 |
| eglynn_ | hoangdo: ... (a) is prolly straigtforward *if* you control the VM image | 09:00 |
| ildikov | sileht: I just wanted to fix the doc :) | 09:01 |
| sileht | ildikov, welcome | 09:01 |
| eglynn_ | hoangdo: ... (b) is not straightforward | 09:01 |
| ildikov | sileht: also thanks for the help, it can happen that I will ask some further questions, but I think I have enough info for now | 09:01 |
| eglynn_ | hoangdo: ... one of the problems is that keystone tokens have a limited lifetime | 09:02 |
| hoangdo | (a) is ok, we can create our own image | 09:02 |
| eglynn_ | hoangdo: ... and it's unlikely you'd want to expose a user name and passwd onto the VM | 09:02 |
| eglynn_ | hoangdo: .... perhaps keystone trusts could be use to delegate very limited privilege to such an agent | 09:02 |
| hoangdo | eglynn_: you're right, expose OpenStack username and pass to VMs is too strange | 09:03 |
| eglynn_ | hoangdo: exactly | 09:04 |
| eglynn_ | hoangdo: ... passing in a token also is problematic as it would need to be regularly refreshed | 09:05 |
| eglynn_ | hoangdo: ... so trusts are probably the lesser of 3 evils | 09:05 |
| hoangdo | eglynn_ I'm lost ^^. What's the best practice in this case. I'm sure someone must need this use case before me. It's pretty common | 09:05 |
| eglynn_ | hoangdo: ... lost? | 09:06 |
| eglynn_ | hoangdo: ... lost at what point | 09:06 |
| eglynn_ | ? | 09:06 |
| eglynn_ | boris-42: o/ | 09:07 |
| boris-42 | eglynn_ o+) | 09:07 |
| hoangdo | eglynn_: well I don't want to "hack". My intend is following the common practice and dev a plugin. | 09:07 |
| boris-42 | eglynn_ it's hangout? | 09:07 |
| boris-42 | eglynn_ hangout our irc?) | 09:08 |
| eglynn_ | boris-42: let's just IRC, I'm stuck with a low-bandwidth connection this morning | 09:08 |
| boris-42 | eglynn_ heh | 09:08 |
| eglynn_ | hoangdo: ... as I said, it's not something we do directly right now | 09:08 |
| boris-42 | eglynn_ so we were speaking about operators program | 09:08 |
| boris-42 | eglynn_ and making operators life easier=) | 09:08 |
| eglynn_ | hoangdo: ... I think keystone trusts *may* provide a path to making it possible | 09:08 |
| eglynn_ | hoangdo: ... but you probably would need to clarify/confirm that with the keystone domain experts | 09:09 |
| eglynn_ | hoangdo: ... make sense? | 09:09 |
| hoangdo | eglynn_: yes. thanks. I think I'll search for other solution before come back to this. | 09:10 |
| eglynn_ | hoangdo: cool, thanks! | 09:10 |
| eglynn_ | boris-42: yeah, making operators lives easier ... we're all about that! :) | 09:11 |
| eglynn_ | boris-42: ... so how are we going to acheive that? | 09:13 |
| boris-42 | eglynn_ so I am working on doc | 09:15 |
| boris-42 | eglynn_ that explains how=) | 09:15 |
| boris-42 | eglynn_ basically we almost have everything | 09:15 |
| boris-42 | eglynn_ so what we need is next | 09:16 |
| boris-42 | 1) horizon plugin that will be control plane | 09:16 |
| eglynn_ | boris-42: cool, is the doc in the public domain somewhere? | 09:16 |
| boris-42 | eglynn_ not yet=) | 09:16 |
| boris-42 | eglynn_ didn't finished it | 09:16 |
| boris-42 | eglynn_ too important document to make it of half of hour=) | 09:16 |
| boris-42 | so but principles are quite simple | 09:16 |
| eglynn_ | boris-42: once the doc is finished, will be opening it up for review? | 09:17 |
| boris-42 | eglynn_ yep | 09:17 |
| eglynn_ | cool | 09:17 |
| boris-42 | eglynn_ in mailing list=) | 09:17 |
| eglynn_ | boris-42: cool, I'll look forward to reading it | 09:17 |
| boris-42 | eglynn_ so what we need is to combine together 1) ceilometer 2) osprofiler 3) rally 4) satori 5) rubick under horizon plugin as a control plane | 09:17 |
| eglynn_ | boris-42: for context on the channel, do you wanna give a one-liner for each of items 2) thru' 5)? | 09:19 |
| boris-42 | sure (actually typing) | 09:19 |
| boris-42 | 2) osprofiler allows us to trace request through all services | 09:20 |
| boris-42 | dev case I already presented on summit | 09:20 |
| boris-42 | but there is as well operators case | 09:20 |
| boris-42 | we can track what amount of time request work in what service | 09:20 |
| boris-42 | and draw stacked area | 09:20 |
| eglynn_ | yep, so osprofiler is tool to measure the fine-grained latency of distributed openstack interactions by propogating a request ID with RPC calls | 09:21 |
| boris-42 | eglynn_ yep | 09:21 |
| boris-42 | 3) rally - will allow us to run periodical benchmarks | 09:21 |
| boris-42 | that can measure OpenStack API, VMs, Netowrk performance of cloud | 09:21 |
| *** Infitialis has joined #openstack-ceilometer | 09:21 | |
| boris-42 | as well we can have notification if something went wrong (i mean email operator) | 09:22 |
| boris-42 | or requests takes too much | 09:22 |
| boris-42 | as well as rally has integrated tempest we can make health checks based on taht | 09:22 |
| boris-42 | e.g. running smoke tests periodically | 09:22 |
| eglynn_ | boris-42: intended to run against a "live" cloud? | 09:23 |
| boris-42 | 4) satori - it discovers configuration of everything in cloud | 09:23 |
| boris-42 | eglynn_ yep | 09:23 |
| boris-42 | eglynn_ I know tempest cleanup mechanism should be improved before that=) | 09:23 |
| boris-42 | eglynn_ but we can start from rally benchmarks=) | 09:23 |
| eglynn_ | boris-42: WRT satori ... including scattered text-based config like ceilo pipeline.yaml or glance policy.json etc? | 09:24 |
| *** lsmola has joined #openstack-ceilometer | 09:25 | |
| boris-42 | eglynn_ ? | 09:25 |
| boris-42 | eglynn_ https://github.com/stackforge/satori | 09:25 |
| boris-42 | eglynn_ it should discover everything that is possible and even a bit more | 09:25 |
| boris-42 | =) | 09:25 |
| eglynn_ | boris-42: reason I ask it that ... | 09:26 |
| eglynn_ | boris-42: we discussed at summit alternative ways of managing the info embedded in the ceilometer pipeline.yaml | 09:27 |
| eglynn_ | boris-42: ... as currently this is a flat text file propogated all over the place | 09:27 |
| eglynn_ | boris-42: ... so difficult to ensure consistency and also problematic to push detailed deployment-specific info into the pipeline.yamls | 09:28 |
| boris-42 | eglynn_ I think the best solution is to have only one config argument | 09:28 |
| eglynn_ | boris-42: ... e..g. ildikov had a requirement to expose project UUIDs into the pipeline.yaml for tenant-specific metering | 09:28 |
| boris-42 | eglynn_ where is the DB | 09:28 |
| ildikov | hi All | 09:28 |
| boris-42 | eglynn_ and store all info in DB=) but it's if you are asking me=) | 09:28 |
| ildikov | yes, I'm the one to blame ;) | 09:29 |
| boris-42 | ildikov hey there=) | 09:29 |
| eglynn_ | boris-42: well that's the point, this info is not in DB currently | 09:29 |
| boris-42 | eglynn_ I mean it's the one more big issue of arch of OpenStack | 09:29 |
| eglynn_ | boris-42: ... it's in a /etc/ceilometer/pipeline.yaml file on every compute node and ceilo controller host | 09:29 |
| openstackgerrit | ZhiQiang Fan proposed a change to openstack/python-ceilometerclient: Fix alarm-threshold-update --query option https://review.openstack.org/90882 | 09:30 |
| boris-42 | eglynn_ so actually satori is not only about that stuff | 09:30 |
| ildikov | boris-42: the plan is to store the config in DB and provide the possibility to dynamically reconfigure the system, but this solution needs a longer timeframe | 09:30 |
| boris-42 | ildikov so you are going to work on it? | 09:30 |
| ildikov | boris-42: me and nealph is also inetersted because it would be useful for TripleO too | 09:31 |
| *** r0j4z0 has joined #openstack-ceilometer | 09:31 | |
| boris-42 | eglynn_ ildikov okay guys it will be nice =) | 09:31 |
| ildikov | boris-42: we are kind of waiting for the TSDaaS with the design, but I would like to start working on this as soon as we can | 09:31 |
| boris-42 | to have but it's not related to current discussion=) | 09:31 |
| boris-42 | TSDaaS?) | 09:31 |
| eglynn_ | boris-42: yeah I was just wondering whether satori could potentially help out with that distributed config file issue | 09:31 |
| boris-42 | eglynn_ but it's not only about that, it has even more bigger scope | 09:32 |
| eglynn_ | boris-42: sure | 09:32 |
| boris-42 | eglynn_ it discovers configuration of system, hardware and so on | 09:32 |
| ildikov | boris-42: Time Series Data aaS :) | 09:32 |
| boris-42 | gnochhi? | 09:32 |
| eglynn_ | boris-42: a-ha, fair enough | 09:32 |
| ildikov | boris-42: yes, I just did not want to mention anything food related at lunchtime ;) | 09:33 |
| boris-42 | eglynn_ so next thing is rubick | 09:33 |
| eglynn_ | boris-42: ... right I've prolly side-tracked you a bit, so please carry on | 09:33 |
| boris-42 | ildikov hehe=) | 09:33 |
| boris-42 | eglynn_ so the next thing is rubick | 09:33 |
| * eglynn_ listens ... | 09:34 | |
| boris-42 | it will make smart analyze based on rules and whatever to analyze what issues we have in clouds | 09:34 |
| boris-42 | and troubleshooting sutff | 09:34 |
| boris-42 | so where and what can produce potential (or produce real) issues | 09:34 |
| eglynn_ | interesting, as in runs analytics over the timing data collected by osprofiler? | 09:35 |
| boris-42 | eglynn_ nope at this moment it is collecting data by self as I know | 09:35 |
| boris-42 | eglynn_ but there will be some kind of integration satori and rubick | 09:36 |
| boris-42 | eglynn_ so it will analyze info from satori | 09:36 |
| eglynn_ | boris-42: fair enough | 09:36 |
| boris-42 | eglynn_ as well what I think is to analyze osprofiler data (in future) and notifications | 09:36 |
| boris-42 | eglynn_ e.g. some host started working slower then usually | 09:36 |
| boris-42 | eglynn_ and you get babaha notifiertion in horizon | 09:36 |
| eglynn_ | boris-42: ... initially rubick sounded similar to how rackspace use stacktach data to detect operational anomolies in near-realtime | 09:36 |
| boris-42 | eglynn_ on host XXX potsntial issues | 09:36 |
| boris-42 | potential* | 09:37 |
| boris-42 | eglynn_ and then you can retriwe via web UI | 09:37 |
| boris-42 | all info about that host / hardware / probably logs | 09:37 |
| boris-42 | you can run with rally some benchmarks related to issue on that host and collect profiling info | 09:38 |
| boris-42 | and do all these stuff via Horizon Pluging | 09:38 |
| boris-42 | Plugin* | 09:38 |
| boris-42 | as well there should be one more project called logging-as-a-service | 09:38 |
| eglynn_ | #link https://wiki.openstack.org/wiki/Rubick/Service_architecture | 09:38 |
| eglynn_ | interesting: "Heat metadata plugin extracts configration metadata from Heat stacks created by TripleO/Tuskar service" | 09:39 |
| boris-42 | eglynn_ it was the initial goal | 09:39 |
| eglynn_ | I suspect Tuskar would be playing in a somewhat similar space? | 09:39 |
| boris-42 | eglynn_ not sure | 09:39 |
| boris-42 | eglynn_ tuskar web ui for trippleO? | 09:39 |
| eglynn_ | boris-42: kinda | 09:40 |
| eglynn_ | boris-42: ... with some extra smarts | 09:40 |
| boris-42 | eglynn_ actually not sure | 09:40 |
| boris-42 | eglynn_ that all OpenStack users would like to use triple with tuskar | 09:40 |
| boris-42 | to understand what the hell is happening with cloud=) | 09:40 |
| boris-42 | eglynn_ so back to rubick (after summit, they changed a bit direction, to use satori ) | 09:41 |
| eglynn_ | boris-42: extra smarts would be around stuff like datacenter build-out planning, provisioning new h/w according to its best role etc., visualizing SNMP metrics etc. | 09:41 |
| boris-42 | eglynn_I am still not sure that Tuskar should be it | 09:42 |
| boris-42 | eglynn_ any way we will discuss this stuff in mailing list (about Tuskar) | 09:42 |
| eglynn_ | I wonder also are the rubick guys aware of the new convergence direction that heat is taking? | 09:42 |
| eglynn_ | convergence == "on stack update, compare modified stack template to *current reality*" | 09:43 |
| eglynn_ | old approach == "on stack update, compare modified stack template to original stack template" | 09:43 |
| boris-42 | eglynn_ one sec | 09:43 |
| *** ogelbukh has joined #openstack-ceilometer | 09:44 | |
| eglynn_ | IIUC the notion | 09:44 |
| boris-42 | ogelbukh ^ | 09:44 |
| ogelbukh | hi | 09:44 |
| boris-42 | ogelbukh he is rubick guy=) | 09:44 |
| boris-42 | eglynn_ ^ | 09:44 |
| ogelbukh | boris-42: hello | 09:44 |
| eglynn_ | ogelbukh: welcome | 09:44 |
| boris-42 | ogelbukh hi there | 09:44 |
| eglynn_ | ogelbukh: you could tail http://eavesdrop.openstack.org/irclogs/%23openstack-ceilometer/%23openstack-ceilometer.2014-06-04.log to get the context | 09:44 |
| ogelbukh | eglynn_: thank you | 09:44 |
| boris-42 | eglynn_ btw | 09:45 |
| boris-42 | eglynn_ probably osprofiler should be a part of ceilometer program? | 09:46 |
| boris-42 | eglynn_ cause it's mostly related to it=) | 09:46 |
| boris-42 | eglynn_ or operators one of those=) | 09:46 |
| eglynn_ | boris-42: ... that's a good question | 09:46 |
| boris-42 | eglynn_ if we have operators program then it can be there.. | 09:47 |
| eglynn_ | boris-42: ... I don't know if there's much benefit to a tool like osprofiler to be part of an integrated release | 09:47 |
| boris-42 | eglynn_ yep probably just keep it on stackforge | 09:47 |
| boris-42 | eglynn_ it will simplify work on it lol | 09:47 |
| eglynn_ | boris-42: ... yeah it's kind of ancilliary to the core cloud, though definitely very useful | 09:48 |
| *** Qu310 has quit IRC | 09:48 | |
| eglynn_ | boris-42: ... also there's the whole DefCore thing in the background | 09:48 |
| *** Qu310 has joined #openstack-ceilometer | 09:48 | |
| boris-42 | eglynn_ oh defcore currently is something bad=) | 09:48 |
| eglynn_ | boris-42: ... yep, it's scarey to define the capabilities of the cloud in terms of tempest test that existed two cycles back in time | 09:49 |
| boris-42 | eglynn_ yep=) | 09:49 |
| boris-42 | eglynn_ exactly but I was more polite* | 09:49 |
| boris-42 | lol | 09:49 |
| eglynn_ | boris-42: LOL :) | 09:49 |
| eglynn_ | boris-42: ... so what's the timeline for you publishing your master document? | 09:50 |
| eglynn_ | boris-42: ... sounds like it'll make for very interesting reading :) | 09:50 |
| boris-42 | eglynn_ yep =) | 09:50 |
| boris-42 | eglynn_ so actually I should make it on this week | 09:50 |
| eglynn_ | boris-42: cool | 09:50 |
| boris-42 | eglynn_ I hope tomorrow I will finish | 09:50 |
| boris-42 | eglynn_ btw we will need to make deep dive | 09:51 |
| eglynn_ | boris-42: excellent, no doubt it'll generate a lot of traffic/interest on the ML | 09:51 |
| boris-42 | eglynn_ lol=) | 09:51 |
| eglynn_ | boris-42: deep-dive reviewing of the doc, or deep-dive prototyping up the ideas expressed in the doc? | 09:52 |
| boris-42 | eglynn_ deep dive to adopt osprofiler to profile ceilometer | 09:53 |
| *** underyx is now known as Underyx|off | 09:54 | |
| boris-42 | eglynn_ that is the last concern that I didn't address in osprofiler | 09:54 |
| eglynn_ | boris-42: a-ha, cool ... the circular profiling :) | 09:54 |
| boris-42 | eglynn_ yep | 09:54 |
| boris-42 | =) | 09:54 |
| ogelbukh | who is profiling the profiler | 09:54 |
| eglynn_ | boris-42: BTW what version of ceilo are you targeting, and which storage driver? | 09:54 |
| boris-42 | ogelbukh we are+) | 09:54 |
| ogelbukh | profiler is ) | 09:55 |
| boris-42 | eglynn_ I was using SQL storage | 09:55 |
| boris-42 | eglynn_ and current master on time of summit | 09:55 |
| boris-42 | eglynn_ it's already a bit out of date I'll probably need to rebase | 09:55 |
| eglynn_ | boris-42: reason I asked, is that until very recent the performance of the sql-a driver was simply not viable | 09:55 |
| eglynn_ | boris-42: ... this has improved significantly since summit | 09:55 |
| boris-42 | eglynn_ yep sure but osprofile doesn't care of backedn | 09:56 |
| eglynn_ | boris-42: ... but still, mongodb would be the only realistic option for production | 09:56 |
| boris-42 | eglynn_ it's about ceilometer how to store data | 09:56 |
| boris-42 | eglynn_ I mean osprofiler is not related to the backend at all=) | 09:56 |
| eglynn_ | boris-42: it wouldn't profile the latency of the collector persisting data in the metering store? | 09:57 |
| boris-42 | eglynn_ hm but there are 2 timestamps | 09:57 |
| eglynn_ | boris-42: ... or profile the latency of API calls that are satisfied with queries on the metering store? | 09:57 |
| boris-42 | eglynn_ as I understood | 09:57 |
| boris-42 | eglynn_ one is generated on when we are sending message | 09:57 |
| boris-42 | eglynn_ another when it was consumed | 09:57 |
| eglynn_ | boris-42: two timestamps on metering data? | 09:57 |
| *** vrovachev has joined #openstack-ceilometer | 09:57 | |
| boris-42 | eglynn_ one sec | 09:57 |
| eglynn_ | boris-42: ... yep one timestamp when data acquired, and another when data is recorded | 09:58 |
| boris-42 | eglynn_ http://paste.openstack.org/show/82737/ | 09:58 |
| boris-42 | eglynn_ so I am using only timestampt | 09:58 |
| boris-42 | do I need to analyze when it was recorded? | 09:58 |
| eglynn_ | boris-42: ... delta between those two timestamps gives approximate total latency of ceilometer pipeline | 09:58 |
| eglynn_ | boris-42: ... but not the fine-grained latency | 09:59 |
| *** renlt has quit IRC | 09:59 | |
| boris-42 | eglynn_ so yep it's related to profiling ceilometer =) | 09:59 |
| *** r3pl4y has quit IRC | 10:00 | |
| eglynn_ | boris-42: in that paste ... "recorded_at": "2014-05-06T02:53:03.110724" MINUS "timestamp": "2014-05-06T02:52:59.357020" EQUALS ~11s | 10:00 |
| boris-42 | eglynn_ hehe=) | 10:00 |
| boris-42 | eglynn_ devstack installation under load lol | 10:00 |
| boris-42 | eglynn_ in VM | 10:00 |
| boris-42 | eglynn_ with 2cores and 4gb ram | 10:01 |
| eglynn_ | boris-42: so I thought that osprofiling ceilo would yield more detailed fine-grained step-wise latency than that? | 10:01 |
| eglynn_ | boris-42: ... yep, which why I made the point above about sql-a | 10:01 |
| *** r3pl4y has joined #openstack-ceilometer | 10:01 | |
| boris-42 | eglynn_ so my goal on summit was to cobine everything togeterh | 10:01 |
| boris-42 | eglynn_ and show that it works and can work without big changes | 10:02 |
| eglynn_ | boris-42: recommendation would be profile ceilo against mongo as that's the only driver recommended by many distros for production | 10:02 |
| boris-42 | eglynn_ yep sure in real situation we are going to that | 10:02 |
| eglynn_ | boris-42: (e.g. RDO and the Mirantis distro both only support mongo) | 10:02 |
| boris-42 | eglynn_ as well as it should be multimode installation | 10:02 |
| boris-42 | eglynn_ and sql backend for openstack & for ceilometer | 10:02 |
| boris-42 | mongo | 10:02 |
| boris-42 | should be on different nodes=) | 10:02 |
| eglynn_ | boris-42: also sql-a at the time of summit can be taken as broken and uneffectively unusable | 10:03 |
| boris-42 | but it's not related to the code at all=) it's more about how to use it | 10:03 |
| boris-42 | eglynn_ argree? | 10:03 |
| eglynn_ | boris-42: agree with "but it's not related to the code at all=) it's more about how to use it" ? | 10:03 |
| eglynn_ | boris-42: not sure I understand what you meant by that statement | 10:04 |
| boris-42 | I mean | 10:04 |
| boris-42 | osproifler doesn't care about backends and other stuff | 10:04 |
| boris-42 | it just thing that sends special notifications | 10:04 |
| boris-42 | so at this point we are discussing not osprofiler by self | 10:05 |
| eglynn_ | boris-42: sure, my point was that it would be a waste of time to profile ceilometer in a non-realistic configuration | 10:05 |
| boris-42 | but what is the best deployment to profile openstack cloud | 10:05 |
| boris-42 | eglynn_ yep but that things profile everything except ceilometer=) | 10:05 |
| eglynn_ | boris-42: ... i.e. using a broken version of storage driver not supported for prod | 10:05 |
| boris-42 | eglynn_ so agree that that data is not releastic in case of ceilometer | 10:06 |
| eglynn_ | boris-42: yeah, so I thought we were discussing using osprofiler to start profile ceilometer itself *also*? | 10:06 |
| boris-42 | eglynn_ but it shows that we are doing 120 db request do boot single VM | 10:06 |
| boris-42 | =) | 10:06 |
| boris-42 | eglynn_ yep we should | 10:06 |
| boris-42 | eglynn_ but as well I don't think that osprofiler should depend on what backend we are using | 10:07 |
| boris-42 | eglynn_ it should work in the same way, but results will be different | 10:07 |
| boris-42 | +) | 10:07 |
| boris-42 | eglynn_ launch time | 10:07 |
| boris-42 | =) | 10:07 |
| boris-42 | eglynn_ be back soon | 10:07 |
| eglynn_ | boris-42: ... I agree, just pointing out that there's no sense in using a driver configuration known to be broken | 10:07 |
| boris-42 | eglynn_ hehe=) | 10:07 |
| boris-42 | eglynn_ sure | 10:07 |
| *** nosnos has quit IRC | 10:08 | |
| eglynn_ | boris-42: ... cool enough, bon appetit! | 10:08 |
| boris-42 | eglynn_ see u | 10:08 |
| sileht | DinaBelova, can you removed the -1 about infra issue on this review https://review.openstack.org/#/c/97176/ ? | 10:17 |
| *** r3pl4y has quit IRC | 10:19 | |
| *** r3pl4y has joined #openstack-ceilometer | 10:21 | |
| *** matsuhashi has quit IRC | 10:24 | |
| *** Underyx|off is now known as underyx | 10:32 | |
| *** Longgeek has quit IRC | 10:34 | |
| *** Longgeek has joined #openstack-ceilometer | 10:35 | |
| *** shakamunyi has joined #openstack-ceilometer | 10:37 | |
| zqfan | eglynn: hi, can you please review the patch: https://review.openstack.org/#/c/93658/ | 10:38 |
| eglynn_ | zqfan: looking | 10:38 |
| sileht | DinaBelova, thx | 10:40 |
| zqfan | eglynn, thanks | 10:41 |
| DinaBelova | sileht, yeah, np :) I'm still not sure how these +1/-1 are appearing - as that's new patch set, but still -1 | 10:41 |
| DinaBelova | strange :) | 10:41 |
| *** shakamunyi has quit IRC | 10:41 | |
| r0j4z0 | hi all | 10:44 |
| r0j4z0 | on the notification agent, im able to pipeline only certain events? | 10:44 |
| r0j4z0 | for example if i want to store samples only with compute.instance.create.end | 10:45 |
| r0j4z0 | the idea is be able to fire an alarm when some random event occurs | 10:46 |
| *** matsuhashi has joined #openstack-ceilometer | 10:47 | |
| eglynn_ | r0j4z0: we don't support the notion of alarming on events | 10:50 |
| eglynn_ | r0j4z0: rather we alarm on statistics | 10:50 |
| eglynn_ | r0j4z0: ... i.e. when an aggregated statistic cross some threshold | 10:50 |
| eglynn_ | r0j4z0: ... an alarming on notifications BP was targeted at icehouse-3 but the implementation wasn't accepted onto master | 10:51 |
| r0j4z0 | i see... | 10:51 |
| *** _nadya_ has quit IRC | 10:51 | |
| r0j4z0 | then i cant store events as samples and then alarm based on that samples using some query | 10:52 |
| zqfan | hi, I find that ceilometer-specs has two files which are exactly same: specs/template.rst and specs/juno/template.rst, I want to remove the juno/template.rst, is it ok? | 10:52 |
| eglynn_ | r0j4z0: ... you can derive samples from notifications and alarm on the trend of values of those samples | 10:53 |
| eglynn_ | zqfan: one is a link to the other | 10:53 |
| eglynn_ | zqfan: we may have per-cycle versions of the template in the future | 10:54 |
| r0j4z0 | thank you eglynn_ i will try that :D | 10:55 |
| eglynn_ | zqfan: ... I just followed on the tripleo-specs led in that regard ... https://github.com/openstack/tripleo-specs/blob/master/specs/juno/template.rst | 10:55 |
| *** nacim has quit IRC | 10:55 | |
| eglynn_ | zqfan: ... but I'm not too fussed about it one way or the other | 10:55 |
| r0j4z0 | eglynn_ is https://review.openstack.org/#/c/69473/? | 10:57 |
| zqfan | eglynn, oh yes, it is a link, sorry, not notice that | 10:57 |
| eglynn_ | r0j4z0: ... yep, that's the one | 10:58 |
| r0j4z0 | that is just what i needed!! | 10:58 |
| r0j4z0 | :( | 10:58 |
| eglynn_ | r0j4z0: ... we may be able to resurrect this once the events API is implemented for all storage drivers | 10:58 |
| eglynn_ | r0j4z0: (... currently only sql-a, but planned for mongo & hbase) | 10:59 |
| r0j4z0 | i see | 10:59 |
| r0j4z0 | then the only option is to have a consumer on the queue to get the events and parse by myself to get alarmed when an event occurs | 11:00 |
| *** r3pl4y has quit IRC | 11:00 | |
| *** r3pl4y has joined #openstack-ceilometer | 11:01 | |
| r0j4z0 | or query the API each X seconds to get the events and traits | 11:02 |
| *** _nadya_ has joined #openstack-ceilometer | 11:05 | |
| *** zqfan has quit IRC | 11:14 | |
| openstackgerrit | Pradeep Kilambi proposed a change to openstack/ceilometer-specs: Spec for metering LBaaS https://review.openstack.org/94958 | 11:23 |
| *** matsuhashi has quit IRC | 11:25 | |
| *** matsuhashi has joined #openstack-ceilometer | 11:26 | |
| *** matsuhashi has quit IRC | 11:29 | |
| *** matsuhashi has joined #openstack-ceilometer | 11:29 | |
| eglynn_ | r0j4z0: yeap, unless the event of interest can be easily mapped on to a numerical value | 11:33 |
| eglynn_ | r0j4z0: ... in which case you could have a notification handler to consume the event & emit a sample, then alarm on the trend in values of that sample type | 11:34 |
| *** nacim has joined #openstack-ceilometer | 11:34 | |
| r0j4z0 | eglynn_ yes but the idea was to have an alarm with the data on the payload of the event, for example with the fixed_ips on compute.instance.create.end to be able to bootstrap the image using the event | 11:37 |
| eglynn_ | r0j4z0: in that case, a statistics-based approach clearly wouldn't be appropriate | 11:38 |
| r0j4z0 | yes | 11:38 |
| r0j4z0 | i think the best approach is to have a consumer on the notification queue and send the notification when the event occurs by myslef | 11:39 |
| r0j4z0 | myself* | 11:39 |
| eglynn_ | r0j4z0: yep, sounds reasonable | 11:40 |
| *** Alexei_987 has quit IRC | 11:42 | |
| *** Alexei_987 has joined #openstack-ceilometer | 11:42 | |
| *** r3pl4y has quit IRC | 11:46 | |
| *** r3pl4y has joined #openstack-ceilometer | 11:48 | |
| *** alexpilotti has joined #openstack-ceilometer | 11:53 | |
| *** nacim has quit IRC | 11:54 | |
| *** r3pl4y has quit IRC | 11:58 | |
| *** r3pl4y has joined #openstack-ceilometer | 12:00 | |
| *** promulo has quit IRC | 12:03 | |
| openstackgerrit | Pradeep Kilambi proposed a change to openstack/ceilometer-specs: Spec for metering LBaaS https://review.openstack.org/94958 | 12:05 |
| openstackgerrit | Alexei Kornienko proposed a change to openstack/ceilometer: Refactor tests to remove direct access to test DBManagers https://review.openstack.org/95613 | 12:06 |
| *** alexpilotti has quit IRC | 12:07 | |
| openstackgerrit | Nadya Privalova proposed a change to openstack/ceilometer: [HBase] get_resource optimization https://review.openstack.org/87249 | 12:16 |
| *** lcostantino has joined #openstack-ceilometer | 12:16 | |
| *** alexpilotti has joined #openstack-ceilometer | 12:22 | |
| *** jdob has joined #openstack-ceilometer | 12:22 | |
| *** r3pl4y has quit IRC | 12:22 | |
| *** lcostantino has quit IRC | 12:23 | |
| *** r3pl4y has joined #openstack-ceilometer | 12:24 | |
| *** ddieterly has quit IRC | 12:27 | |
| *** ddieterly has joined #openstack-ceilometer | 12:27 | |
| openstackgerrit | A change was merged to openstack/ceilometer: Improve performance of api requests with hbase scan https://review.openstack.org/93576 | 12:29 |
| *** eglynn_ has quit IRC | 12:32 | |
| *** cmart has joined #openstack-ceilometer | 12:46 | |
| cmart | Hello | 12:51 |
| *** `jpg has quit IRC | 12:52 | |
| *** psharma has quit IRC | 12:52 | |
| *** anand_ts has joined #openstack-ceilometer | 12:54 | |
| *** `jpg has joined #openstack-ceilometer | 12:54 | |
| *** fnaval has joined #openstack-ceilometer | 12:55 | |
| cmart | Just for you guys to check it out. There is a thread in the ML with designs related to the Alarm Management Page.It will be great to have your feedback :) (http://openstack.markmail.org/search/?q=alarm#query:alarm%20order%3Adate-backward+page:1+mid:t5jtw5zfpwswktiv+state:results) | 12:58 |
| *** ddieterly has quit IRC | 12:58 | |
| openstackgerrit | Pooja Tiwari proposed a change to openstack/ceilometer: Alarm default description update https://review.openstack.org/97777 | 12:58 |
| *** r3pl4y has quit IRC | 12:59 | |
| *** r3pl4y has joined #openstack-ceilometer | 13:01 | |
| *** thomasem has joined #openstack-ceilometer | 13:03 | |
| *** anand_ts has quit IRC | 13:05 | |
| *** Thumper650 has joined #openstack-ceilometer | 13:05 | |
| Thumper650 | hi all... have a strange problem | 13:06 |
| Thumper650 | I'm runnig seperate control, compute and telemetry nodes | 13:06 |
| Thumper650 | every time I issue an ceilomter command on any of them, I get the follwing output | 13:06 |
| Thumper650 | root@telemetry-01:~# ceilometer meter-list | 13:06 |
| Thumper650 | Unsupported scheme: | 13:06 |
| Thumper650 | It seems to be breaking here: | 13:07 |
| Thumper650 | + def get_proxy_url(self): | 13:07 |
| Thumper650 | + scheme = urlutils.urlparse(self.endpoint).scheme | 13:07 |
| Thumper650 | + if scheme == 'https': | 13:07 |
| Thumper650 | + return os.environ.get('https_proxy') | 13:07 |
| Thumper650 | + elif scheme == 'http': | 13:07 |
| Thumper650 | + return os.environ.get('http_proxy') | 13:07 |
| Thumper650 | + msg = 'Unsupported scheme: %s' % scheme | 13:07 |
| Thumper650 | + raise exc.InvalidEndpoint(msg) | 13:07 |
| Thumper650 | the reply hints that the scheme variable is empty... but I'm not sure what populates it | 13:08 |
| *** cmart has quit IRC | 13:10 | |
| *** jmckind has joined #openstack-ceilometer | 13:11 | |
| *** eglynn_ has joined #openstack-ceilometer | 13:11 | |
| *** cmart has joined #openstack-ceilometer | 13:14 | |
| *** joesavak has joined #openstack-ceilometer | 13:16 | |
| *** shakamunyi has joined #openstack-ceilometer | 13:17 | |
| openstackgerrit | Ildiko Vancsa proposed a change to openstack/ceilometer: Fix list of modules not included in auto-gen docs https://review.openstack.org/97268 | 13:17 |
| *** julim has joined #openstack-ceilometer | 13:18 | |
| *** Longgeek has quit IRC | 13:18 | |
| *** Longgeek has joined #openstack-ceilometer | 13:18 | |
| eglynn_ | Thumper650: check the URLs set in the service catalog for ceilometer | 13:19 |
| *** Longgeek has quit IRC | 13:19 | |
| *** Longgeek has joined #openstack-ceilometer | 13:19 | |
| *** Longgeek has quit IRC | 13:19 | |
| *** Longgeek_ has joined #openstack-ceilometer | 13:19 | |
| openstackgerrit | Christian Martinez proposed a change to openstack/ceilometer: Adding alarm list filtering by state and meter https://review.openstack.org/96582 | 13:20 |
| eglynn_ | Thumper650: $ keystone endpoint-list | grep $(keystone service-list | awk '/ceilometer/ {print $2}') | 13:21 |
| *** Longgeek_ has quit IRC | 13:21 | |
| eglynn_ | ^^^ there's gotta be a better way than that ;) | 13:21 |
| Thumper650 | eglynn: I have the endpoint set to a virtual IP balanced between my two telemetry hosts (that talk to the same DB) | 13:23 |
| *** Longgeek has joined #openstack-ceilometer | 13:24 | |
| Thumper650 | hmmm, this may be the result of some weird DNS... brb | 13:26 |
| *** palar has joined #openstack-ceilometer | 13:27 | |
| *** r3pl4y has quit IRC | 13:27 | |
| *** ddieterly has joined #openstack-ceilometer | 13:29 | |
| *** r3pl4y has joined #openstack-ceilometer | 13:29 | |
| *** alexpilotti has quit IRC | 13:30 | |
| *** `jpg has quit IRC | 13:32 | |
| *** gordc has joined #openstack-ceilometer | 13:33 | |
| Thumper650 | guess not... | 13:35 |
| *** fnaval has quit IRC | 13:38 | |
| *** _nadya_ has quit IRC | 13:38 | |
| Thumper650 | Fixed thanks to eglynn_'s sharp eyes... malformed endpoint publicurl | 13:46 |
| hoangdo | eglynn_: hi eglynn, it's me, the guy want to monitoring the software inside-VM. I have an idea: what if I publish a REST api for our software. Can ceilometer monitors from outside ? | 13:46 |
| hoangdo | eglynn_: is it simplify the work? | 13:47 |
| eglynn_ | hoangdo: if the REST API endpoint is callable from outside the VM, then yes it would simplify | 13:47 |
| eglynn_ | hoangdo: ... you'd still need to integrate with a ceilometer agent | 13:47 |
| eglynn_ | hoangdo: ... write a pollster to call your REST API | 13:48 |
| hoangdo | is it similar to central agent? | 13:48 |
| ildikov | hoangdo: here are the curently existing pollsters: https://github.com/openstack/ceilometer/tree/master/ceilometer/compute/pollsters | 13:50 |
| hoangdo | ildikov: wait, all of those pollsters run on (physical) compute node, right? | 13:51 |
| ildikov | hoangdo: right | 13:51 |
| *** _nadya_ has joined #openstack-ceilometer | 13:53 | |
| *** jdob has quit IRC | 13:53 | |
| hoangdo | ildikov: in our case (REST api), should pollsters run on Controller node. I'm not sure we can call api from compute node | 13:53 |
| boris-42 | eglynn_ +1 pls lol https://review.openstack.org/#/c/97778/ =) | 13:53 |
| *** rbowen has joined #openstack-ceilometer | 13:55 | |
| hoangdo | ildikov: I'm not sure about networking. we are using neutron GRE. And I intend to place an LBaaS in front of REST VM | 13:56 |
| *** jdob has joined #openstack-ceilometer | 13:56 | |
| *** heyongli has joined #openstack-ceilometer | 13:56 | |
| *** r3pl4y has quit IRC | 13:57 | |
| ildikov | hoangdo: hmm, I see | 13:58 |
| *** ilyashakhat has joined #openstack-ceilometer | 13:59 | |
| *** r3pl4y has joined #openstack-ceilometer | 13:59 | |
| hoangdo | ildikov: should it run on network node? | 14:01 |
| openstackgerrit | A change was merged to openstack/ceilometer-specs: Spec for metering LBaaS https://review.openstack.org/94958 | 14:02 |
| *** promulo has joined #openstack-ceilometer | 14:02 | |
| ildikov | hoangdo: it depends on your network toplogy, that where the REST API(s) are available from | 14:02 |
| hoangdo | ildikov: REST api will run on a VM. Initially, I intend to assign the VM an public IP. | 14:04 |
| *** fnaval has joined #openstack-ceilometer | 14:04 | |
| ildikov | hoangdo: currently the Ceilometer API supports to send samples to Ceilometer | 14:08 |
| *** rbowen has quit IRC | 14:08 | |
| ildikov | hoangdo: so I was just thinking about if that would be a good solution or not for this case | 14:09 |
| EmilienM | eglynn_: trying to get reviews on #openstack-qa about https://review.openstack.org/#/c/94468/ | 14:12 |
| EmilienM | eglynn_: a bit hard though. | 14:12 |
| eglynn_ | EmilienM: ... I'll also add my non-binding $0.02 | 14:13 |
| eglynn_ | EmilienM: ... hard to get traction on the review? | 14:13 |
| EmilienM | eglynn_: non-binding? | 14:14 |
| hoangdo | ildikov: so even I write an agent run inside the node, how can it communicate with the Ceilometer? | 14:15 |
| ildikov | hoangdo: the node is the VM? | 14:16 |
| eglynn_ | EmilienM: ... non-binding in the sense of not a core +2 on the review | 14:16 |
| EmilienM | eglynn_: ah | 14:16 |
| EmilienM | ok | 14:16 |
| *** Longgeek has quit IRC | 14:27 | |
| *** r3pl4y has quit IRC | 14:29 | |
| *** heyongli has quit IRC | 14:29 | |
| cmart | Hello! | 14:31 |
| hoangdo | ildikov: yes a VM | 14:31 |
| hoangdo | ildikov: because I want to monitor the software info (rq queue info) | 14:31 |
| ildikov | hoangdo: somehow you have to be able to connect even the VM or something that collects the info from the VM with Ceilometer | 14:32 |
| ildikov | hoangdo: so if the VMs are in a separate network, it will block this for sure | 14:33 |
| ildikov | cmart: hi | 14:33 |
| cmart | Hi! | 14:33 |
| *** gordc1 has joined #openstack-ceilometer | 14:33 | |
| *** gordc has quit IRC | 14:34 | |
| cmart | I'm working on an alarm management page for horizon.. lblanchard sent some page designs yesterday on the ML that are a guide to follow, but IMHO it needs to be modified | 14:35 |
| cmart | it will be great if you guys (and girls) can give her some feedback about it | 14:35 |
| cmart | (http://openstack.markmail.org/search/?q=alarm#query:alarm%20order%3Adate-backward+page:1+mid:t5jtw5zfpwswktiv+state:results) | 14:35 |
| ildikov | cmart: what would you like to modify? | 14:36 |
| hoangdo | ildikov: VMs always on separate network, I guess. Our VMs network controlled by neutron, and I think Ceilometer use other network. So there is no way to poll info from inside VM | 14:36 |
| hoangdo | ildikov: blocked! Do you have any suggestion? | 14:37 |
| ildikov | hoangdo: I think the first step should be to figure out how to transmit data between the VMs and Ceilometer (agent or API) | 14:37 |
| ildikov | cmart: I checked the design plan quickly | 14:39 |
| cmart | for instance the way that alarms are created. For me, it should be a workflow, and it should contemplate the case of "combined alarms" (which is really helpful for me at least). | 14:39 |
| ildikov | cmart: do you want to collect independent opinions or you have ideas that you would like to discuss? | 14:39 |
| ildikov | cmart: a-ha, yes, I agree, I missed that too | 14:40 |
| *** rwsu has joined #openstack-ceilometer | 14:40 | |
| *** promulo has quit IRC | 14:40 | |
| ildikov | cmart: I also do not remember how much it was supported to specify query to the alarms | 14:40 |
| cmart | ildikov: I'm kind of new with the alarms stuff, and I think that "alarm experts" should give their feedback around that.. | 14:40 |
| cmart | regarding queries, I was working on a bug related to that | 14:41 |
| cmart | currently, we have two ways of "querying alarms". With alarm-list --q or query-alarm "a_complex_filter" | 14:41 |
| ildikov | cmart: do you mean the state filtering? | 14:42 |
| cmart | my fix works around the alarm-list command. It allows you to filter the alarm-list by state and meter_name (which is enougth for now) | 14:42 |
| cmart | filter by alarm state is like: "Ok, give me all the alarms that are in the state "ok" (like "active alarms") | 14:43 |
| cmart | smth like: ceilometer alarm-list --q "state=string::insufficient data" | 14:43 |
| ildikov | cmart: a-ha, ok, I remember that one | 14:44 |
| ildikov | cmart: the query-alarm did not solve this issue? | 14:45 |
| cmart | ildikov: it has some issues around filtering by meter name (specially on the sqlalchemy driver) | 14:46 |
| ildikov | cmart: hmm, what kind of issues? | 14:46 |
| cmart | the query:_alarm method was very "generic". It uses a queryTransformer to convert the filter expression into a valid sql statement | 14:47 |
| cmart | in the case of meter, that information is stored within the rule column inside the alarm models.. | 14:48 |
| ildikov | cmart: ok, I think I know what you think, the meter name is embedded in the threshold rule | 14:48 |
| cmart | yes | 14:48 |
| *** matsuhashi has quit IRC | 14:49 | |
| ildikov | cmart: ok, I know that issue, it's on the list to add support to these cases too... | 14:49 |
| cmart | yes | 14:49 |
| ildikov | cmart: as for the original question, I'm wondering if it would worth to add an item to the meeting agenda | 14:49 |
| ildikov | cmart: or one more mail on the ML with Ceilometer tag included that hey guys please check | 14:50 |
| cmart | I can do that. I'll forward that email and add the ceilometer tag on the subject | 14:50 |
| ildikov | cmart: I plan to have a deeper look at that doc anyway | 14:51 |
| ildikov | cmart: and also if you already have a list that you would like to discuss here, we can that also | 14:51 |
| cmart | ildikov: what I can do is to have a proposal (based on the proposed design and "my thoughts") and share it with you so we can discuss it in the next meeting (or the next) | 14:53 |
| ildikov | cmart: that sounds good to me | 14:54 |
| cmart | ildikov: cool! Should I write an etherpad? | 14:54 |
| ildikov | cmart: I think that would be useful | 14:55 |
| cmart | ildikov: will do. Tomorrow is the meeting, right? | 14:56 |
| ildikov | cmart: for this week yes | 14:56 |
| ildikov | cmart: I just need one or two mins to clean up the agenda | 14:56 |
| cmart | ildikov: OK. I will write that and let you know (so, if you have space, we can add that topic to the agenda:)) | 14:57 |
| hoangdo | ildikov: hi, I found this post: https://ask.openstack.org/en/question/1490/whats-the-best-way-to-obtain-metrics-from-inside-vm-os-via-ceilometer/ | 14:59 |
| hoangdo | seems like it's implemented in Havana ? | 14:59 |
| amalagon | hi jd__ I was wondering if I could ask you about the --config-file flag when calling gnocchi-api? | 15:01 |
| ildikov | cmart: ok, I will let you know , if it fits or not | 15:01 |
| jd__ | amalagon: sure | 15:01 |
| amalagon | jd__: thanks; so right now I can't get gnocchi-api to work without the --config-file specified; it gives me an error about 'NoneType' object has no attribute 'drivername' | 15:03 |
| *** jsavak has joined #openstack-ceilometer | 15:03 | |
| *** joesavak has quit IRC | 15:03 | |
| ildikov | hoangdo: that should be the API support for sending samples to Ceilometer via its API, what I mentioned earlier | 15:04 |
| jd__ | amalagon: where's your configuration file? | 15:04 |
| *** idegtiarov has quit IRC | 15:04 | |
| amalagon | jd__: /etc/gnocchi/ | 15:05 |
| jd__ | amalagon: ok I see, I'm sending a ptch | 15:05 |
| amalagon | jd__: thanks! er, should I have put gnocchi.conf someplace different? | 15:06 |
| jd__ | amalagon: no it's just a bug | 15:06 |
| ildikov | hoangdo: http://docs.openstack.org/developer/ceilometer/webapi/v2.html#post--v2-meters-%28meter_name%29 | 15:06 |
| openstackgerrit | Ildiko Vancsa proposed a change to openstack/ceilometer: Fix list of modules not included in auto-gen docs https://review.openstack.org/97268 | 15:07 |
| *** cmart has quit IRC | 15:08 | |
| jd__ | amalagon: https://review.openstack.org/#/c/97819/ | 15:09 |
| amalagon | jd__: cool! | 15:09 |
| hoangdo | ildikov: thanks ildikov | 15:11 |
| ildikov | hoangdo: np, I hope it will help | 15:14 |
| *** Infitialis has quit IRC | 15:14 | |
| amalagon | jd__: hey, just to double check (and alert for the newbie question); I pulled the code from the review but gnocchi-api still gives the same error; is there something else I should be doing? | 15:17 |
| jd__ | amalagon: no let me check | 15:19 |
| eglynn_ | hoangdo: WRT https://ask.openstack.org/en/question/1490/whats-the-best-way-to-obtain-metrics-from-inside-vm-os-via-ceilometer/ | 15:20 |
| jd__ | amalagon: ah did you reinstall it after or something? | 15:20 |
| jd__ | amalagon: just to be sure it loads the right service.py file | 15:20 |
| amalagon | jd__: ohh..no I didn't, sorry about that | 15:20 |
| eglynn_ | hoangdo: ... that approach is exactly what I was talking about earlier | 15:20 |
| jd__ | amalagon: yeah that might be it :) | 15:20 |
| amalagon | jd__: it's happy now! :D | 15:21 |
| eglynn_ | hoangdo: ... *however*, the answer does not address the important issue of how the caller of the API is authenticated | 15:21 |
| jd__ | amalagon: cool :) | 15:21 |
| eglynn_ | hoangdo: that's why I brought up the whole question of propogating credentials | 15:21 |
| *** nati_ueno has joined #openstack-ceilometer | 15:23 | |
| *** rbowen has joined #openstack-ceilometer | 15:24 | |
| *** zqfan_home has joined #openstack-ceilometer | 15:24 | |
| *** IvanBerezovskiy has left #openstack-ceilometer | 15:27 | |
| *** r3pl4y has joined #openstack-ceilometer | 15:31 | |
| *** joesavak has joined #openstack-ceilometer | 15:31 | |
| *** jsavak has quit IRC | 15:34 | |
| openstackgerrit | Chinmaya Bharadwaj proposed a change to openstack/ceilometer: VMware: Fixes ceilometer-compute service start failure https://review.openstack.org/97831 | 15:37 |
| *** zqfan_home is now known as zqfan | 15:37 | |
| *** chinmay_ has joined #openstack-ceilometer | 15:37 | |
| *** Thumper650 has quit IRC | 15:40 | |
| *** promulo has joined #openstack-ceilometer | 15:40 | |
| chinmay_ | @jaypipes : hi | 15:44 |
| openstackgerrit | A change was merged to openstack/python-ceilometerclient: Refactor split_by_op and split_by_datatype https://review.openstack.org/96514 | 15:46 |
| openstackgerrit | OpenStack Proposal Bot proposed a change to openstack/ceilometer: Updated from global requirements https://review.openstack.org/96819 | 15:47 |
| *** rbowen has quit IRC | 15:49 | |
| *** chinmay_ has quit IRC | 15:51 | |
| openstackgerrit | OpenStack Proposal Bot proposed a change to openstack/python-ceilometerclient: Updated from global requirements https://review.openstack.org/91238 | 15:52 |
| *** _cjones_ has joined #openstack-ceilometer | 15:55 | |
| amalagon | hi eglynn_! just want to run something by you - for the create database command in psql, I can do createdb -u USERNAME but not createdb -u root - is it confusing to put the line in the readme as createdb -u USERNAME? | 15:58 |
| eglynn_ | amalagon: well that should be fine, I prolly mis-directed you with the reference to root in my comment on gerrit | 15:58 |
| *** nati_ueno has quit IRC | 15:59 | |
| eglynn_ | amalagon: i.e. feel free to use "createdb -u USERNAME" instead of "createdb -u root" is that's what actually works | 15:59 |
| amalagon | eglynn_: alright, thanks! just wanted to double check | 16:00 |
| eglynn_ | amalagon: np! | 16:00 |
| *** Ruetobas has quit IRC | 16:01 | |
| *** skelpter has joined #openstack-ceilometer | 16:01 | |
| *** Ruetobas has joined #openstack-ceilometer | 16:03 | |
| *** jsavak has joined #openstack-ceilometer | 16:06 | |
| *** joesavak has quit IRC | 16:07 | |
| *** joesavak has joined #openstack-ceilometer | 16:08 | |
| *** Ruetobas has quit IRC | 16:08 | |
| *** jsavak has quit IRC | 16:11 | |
| *** ddieterl_ has joined #openstack-ceilometer | 16:12 | |
| openstackgerrit | Christian Berendt proposed a change to openstack/ceilometer: debug level logs should not be translated https://review.openstack.org/93021 | 16:14 |
| *** Ruetobas has joined #openstack-ceilometer | 16:14 | |
| *** underyx is now known as Underyx|off | 16:14 | |
| *** ddieterly has quit IRC | 16:14 | |
| openstackgerrit | Mehdi Abaakouk proposed a change to openstack/ceilometer: Allow to have different DB for alarm and metering https://review.openstack.org/94829 | 16:21 |
| openstackgerrit | Mehdi Abaakouk proposed a change to openstack/ceilometer: Allows to share engine between both sql driver https://review.openstack.org/97847 | 16:21 |
| eglynn_ | gordc1: o/ | 16:36 |
| *** gordc1 is now known as gordc | 16:37 | |
| gordc | eglynn_: hey, whatsup? | 16:37 |
| eglynn_ | gordc: ... still on for that sql-alchemy call later today with Mike Bayer? | 16:38 |
| gordc | eglynn_: yep -- just making notes to the etherpad. it's at 2pm ET right? ~1hr20min from now? | 16:38 |
| eglynn_ | gordc: excellent, yeap at 1800UTC ... thank you sir! | 16:39 |
| gordc | eglynn_: cool cool. will dial in to conference then. | 16:40 |
| *** _nadya_ has quit IRC | 16:40 | |
| eglynn_ | gordc: nice one :) | 16:40 |
| *** Alexei_987 has quit IRC | 16:46 | |
| *** cmart has joined #openstack-ceilometer | 16:53 | |
| *** joesavak has quit IRC | 17:03 | |
| *** joesavak has joined #openstack-ceilometer | 17:03 | |
| *** niteshselkari has joined #openstack-ceilometer | 17:05 | |
| *** niteshselkari has quit IRC | 17:12 | |
| *** thomasem has quit IRC | 17:13 | |
| *** shakamunyi has quit IRC | 17:13 | |
| *** thomasem has joined #openstack-ceilometer | 17:13 | |
| *** niteshselkari_ has joined #openstack-ceilometer | 17:15 | |
| *** safchain has quit IRC | 17:17 | |
| niteshselkari_ | hi all | 17:18 |
| niteshselkari_ | <eglynn_>: hi eglynn. I had asked this question on ask.openstack. https://ask.openstack.org/en/question/30801/how-can-i-find-volume-space-utilized-by-an-instance/ | 17:20 |
| eglynn_ | niteshselkari_: yeah I know, it's on my list of things to look into | 17:21 |
| *** fnaval has quit IRC | 17:22 | |
| openstackgerrit | Cristian A Sanchez proposed a change to openstack/python-ceilometerclient: Make HTTP client aware of no_proxy variable https://review.openstack.org/95565 | 17:24 |
| *** thomasem has quit IRC | 17:25 | |
| openstackgerrit | Chinmaya Bharadwaj proposed a change to openstack/ceilometer: VMware: Fixes ceilometer-compute service start failure https://review.openstack.org/97831 | 17:25 |
| *** thomasem has joined #openstack-ceilometer | 17:26 | |
| niteshselkari_ | <eglynn>: What approach I can take to find out this... | 17:26 |
| *** skelpter has quit IRC | 17:30 | |
| *** nati_ueno has joined #openstack-ceilometer | 17:34 | |
| cmart | ZhiQiang Fan, I don't know what your irc nickname is, but thanks for all the support! | 17:36 |
| DinaBelova | eglynn_, jd__ btw - what do you think about how will live gnocchi in the future? As a separated project, or part of the ceilometer itself? | 17:37 |
| zqfan | cmart, irc nick zqfan | 17:37 |
| eglynn_ | DinaBelova: part of ceilometer itself was my assumption | 17:37 |
| cmart | zqfan: Why I didn't think on that?? haha Sorry! And thanks for all your help! | 17:37 |
| eglynn_ | DinaBelova: ... the initial separateness enables rapid iteration/innovation | 17:37 |
| DinaBelova | eglynn_, yeah, ok, I also thought that if this POC will be cool - it should not be one more service :) | 17:38 |
| DinaBelova | yeah, just to be sure | 17:38 |
| eglynn_ | DinaBelova: POC == proof of concept? | 17:38 |
| DinaBelova | yes :) | 17:38 |
| DinaBelova | because now we're playing there :) but it'll be something more :) | 17:38 |
| DinaBelova | the overall future of ceilometer :) | 17:39 |
| eglynn_ | DinaBelova: ... yeah, so my assumption is that being the core of the v3 API for ceilo, it'll have to come under the ceilometer umbrella | 17:39 |
| *** harlowja_away is now known as harlowja | 17:39 | |
| DinaBelova | well - yeah, there are too many projects in openstack :D | 17:39 |
| DinaBelova | already I mean :) | 17:40 |
| eglynn_ | DinaBelova: ... however, it *could* still be realized as a separate service | 17:40 |
| eglynn_ | DinaBelova: ... (in the sense of the ceilometer v2 and v3 APIs being hosted in different physical processes) | 17:40 |
| DinaBelova | well, this should be discussed later I guess - when we'll have the all picture | 17:40 |
| *** Alexei_987 has joined #openstack-ceilometer | 17:41 | |
| eglynn_ | DinaBelova: ... but either way, still part of the group of agents/processes/services that we call "ceilometer" | 17:41 |
| DinaBelova | ok, thanks! | 17:41 |
| DinaBelova | call in 20 mins, btw? | 17:41 |
| eglynn_ | DinaBelova: ... yeap, prolly a major agenda item for the mid-cycle meetup | 17:41 |
| DinaBelova | eglynn_, for sure :) | 17:41 |
| eglynn_ | DinaBelova: (if not discussed and decided before then) | 17:41 |
| eglynn_ | DinaBelova: ... yep, sql-a call at 1800UTC | 17:41 |
| DinaBelova | ok, cool | 17:42 |
| *** thomasem_ has joined #openstack-ceilometer | 17:45 | |
| openstackgerrit | ZhiQiang Fan proposed a change to openstack/ceilometer: Update doc for sample config file issue https://review.openstack.org/94324 | 17:46 |
| *** thomasem has quit IRC | 17:46 | |
| *** zqfan has quit IRC | 17:48 | |
| *** _nadya_ has joined #openstack-ceilometer | 17:52 | |
| *** shakayumi has joined #openstack-ceilometer | 18:08 | |
| *** shakayumi has quit IRC | 18:08 | |
| *** _nadya_ has quit IRC | 18:09 | |
| *** shakayumi has joined #openstack-ceilometer | 18:09 | |
| *** shakayumi has quit IRC | 18:09 | |
| *** niteshselkari_ has quit IRC | 18:12 | |
| *** jsavak has joined #openstack-ceilometer | 18:16 | |
| *** joesavak has quit IRC | 18:16 | |
| *** shakayumi has joined #openstack-ceilometer | 18:18 | |
| *** nati_uen_ has joined #openstack-ceilometer | 18:23 | |
| *** nati_ueno has quit IRC | 18:26 | |
| openstackgerrit | Chinmaya Bharadwaj proposed a change to openstack/ceilometer: VMware: Fixes ceilometer-compute service start failure https://review.openstack.org/97831 | 18:26 |
| *** jdob has quit IRC | 18:28 | |
| *** jdob has joined #openstack-ceilometer | 18:28 | |
| *** fnaval has joined #openstack-ceilometer | 18:35 | |
| *** r0j4z0 has quit IRC | 18:41 | |
| *** CAP1089 has joined #openstack-ceilometer | 18:41 | |
| *** CAP1089 is now known as r0j4z0 | 18:41 | |
| *** promulo has quit IRC | 18:47 | |
| openstackgerrit | Chinmaya Bharadwaj proposed a change to openstack/ceilometer: VMware: Fixes ceilometer-compute service start failure https://review.openstack.org/97831 | 18:54 |
| *** _cjones_ has quit IRC | 19:00 | |
| *** _cjones_ has joined #openstack-ceilometer | 19:01 | |
| openstackgerrit | Christian Berendt proposed a change to openstack/python-ceilometerclient: Overwrite HelpFormatter constructur to extend argument column https://review.openstack.org/97881 | 19:04 |
| *** ddutta has joined #openstack-ceilometer | 19:07 | |
| eglynn_ | DinaBelova, gordc: ... so, an useful exercise, or? | 19:19 |
| gordc | eglynn_: yeah, definitely. i'll start testing out some of the ideas Mike threw out... see if we can improve what we have. | 19:23 |
| eglynn_ | gordc: excellent :) | 19:23 |
| gordc | nice to have an expert to push us in right direction. | 19:23 |
| eglynn_ | yeah, my thought exactly | 19:23 |
| eglynn_ | ... he seems like a pretty constructive guy to me | 19:24 |
| gordc | eglynn_: agreed. i wasn't even aware there was a term to the metadata table solution i implemented. | 19:24 |
| gordc | now i can google how other people have done it. | 19:25 |
| *** promulo has joined #openstack-ceilometer | 19:25 | |
| eglynn_ | gordc: not only a term for it, an actual 3 leter acronym! :) | 19:25 |
| gordc | that's when you know it's a solid idea... when its given an acronym.lol | 19:26 |
| eglynn_ | first a three letter acronym ... then a whole O'Reilly book ... then a patent! ;) | 19:27 |
| eglynn_ | gordc, DinaBelova: BTW if there's anything I missed or described badly in the short summary on the etherpad, please feel free to hack away at it! | 19:27 |
| gordc | will do. i'll take a look at it later today... off to another call. | 19:28 |
| eglynn_ | gordc: cool, thank you! :) | 19:28 |
| eglynn_ | right-o, getting late in my TZ, I'm gonna call it a day | 19:28 |
| eglynn_ | ... chat tmrw! | 19:28 |
| gordc | cheers | 19:28 |
| *** nati_uen_ has quit IRC | 19:33 | |
| *** ddutta has quit IRC | 19:36 | |
| DinaBelova | eglynn_, yeah, useful really :) | 19:38 |
| DinaBelova | and Mike has really huge experience here | 19:38 |
| *** nati_ueno has joined #openstack-ceilometer | 19:39 | |
| DinaBelova | so that's cool to know his PoV | 19:39 |
| *** palar_ has joined #openstack-ceilometer | 19:40 | |
| *** palar has quit IRC | 19:43 | |
| *** palar_ has quit IRC | 19:44 | |
| *** ddutta has joined #openstack-ceilometer | 19:47 | |
| *** safchain has joined #openstack-ceilometer | 19:48 | |
| *** jsavak has quit IRC | 19:49 | |
| *** joesavak has joined #openstack-ceilometer | 19:50 | |
| *** eglynn_ has quit IRC | 19:50 | |
| *** jsavak has joined #openstack-ceilometer | 19:51 | |
| *** joesavak has quit IRC | 19:54 | |
| *** promulo has quit IRC | 19:59 | |
| *** nati_ueno has quit IRC | 20:04 | |
| *** nati_uen_ has joined #openstack-ceilometer | 20:07 | |
| *** nati_ueno has joined #openstack-ceilometer | 20:09 | |
| *** nati_uen_ has quit IRC | 20:10 | |
| *** ddutta has quit IRC | 20:15 | |
| *** fnaval has quit IRC | 20:31 | |
| *** ddutta has joined #openstack-ceilometer | 20:39 | |
| *** fnaval has joined #openstack-ceilometer | 20:43 | |
| *** ddutta has quit IRC | 20:44 | |
| *** ddutta has joined #openstack-ceilometer | 20:44 | |
| *** cmart has quit IRC | 20:45 | |
| *** claudiub has joined #openstack-ceilometer | 20:51 | |
| *** ddutta has quit IRC | 20:52 | |
| *** harlowja has quit IRC | 20:54 | |
| *** harlowja has joined #openstack-ceilometer | 20:54 | |
| *** jdob has quit IRC | 21:01 | |
| *** _nadya_ has joined #openstack-ceilometer | 21:09 | |
| *** _nadya_ has quit IRC | 21:14 | |
| *** nati_ueno has quit IRC | 21:26 | |
| *** julim has quit IRC | 21:32 | |
| *** jsavak has quit IRC | 21:44 | |
| *** gordc has left #openstack-ceilometer | 21:51 | |
| *** prad has quit IRC | 22:28 | |
| *** `jpg has joined #openstack-ceilometer | 22:31 | |
| *** skelpter has joined #openstack-ceilometer | 22:41 | |
| *** `jpg has quit IRC | 22:41 | |
| *** skelpter has left #openstack-ceilometer | 22:45 | |
| *** shakayumi has quit IRC | 22:55 | |
| *** thomasem_ has quit IRC | 22:58 | |
| *** shakayumi has joined #openstack-ceilometer | 22:59 | |
| *** prad has joined #openstack-ceilometer | 22:59 | |
| *** `jpg has joined #openstack-ceilometer | 23:01 | |
| *** ddieterl_ has quit IRC | 23:04 | |
| *** shakayumi has quit IRC | 23:15 | |
| *** skelpter has joined #openstack-ceilometer | 23:34 | |
| *** skelpter has left #openstack-ceilometer | 23:41 | |
| *** jaypipes has quit IRC | 23:48 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!