Monday, 2021-05-17

*** yoctozepto has quit IRC00:17
*** yoctozepto has joined #cloudkitty00:17
*** vishalmanchanda has joined #cloudkitty04:43
*** sboyron has joined #cloudkitty05:51
*** sboyron has quit IRC05:52
*** sboyron has joined #cloudkitty05:55
*** cylopez has joined #cloudkitty07:30
*** mkarpiarz has joined #cloudkitty07:50
*** yoctozepto has quit IRC11:55
*** yoctozepto has joined #cloudkitty12:31
priteaumkarpiarz: I believe we have a meeting today, in 40 minutes13:18
mkarpiarzThanks, this meeting was set at 2PM in my diary. I'll fix this.13:21
priteauIt's set in UTC so switches time when clocks change13:23
*** rafaelweingartne has joined #cloudkitty13:51
rafaelweingartnehello guys13:53
mkarpiarzHi, rafaelweingartne!13:55
priteauHello14:00
rafaelweingartne#startmeeting cloudkitty14:00
openstackMeeting started Mon May 17 14:00:46 2021 UTC and is due to finish in 60 minutes.  The chair is rafaelweingartne. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: cloudkitty)"14:00
openstackThe meeting name has been set to 'cloudkitty'14:00
rafaelweingartneRoll count14:00
priteauo/14:01
mkarpiarzHi!14:01
jonhero/14:02
rafaelweingartne#topic Xena release14:04
*** openstack changes topic to "Xena release (Meeting topic: cloudkitty)"14:04
rafaelweingartneI guess that we are moving towards Xena releases. I think that it might be good to apply the agreement we had during the PTG meeting of merging things sooner than latter, and from the middle/end of the release cycle we can then focus on stabilization14:05
rafaelweingartnehaving said that, I would like to ask you guys to review some of the patches I have open, they are interesting for Xena release, I guess14:05
rafaelweingartnealso, I have opened a specification for the reprocessing API that we also discussed in the PTG14:06
rafaelweingartneit would be important to get some feedback before I move on with the implementation14:06
priteauAgreed. If you can provide links and/or tag them as Review-Priority+1, I will allocate time for review14:07
rafaelweingartnesure I will tag them14:07
rafaelweingartnehttps://review.opendev.org/q/owner:rafael%2540apache.org+project:openstack/cloudkitty+status:open14:08
priteauThank you14:09
priteauI've been a bit distracted from reviews, but for a good reason. I was working on a new cloudkitty collector14:09
rafaelweingartneand, this one14:09
rafaelweingartnehttps://review.opendev.org/q/owner:rafael%2540apache.org+project:openstack/cloudkitty-specs+status:open14:09
mkarpiarzSure, I should be able to help with these as well.14:09
priteauI will try to contribute it soon14:09
rafaelweingartneBTW, do you guys know how to add an extra style in the pdf-docs job?14:11
rafaelweingartneWhen I run the job to build the pdf-docs in my laptop, it works14:11
rafaelweingartneand it works, because I added/installed one of the latex dependencies manually14:11
rafaelweingartnehowever, in the CI jobs this style does not seem to exist14:11
priteauDo you really need to? I am not sure people really look at pdf docs14:12
rafaelweingartneme neither... when I tested for instance, I only built the HTML ones14:13
rafaelweingartnebut the CI jobs are runing the PDF build14:13
rafaelweingartneand this causes my specs proposal to receive a -1 from Zuul14:13
mkarpiarzDo we have the ability to disable PDF builds then?14:14
priteauI contributed the pdf-docs fix14:14
priteauhttps://review.opendev.org/c/openstack/cloudkitty-specs/+/79162414:14
priteaumkarpiarz: could you please review it?14:15
priteauIt's an OpenStack-wide issue, the fix comes from ironic-specs14:15
priteaurafaelweingartne: It you rebase on top of d1803c94ef2ecb616d7bbb153eaa29bb2e51c6cd it should work14:16
rafaelweingartneI see14:17
rafaelweingartneI will do so then14:17
rafaelweingartnethanks for the tips14:17
openstackgerritRafael Weingartner proposed openstack/cloudkitty-specs master: Propose reprocessing API  https://review.opendev.org/c/openstack/cloudkitty-specs/+/79124514:22
openstackgerritRafael Weingartner proposed openstack/cloudkitty-specs master: Propose reprocessing API  https://review.opendev.org/c/openstack/cloudkitty-specs/+/79124514:23
rafaelweingartnedone14:24
openstackgerritMerged openstack/cloudkitty-specs master: Update tox config  https://review.opendev.org/c/openstack/cloudkitty-specs/+/79162414:25
rafaelweingartneWell, from my side those are the priorities14:26
rafaelweingartnedo you guys have some other?14:26
openstackgerritPierre Riteau proposed openstack/cloudkitty-specs master: [ussuri][goal] Update contributor documentation  https://review.opendev.org/c/openstack/cloudkitty-specs/+/79132014:26
mkarpiarzNone at the moment.14:27
priteauAs mentioned, I have written a new collector, which uses the Nova simple tenant usage API. I will need to write some tests before submitting it14:28
rafaelweingartnehmm14:28
rafaelweingartnethis API is scheduled or planned to be removed14:28
rafaelweingartneright?14:28
rafaelweingartneit also only shows for how long a VM exist in the environment, and not the actual runtime14:29
priteauIs it planned to be removed? I've not heard about it14:29
priteauAnd yes, it has shortcomings, so it isn't a replacement for Gnocchi / Monasca / Prometheus14:30
rafaelweingartnewell14:30
priteauHowever, it allows you to gather information about past usage data which isn't possible if you are missing metrics from the above systems14:30
rafaelweingartnethat is what people told me when I proposed a change in the API14:30
rafaelweingartneto allow operators to configure the API to output more meaningful data14:31
rafaelweingartnepriteau, exactly the same issue we had :)14:31
rafaelweingartnewe thought about using it, but then, when we discovered that it only shows for how long a VM exists, it was not useful anymore14:31
priteauDo you have a link to your proposed API change?14:32
rafaelweingartne#link https://review.opendev.org/c/openstack/nova/+/71111314:32
rafaelweingartneyou can see the discussion there14:32
priteauThanks14:33
priteauIt was useful for us as we believe started and stopped instances should be billed in the same way. The main issue was shelved instances being included.14:35
rafaelweingartneah, I see14:36
rafaelweingartnefor the cases we have applied Openstack so far that is not a valid use case14:36
rafaelweingartneusers only want to pay for actual usave of running VMs14:36
rafaelweingartneonly volumes are billed no matter if the VM is running or not :)14:36
priteauShut down instances consume the same amount of CPU / memory / disk resources as running ones ;-)14:37
rafaelweingartnewell, they are down14:37
rafaelweingartneso they are not running14:37
rafaelweingartneI guess it depends on how one handle this situations14:37
priteauYes but from a nova scheduler / placement point of view, they will still consume resources14:38
rafaelweingartneit depends on the perspective public cloud versus private cloud14:38
rafaelweingartnethey are allocated, which means logically create in the system14:38
rafaelweingartnebut not actually running in the hypervisor14:38
priteauAnyway, it's a small collector, not much maintenance, so I don't think it would hurt to include it14:39
rafaelweingartnebut anyways, I just mentioned that because we tried to used this API for a DR, and in the end, it was useless for our context14:39
rafaelweingartnethe more we aggregate the better, as long as we have a clear documentation14:40
rafaelweingartnewhich was the case in Nova14:40
rafaelweingartnepeople did not want to change this behavior of the API, but I suggested them, to at least clarify the behavior of the API14:40
rafaelweingartneWell, do we have some other priority for Xena?14:44
priteauNothing from me14:45
rafaelweingartneI will open for general questions then14:45
rafaelweingartne#topic AOB14:45
*** openstack changes topic to "AOB (Meeting topic: cloudkitty)"14:45
priteaurafaelweingartne: please review https://review.opendev.org/c/openstack/cloudkitty/+/789727 (trivial)14:49
rafaelweingartnewell, we are running of time14:51
rafaelweingartneand I guess that we covered most of the planned topics14:51
rafaelweingartneif you guys have nothing else, I will close for today14:51
rafaelweingartneThank you guys for participating. Have a nice week.14:52
rafaelweingartne#endmeeting14:52
*** openstack changes topic to "Rating component for OpenStack https://wiki.openstack.org/wiki/CloudKitty"14:52
openstackMeeting ended Mon May 17 14:52:13 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cloudkitty/2021/cloudkitty.2021-05-17-14.00.html14:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cloudkitty/2021/cloudkitty.2021-05-17-14.00.txt14:52
openstackLog:            http://eavesdrop.openstack.org/meetings/cloudkitty/2021/cloudkitty.2021-05-17-14.00.log.html14:52
priteauThanks rafaelweingartne!14:53
*** vishalmanchanda has quit IRC14:54
openstackgerritMerged openstack/cloudkitty-specs master: [ussuri][goal] Update contributor documentation  https://review.opendev.org/c/openstack/cloudkitty-specs/+/79132014:54
*** rafaelweingartne has quit IRC14:55
*** cylopez has quit IRC14:59
*** sboyron has quit IRC21:01

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!