*** zhurong has joined #cloudkitty | 01:51 | |
*** zhangguoqing has joined #cloudkitty | 02:36 | |
*** gongysh has joined #cloudkitty | 03:17 | |
*** zhurong has quit IRC | 03:21 | |
*** liujiong has joined #cloudkitty | 03:32 | |
*** zhangguoqing has quit IRC | 03:53 | |
*** zhangguoqing has joined #cloudkitty | 04:35 | |
*** jojden has quit IRC | 04:38 | |
*** jojden has joined #cloudkitty | 04:39 | |
jojden | hi | 04:50 |
---|---|---|
jojden | my cloudkitty database table "rated_data_frames" is having zero rows | 04:52 |
jojden | why | 04:52 |
*** gongysh has quit IRC | 05:11 | |
*** zhangguoqing has quit IRC | 05:16 | |
*** zhurong has joined #cloudkitty | 05:52 | |
*** dinghh has left #cloudkitty | 05:57 | |
*** zhurong has quit IRC | 06:01 | |
*** gongysh has joined #cloudkitty | 06:17 | |
*** zhangguoqing has joined #cloudkitty | 06:56 | |
*** zhangguoqing has quit IRC | 06:57 | |
*** zhangguoqing has joined #cloudkitty | 06:59 | |
*** zhangguo_ has joined #cloudkitty | 07:00 | |
*** zhangguoqing has quit IRC | 07:01 | |
jojden | root@os-controller1:~# service cloudkitty-writer status | 07:09 |
jojden | cloudkitty-writer: unrecognized service | 07:09 |
jojden | to work cloudkitty properly cloudkitty-writer status should be running right ? | 07:10 |
liujiong | jojden: no cloudkitty-writer service | 07:22 |
liujiong | just cloudkitty-api and cloudkitty-processor | 07:22 |
jojden | ok | 07:25 |
jojden | then how the data is inserted into the rated_data_frames tables | 07:25 |
jojden | I guess the cloudkitty-writer do the job | 07:26 |
jojden | my issue is the table is empty | 07:26 |
jojden | so my invoice is showing as $0 | 07:26 |
jojden | can you help me liujiong | 07:26 |
liujiong | can you check the status of cloudkitty-api and cloudkitty-processor services? | 07:28 |
jojden | those are running | 07:29 |
jojden | cloudkitty-processor start/running, process 17394 | 07:29 |
jojden | cloudkitty-api start/running, process 20699 | 07:29 |
liujiong | can you check a few configurations in cloudkitty's config file? | 07:36 |
liujiong | what's the value of services/window/period in collect section? | 07:37 |
*** jd_ has quit IRC | 07:41 | |
jojden | it was 3600 | 07:42 |
jojden | but for the testing purppose i made it as 300 ( 5 minutes) | 07:42 |
jojden | window is 1800 | 07:43 |
jojden | services are compute,image,volume,network.bw.in,network.bw.out,network.floating | 07:43 |
jojden | liujiong | 07:43 |
*** jd_ has joined #cloudkitty | 07:43 | |
liujiong | ok, configuration seems fine | 07:44 |
liujiong | are there error logs saved? | 07:46 |
jojden | i checked the error logs | 07:46 |
jojden | with debug true | 07:46 |
aolwas | jojden: cloudkitty-writer is used to export data frome CK storage in text format like CSV | 07:48 |
liujiong | ok | 07:48 |
jojden | https://pastebin.com/cidRm3KN | 07:48 |
jojden | ok | 07:48 |
liujiong | execute `cloudkitty report-tenant-list` to check if it has values | 07:49 |
jojden | may i know which service is responsible to insert the data into the rated_dateframes | 07:49 |
jojden | ok | 07:49 |
aolwas | cloudkitty-processing | 07:49 |
liujiong | cloudkitty-processor do that job, yes! | 07:49 |
jojden | cloudkitty report-tenant-list have values | 07:49 |
huats | jojden: what release ok CK are you using ? | 07:50 |
aolwas | liujiong: from what jojden told me last week, CK used to work well and suddenly stop writing dataframes | 07:50 |
aolwas | but there is nothing in the log | 07:51 |
jojden | 0.5.1 | 07:51 |
jojden | correct aolwas | 07:51 |
jojden | but we checked the logs too | 07:51 |
huats | jojden: ok so it means mitaka | 07:51 |
jojden | ok | 07:52 |
huats | I guess it could be the JSON issue we had... | 07:52 |
jojden | oh | 07:52 |
huats | but | 07:52 |
jojden | we are using openstack 12, means liberty | 07:52 |
jojden | so if i degrade cloudkitty then it will be solved ? | 07:52 |
huats | no no | 07:53 |
huats | wait :) | 07:53 |
jojden | ok :) | 07:53 |
huats | and you said it stopped working ? | 07:53 |
huats | without any changes ? | 07:53 |
jojden | yes | 07:53 |
jojden | yes, we have installed refstack for the certification and run tests | 07:53 |
jojden | so i guess might be any modification due to refstack installtions | 07:54 |
huats | what release of refstack have you installed ? | 07:55 |
huats | latest ? | 07:55 |
huats | I fear that your refstack installed some dependencies that conflicts with the one inside CK | 08:00 |
huats | but it is not clear | 08:00 |
jojden | hmm | 08:23 |
jojden | i too think so | 08:23 |
jojden | I have installed latest version of the refstack only | 08:24 |
jojden | huats | 08:26 |
*** gongysh has quit IRC | 08:58 | |
*** gongysh has joined #cloudkitty | 09:16 | |
*** zhangguo_ has quit IRC | 10:04 | |
*** gongysh has quit IRC | 10:08 | |
*** liujiong has quit IRC | 10:12 | |
*** zhangguoqing has joined #cloudkitty | 10:22 | |
openstackgerrit | Shubhendu Poothia proposed openstack/cloudkitty master: Set access_policy for messaging's dispatcher https://review.openstack.org/459637 | 11:22 |
*** zhangguoqing has quit IRC | 11:26 | |
*** zhangguoqing has joined #cloudkitty | 11:27 | |
*** pabardina_ has joined #cloudkitty | 12:02 | |
*** pabardina_ has quit IRC | 12:02 | |
*** pabardina has quit IRC | 12:03 | |
*** pabardina has joined #cloudkitty | 12:04 | |
*** peschk_l has joined #cloudkitty | 12:27 | |
huats | Hello everyone | 12:29 |
zhangguoqing | hi | 12:29 |
peschk_l | hello! | 12:30 |
huats | I see that you guys are here on time :) | 12:30 |
huats | let's wait 5 minutes | 12:30 |
huats | for the late arrivals | 12:30 |
zhangguoqing | ok :) | 12:30 |
pabardina | hi | 12:31 |
huats | ok guys | 12:36 |
huats | I think it is time ! | 12:36 |
huats | First of all, thanks for being here ! | 12:37 |
huats | I really think it was necessary to have such meeting | 12:38 |
huats | in order to define and talk about the evolution of cloudkitty | 12:38 |
huats | Here is the Agenda that I have planned for today | 12:38 |
huats | - Mascot | 12:38 |
huats | - Moving to Storyboard | 12:38 |
huats | - Specs | 12:38 |
huats | - Pike | 12:39 |
huats | - Current bugs and patches | 12:39 |
huats | - Stable releases | 12:39 |
huats | - Boston Summit | 12:39 |
huats | - PTG | 12:39 |
huats | -Open Discussion | 12:39 |
huats | Does that sounds ok for everyone ? | 12:39 |
pabardina | yes ! | 12:40 |
zhangguoqing | Good, it's plentiful. | 12:40 |
*** mc__ has joined #cloudkitty | 12:40 | |
huats | Ok then, let's go | 12:40 |
aolwas | good for me | 12:41 |
huats | - Mascot | 12:41 |
aolwas | Hi guys | 12:41 |
huats | First of all like all of you know we have now a new mascot | 12:41 |
huats | like all OpenStack Projects | 12:41 |
huats | https://www.dropbox.com/sh/5krzib412pmfcrv/AAAK-WqHaKhhhqJSan6IMo_ta?dl=0 | 12:41 |
huats | and the good thing is that I have some stickers with it !!! it you are coming to Boston I'll be able to give you some. If not just drop me an email with your address and I'll ship you some... | 12:42 |
huats | Oh and it is merged in the documentation already. | 12:42 |
huats | I don't see any reaction here | 12:44 |
huats | move on ? | 12:44 |
huats | go | 12:45 |
huats | - Moving to Storyboard | 12:45 |
huats | We have been approached by the OpenStack foundation to switch over storyboard (https://storyboard.openstack.org/) | 12:45 |
huats | They have tested our current usage of launchpad for a switch to storyboard and it went quite good. | 12:45 |
huats | I am clearly in favor of doing it. How to you feel about it ? | 12:45 |
huats | no one ? | 12:47 |
pabardina | sounds great, +! | 12:47 |
pabardina | +1 | 12:47 |
aolwas | why not | 12:47 |
aolwas | I need to look at it a bit more to have a more precise opinion | 12:47 |
aolwas | does it mean that launchpad will be abandonned ? | 12:48 |
huats | aolwas: actually every project will move to it | 12:48 |
aolwas | ok ... +1 then ;-) | 12:48 |
huats | but being one of th e first means we will have a better help from the foundation :) | 12:48 |
huats | zhangguoqing: ? peschk_l ? | 12:49 |
zhangguoqing | I have the same question: launchpad will be abandonned? | 12:50 |
peschk_l | +1 for storyboard, I think it will be easier to understand than launchpad | 12:51 |
peschk_l | this would be a good point for new contributors | 12:51 |
zhangguoqing | how to deal with the rest of bugs on launchpad? | 12:51 |
huats | it would be yes | 12:51 |
huats | all the bugs will be imported for us | 12:51 |
huats | by the foundation | 12:52 |
zhangguoqing | ok | 12:52 |
huats | ok then | 12:53 |
huats | I'll contact them | 12:53 |
huats | to say yes for us | 12:53 |
huats | Next topic | 12:53 |
huats | - Specs | 12:53 |
huats | As a reminder we now have a spec repository. So we need to use it before coding !!! aolwas was staring a discussion for that. We need to follow him. | 12:54 |
huats | and follow that discussion | 12:54 |
huats | aolwas: do you want to elaborate your thought ? | 12:55 |
aolwas | you talk about aaron's spec ? | 12:55 |
huats | Yes. But you have started to explain your idea on how to deal with specs | 12:56 |
huats | (during that exchange) | 12:56 |
huats | (IIRC) | 12:56 |
aolwas | Aaron has proposed several patches to improve services management in CK | 12:59 |
aolwas | some based on unfinished work if I'm not wrong | 12:59 |
aolwas | the service-collector mapping api for example | 13:00 |
aolwas | and I'm afraid we're not going in the good direction | 13:00 |
aolwas | mostly by restricting the possibility to use multiple processors for different services | 13:01 |
aolwas | things that I unfortunately began to do with the user experrience improvement patch ... We saw the consequences when we intregrated it the horizon | 13:02 |
aolwas | and that's why you have custom services and custom fields choices | 13:02 |
huats | so the idea here is not only technical. It is to have a great discussion before starting to code on such feature. To avoid to loose some work but also to ease the review, since it will be always simplier to review somethig discuss before. | 13:03 |
huats | that is why the usage of specs is really important | 13:03 |
aolwas | that was clearly my idea when I begin to write specs in launchpad (before liujiong create the specs repository) | 13:04 |
huats | I know | 13:04 |
huats | I wanted to emphasize that :) | 13:04 |
aolwas | :) | 13:05 |
huats | I guess we all agree on that... | 13:05 |
huats | and that lead us to the next topic : Pike development :) | 13:05 |
huats | The firs thing we need to achieve is the Release Goal (OpenStack wide) | 13:05 |
huats | in Pike there are 2 | 13:06 |
huats | Gate for python3.5 | 13:06 |
huats | We have checked that is alreay the case | 13:06 |
huats | I'll have a talk with the guy in charge of that anyway | 13:06 |
huats | The second one is : WSGI for service API. Some work was in progress. zhangguoqing it was you IIRC. Do you have any idea on that acheivment ? | 13:07 |
peschk_l | when is Pike's feature freeze ? | 13:08 |
huats | End of July | 13:09 |
zhangguoqing | No problem, I will achieve it. | 13:09 |
huats | zhangguoqing: great! | 13:09 |
huats | may be we can have a talk about that later ? | 13:10 |
huats | or specs ;) | 13:10 |
huats | zhangguoqing: ^ | 13:10 |
zhangguoqing | if on specs, I wish more actives and soon feedback. | 13:11 |
zhangguoqing | when I push it on the specs. | 13:11 |
huats | let's try to acheive that !!! | 13:12 |
aolwas | yes | 13:12 |
huats | OK then | 13:13 |
zhangguoqing | what is other Release Goal? | 13:13 |
huats | Gate test for Python 3.5 | 13:13 |
huats | and we already have it | 13:13 |
huats | (like I said) | 13:13 |
huats | Here are the big works I'll like to tackle for Pike, or at least have some discussions... | 13:15 |
huats | ‣ opening to other metrics provider (monasca by instance). I know @pabardina is about to start that | 13:15 |
huats | ‣ multiple collectors at the same time using the GUI or not, with a clean approach | 13:15 |
huats | ‣ improve the gnocchi collector | 13:15 |
huats | ‣ versionning of pricing policy | 13:15 |
aolwas | I already have a short specs for policy versioning in launchpad | 13:16 |
aolwas | I'll push it to specs repo as soon as possible | 13:17 |
huats | ok | 13:17 |
huats | do you have any other thing you'll like to tackle ? | 13:17 |
aolwas | yes | 13:17 |
huats | I would really like that we focus all together in the list we define "today" (or the days after) | 13:18 |
huats | and that we avoid some big work on new features (not talking of Bugs of course) that are not defined by us as a whole | 13:19 |
aolwas | I don't known if it can (or should) be done for pike but I wonder if we can improve how we handle services and metrics for current and future collectors | 13:19 |
aolwas | today, we need to push a patch to just add a new service or a new metadata in a collector | 13:20 |
aolwas | it would be nice if it could be done in a configuration file (a bit in the way it is done in ceilometer for example) | 13:21 |
huats | indeed | 13:22 |
huats | can you write a spec for that soon ? | 13:22 |
aolwas | I can try | 13:22 |
huats | ok | 13:22 |
zhangguoqing | It seems hard to do, aolwas, come on. :) | 13:23 |
aolwas | huats: you didn't anwser to peschk_l about Pike feature freeze ? | 13:23 |
huats | I did | 13:23 |
huats | [15:09:09] <huats> End of July | 13:23 |
aolwas | Sorry :-D | 13:24 |
huats | ;) | 13:24 |
huats | Next topic ? | 13:24 |
huats | or anything to add ? zhangguoqing ? pabardina ? aolwas ? | 13:25 |
zhangguoqing | next topic. | 13:25 |
aolwas | do we fix now specs we really want in Pike ? | 13:26 |
huats | I would love to | 13:26 |
huats | that we "choose" our goals | 13:26 |
huats | and then write specs soon | 13:26 |
huats | The opening to other metrics provider is really something that is asked more and more (by monasca by instance) | 13:28 |
huats | that is why pabardina is about to work on that | 13:28 |
aolwas | I'll add gnocchi improvement and wsgi | 13:28 |
huats | I agree | 13:28 |
huats | zhangguoqing: you take care of the wsgi ? | 13:29 |
huats | and gnocchi improvment ? | 13:29 |
huats | (the gnocchi collector I mean) | 13:29 |
aolwas | the other specs seem for me not mature enough to implement them for Pike | 13:29 |
zhangguoqing | yes, wsgi no problem, but how to improvment gnocchi collector? | 13:30 |
huats | zhangguoqing: to have to same level of data in the gnocchi collector that on the ceilometer one | 13:31 |
aolwas | we need to stabilize the code ... and also discuss about all resources and metrics we need to add the CK to cover most of the need | 13:31 |
huats | zhangguoqing: like aolwas said | 13:32 |
huats | regarding the metrics we (@Objectif LIbre) might have some customer that will help us for that | 13:32 |
zhangguoqing | CK should always follows to the change of telemetry. | 13:32 |
aolwas | I have an almost ready patch for radosgw | 13:33 |
huats | zhangguoqing: I agree but we don't have all metrics | 13:33 |
zhangguoqing | could you point that detail? | 13:33 |
huats | so that is why I was saying improve the gnocchi collector | 13:33 |
huats | what detail ? | 13:33 |
huats | zhangguoqing: ^ | 13:34 |
zhangguoqing | what should we add or complete | 13:34 |
huats | ok | 13:34 |
huats | zhangguoqing: I will | 13:35 |
zhangguoqing | that mean add some services? | 13:35 |
huats | and this is clearly that can be splitted | 13:35 |
huats | can we have a bbasic agreement on that and we wil refine it soon? | 13:36 |
zhangguoqing | ok | 13:36 |
huats | Next Topic : Stable Releases | 13:38 |
huats | We need to be have some stable release. | 13:39 |
huats | - mitaka | 13:39 |
huats | The release is pending approval by the release and stable guys... | 13:39 |
huats | - newton | 13:39 |
huats | There is nothing to do/pending | 13:39 |
huats | - ocata | 13:39 |
huats | I'll start cheery pick really soon, but is there any patch you'll like to see included ? | 13:40 |
huats | it is really important that they are just Fix | 13:40 |
huats | and named Fix | 13:40 |
peschk_l | aolwas recent patch on the gnocchi collector should be included | 13:40 |
huats | yes | 13:41 |
aolwas | liujiong have +2, i'll +w after the meeting | 13:41 |
huats | I have it on my mind already | 13:41 |
aolwas | I'll check but I think my other bug fix on gnocchi have already been backported by liujiong and zhangguoqing | 13:42 |
huats | ok | 13:42 |
huats | we'l discuss that | 13:42 |
huats | together | 13:42 |
huats | but if you have any bug you awnt | 13:43 |
huats | please let me know quite soon | 13:43 |
huats | Next topic ? | 13:43 |
peschk_l | next topic | 13:44 |
huats | OpenStack Summit Boston | 13:44 |
huats | Does any of you guys are going to Boston ? | 13:45 |
huats | zhangguoqing: ? | 13:45 |
pabardina | no | 13:46 |
zhangguoqing | I don't know now, that has not confirm. | 13:46 |
huats | ok | 13:46 |
huats | please let me know if it is the case | 13:46 |
huats | do you know if Jeremy or Aaron or attending it ? | 13:47 |
huats | We will have 2 sessions related to cloudkitty : one talk on the current state of cloudkitty and a handson on how to use cloudkitty with gnocchi | 13:47 |
huats | And also an onboarding session to try to attract new developers ! | 13:47 |
*** bcornec has joined #cloudkitty | 13:47 | |
huats | zhangguoqing: ^ ? | 13:48 |
zhangguoqing | maybe not, I think. It's hard opportunity to Summit for chinese company. | 13:48 |
huats | ok | 13:48 |
huats | Next topic is PTG | 13:49 |
huats | In september the next PTG is about to take place in Denver. Does some of you would be interested to have some cloudkitty sessions there ? | 13:49 |
huats | I think it is quite complicated for a small project like us | 13:49 |
huats | but I am open for discussion :) | 13:50 |
mc__ | Why not :) | 13:52 |
aolwas | I think it will be more useful to have regular IRC meeting than going to the PTG for CK | 13:52 |
huats | It is my opinion too (for regular meeting) | 13:53 |
zhangguoqing | Agree! | 13:54 |
huats | That is all on my side | 13:55 |
huats | Next topic : Open Discussion | 13:55 |
huats | Does any of you have some topic to discuss ? | 13:55 |
zhangguoqing | A bug: https://bugs.launchpad.net/cloudkitty/+bug/1675635 | 13:56 |
openstack | Launchpad bug 1675635 in cloudkitty "multi-cloudkitty-processor daemons will get the incorrect cost" [Undecided,New] - Assigned to zhangguoqing (474751729-o) | 13:56 |
huats | yes zhangguoqing ? | 13:57 |
aolwas | zhangguoqing: have you look at my question ? | 13:57 |
huats | aolwas: is it the "config" issue we had using the lock ? | 13:58 |
zhangguoqing | yes, we can not discuss some bug in open discussion? | 13:58 |
huats | sure we can | 13:59 |
huats | the question was : what do you want to discuss on it ? | 13:59 |
huats | :) | 13:59 |
aolwas | at first yes but it seems that distributed lock with redis backend does no work | 13:59 |
zhangguoqing | The multi-cloudkitty-processor daemons in single node is OK, but in multi-machine always wrong. | 13:59 |
huats | ok | 14:00 |
zhangguoqing | In multi-machine, I have tested the mysql lock backend, but remain wrong. | 14:00 |
aolwas | do you think it's a CK bug or a tooz bug ? | 14:00 |
zhangguoqing | radis is too. So I'm not sure the reason, who can help and discuss it. | 14:01 |
aolwas | I know we have to implement this for a client but I don't kown if my collegue had the time to look at it. | 14:02 |
zhangguoqing | It's OK in single machine, that mean the tooz and CK work well. | 14:03 |
aolwas | I'll check with him and get you posted | 14:03 |
zhangguoqing | ok, I want someone test it again in multi-machine. | 14:04 |
*** gpocentek has joined #cloudkitty | 14:05 | |
huats | aolwas: gpocentek just arrived | 14:06 |
huats | may be he can answer :) | 14:06 |
gpocentek | hi | 14:07 |
gpocentek | what's the question? | 14:07 |
huats | it is related to the multi-cloudkitty-processor daemons | 14:08 |
huats | have you been able to have a look at it or not yet ? | 14:08 |
huats | because zhangguoqing was mentionning https://bugs.launchpad.net/cloudkitty/+bug/1675635 | 14:08 |
openstack | Launchpad bug 1675635 in cloudkitty "multi-cloudkitty-processor daemons will get the incorrect cost" [Undecided,New] - Assigned to zhangguoqing (474751729-o) | 14:08 |
gpocentek | I didn't find time yet | 14:08 |
huats | ok | 14:09 |
huats | so apparently zhangguoqing was sayging taht it was OK in a single node (for multiprocessor) | 14:09 |
huats | but it fails with multi-node | 14:09 |
huats | so he might be interested to follow your advance on that point | 14:10 |
gpocentek | I'll follow up on the bug when I test it | 14:11 |
huats | grear | 14:12 |
huats | thanks | 14:12 |
huats | great | 14:12 |
zhangguoqing | gpocentek: that's good. I think it's urgency for production environment. thanks. | 14:12 |
huats | any other topics to discuss ? | 14:12 |
aolwas | it's good for me | 14:13 |
zhangguoqing | Code Review timely, which I always say, it's importance to boost our goal. :) | 14:14 |
huats | ok then | 14:16 |
huats | I think it is the end of this meeting ! | 14:17 |
huats | thanks for attending it !!! | 14:17 |
aolwas | thx | 14:17 |
aolwas | bye | 14:17 |
zhangguoqing | thanks, good night :) | 14:18 |
*** gpocentek has left #cloudkitty | 14:20 | |
*** zhangguoqing has quit IRC | 14:21 | |
*** zhangguoqing has joined #cloudkitty | 14:22 | |
*** pabardina has quit IRC | 14:23 | |
*** zhangguoqing has quit IRC | 14:26 | |
*** peschk_l has quit IRC | 14:31 | |
*** peschk_l has joined #cloudkitty | 14:31 | |
huats | good night | 14:31 |
*** zhangguoqing has joined #cloudkitty | 14:36 | |
*** zhangguoqing has quit IRC | 14:37 | |
*** peschk_l has quit IRC | 15:23 | |
*** peschk_l has joined #cloudkitty | 15:24 | |
*** zhangguoqing has joined #cloudkitty | 15:45 | |
*** zhangguoqing has quit IRC | 15:46 | |
*** liujiong has joined #cloudkitty | 15:52 | |
*** mc__ has quit IRC | 15:57 | |
*** liujiong has quit IRC | 16:04 | |
*** peschk_l has quit IRC | 16:30 | |
*** zhangguoqing has joined #cloudkitty | 16:35 | |
*** zhangguoqing has quit IRC | 16:37 | |
*** zhangguoqing has joined #cloudkitty | 17:19 | |
*** zhangguoqing has quit IRC | 17:20 | |
*** peschk_l has joined #cloudkitty | 18:40 | |
*** bcornec has quit IRC | 18:53 | |
*** peschk_l has quit IRC | 20:35 | |
*** openstack has joined #cloudkitty | 23:28 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!