| *** evrardjp has quit IRC | 05:33 | |
| *** evrardjp has joined #cloudkitty | 05:33 | |
| *** sboyron has joined #cloudkitty | 07:16 | |
| *** sboyron has quit IRC | 07:40 | |
| *** sboyron has joined #cloudkitty | 08:11 | |
| *** rafaelweingartne has joined #cloudkitty | 13:57 | |
| priteau | Hi rafaelweingartne | 14:00 |
|---|---|---|
| jopdorp | is there meeting? | 14:00 |
| rafaelweingartne | Hello Pierre | 14:00 |
| rafaelweingartne | are you going to chair today? | 14:01 |
| priteau | Sorry, I thought you were | 14:01 |
| rafaelweingartne | I saw you, and I thought you were that is why I was waiting :) | 14:01 |
| jopdorp | rafaelweingartne: is the meeting here or in openstack-meetin-alt? | 14:01 |
| rafaelweingartne | #startmeeting cloudkitty | 14:02 |
| openstack | Meeting started Mon Nov 16 14:02:11 2020 UTC and is due to finish in 60 minutes. The chair is rafaelweingartne. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:02 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:02 |
| *** openstack changes topic to " (Meeting topic: cloudkitty)" | 14:02 | |
| openstack | The meeting name has been set to 'cloudkitty' | 14:02 |
| priteau | jopdorp: it's here :-) | 14:02 |
| jopdorp | great :) | 14:02 |
| rafaelweingartne | Hello guys, sorry for the delay. Let's start the CloudKitty meeting | 14:02 |
| rafaelweingartne | Roll count | 14:02 |
| jopdorp | o/ | 14:03 |
| priteau | o/ | 14:03 |
| rafaelweingartne | \o | 14:03 |
| rafaelweingartne | #topic Review priorities | 14:04 |
| *** openstack changes topic to "Review priorities (Meeting topic: cloudkitty)" | 14:04 | |
| rafaelweingartne | Do you guys have some review priorities to ask for? I might have missed some emails, but I did not receive any requests in the past weeks or so | 14:04 |
| priteau | Indeed it's been quiet on the code front. I am just recently back from paternity leave and have not quite yet caught up with everything | 14:05 |
| jopdorp | There are some specs I am open to write or implement regarding billing integration with moneybird and/or a rating page that looks more like an invoice | 14:06 |
| jopdorp | And maybe to look at the elasticsearch driver | 14:07 |
| rafaelweingartne | jopdorp: that would be awesome | 14:07 |
| jopdorp | i remember seeing a blueprint a while ago about billing integration | 14:08 |
| rafaelweingartne | priteau: there are some follow ups from the PTG meeting that I will try to work on as well. Specially, the project awareness topic. | 14:08 |
| priteau | Is moneybird a paid solution? There's not much information on the english website | 14:08 |
| jopdorp | yes | 14:09 |
| rafaelweingartne | We need to write down some success use cases to demonstrate for the public how people are leveraging CloudKitty as the bedrock of their billing chain | 14:09 |
| jopdorp | so we use it with gnocchi a the srouce, elasticsearch driver for the storage and moneybird for billing | 14:10 |
| priteau | I can talk with people managing clouds where we've set up cloudkitty | 14:10 |
| jopdorp | priteau: we work with mark and isaac | 14:10 |
| priteau | jopdorp: I know :-) | 14:11 |
| rafaelweingartne | jopdorp: what is the idea behind this moneybird integration? If the system (moneybird) generate invoices, why can't it consume CloudKitty API instead? | 14:11 |
| jopdorp | I'm not sure I understood the answer correctly | 14:12 |
| jopdorp | I made a django app that consumes the cloudkitty api, with a react frontend that can get the summary for a time period from cloudkitty | 14:12 |
| rafaelweingartne | Why does CloudKitty need a driver/integration with MoneyBird? Would CloudKitty consume its API? Or, would CloudKitty push data to it? | 14:12 |
| jopdorp | the uses the moneybird api to create an invoice | 14:12 |
| jopdorp | we might create a driver architecture so people can choose the billing system cloudkitty should itnegrate with | 14:13 |
| jopdorp | invoice*/finance system | 14:13 |
| priteau | rafaelweingartne: I guess that MoneyBird cannot be customised, so we need to push data to it, hence the need for some glue between cloudkitty and the billing system | 14:14 |
| rafaelweingartne | That is a good topic, we discussed that in the PTG | 14:14 |
| jopdorp | sorry to have missed that | 14:14 |
| rafaelweingartne | #link https://etherpad.opendev.org/p/cloudkitty-ptg-wallaby | 14:14 |
| rafaelweingartne | One of the discussions reached the conclusion that "Invoicing is out of the escope of Cloudkitty. The invoice system should instead consume it (CloudKitty)."" | 14:14 |
| jopdorp | i see | 14:15 |
| jopdorp | ok | 14:15 |
| jopdorp | https://review.opendev.org/#/c/708121/ | 14:15 |
| jopdorp | is this also about something like a per-instance usage summary? | 14:15 |
| rafaelweingartne | jopdorp: it can be, we extended that API, to allow operators/integrators to customize the usage/rating reports | 14:16 |
| jopdorp | I might have a look at the elasticsearch clieant part for custom fields | 14:16 |
| jopdorp | https://review.opendev.org/#/c/708121/3/cloudkitty/storage/v2/elasticsearch/client.py | 14:17 |
| rafaelweingartne | that would be awesome | 14:17 |
| jopdorp | okay I'll put it in my todo | 14:17 |
| rafaelweingartne | I just implemented it for the backends we were using | 14:17 |
| jopdorp | should i commit it as part of that review? | 14:18 |
| rafaelweingartne | I would rather create a new commit, and add it as depending on https://review.opendev.org/#/c/708121 | 14:18 |
| jopdorp | will do | 14:19 |
| rafaelweingartne | At least, to me, it facilitates the review process | 14:19 |
| priteau | +1 | 14:19 |
| jopdorp | I might need some help with how to do that | 14:19 |
| priteau | Smaller commits are easier to review | 14:19 |
| rafaelweingartne | exactly | 14:19 |
| jopdorp | never did that before, I'm quite new in participating as a dev in the openstack community | 14:19 |
| rafaelweingartne | if you need some assistance, just ping me | 14:20 |
| jopdorp | okay! | 14:20 |
| priteau | https://docs.openstack.org/contributors/code-and-documentation/index.html | 14:21 |
| jopdorp | thanks | 14:21 |
| priteau | It's very lengthy so in particular check: | 14:21 |
| priteau | * Account Setup | 14:21 |
| priteau | * Setting Up Your Gerrit Account | 14:22 |
| jopdorp | ui do have a gerrit account | 14:22 |
| jopdorp | just the step of making a review depend on another review | 14:22 |
| jopdorp | not sure how to do that | 14:22 |
| priteau | oh, that's easy | 14:22 |
| priteau | https://docs.openstack.org/contributors/code-and-documentation/patch-best-practices.html#depends-on-tag | 14:22 |
| jopdorp | https://docs.openstack.org/contributors/code-and-documentation/patch-best-practices.html#patch-chains-depends-on-tag-and-gerrit-topics | 14:22 |
| jopdorp | Depends-On: Id4dd83d0703ec0dff32510e6dd1d2dad9b181306 | 14:23 |
| jopdorp | in the commit message? | 14:23 |
| jopdorp | that would be the change id of the other change | 14:23 |
| rafaelweingartne | yes | 14:24 |
| jopdorp | ok thanks | 14:24 |
| rafaelweingartne | I normally use the full URL, but I guess that is not needed | 14:24 |
| jopdorp | https://review.opendev.org/#/c/708121 ? | 14:25 |
| rafaelweingartne | that is how I have been doing so far | 14:25 |
| jopdorp | will do it like that | 14:25 |
| priteau | You can use either | 14:25 |
| jopdorp | cool | 14:26 |
| priteau | you can also skip the '/#/c' part from the URL | 14:26 |
| rafaelweingartne | Moving on | 14:30 |
| rafaelweingartne | #topic Wallaby release | 14:30 |
| *** openstack changes topic to "Wallaby release (Meeting topic: cloudkitty)" | 14:30 | |
| rafaelweingartne | We should start discussing the new features that we would like to see in Wallaby, so we can work towards them. | 14:30 |
| priteau | My priority is not so much a feature but figuring out why we are seeing issues using metadata with Monasca | 14:31 |
| rafaelweingartne | I guess that we are not going to define them today, but it would be interesting to start thinking and taking notes of the things we want to see in this release. | 14:31 |
| priteau | I don't think there is a bug report about it, I need to confirm it's not a configuration issue | 14:31 |
| rafaelweingartne | #action create a list with possible features we would like to see in Wallaby | 14:32 |
| rafaelweingartne | priteau: if you need some help, let me know if I can help you somehow | 14:32 |
| priteau | thanks, I will let you know if needed | 14:33 |
| priteau | I'd also like to see more testing of different backends | 14:35 |
| rafaelweingartne | +1 | 14:36 |
| jopdorp | +1 | 14:37 |
| jopdorp | oh there is something that we faced | 14:37 |
| jopdorp | that is the pricing tab in the new instance form in horizon | 14:37 |
| jopdorp | it always states 0$ | 14:37 |
| jopdorp | i think that's because we only have metered costs, no one time costs or something like that | 14:38 |
| jopdorp | no startup costs | 14:38 |
| jopdorp | so i was thinking about creating a toggle to remove it | 14:38 |
| jopdorp | in the cloudkitty-dashboard config | 14:38 |
| rafaelweingartne | Maybe that is a bug? | 14:39 |
| rafaelweingartne | I thought CloudKitty did not support one time charging yet | 14:40 |
| rafaelweingartne | jopdorp: could you investigate into that, and then open a bug report if that is the case? | 14:40 |
| jopdorp | yes | 14:41 |
| rafaelweingartne | awesome, thanks! | 14:42 |
| jopdorp | i think it is about overrides.py and _launch_details_price.html | 14:42 |
| jopdorp | https://opendev.org/openstack/cloudkitty-dashboard/src/branch/master/cloudkittydashboard/overrides.py | 14:43 |
| jopdorp | https://opendev.org/openstack/cloudkitty-dashboard/src/branch/master/cloudkittydashboard/dashboards/project/rating/templates/rating/_launch_details_price.html | 14:43 |
| rafaelweingartne | that looks like it | 14:44 |
| rafaelweingartne | Now, I open for general questions and topics that people might have. | 14:49 |
| rafaelweingartne | #topic AOB | 14:49 |
| *** openstack changes topic to "AOB (Meeting topic: cloudkitty)" | 14:50 | |
| rafaelweingartne | I will leave it open for more 5 minutes before closing the meeting | 14:50 |
| jopdorp | well | 14:50 |
| jopdorp | I'm open to becoming a core reviewer in the cloudkitty project | 14:50 |
| jopdorp | we rely on it | 14:50 |
| jopdorp | and cloudkitty needs to stay alive!! :D | 14:51 |
| rafaelweingartne | jopdorp: I do not know how this invitation process works. Maybe Pierre can guide us here | 14:51 |
| jopdorp | priteau: suggestions? | 14:51 |
| priteau | jopdorp: have you done cloudkitty reviews so far? | 14:53 |
| jopdorp | no | 14:54 |
| jopdorp | suggestions for changes to look at? | 14:54 |
| priteau | Sorry, I have to go | 14:56 |
| rafaelweingartne | jopdorp: I would start here https://review.opendev.org/#/q/status:open+project:openstack/cloudkitty | 14:57 |
| jopdorp | I'll have a look | 14:57 |
| rafaelweingartne | Normally, any OpenSource project works like the following. People start contributing, and then, after sucessfull and continous contributions | 14:57 |
| rafaelweingartne | the contributors are invited to become core reviewers/committers or other positions in the project | 14:58 |
| rafaelweingartne | I will have to leave as well | 14:59 |
| rafaelweingartne | Thank you guys for participating. Have a nice week. | 14:59 |
| rafaelweingartne | #endmeeting | 14:59 |
| *** openstack changes topic to "Rating component for OpenStack https://wiki.openstack.org/wiki/CloudKitty" | 14:59 | |
| openstack | Meeting ended Mon Nov 16 14:59:27 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:59 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/cloudkitty/2020/cloudkitty.2020-11-16-14.02.html | 14:59 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/cloudkitty/2020/cloudkitty.2020-11-16-14.02.txt | 14:59 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/cloudkitty/2020/cloudkitty.2020-11-16-14.02.log.html | 14:59 |
| jopdorp | rafaelweingartne: There is https://review.opendev.org/#/c/684747/ which depends on https://review.opendev.org/#/c/684734/5 | 15:01 |
| jopdorp | Am I correct to assume that one of us has to pick up https://review.opendev.org/#/c/684734/5 because the people who intially created it are not actively involved in cloudkitty anymore? | 15:02 |
| rafaelweingartne | yes | 15:05 |
| rafaelweingartne | somebody needs to take over | 15:05 |
| jopdorp | I'm not sure I'm comfortable picking that one up yet | 15:07 |
| jopdorp | what's the policy on unit tests? | 15:09 |
| jopdorp | I'm looking at this one https://review.opendev.org/#/c/721955/ | 15:09 |
| jopdorp | the code looks like it would work to me, bet there's no test covering that there is only one entry per granularity | 15:10 |
| rafaelweingartne | unit tests are appreciated, but I am not sure if we can force people to add them. | 15:15 |
| rafaelweingartne | We can suggest though | 15:15 |
| priteau | jopdorp: Sorry for dropping out earlier, I needed to get my daughter from school. | 15:52 |
| priteau | Generally the policy for joining a core reviewer team is to have contributed to the project before, with commits and reviews. We bended the rules to recreate a core team this summer when the old one became inactive, it would be best to follow the correct process from now on. If you can do a few quality regular reviews (+1), I am sure that should be enough to become a core reviewer :-) | 15:53 |
| jopdorp | priteau: alright! | 15:58 |
| *** rafaelweingartne has quit IRC | 17:04 | |
| *** sboyron has quit IRC | 22:08 | |
| *** sboyron has joined #cloudkitty | 22:09 | |
| *** sboyron has quit IRC | 23:03 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!