Monday, 2016-04-11

*** ducttape_ has joined #openstack-monasca00:31
*** bobh_ has joined #openstack-monasca00:48
*** bobh_ has quit IRC00:53
*** efoley has joined #openstack-monasca01:11
*** ducttape_ has quit IRC01:32
*** bmotz has quit IRC01:42
*** bmotz has joined #openstack-monasca01:42
*** bobh_ has joined #openstack-monasca01:49
*** bobh_ has quit IRC01:52
*** bobh_ has joined #openstack-monasca01:52
*** efoley has quit IRC01:55
*** ljxiash has joined #openstack-monasca01:55
*** bobh_ has quit IRC02:01
*** bobh_ has joined #openstack-monasca02:20
*** ukaynar_ has joined #openstack-monasca02:26
*** ukaynar_ has quit IRC02:30
*** ukaynar_ has joined #openstack-monasca02:30
*** vishwanathj has joined #openstack-monasca02:32
*** vishwanathj has quit IRC02:32
*** bobh_ has quit IRC03:02
*** bobh_ has joined #openstack-monasca03:25
*** bobh_ has quit IRC03:29
*** bobh_ has joined #openstack-monasca04:25
*** bobh_ has quit IRC04:31
*** ukaynar_ has quit IRC04:32
*** ljxiash has quit IRC05:29
*** pcaruana has joined #openstack-monasca05:39
*** bobh_ has joined #openstack-monasca06:03
*** bobh_ has quit IRC06:07
*** witek has joined #openstack-monasca06:48
*** ljxiash has joined #openstack-monasca08:48
*** rbak has quit IRC08:59
*** pcaruana has quit IRC09:00
*** nadya has joined #openstack-monasca09:02
*** bobh_ has joined #openstack-monasca09:09
*** kei_yama has quit IRC09:13
*** kei_yama has joined #openstack-monasca09:13
*** bobh_ has quit IRC09:14
*** hosanai has quit IRC09:41
openstackgerritKoji Nakazono proposed openstack/monasca-log-api: Add devstack plugin installer  https://review.openstack.org/30039609:54
openstackgerritTomasz TrÄ™bski proposed openstack/monasca-common: Periodicity for metrics  https://review.openstack.org/29275310:07
*** nadya has quit IRC11:09
*** bobh_ has joined #openstack-monasca11:10
*** bobh_ has quit IRC11:14
*** nadya has joined #openstack-monasca11:47
*** vaquerog has joined #openstack-monasca11:56
*** kei_yama has quit IRC12:06
*** kei_yama has joined #openstack-monasca12:11
*** Gen has joined #openstack-monasca12:11
*** Gen has quit IRC12:11
*** Gen has joined #openstack-monasca12:12
*** kse has quit IRC12:16
*** Gen has quit IRC12:34
*** kei_yama has quit IRC12:37
*** Gen has joined #openstack-monasca12:58
*** ljxiash has quit IRC13:36
*** ddieterly has joined #openstack-monasca13:49
*** ljxiash has joined #openstack-monasca13:49
*** bobh_ has joined #openstack-monasca13:55
*** bobh_ has quit IRC14:00
*** hosanai has joined #openstack-monasca14:05
*** nadya has quit IRC14:07
*** rbak has joined #openstack-monasca14:13
*** ddieterly is now known as ddieterly[away]14:21
*** craigbr has joined #openstack-monasca14:23
*** ddieterly[away] is now known as ddieterly14:23
*** rhochmuth has joined #openstack-monasca14:24
*** Fdaisuke_ has joined #openstack-monasca14:24
*** tongli has joined #openstack-monasca14:28
*** vaquerog_ has joined #openstack-monasca14:28
*** suksant has joined #openstack-monasca14:30
rhochmuth#topic monasca-analytics14:30
*** vaquerog has quit IRC14:31
hosanaihello14:32
rhochmuthhi hisashi14:33
openstackgerritRyan Bak proposed openstack/monasca-agent: Rework agent checks to use multiprocessing library  https://review.openstack.org/30135514:33
rhochmuthluis should be here in a minute14:33
hosanairhochmuth: hi. OK we will wait him.14:33
Fdaisuke_Hi,14:33
rhochmuthhi14:33
Fdaisuke_I work with hosanai at same company.14:34
hosanairhochmuth: Fdaisuke_ is my coleague i think are you daisuke?14:34
rhochmuthcool14:34
vaquerog_Hi gentlemen, this is Luis14:34
*** david______ has joined #openstack-monasca14:34
hosanaivaquerog_: hi!14:34
*** david______ has quit IRC14:34
vaquerog_Suksant is in the channel too, from the Labs team in the UK (and David will be joining as well)14:35
rhochmuthhi luis, are you the only one from bristol?14:35
rhochmuthcool, typed to quick14:35
rhochmuthhi suksant14:35
suksantHi14:35
rhochmuthlooks like we have a good group14:35
rhochmuthshould we wait for anyone else?14:35
hosanaimaybe david?14:35
rhochmuthso is this a good meeting time?14:36
vaquerog_david is here in the same room, so we can probably go ahead. He'll be on in 2 secs14:36
*** david_subiros_pe has joined #openstack-monasca14:36
david_subiros_pehi14:36
rhochmuthhi david14:36
rhochmuthi think that is everyone14:36
rhochmuthwelcome to the wayback machine14:37
vaquerog_:)14:37
hosanaii'm so sorry for the last meeting14:37
*** craigbr has quit IRC14:37
rhochmuthhosanai, that was my fault14:37
rhochmuthso, where should we begin14:38
rhochmuthi'm still in the process of submitting your repo for opensstack14:38
rhochmuthactually, i had to do another one14:38
vaquerog_:'( sorry to hear that14:38
rhochmuthbut, now that monasca-transform is done, i'll submit monasca-anlytics today14:38
rhochmuthit want' worth submitting both at the same time, because io would jsut make the same mistakes twice14:39
rhochmuthbut, now i'm all clear14:39
rhochmuthi think14:39
rhochmuthso, i'll get that done today14:39
hosanaicool!14:39
rhochmuthit will still proabbly take a week or two to get approved14:39
vaquerog_Excellent!14:39
rhochmuthbecause the repo is a part of an official project, the governance committee needs to approve14:40
rhochmuthi think14:40
vaquerog_We are almost done and waiting for our legal guys to approve the release14:40
rhochmuthbut, i don't expect any issues14:40
hosanairhochmuth: til approval, can we see the repo?14:40
rhochmuthso, the final approval should hopefully be just a formality14:40
*** ducttape_ has joined #openstack-monasca14:40
rhochmuthno, they create it14:40
vaquerog_I will, since we are mostly building on open source tools14:40
rhochmuthi believe14:41
hosanaii see.14:41
rhochmuthso, in the mean time, i think we would have to create a public github repo somewhere14:41
vaquerog_we can sync up and I can give you an overview before approval14:41
rhochmuthwe could do that14:41
rhochmuthtakes like 5 minutes14:41
vaquerog_so that we can start discussing next steps and roadmap as a team14:41
rhochmuthso luis, that sounds good14:41
hosanaisounds good!14:42
rhochmuthif you want to give an overview, that woudl be great14:42
vaquerog_at the moment we have a thin orchestration layer on top of Spark14:42
vaquerog_that simply controls how data and results flow bewteen different algorithms14:42
vaquerog_we plan to expand that to Flink14:42
vaquerog_they say that it kicks spark's bottom out in most performance tests14:42
vaquerog_plus, our experience is that spark is very knobby and there are many levers to be adjusted14:43
rhochmuthhmmm, i hadn't seen that14:43
vaquerog_any thoughts on that?14:43
rhochmuthi had a very brief look at flink14:43
rhochmuththe monasca-transform engine that is currently in progress is based on spark right no14:44
vaquerog_I think these slides gave more details http://es.slideshare.net/sbaltagi/flink-vs-spark14:44
rhochmuthit hasn't been formally reviewed yet14:44
*** craigbr has joined #openstack-monasca14:44
rhochmuthok, i'll look at off-line14:44
rhochmuthas you know, the threshold engine is storm14:44
hosanaithanks for the info i will read it later.14:45
rhochmuthso, you've got storm, spark, samaz and now flink to look at14:45
vaquerog_well lets assume we just build on spark for the time being14:45
*** rbrndt has joined #openstack-monasca14:45
vaquerog_on top of that we have this thin orchestration layer that simply deals with data handling and sending the right algorithm14:45
vaquerog_on top of the thin orchestration there is all the intelligence14:46
vaquerog_we have a lightweight dataflow language that specifies how data, algorithms and results are put together14:46
vaquerog_for instance14:46
vaquerog_you can use 4 different algorithms to infer causality on alertsa14:46
vaquerog_you can run thos ein parallel14:46
vaquerog_but you want the output to be a combination of those14:47
vaquerog_meaning that if "A" is caused by "B" in all algorithms14:47
hosanaii would like to know more about dataflow language. what is it?14:47
vaquerog_ten, the aggregate output should have a high certainty that is true14:47
vaquerog_at the moment is just a json description14:47
vaquerog_I think we can share that with you even without legal approval14:48
vaquerog_again14:48
vaquerog_we can change oit, refine it14:48
vaquerog_or go to some sort of DSL that we can use more programmatically14:48
vaquerog_any thoughts on that? what would be your preference?14:48
rhochmuthi think json is fine for now14:49
rhochmuthand over-time can look into something more advanved14:49
vaquerog_ok, that sounds good14:50
rhochmuthhosanai, any preference14:50
hosanaiso far, json is fine for us. but i would like to know from monasca point of view.14:51
hosanaiwhat is best for technically?14:51
hosanais/what/which/14:51
vaquerog_Not sure I fully understand the question, but let me try to ive an answer14:52
rhochmuthso, my understanding is that currently there is a json config file to define the pipeline14:52
vaquerog_the algorithmic flow would be consumed solely by monasca-analytics14:52
rhochmuthright14:52
vaquerog_yes, you define the data processing pipeline there and the thin orchestration relies that to spark/flink14:53
rhochmuthso, when monasca-analytics starts-up, it reads the pipeline definition14:53
vaquerog_from the Monasca standpoint, I presume it makes little difference14:53
rhochmuthcorrect14:53
vaquerog_you can specify kafka as a source of the dataflow14:53
*** bobh_ has joined #openstack-monasca14:53
hosanaisorry, i understand my mis-understanding14:53
vaquerog_also as a sink so that anyone can dump/consume data into the flow14:53
vaquerog_we will provide a couple of examples14:54
vaquerog_one on how to do anomaly detection (an example of flow that can be run on monasca-analytics)14:54
vaquerog_and another one on alert aggregation14:54
vaquerog_for instance, the result of an alert aggregation flow can be dumped on vitrage for further manipulation14:55
hosanaiwhat is vitrage?14:55
rhochmuthvitrage is a new project in openstack for root cause canalysis14:55
rhochmuthit uses topologicial information to do rca14:56
vaquerog_https://github.com/openstack/vitrage/14:56
rhochmuthand there will be two presentaitons in Austin14:56
hosanairhochmuth: thanks! i will check it.14:56
rhochmuthunfortunately, one overlaps with monasca design summit related discussions14:56
vaquerog_it is just an example of consumer of one of the 9very many) possible algorithmic flows14:56
vaquerog_sorry, Roland, could you elaborate on that a bit?14:57
rhochmuththe overlap?14:57
vaquerog_yes, please14:57
rhochmuthnow that monasca is an official openstack project there will be design summit sessions in Austin14:58
*** craigbr has quit IRC14:58
rhochmuthmonstly, they are all wednesday morning, and one wednesday agernoon14:58
vaquerog_ok, I see14:58
vaquerog_thanks14:58
rhochmuthso, you had mentioned to me several algorithms14:58
rhochmuthvia email14:58
rhochmuthi was wondering what the state of your current development in that area was14:59
vaquerog_yes, at the moment we will provide two examples on alert causality inference and anomaly detection14:59
vaquerog_we plan to make them a bit more complex14:59
vaquerog_we believe the community would be an excellent place to:14:59
vaquerog_1) share data (or data samplees)15:00
vaquerog_2) share algorithms15:00
rhochmuthany other references, so hosanai and Fdaisuke_ can get started15:00
rhochmuthor doe we will have to wait for the osrb approval15:00
vaquerog_the second one is interesting since we can (over time) create a library of algorithmics based on best practices or success stories for the benefit of the community15:00
rhochmuthyes, i agree,15:01
vaquerog_we can point you to the libraries and papers we used to build those15:01
rhochmuththat would be great15:01
rhochmuthi believe you sent me some linke, which i reviewed15:01
hosanaigreat!15:01
rhochmuthit looked good15:01
rhochmuthbut, would be good to post again here or via email15:01
*** ducttape_ has quit IRC15:01
david_subiros_pethis is the anomaly detection algorithm that we are using: http://scikit-learn.org/stable/modules/generated/sklearn.svm.OneClassSVM.html15:02
Fdaisuke_So, cool15:02
*** bmotz_ has joined #openstack-monasca15:02
vaquerog_as you can imagine all of them are basd on unsupervised learning techniques15:02
*** craigbr has joined #openstack-monasca15:02
*** ducttape_ has joined #openstack-monasca15:02
vaquerog_part of the roadmap we'd like to discuss is techniques for labelling data and beenfiting from semi-supervised/supervised techniques15:03
vaquerog_reconginsing cats in youtube is easy15:03
hosanaii see unsupervised one is suitable for our use cases.15:03
vaquerog_my 2 year old daughter can do that without millions of samples to train her (Google always go for the easy problems :P )15:03
vaquerog_openstack is more complex and there is not an abundance of experts with time to collaborate15:04
vaquerog_that is why unsupervised is highly relevant here15:04
vaquerog_and semi-supervised can be part of the roadmap, if you think that is a good idea and could be useful15:04
vaquerog_any thoughts?15:04
hosanaido you have a plan to use supervised tech in future?15:05
rhochmuthi think unsupervised is where to start15:05
rhochmuthwe dont' have large datasets available that are classified for anomalies15:05
suksantfor causality, we try LiNGAM (we implemented it based on scikit-learn)15:05
*** bmotz has quit IRC15:05
rhochmuthor alarm clustering15:05
hosanairhochmuth: we don't have ORACLE (great teacher) :-)15:06
*** dschroeder has joined #openstack-monasca15:06
suksanthttps://sites.google.com/site/sshimizu06/lingam15:06
vaquerog_well, we were thinking of using things ike label propagation to walk that huge gap (for instance, if you have a graph of connected samples, some of them anomalous, you could do some label propagation)15:06
vaquerog_and throw that to an admin to guide the algorithmic flow15:06
vaquerog_What suksant just added is the algorithm we will be giving as an example of causality15:07
vaquerog_what datasets could we use today?15:07
rhochmuthso getting data is the problem15:08
rhochmuthi can get data for our internal clouds from the last time i did this15:08
hosanaisorry, causality means kind of correlation analytics. i coun't follow it.15:08
rhochmuthbut, that is all the data i have access to these days15:08
vaquerog_We could also start analysing the openstack build and test environment15:08
vaquerog_I guess some tests pass and when you deploy in production you find odd stuff going on15:09
rhochmuthi'm wondering if twc could provide data from thier environment15:09
vaquerog_thworing some analytics at that dataset may save many hours15:09
rhochmuththe openstack build/test environment doesnt' use monasca15:09
rhochmuthnot sure what historical data they have avaialble15:10
rhochmuthfor metrics and alarms15:10
hosanairhochmuth: does monasca use in OIC?15:10
rhochmuthhosanai: i thought you also had algorithms that fujitsi had developed?15:11
rhochmuthsorry, i don't know what oic is15:11
hosanairhochmuth: wait a minute i will check the correct name.15:11
rhochmuthluis, how soon do you think osrb approval will occur15:12
hosanaiOpenStack Innovasion center15:12
rhochmuththanks hosanai.15:12
rhochmuthi'm not aware of anything going on in there15:13
suksantwe started the process few weeks ago. i will follow up with the responsible person.15:13
rhochmuthnever even heard of it before15:13
hosanaiin lab we have some algorithms but i think we will not use them in monasca15:13
rhochmuththanks suksant15:13
rhochmuthso, how do we get coordinated more, if can't release code and no repo yet?15:14
rhochmuthis there anything we can do in the mean time15:14
vaquerog_We'll send the flow spec to get feedback15:14
rhochmuthany code that can be released? It doesnt' sound like it15:14
rhochmuthok15:14
rhochmuthcan i add that to the monasca wiki?15:15
vaquerog_and I can show that presentations (an expanded version of what we have just discussed) using lync or something similar15:15
*** ljxiash has quit IRC15:15
rhochmuthok15:15
*** craigbr has quit IRC15:15
vaquerog_we expect to be able to release in a few weeks15:15
rhochmuththanks15:15
rhochmuthso, i'll have the repo ready to go15:16
rhochmuthby then15:16
vaquerog_we'll chase the attorneys (we usually run away from them :)15:16
rhochmuthlol15:16
vaquerog_Hisashi, your feedback is VERY important for us15:16
hosanaiFdaisuke_ and I would like to play (test) with the code first to understand it.15:16
vaquerog_it would be great if you coul dshare your plans, concerns and what you'd like us to work together on15:17
vaquerog_that makes sense, but we dould ditch our code and start afresh if it doesn't meet your requirements15:17
vaquerog_I think it would be good to understand those a little bit mroe15:17
*** openstackgerrit has quit IRC15:18
rhochmuthhosanai and Fdaisuke_: do you have any code that is avaialble from you end for review?15:18
rhochmuthor algorithms and descriptions?15:18
*** openstackgerrit has joined #openstack-monasca15:18
hosanairhochmuth: we don't have it. our current plan is understand luis's code then check differences15:19
rhochmuththx15:19
vaquerog_not having code is fine for us15:20
vaquerog_but understanding desired features, requirements, and use cases would be great15:20
rhochmuthso, how about i create a landing page for monasca-analytics in the monasca wiki15:21
hosanaivaquerog_: ok, i will prepare them based on our POC's info15:21
rhochmuthand we can start to identiy some of those use case15:21
rhochmuthand we can start to post information and collaboration more on this15:22
vaquerog_Great! Thanks!!15:22
rhochmuthi'll get somethign in-place today15:22
hosanairhochmuth: it's a good idea !15:22
hosanaioh, too quick :-)15:22
rhochmuthi was wondering what led to your selection of the svm for outlier detection?15:23
vaquerog_Excellent! We can then put together a list of requirements and share more broadly to define our roadmap15:23
rhochmuthso, i've got two action items. 1 repo, 2 wiki15:24
vaquerog_well, we tried a few15:24
vaquerog_there is not too many open source options in unsupervised15:24
vaquerog_well, not ones that are computationally efficient15:24
rhochmuthhmmm, did you consider non-parametric statistics15:25
vaquerog_yes, but didn't have time to explore it further. Most of our efforts were derailed into building the thin orchestration and the interpreter for the flow15:25
rhochmuthi see15:26
david_subiros_pewe tried this one as well: https://unsupervisedlearning.wordpress.com/2014/08/04/topological-anomaly-detection/ but got better results with SVM one class.15:26
rhochmuththx david15:26
rhochmuthi'll review that one too15:26
david_subiros_peMaybe we can try more options, and depending on the data source we can use different algorithms15:26
rhochmuthwhat types of things did you use svm for?15:27
vaquerog_kernel density anomaly detection is one clear candidate to be added15:27
rhochmuththere were some interesting papers by twitter last year on this topic15:27
rhochmuthi'll dig them up15:27
hosanaicould you share links for it?15:27
rhochmuthor jsut googel twitter breakout detection and anomaly detection15:27
david_subiros_peWe used SVM one class to find anomalies in firmware/hardware level15:27
rhochmuthi'll have to find again15:27
vaquerog_ok, we'll do15:27
rhochmuthi was working on portign the breakout detection to python15:28
rhochmuththat is funny, my ull request is still there at, https://github.com/twitter/BreakoutDetection/pulls15:28
rhochmuthhere is the github repo, https://github.com/twitter/BreakoutDetection15:29
rhochmuththe underlying code is all C/C++15:29
rhochmuththey have an R binding15:29
rhochmuthi tried to add Python15:29
rhochmuthbut then broke the R15:29
rhochmuththe python port works15:29
vaquerog_:) We love breaking things15:29
hosanailol15:29
*** craigbr has joined #openstack-monasca15:29
rhochmuththere is a bloq or paper on that method15:30
rhochmuthand then there was a follow-up for anomaly detection15:30
suksantThis one I suppose https://github.com/twitter/AnomalyDetection15:30
rhochmuththe stuff that i had previousely done using Komagorov-Smirnov two sample tests15:31
rhochmuthsuksant: correct, that is the one15:31
rhochmuthit looks like they aren't actively working on it15:31
rhochmuthbut it should be good to review and use15:32
rhochmuthso, i have to run to another meeting15:32
rhochmuthshould we schedule another meeting for next week15:33
vaquerog_ok,15:33
rhochmuthor two weeks?15:33
vaquerog_we'll send you the json flow descriptor15:33
rhochmuthactually, in two weeks i'll be at openstack summit15:33
rhochmuthso, probably next week15:33
vaquerog_and we can present the slides I mentioned above15:33
vaquerog_ok15:33
vaquerog_next week then15:33
rhochmuthsounds good15:33
hosanairhochmuth: ok. thanks & have a nice day!15:34
rhochmuthi'll schedule it in outlook15:34
rhochmuthso you next week same time15:34
vaquerog_cheers15:34
vaquerog_bye15:34
Fdaisuke_ok, Thank you in advance.15:34
rhochmuththanks eveyrone!15:34
david_subiros_pebye, thanks!15:34
suksantthank you. bye.15:34
*** vaquerog_ has quit IRC15:34
*** david_subiros_pe has quit IRC15:34
*** suksant has quit IRC15:34
openstackgerritZhiQiang Fan proposed openstack/python-monascaclient: Implement monasca metric-name-list  https://review.openstack.org/30368315:34
*** rbrndt__ has joined #openstack-monasca15:38
*** rbrndt has quit IRC15:39
*** _ducttape_ has joined #openstack-monasca15:45
*** ducttape_ has quit IRC15:47
*** hosanai has quit IRC15:48
*** ddieterly is now known as ddieterly[away]15:48
*** ddieterly[away] is now known as ddieterly15:51
openstackgerritMerged openstack/monasca-api: Dimension Filtering in Vertica  https://review.openstack.org/29265416:04
openstackgerritBradley Klein proposed openstack/monasca-api: Replace measurements table join with subquery  https://review.openstack.org/30420816:10
*** openstackstatus has joined #openstack-monasca16:11
*** ChanServ sets mode: +v openstackstatus16:11
*** craigbr has joined #openstack-monasca16:11
-openstackstatus- NOTICE: Reminder, Gerrit will be offline from 20:00 to 21:00 UTC for a server replacement http://lists.openstack.org/pipermail/openstack-dev/2016-April/091274.html16:19
openstackgerritBradley Klein proposed openstack/monasca-api: Replace measurements table join with subquery that fits in memory  https://review.openstack.org/30420816:19
openstackgerritBradley Klein proposed openstack/monasca-api: Replace measurements table join with subquery that fits in memory  https://review.openstack.org/30420816:53
*** Fdaisuke_ has quit IRC16:54
*** nadya has joined #openstack-monasca17:18
*** ddieterly is now known as ddieterly[away]17:31
*** craigbr has quit IRC17:40
*** ddieterly[away] is now known as ddieterly17:53
*** craigbr has joined #openstack-monasca17:56
*** ddieterly is now known as ddieterly[away]18:16
*** craigbr has quit IRC18:22
*** craigbr has joined #openstack-monasca18:26
openstackgerritDavid Schroeder proposed openstack/monasca-agent: A couple small fixes to the postfix plugin  https://review.openstack.org/30427618:30
*** nadya has quit IRC18:34
*** vishwanathj has joined #openstack-monasca18:37
*** vishwana_ has joined #openstack-monasca18:39
*** vishwanathj has quit IRC18:41
*** vishwana_ is now known as vishwanathj18:43
*** ddieterly[away] is now known as ddieterly18:44
*** rbrndt has joined #openstack-monasca18:55
*** rbrndt__ has quit IRC18:55
*** craigbr_ has joined #openstack-monasca19:04
*** craigbr has quit IRC19:04
*** craigbr_ is now known as craigbr19:04
*** ddieterly is now known as ddieterly[away]19:27
*** nadya has joined #openstack-monasca19:30
*** craigbr has quit IRC19:46
*** ddieterly[away] is now known as ddieterly19:50
-openstackstatus- NOTICE: Gerrit will be offline from 20:00 to 21:00 UTC (starting 10 minutes from now) for a server replacement http://lists.openstack.org/pipermail/openstack-dev/2016-April/091274.html19:50
*** ddieterly is now known as ddieterly[away]19:52
*** craigbr has joined #openstack-monasca19:52
*** ddieterly[away] is now known as ddieterly19:55
*** nadya has quit IRC20:00
*** openstackgerrit has quit IRC20:05
-openstackstatus- NOTICE: Gerrit is offline until 21:00 UTC for a server replacement http://lists.openstack.org/pipermail/openstack-dev/2016-April/091274.html20:06
*** ChanServ changes topic to "Gerrit is offline until 21:00 UTC for a server replacement http://lists.openstack.org/pipermail/openstack-dev/2016-April/091274.html"20:06
*** openstackgerrit has joined #openstack-monasca20:28
*** ddieterly is now known as ddieterly[away]20:35
*** dschroeder has quit IRC20:36
*** openstackgerrit has quit IRC20:41
*** ddieterly[away] is now known as ddieterly20:42
*** openstackgerrit has joined #openstack-monasca20:55
*** dschroeder has joined #openstack-monasca21:00
*** ChanServ changes topic to "OpenStack Monitoring as a Service | https://wiki.openstack.org/wiki/Monasca"21:06
-openstackstatus- NOTICE: Gerrit move maintenance completed successfully; note that DNS has been updated to new IP addresses as indicated in http://lists.openstack.org/pipermail/openstack-dev/2016-April/091274.html21:06
openstackgerritBradley Klein proposed openstack/monasca-api: Check gate/tempest with master  https://review.openstack.org/30431921:37
openstackgerritBradley Klein proposed openstack/monasca-api: Replace measurements table join with subquery that fits in memory  https://review.openstack.org/30420821:38
*** craigbr has quit IRC21:45
*** ddieterly is now known as ddieterly[away]21:48
*** bobh_ has quit IRC21:55
*** stackedsax has quit IRC22:15
*** _ducttape_ has quit IRC22:19
*** ddieterly[away] is now known as ddieterly22:37
*** ddieterly is now known as ddieterly[away]22:55
*** ddieterly[away] is now known as ddieterly22:55
*** rbrndt has quit IRC22:59
*** rbak has quit IRC23:04
*** ddieterly is now known as ddieterly[away]23:05
*** ddieterly[away] has quit IRC23:06
*** tongli_ has joined #openstack-monasca23:22
*** tongli_ has quit IRC23:22
*** tongli_ has joined #openstack-monasca23:22
*** bobh_ has joined #openstack-monasca23:23
*** kse has joined #openstack-monasca23:24
*** tongli has quit IRC23:25
*** tongli_ has quit IRC23:27
*** kei_yama has joined #openstack-monasca23:29
*** rhochmuth has quit IRC23:37
*** tongli has joined #openstack-monasca23:47
*** hosanai has joined #openstack-monasca23:49
*** tongli has quit IRC23:51

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