Friday, 2013-11-29

*** nati_ueno has quit IRC00:01
*** matsuhashi has joined #openstack-metering00:33
*** mgagne has quit IRC00:37
*** nosnos has joined #openstack-metering01:20
*** mengxd has joined #openstack-metering01:37
*** rongze has joined #openstack-metering01:59
*** rongze has quit IRC02:18
*** rongze has joined #openstack-metering02:20
*** ArcTanSusan has joined #openstack-metering02:25
*** bingbu has joined #openstack-metering02:31
*** suo has joined #openstack-metering02:41
openstackgerritLianhao Lu proposed a change to openstack/ceilometer: Add resource loader support  https://review.openstack.org/5874702:42
openstackgerritLianhao Lu proposed a change to openstack/ceilometer: Added resources support in pollster's interface  https://review.openstack.org/5848902:42
*** rongze has quit IRC03:06
*** rongze has joined #openstack-metering03:06
*** rbrady has quit IRC03:55
*** rongze has quit IRC04:11
*** rongze has joined #openstack-metering04:17
*** urulama has joined #openstack-metering04:21
*** boris-42 has joined #openstack-metering04:49
*** rongze has quit IRC04:50
*** rongze has joined #openstack-metering05:08
*** ArcTanSusan has quit IRC05:27
*** nati_ueno has joined #openstack-metering05:44
*** urulama has quit IRC05:45
*** ArcTanSusan has joined #openstack-metering05:47
*** urulama has joined #openstack-metering05:47
*** ildikov has joined #openstack-metering05:59
openstackgerritJenkins proposed a change to openstack/ceilometer: Imported Translations from Transifex  https://review.openstack.org/5760306:05
*** sdake_ has joined #openstack-metering06:07
*** nadya has joined #openstack-metering06:13
*** nadya is now known as Guest2065506:13
*** ChanServ changes topic to "This chan is deprecated, please join #openstack-ceilometer"06:16
*** ArcTanSusan has quit IRC06:16
*** ildikov has quit IRC06:20
*** sdake_ has quit IRC06:20
*** ArcTanSusan has joined #openstack-metering06:26
*** urulama has quit IRC06:50
*** Guest20655 has quit IRC06:52
*** rongze has quit IRC07:03
*** rongze has joined #openstack-metering07:06
*** rongze has quit IRC07:27
*** rongze has joined #openstack-metering07:28
*** nosnos_ has joined #openstack-metering07:33
*** nati_ueno has quit IRC07:34
*** nati_ueno has joined #openstack-metering07:35
*** nosnos has quit IRC07:37
*** rongze_ has joined #openstack-metering07:50
*** rongze has quit IRC07:53
*** rongze has joined #openstack-metering08:11
*** boris-42 has quit IRC08:13
*** rongze_ has quit IRC08:15
*** matsuhashi has quit IRC08:28
*** nprivalova has joined #openstack-metering08:37
*** shardy_afk is now known as shardy08:39
*** herndon has quit IRC08:42
*** tian has quit IRC08:42
*** llu has quit IRC08:43
*** tian has joined #openstack-metering08:44
*** llu has joined #openstack-metering08:44
*** rongze has quit IRC08:44
*** rongze has joined #openstack-metering08:45
*** SergeyLukjanov has joined #openstack-metering09:17
*** dperaza has joined #openstack-metering09:20
*** matsuhashi has joined #openstack-metering09:20
*** dperaza1 has quit IRC09:26
*** matsuhashi has quit IRC09:29
*** matsuhas_ has joined #openstack-metering09:31
*** boris-42 has joined #openstack-metering09:31
*** nosnos_ has quit IRC09:36
*** eglynn has joined #openstack-metering09:38
*** mengxd has quit IRC09:44
*** ruhe has joined #openstack-metering10:02
*** matsuhas_ has quit IRC10:12
*** ildikov has joined #openstack-metering10:14
*** matsuhashi has joined #openstack-metering10:17
*** ArcTanSusan has quit IRC10:19
*** bingbu has quit IRC10:19
*** nprivalova has quit IRC10:21
openstackgerritA change was merged to openstack/ceilometer: Imported Translations from Transifex  https://review.openstack.org/5760310:37
*** nati_ueno has quit IRC10:42
*** nprivalova has joined #openstack-metering10:44
*** ruhe has quit IRC10:45
*** ruhe has joined #openstack-metering11:17
*** mengxd has joined #openstack-metering11:19
openstackgerritChenZheng proposed a change to openstack/ceilometer: Add i18n warpping for all LOG messages  https://review.openstack.org/5468311:20
*** SergeyLukjanov is now known as _SergeyLukjanov11:30
*** _SergeyLukjanov has quit IRC11:30
*** ruhe has quit IRC11:31
*** mengxd has quit IRC11:56
*** matsuhashi has quit IRC12:19
*** matsuhashi has joined #openstack-metering12:19
*** matsuhashi has quit IRC12:23
*** rongze has quit IRC12:41
*** SergeyLukjanov has joined #openstack-metering12:49
*** ruhe has joined #openstack-metering12:49
*** boris-42 has quit IRC13:07
*** mengxd has joined #openstack-metering13:11
*** mengxd has quit IRC13:11
*** rongze has joined #openstack-metering13:12
*** Shaan7 has joined #openstack-metering13:19
*** jd__ has left #openstack-metering13:22
*** rbrady has joined #openstack-metering13:24
*** suo has quit IRC13:27
*** rongze has quit IRC13:28
*** scroiset has left #openstack-metering13:36
*** ruhe has quit IRC13:45
*** rbrady has quit IRC14:11
*** herndon has joined #openstack-metering14:11
openstackgerritChenZheng proposed a change to openstack/ceilometer: Add i18n warpping for all LOG messages  https://review.openstack.org/5468314:13
*** nati_ueno has joined #openstack-metering14:13
*** jergerber has joined #openstack-metering14:17
*** thomasem has joined #openstack-metering14:21
lsmolaeglynn, hello, are yo uaround14:22
eglynnlsmola: I am14:22
eglynnlsmola: 'sup?14:22
lsmolaeglynn, I am trying to build something like this http://people.redhat.com/~lsurette/OpenStack/Horizon%20Overview%20Pages_v1.0.pdf14:22
lsmolaeglynn, do you think it's possible e.g. for current instance?14:23
eglynnlsmola: are those little trend lines what are known as sparklines?14:23
lsmolaeglynn, basically if I do SUM of some appropriate period like 3 minutes, it gives me almost the time series i want14:24
lsmolaeglynn, yes, this will be used as sparklines in tables too14:24
eglynnlsmola: so the "90 instances used, 10 remaining" ... that refers to quotas, right?14:24
lsmolaeglynn, yes14:24
lsmolaeglynn, (if you will make quotas lower, it will show values more then 100%, but let it be)14:25
lsmolaeglynn, the thing is if i can rely on aggregation14:25
eglynnlsmola: k, so basically there's a mix here between two different accounting systems IIUC14:25
eglynnlsmola: ceilometer to determine the current usage14:26
*** thomasem has quit IRC14:26
eglynnlsmola: ... and nova os-quotas to determine the high-water-mark, correct?14:26
lsmolaeglynn, let's say that it is polling for presence of all of them every 10 minutes, I have to basically rely on it will be collected like in 3 minutes, so I set the aggregation for 5minutes14:27
lsmolaeglynn, yes14:27
lsmolaeglynn, but basically every sample that is running wild, is miss-counted :-(14:28
eglynnlsmola: OK, so just thinking aloud for a second ...14:28
lsmolaeglynn, I am thinking whether it would be better to actually get new meters14:28
eglynnlsmola: there's a possibility that the "remaining" portion reported may be slightly misleading14:28
lsmolaeglynn, making samples for Instances_used (for project) and instances_total14:29
eglynnlsmola: as in reality, it the value in the quota_usages table in the nova DB that's used for the quota headroom determination14:29
eglynnlsmola: not the instances meters in ceilo14:29
lsmolaeglynn, well I have decided to take those from nova, so it is always accurate, so I am taking just the timeseries from ceilometer14:29
lsmolaeglynn, have to go on meeting14:30
eglynnlsmola: which one is not always accurate, the nova-maintained instance count?14:30
eglynnlsmola: a-ha, k, laters ...14:30
lsmolaeglynn, nope the aggregation of ceilometer14:30
lsmolaeglynn, i'' tkae laptop14:31
*** ruhe has joined #openstack-metering14:31
eglynnlsmola: so it would concern me reporting a "remaining" value that doesn't always match the concept of remaining headroom within the nova quotas logic14:31
eglynnlsmola: ok, I get it, the remaining value *does* always match the concept of remaining headroom within the nova quotas logic14:32
eglynnlsmola: but the trendline (populated from ceilo) may diverge from that?14:33
*** lsmola_ has joined #openstack-metering14:35
*** lsmola has quit IRC14:35
lsmola_eglynn, sorry, got disconnected14:35
lsmola_eglynn, so the aggregation of ceilometer is not correct14:35
lsmola_eglynn, it is stored as many samples, showing just existence of the instances in time by 1 or 014:35
lsmola_eglynn, and i want to extract the actual number of running instances in time for some project14:36
lsmola_eglynn, which is not really reliable, as I have to time it precisely, so i correctly SUM only instances that belongs together14:37
lsmola_eglynn, would it make sense to create new metrics, something like instances_count and instances_total, for project?14:38
lsmola_eglynn, the same for other meters probably?14:39
eglynnlsmola_: hmmm, by "1 or 0" you mean either presence of a sample with volume=1 in the timeslice, or the absence of a sample in that timeslice?14:39
eglynnlsmola_: i.e. there's no actual samples with volume=0, right?14:39
lsmola_eglynn, yes14:41
lsmola_eglynn, hmm, not sure really, how it acts when the instance is suspended14:41
*** ruhe is now known as ruhe_14:41
lsmola_eglynn, i am now in the process of documenting that behaviour14:41
*** ruhe_ has quit IRC14:42
eglynnlsmola_: k, so there are at least 3 drivers for samples being ingested for that instances meter ...14:43
eglynn1. compute agent polling (once every 600s out-of-the-box)14:43
lsmola_eglynn, but the absence and the 0 will act the same when SUM is used14:43
eglynn2. nova instance auditing, giving instance.exists notifications hourly or daily14:43
lsmola_eglynn, though count of the samples would be different14:44
eglynn3. instance deletion triggers a last sample for the instance IIUC14:44
eglynnso can you account for #1 & #2 with a SUM and group-by resource_id with period approximating the compute agent poilling?14:45
eglynns/poilling/polling period/14:45
lsmola_eglynn, are the compute agent somehow synced? like do they send it all in the same time?14:46
eglynnlsmola_: no they are not synced, and in fact the configured periods could actually differ between agents14:47
eglynnlsmola_: so it would have to be the longer configure period, plus a fudge factor to handle drift14:47
eglynn(between agents)14:48
lsmola_eglynn, if it's every 10minutes, and I can rely on all samples are send in 5 minutes, then I would set it around 6 minutes14:48
eglynnlsmola_: why not go longer, say 15mins, then have the group-by resource_id exclude the dups?14:49
eglynndupes? ... duplicates I meant, i.e. multiple samples in the period for the same instance14:49
*** lsmola has joined #openstack-metering14:51
lsmolaeglynn, sorry, got disconnected again14:51
eglynnreplay ...14:52
eglynn[14:42] <eglynn> lsmola_: why not go longer, say 15mins, then have the group-by resource_id exclude the dups?14:52
eglynn[14:42] <eglynn> dupes? ... duplicates I meant, i.e. multiple samples in the period for the same instance14:52
lsmolaeglynn, hmm14:52
*** lsmola_ has quit IRC14:53
lsmolaeglynn, when I use SUM14:53
lsmolaeglynn, and group by resource_id, it will SUM them, not exclude them, right?14:53
lsmolaeglynn, though if i am able to exclude duplicates, it's basically solved14:54
lsmolaeglynn, I just have to pick long enough period, to be sure every sample got the chance14:54
lsmolaeglynn, right now, I am using group by project_id14:55
eglynnlsmola: yeah, that's what I was thinking ... i.e you get the sum of the grouped-by samples, not the grouped-by sum of the samples14:55
lsmolaeglynn, is there a way to say unique resource_id ?14:55
*** sandywalsh has quit IRC14:55
lsmolaeglynn, hmm, not sure I get how that could be done, i need to do it in one query btw..14:56
eglynnlsmola: you can have multiple groupby fields14:56
eglynnlsmola: so I'm thinking you groupby *both* project_id and resource_id14:57
lsmolaeglynn, ok, I thought that will just do the same14:57
* lsmola intensively thinks14:57
lsmolaeglynn, well that would work if i could make for resource id different operation14:58
eglynnlsmola: there's still a problem though, how to account for recent instance deletion that occurred within the last period?14:58
eglynnlsmola: "make for resource id different operation"?14:58
lsmolaeglynn, well it should be alright, always show as the latest sample actual info from nova14:59
lsmolaeglynn, wel if it will be SUM of group_by resource_id and project_id, it will also sum the duplicate instances, right?15:00
lsmolaeglynn, so something like Unique constraint on resource_id has to be used15:00
lsmolaeglynn, hm, now I don't know how i meant the latter15:01
eglynnlsmola: yeah, you may be right ... I think I understand what you're getting at15:02
eglynnlsmola: let me do a little experimentation to figure out how this can be made work15:02
lsmolaeglynn, is there something liek Unique?15:02
lsmolaeglynn, excellent15:03
eglynnlsmola: nothing like unqiue currently, but let me see if I can figure out a way to get what you need15:03
eglynnlsmola: I'll give you a shout later (or email)15:03
lsmolaeglynn, ok, great15:03
lsmolaeglynn, great, thank you very much15:04
*** boris-42 has joined #openstack-metering15:04
*** gordc has joined #openstack-metering15:06
*** sandywalsh has joined #openstack-metering15:09
ildikoveglynn, lsmola: can you update me too with the results of the experimentation? this topic looks interesting for my API improvement blueprint15:11
eglynnildikov: cool, will do!15:11
ildikoveglynn: thanks :)15:12
*** ruhe has joined #openstack-metering15:13
lsmolaeglynn, hmm from mongo doc, i think we could use SUM of distinct('resource_id', 'value') Group BY period, project_id15:13
eglynnlsmola: yep, I was thinking along exactly those lines ... would obviously require API extentions to expose15:14
lsmolaeglynn, or, more group_by in a pipeline, if that is possible, though that makes my brain hurt :-)15:14
lsmolaeglynn, ok15:15
lsmolaildikov, do you think it would be possible to add support of "distinct" ?15:15
lsmolaildikov, so we can make beautiful queries like this? :-)15:16
eglynnlsmola: gotta divert off to sort out some internal stuff for a few mins, I'll back to this issue in a while ...15:16
lsmolaeglynn, np15:17
ildikovlsmola: we had a short brainstorming session this week about what we should support in reach queries15:17
lsmolaildikov, the use case is for new Horizon overview page http://people.redhat.com/~lsurette/OpenStack/Horizon%20Overview%20Pages_v1.0.pdf15:18
ildikovlsmola: it is the beginning of the process, but we would like to implement a modular and extendable solution, to be able to support functionalities like this15:18
lsmolaildikov, http://ask-openstackux.rhcloud.com/question/59/improvements-to-horizon-overview/15:18
lsmolaildikov, hmm, cool15:18
ildikovlsmola: that is why I asked you for update, to collect some real life UCs for the further design of this part of the API15:18
lsmolaildikov, though that means that it will take longer time right?15:19
lsmolaildikov, cause we would like those new overview pages and sparklines to land in I15:19
*** ruhe has quit IRC15:19
*** sphoorti has joined #openstack-metering15:20
ildikovthe first draft of the improvement is targeted to I-215:20
ildikovlsmola: but if we have valid UCs, then it is easier to include it into our implementation even into Icehouse15:21
lsmolaildikov, ok, cool15:24
*** ruhe has joined #openstack-metering15:25
*** rongze has joined #openstack-metering15:29
ildikovlsmola: sorry, I was interrupted15:40
*** herndon has quit IRC15:41
ildikovlsmola: thanks for the docs, I will look into them and I will think it over, how this can fit into our solution15:42
lsmolaildikov, ok, excellent15:43
lsmolaildikov, do you have some BP for this that i can follow?15:43
ildikovlsmola: please inform me, if there are any new use cases/requirements related to this area15:43
ildikovlsmola: https://blueprints.launchpad.net/ceilometer/+spec/complex-filter-expressions-in-api-queries15:44
ildikovlsmola: you can find a link in the blueprint with some details of the idea15:45
ildikovlsmola: feel free to write some comments15:45
lsmolaildikov, ok, cool, I will definitely read that15:46
ildikovlsmola: I would only ask to use Authorship colors on the etherpad15:46
lsmolaildikov, just out of my Head there is still sample-api bp, + some bp I've created that should allow ordering and limiting15:47
ildikovlsmola: ok, cool :)15:47
lsmolaildikov, those are basically things that would make my life easier regarding Horizon integration:-)15:47
lsmolaildikov, I have it tracked here as dependencies https://blueprints.launchpad.net/horizon/+spec/ceilometer-api-enhancements15:48
ildikovlsmola: you will see on the etherpad, that the main idea is to use POST requests and use the body to send query filters to the API in JSON format15:49
ildikovlsmola: as we plan to use the request body, it gives us some freedome, which we do not have in case of the query in GET15:50
lsmolaildikov, oh very cool, looking forward to use that for Alarms15:51
ildikovlsmola: we also planned to use a separate query resource, in order to avoid messing up the current solution and having a fresh start15:52
ildikovlsmola: the proof of concept implementation is started, hopefully we will have something to show soon15:53
lsmolaildikov, yeah that might make sense15:53
lsmolaildikov, great!!15:53
ildikovlsmola: hopefully it will ;)15:56
openstackgerritIlya Tyaptin proposed a change to openstack/ceilometer: Fix for get_statistics with postgresql  https://review.openstack.org/5920415:56
*** SergeyLukjanov is now known as _SergeyLukjanov15:56
*** ruhe has quit IRC15:58
*** giroro_ has quit IRC16:01
*** Ruetobas has joined #openstack-metering16:03
*** shengyao is now known as shengyao_afk16:03
*** Ruetobas has quit IRC16:07
*** Ruetobas has joined #openstack-metering16:07
*** nprivalova has quit IRC16:12
*** fnaval has quit IRC16:20
*** mgagne has joined #openstack-metering16:27
*** mgagne has joined #openstack-metering16:27
*** nati_ueno has quit IRC16:28
eglynndarn and drats ... looks like we have a regression in python-ceiloclient 1.0.7 :(16:29
eglynnthis changed line specifically http://goo.gl/QfneZz16:29
eglynncauses sample-list with prettytable-0.6.1-1 on RHEL to fail with "Invalid field name: None!"16:30
eglynnlooking at the review https://review.openstack.org/4733116:30
eglynnI don't I fully understand the motivation for sortby=None16:30
eglynnbecause the samples are already sorted in ts order by the API, None == "don't re-sort", or?16:31
eglynnsileht, gordc: ^^^ do you remember?16:31
eglynnI'm guessing that newer versions of prettytable allow sortby=None16:32
eglynnbut the requirement is still PrettyTable>=0.6,<0.8 so the so should still work against 0.6.1 on RHEL16:33
eglynnmeh! methinks I'll need to cut a 1.0.8 with a fix, and quick ...16:34
gordceglynn: i don't remember what the purpose of sortby was16:35
eglynnI think the original code set sortby=0 which sorted on resource_id (first field in the list)16:35
eglynnthe patch seems to want to change this to display samples in timestamp order, relying on the API layer pre-sorting in that order instead or re-sorting on the client side16:36
gordci see... i thought prettytable just formatted the output... it sorts as well?16:36
eglynngordc: yeah, it does16:37
eglynngordc: unless you tell it to sortby None, in which case it barfs on RHEL :(16:38
gordcoh, wasn't aware of that.16:39
*** sdake_ has joined #openstack-metering16:40
*** sdake_ has quit IRC16:40
*** sdake_ has joined #openstack-metering16:40
silehteglynn, the bad new is that is a oslo.cliutils issue16:46
sileht:q16:47
silehtoups16:47
openstackgerritIlya Tyaptin proposed a change to openstack/ceilometer: Fix for get_statistics with postgresql  https://review.openstack.org/5921416:47
*** nati_ueno has joined #openstack-metering16:47
eglynnsileht: so not specific to that version of prettytable?16:47
silehteglynn, I just think of where we can fix that in openstack16:48
eglynnsileht: a-ha, I see ...16:48
silehteglynn, I haven't yet find when prettytable introduce sortby=None16:49
silehteglynn, https://code.google.com/p/prettytable/source/detail?r=8716:53
silehteglynn, None is allowed since 0.716:54
eglynnsileht: yep, good spot ... but since we still only require >=0.6, it's a regression to rely on that16:54
gordceglynn: isn't jenkins suppose to auto patch our requirements?16:55
eglynngordc: it grabs the newest in pypi within the declared range16:56
eglynngordc: but the distros are free to use any version within that range if declared16:57
gordcseems like it was bumped to >=0.7 in requirements: https://github.com/openstack/requirements/blob/master/global-requirements.txt#L5216:57
eglynngordc: a-ha, sorry didn't spot that16:57
silehteglynn, gordc but oslo-incubator is not yet up2date https://github.com/openstack/oslo-incubator/blob/master/requirements.txt#L816:58
eglynnsileht, gordc: yeah, I dunno if that auto-patching was turned off recently?16:58
eglynn(certainly it was working a month or two ago ...)16:58
gordcsileht: ah i see, are we dependent on that? or can we just bump up our requirements regardless.16:58
gordci guess it could break cliutils if we do...16:59
silehtI think only the requirements repo is important for us16:59
* sileht is looking for the latest auto requriements update16:59
gordceglynn, sileht: i haven't seen an auto-patch in a while... i doubt we're that up to date that it doesn't need to autopatch for us.17:00
eglynnwell either way, I'll need to cut python-ceilocli 1.0.8 ... either with a new prettytable requirement or a work-around17:00
* eglynn is tending towards a work-around at this stage17:01
*** ildikov has quit IRC17:01
silehtaltest autoupdate https://github.com/openstack/python-ceilometerclient/commit/8e341cc620352ba07fb80d81a32ba01199e7d4cb17:01
eglynn(as the global requirements update is less than a week old https://github.com/openstack/requirements/commit/45b937a2 and prolly hasn't been packaged on multiple distros)17:02
*** SergeyLukjanov has joined #openstack-metering17:02
silehteglynn, hum thanks, I guess the debian backport repo have the same issue, the wheezy version is 0.6.1 too17:04
eglynnsileht: yeah, I'm thinking work-around is the safest course of action for now ... I'll propose something at the w/e17:05
silehteglynn, ok cool17:05
silehteglynn, ping me on RIC for quick review17:06
silehts/RIC/IRC17:06
eglynnsileht: cool, thanks!17:06
silehtubuntu backport have 0.6.1 too, everybody is impacted :)17:07
openstackgerritgordon chung proposed a change to openstack/ceilometer: update docs to adjust for naming change  https://review.openstack.org/5922017:21
gordcsileht: eglynn: just an fyi, i asked in infra, the requirements auto-patch job was disabled due to a bug17:22
silehtgordc, ack, thx17:26
*** nadya_ has joined #openstack-metering17:35
*** sdake_ has quit IRC17:37
eglynnsileht: FYI here's the kind of work-around I had in mind https://gist.github.com/anonymous/770920817:41
eglynn... unfortunately requires changes to cliutils to expose the reversesort, that's not ideal :(17:41
openstackgerritgordon chung proposed a change to openstack/ceilometer: synch with oslo-incubator  https://review.openstack.org/5922217:42
*** ruhe has joined #openstack-metering17:43
gordceglynn: yeah... will probably take longer to get that merged in oslo and then transfer over.17:43
eglynngordc: yep, but otherwise we lose the most recent sample first ordering17:44
*** ruhe has quit IRC17:47
openstackgerritgordon chung proposed a change to openstack/ceilometer: synch with oslo-incubator  https://review.openstack.org/5922217:51
openstackgerritgordon chung proposed a change to openstack/python-ceilometerclient: sync with oslo-incubator  https://review.openstack.org/5922517:54
openstackgerritgordon chung proposed a change to openstack/ceilometer: sync with oslo-incubator  https://review.openstack.org/5922217:55
*** nadya_ has quit IRC17:55
*** ildikov has joined #openstack-metering17:56
*** eglynn has quit IRC18:04
*** jergerber has quit IRC18:15
*** rongze has quit IRC18:29
*** ruhe has joined #openstack-metering18:35
*** sandywalsh has quit IRC18:36
*** rongze has joined #openstack-metering18:38
*** eglynn has joined #openstack-metering18:41
*** sphoorti has left #openstack-metering18:44
*** eglynn has quit IRC18:57
*** ruhe has quit IRC19:01
*** rongze has quit IRC19:16
*** rongze has joined #openstack-metering19:34
*** jergerber has joined #openstack-metering19:40
*** rongze has quit IRC19:41
*** nati_ueno has quit IRC19:41
*** eglynn has joined #openstack-metering19:44
*** eglynn has quit IRC19:54
*** sdake_ has joined #openstack-metering20:01
*** sdake_ has quit IRC20:01
*** sdake_ has joined #openstack-metering20:01
*** ArcTanSusan has joined #openstack-metering20:02
*** rongze has joined #openstack-metering20:11
*** boris-42 has quit IRC20:13
*** rongze has quit IRC20:20
*** ArcTanSusan has quit IRC20:31
*** nadya_ has joined #openstack-metering20:35
*** nadya_ has quit IRC20:39
*** ruhe has joined #openstack-metering20:45
*** ArcTanSusan has joined #openstack-metering20:46
*** rongze has joined #openstack-metering20:46
*** sdake_ has quit IRC20:47
*** mgagne has quit IRC20:48
openstackgerritgordon chung proposed a change to openstack/ceilometer: sync with oslo-incubator  https://review.openstack.org/5922220:52
*** rongze has quit IRC20:52
*** eglynn has joined #openstack-metering20:58
*** gordc has quit IRC20:58
*** eglynn has quit IRC21:03
*** eglynn has joined #openstack-metering21:14
*** ruhe is now known as ruhe_21:19
*** ruhe_ is now known as ruhe21:19
*** ruhe has quit IRC21:21
*** eglynn has quit IRC21:32
*** ildikov has quit IRC21:48
*** rongze has joined #openstack-metering21:48
*** rongze has quit IRC21:54
*** SergeyLukjanov has quit IRC22:02
*** sdake_ has joined #openstack-metering22:12
*** ArcTanSusan has quit IRC22:29
*** ArcTanSusan has joined #openstack-metering22:31
*** rongze has joined #openstack-metering22:50
*** rongze has quit IRC22:56
*** eglynn has joined #openstack-metering23:08
*** ArcTanSusan has quit IRC23:16
*** eglynn has quit IRC23:48
*** rongze has joined #openstack-metering23:52
*** rongze has quit IRC23:58

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