Friday, 2019-02-01

peschk_lHi Linkid, will you be there for this afternoon's meeting ?08:58
*** lemko has joined #cloudkitty10:17
openstackgerritLuka Peschke proposed openstack/cloudkitty-dashboard master: Import reverse from django.urls rather than django.core.urlresolvers  https://review.openstack.org/63439310:39
LinkidHi peschk_l ! No sorry, I have to much work to do :/11:30
peschk_lLinkid: all right, you'll have the logs anyways :)12:39
*** lemko has quit IRC13:06
*** my_nd has quit IRC13:10
openstackgerritLuka Peschke proposed openstack/cloudkitty master: Delete v2 gnocchi storage  https://review.openstack.org/62591113:57
*** jferrieu has joined #cloudkitty14:59
peschk_lhuats: are you around ?15:00
peschk_l#startmeeting cloudkitty15:00
openstackMeeting started Fri Feb  1 15:00:55 2019 UTC and is due to finish in 60 minutes.  The chair is peschk_l. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: cloudkitty)"15:00
openstackThe meeting name has been set to 'cloudkitty'15:00
peschk_lhello everybody15:01
jferrieuhi15:01
erolgo/15:01
peschk_lthe agenda for today's meeting can be found at https://etherpad.openstack.org/p/cloudkitty-meeting-topics15:01
peschk_lwe'll proceed with the topics in the order theyy are added. If there is anything you'd like to address, fell free to add your topic to the etherpad15:02
peschk_lhello erolg, nice to see new people around15:02
peschk_lalright, let's start15:03
peschk_l#topic v2 API15:03
*** openstack changes topic to "v2 API (Meeting topic: cloudkitty)"15:03
peschk_lThe spec for the v2 API is still under review. We'd like to merge it as soon as possible. I'll push work that has already been done on it as soon as the spec is accepted15:04
peschk_ljferrieu, huats, could you please have a look at the spec again ? If you both approve the spec, we'll merge it. I already integrated Linkid's remarks15:05
peschk_l#link https://review.openstack.org/#/c/614275/15:05
jferrieuI am reviewing it15:06
peschk_lI believe that's it for the v2 API, not much to say appart from that15:06
peschk_ljferrieu: thanks!15:06
peschk_l#topic Prometheus collector spec15:07
*** openstack changes topic to "Prometheus collector spec (Meeting topic: cloudkitty)"15:07
peschk_las you may know, jferrieu has been working on the Prometheus collector lately. He has submitted a spec. It looks good to me, but additional reviews are of course required. If anybody wants to read it, please do so!15:08
peschk_l#link https://review.openstack.org/#/c/626142/15:08
peschk_ljferrieu: anything to add about this ?15:09
jferrieuI have started to setup a dev environment looking forward to implement unit tests15:10
jferrieuI will push them as soon as the spec is validated by the community15:10
peschk_lall right, nice15:10
peschk_l#topic state of the code cleanup15:11
*** openstack changes topic to "state of the code cleanup (Meeting topic: cloudkitty)"15:11
peschk_las we discussed during last meeting, it has been decided to remove the unmaintained parts of cloudkitty's code. ie some fetchers, the v2 gnocchi storage (which was only for testing purposes), some collectors and the gnocchi transformer15:12
peschk_lthings are going forward on this, as you can see on the associated story:15:13
peschk_l# link https://storyboard.openstack.org/#!/story/200440015:13
peschk_lA patch is under review for the removal of the v2 storage backend, and the writer will be removed in T, S being the deprecation release15:14
peschk_lNo help is required on this, but we definitely need some for the next topic!15:15
peschk_l#topic documentation updates15:15
*** openstack changes topic to "documentation updates (Meeting topic: cloudkitty)"15:15
peschk_lthe associated story can be found here15:16
peschk_l#link https://storyboard.openstack.org/#!/story/200417915:16
peschk_lThree patches are currently under review: One is about collectors (from and admin point of view), another is some developper documentation about how to write a new collector, and the last one updates the hashmap documentation15:17
peschk_l#link https://review.openstack.org/#/c/633035/15:17
peschk_l@link https://review.openstack.org/#/c/625924/15:18
peschk_l#link https://review.openstack.org/#/c/628393/15:18
peschk_lIt would be nice to have reviews on these from users, as they are the target audience of these changes15:19
peschk_ljferrieu and Linkid have already made some reviews on these, but it would be nice to have other point of views15:19
peschk_lhuats: if you have some time to read these, it would be great15:20
peschk_ljust a note for people who are not familiar with gerrit: you can have an html version of the generated documentation by clicking on "openstack-tox-docs" under "Zuul check" in the gerrit interface for a given patch15:21
peschk_la fourth patch about storage backend configuration is also WIP15:21
peschk_lDoes anybody have something to add on this ?15:22
peschk_lall right, moving on15:24
peschk_l#topic state of the dashboard15:24
*** openstack changes topic to "state of the dashboard (Meeting topic: cloudkitty)"15:24
peschk_lAs we have already discussed several times, we are trying to get rid of minified javascript in the dashboard15:25
peschk_lthis will be done in three steps:15:27
peschk_l1. Add non-minified versions of the javascript files next to the minified ones15:27
peschk_l2. Get rid of D3-pie, as it is not packaged in XStatic15:27
peschk_l3. Make the dashboard depend on Xstatic packages for javascript dependencies, rather than having them in the repo15:27
peschk_lstep 1 has been managed by zigo and has already been merged15:27
peschk_lI am affected to step 2 and have submitted a patch for it: https://review.openstack.org/#/c/627994/. Reviews welcome!15:28
peschk_lstep 3 is Linkid's job. It is currently WIP, but he has already submitted a patch he's working on, in case you want to have a look:15:29
*** lemko has joined #cloudkitty15:29
peschk_l#link https://review.openstack.org/#/c/628318/15:29
peschk_lI'm confident that this will be done by the Stein release15:30
peschk_lThere are two more things in the dashboard that must be solved before we release Stein15:30
peschk_l1. The hashmap service used for predictive pricing is harcoded in the dashboard (it's "compute"). This should be configurable by admins.15:31
peschk_lI'm currently working on this and I'll keep you updated15:31
peschk_l2. Some imports are done in ways which are only compatible with django 1.x. This will be an issue when we'll switch to python3/django2. A patch has been submitted this morning to address this:15:33
peschk_l#link https://review.openstack.org/#/c/634393/15:33
peschk_lThese should be the last patches we land before the Stein release. It seems to be a reasonable toarget15:34
peschk_l*target15:34
peschk_lDoes anybody have questions about the dashboard ?15:35
peschk_lmoving on15:36
peschk_l#topic Change in Gnocchi collector's behavior concerning resource metadata15:37
*** openstack changes topic to "Change in Gnocchi collector's behavior concerning resource metadata (Meeting topic: cloudkitty)"15:37
peschk_lThis should be quick. We encoutered the same scenario in several deployments. Sometimes, gnocchi resources do have measures in their associated metrics after their deletion date15:38
peschk_ldue ot its design, the gnocchi collector fails to retrieve the associated metadata15:38
peschk_lmore details are available in the followiong story:15:38
peschk_lhttps://storyboard.openstack.org/#!/story/200489515:38
peschk_l#link https://storyboard.openstack.org/#!/story/200489515:39
peschk_lThe proposed fix can be found here:15:39
peschk_l#link https://review.openstack.org/#/c/634199/15:39
peschk_ljferrieu has already reviewed it, at least one additional review would be nice15:40
peschk_lThat's also something which would be nice to have in Stein15:41
peschk_llet's move on to the final topic. there will be some time for q &a at the end of the meeting15:42
peschk_l#topic Adding collector + fetcher to the state database15:42
*** openstack changes topic to "Adding collector + fetcher to the state database (Meeting topic: cloudkitty)"15:42
peschk_lI'm currently working on a spec for this. The problem is basically the following: Let's say that you use cloudkitty to rate an OpenStack cloud. You have one collector collecting data from gnocchi and another one from monasca15:44
peschk_lif both of these collectors are using the same scope (let's say project_id), the behavior of cloudkitty will be unpredictable15:44
peschk_lor rather: The first collector trying to process a project will lock it and update the state until the current day. This would lead to missing data15:46
peschk_lMore details on this problem and the proposed solution will be available in the spec once it is submitted15:47
peschk_lbut in a nutshell: we could add the collector (ie the datasource) and the fetcher which retrieved the scope into the state management workflow15:48
peschk_lThis would allow to fix the case described above, and would avoid hash collisions between UUIDs from different sources (even if they are very unlikely to occur)15:49
peschk_lDoes anybody have questions on this ?15:50
peschk_l#topic Q & A15:51
*** openstack changes topic to "Q & A (Meeting topic: cloudkitty)"15:51
peschk_lwe have 10 minutes left. If anybody wants to ask some questions on any of today's topics, he/she can do it now15:52
openstackgerritLuka Peschke proposed openstack/cloudkitty master: Delete v2 gnocchi storage  https://review.openstack.org/62591115:53
jferrieuyou were speaking of the state management workflow15:53
jferrieucan I have some details on this? Or at least some resource to help at understanding it?15:54
peschk_ljferrieu: of course15:54
peschk_lFor each running processor the orchestrator retrieves the different scopes (project/domain IDs / namespaces / whatever) to rate15:56
peschk_lfor each scope, a worker is spawned. This worker tries to acquire a lock. If it succeeds, it will process the scope it was given from the state (ie timestamp) it has been left at until the current timestamp - X collect periods15:57
peschk_lcurrently, only the scope_id is stored, next to its timestamp. But in the case described above, the following would happen:15:58
jferrieuyeah I now see the problem I tink15:58
jferrieuit would happen on lock acquiring15:59
peschk_l- gnocchi collector locks the tenant XXX, queries its state, get None. In consequence, it processes data from the beginning of the month until timestamp H and releases the lock15:59
peschk_l- monasca collector tries to acquire the lock, fails, processes some other tenants, and tries again. When it asks for the scope's state, it gets "H". So the monasca collector will only collect data from H to H+116:00
peschk_ladding the collector next to the scope_id would solve this16:01
peschk_l*the colelctor and the scope fetcher16:01
jferrieuok I see now16:03
jferrieuthanks16:03
peschk_lyou're welcome :-)16:03
peschk_lWe're runnig out of time, I'll end the meeting. Thanks everybody for attending!16:04
peschk_l#endmeeting16:05
*** openstack changes topic to "Rating component for OpenStack https://wiki.openstack.org/wiki/CloudKitty"16:05
openstackMeeting ended Fri Feb  1 16:05:02 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:05
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cloudkitty/2019/cloudkitty.2019-02-01-15.00.html16:05
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cloudkitty/2019/cloudkitty.2019-02-01-15.00.txt16:05
openstackLog:            http://eavesdrop.openstack.org/meetings/cloudkitty/2019/cloudkitty.2019-02-01-15.00.log.html16:05
jferrieuThanks a lot, see you16:05
*** lemko has quit IRC18:18
*** jferrieu has quit IRC18:23
*** canori01 has joined #cloudkitty19:38
canori01hi, I installed cloudkitty dashboard from source, but when I load horizon it complains about compression19:44

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