| *** tosky has quit IRC | 00:06 | |
| *** k_mouza has joined #openstack-monasca | 00:45 | |
| *** k_mouza has quit IRC | 00:49 | |
| *** vishalmanchanda has joined #openstack-monasca | 03:52 | |
| *** k_mouza has joined #openstack-monasca | 04:46 | |
| *** k_mouza has quit IRC | 04:50 | |
| *** nikparasyr has joined #openstack-monasca | 07:46 | |
| *** witek has joined #openstack-monasca | 08:21 | |
| *** tosky has joined #openstack-monasca | 08:56 | |
| *** k_mouza has joined #openstack-monasca | 09:00 | |
| *** k_mouza has quit IRC | 09:05 | |
| *** chaconpiza has joined #openstack-monasca | 09:20 | |
| *** k_mouza has joined #openstack-monasca | 10:51 | |
| *** kwazar is now known as quasar_ | 10:55 | |
| *** quasar_ is now known as quasar | 10:55 | |
| *** quasar is now known as quasar` | 10:56 | |
| *** yan0s has joined #openstack-monasca | 12:46 | |
| chaconpiza | Courtesy Monasca meeting reminder in #openstack-monasca: witek,jayahn,iurygregory,ezpz,igorn,haad,sc,joadavis, akiraY,tobiajo,dougsz,fouadben, amofakhar, haru5ny (haruki),kaiokmo,pandiyan,guilhermesp,chaconpiza,hosanai,Wasaac,bandorf,mbindlish,nikparasyr,adriancz | 12:52 |
|---|---|---|
| *** bandorf has joined #openstack-monasca | 12:58 | |
| chaconpiza | #startmeeting monasca | 13:00 |
| openstack | Meeting started Tue Nov 17 13:00:04 2020 UTC and is due to finish in 60 minutes. The chair is chaconpiza. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:00 |
| *** openstack changes topic to " (Meeting topic: monasca)" | 13:00 | |
| openstack | The meeting name has been set to 'monasca' | 13:00 |
| chaconpiza | Hi | 13:00 |
| witek | hi | 13:00 |
| chaconpiza | Hello Witek | 13:00 |
| chaconpiza | The agenda as usual https://etherpad.opendev.org/p/monasca-team-meeting-agenda | 13:00 |
| bandorf | Hi there | 13:00 |
| chaconpiza | Hello Matthias | 13:00 |
| yan0s | Hello! | 13:01 |
| chaconpiza | Hi Yanos and welcome | 13:01 |
| *** dougsz has joined #openstack-monasca | 13:01 | |
| chaconpiza | Let´s start with the topics from the agenda | 13:01 |
| chaconpiza | #topic Fix libvirt configuration (yaml) | 13:02 |
| *** openstack changes topic to "Fix libvirt configuration (yaml) (Meeting topic: monasca)" | 13:02 | |
| chaconpiza | We have a new contributor, Yanos Angelopoulos, who found an issue in Monasca-Agent | 13:02 |
| chaconpiza | https://review.opendev.org/#/c/762221/ | 13:03 |
| chaconpiza | As I wrote in the ticket: "At first glance it looks like we are using oslo-config [1] to handle the configuration like in the rest of Monasca modules. But you are right, monasca-agent is still using .yaml files instead of oslo-config .conf files." | 13:03 |
| chaconpiza | [1] https://opendev.org/openstack/monasca-agent/src/branch/master/monasca_agent/collector/virt/libvirt/inspector.py#L21 | 13:04 |
| witek | hi yan0s, thanks for the contribution | 13:05 |
| chaconpiza | Nevertheless that I misslead at the beginning yan0s found exactly the root cause and fix ;-) | 13:06 |
| chaconpiza | Time ago was an Epic to migrate all Monasca modules to Oslo conf. Maybe Monasca-Agent is a left over of this Epic | 13:06 |
| chaconpiza | I coudn'd find the Story | 13:06 |
| chaconpiza | What is your opinion about to migrate monasca-agent to use oslo conf? | 13:07 |
| chaconpiza | Here we have the related change for Monasca-Notification [2] https://storyboard.openstack.org/#!/story/2000959 | 13:08 |
| witek | +1, but it's more complex than other components | 13:08 |
| chaconpiza | That's right, because of multiple config files for the plugins | 13:08 |
| bandorf | Yes, there are quite a lot | 13:08 |
| chaconpiza | dougsz, how it will impact your deployment? | 13:09 |
| chaconpiza | So far Yanos yaml fix is only merged in the master branch. yan0s, do you need it in a stable branch? | 13:10 |
| chaconpiza | #topic Migrate configuration of Monasca-Agent from yaml to oslo-config .conf | 13:11 |
| *** openstack changes topic to "Migrate configuration of Monasca-Agent from yaml to oslo-config .conf (Meeting topic: monasca)" | 13:11 | |
| yan0s | for now I'm just testing stuff, we are considering switching from ceilometer to monasca | 13:12 |
| chaconpiza | I see | 13:12 |
| yan0s | if we choose to do so then I would want this to be on stable | 13:12 |
| witek | yan0s: if you need, you can use Ceilometer's Monasca publisher to get Ceilometer measurements into Monasca | 13:13 |
| chaconpiza | #action I will create a Story to keep track on "Migrate configuration of Monasca-Agent from yaml to oslo-config .conf" | 13:14 |
| yan0s | witek, I understand that but we want to keep only one project for this job, if possible | 13:14 |
| witek | ack | 13:15 |
| yan0s | for less complexity | 13:15 |
| chaconpiza | let's continue with next topic | 13:16 |
| chaconpiza | #topic [monasca] Transition Stein to EM | 13:16 |
| *** openstack changes topic to "[monasca] Transition Stein to EM (Meeting topic: monasca)" | 13:16 | |
| chaconpiza | Stein branch is going to extended maintenance state | 13:16 |
| yan0s | is there a decision for the previous topic? | 13:16 |
| chaconpiza | yan0s, based on your first contribution I would say that you are on the state to lead the migration to oslo config | 13:18 |
| chaconpiza | of course with the support of the team | 13:18 |
| yan0s | ok | 13:18 |
| witek | if you're ready to work on this, that would be great | 13:19 |
| chaconpiza | right | 13:19 |
| chaconpiza | after the meeting I will create the story and I will assing to you and send you the link to your email | 13:19 |
| yan0s | thanks | 13:20 |
| chaconpiza | 👍 | 13:20 |
| chaconpiza | Alright, coming back to the Stein transition to EM. I checked that all commits hashes are correct | 13:21 |
| chaconpiza | those commits are pointing to the last tag on Stein branch, not necessary to the last commit in the Stein. | 13:22 |
| chaconpiza | But the process is designed like that | 13:22 |
| chaconpiza | I compare with other OpenStack projects. | 13:22 |
| chaconpiza | Of course Monasca-Tempest is an exception with only Master branch | 13:22 |
| chaconpiza | Besides of that there is a small problem with libvirt libraries | 13:23 |
| chaconpiza | not only in Monasca but in few other projects | 13:23 |
| chaconpiza | they want to use Ubuntu Focal for the push into PyPi | 13:24 |
| chaconpiza | We had the same issue in Master and stable/victoria | 13:24 |
| chaconpiza | solved with this change https://review.opendev.org/#/c/757093 | 13:24 |
| chaconpiza | Based on bindep | 13:25 |
| chaconpiza | However they want to solve this situation on other level: https://review.opendev.org/#/c/762699/ | 13:26 |
| chaconpiza | The #action I will cherry pick https://review.opendev.org/#/c/757093 into the stable branches backwards until Stein | 13:26 |
| chaconpiza | it is and innocuous fix | 13:27 |
| witek | lgtm | 13:27 |
| chaconpiza | great | 13:27 |
| chaconpiza | lets move to the next topic | 13:27 |
| bandorf | OK, I'll explain | 13:28 |
| chaconpiza | #topic Upgrade storm version used for monasca-thresh | 13:28 |
| *** openstack changes topic to "Upgrade storm version used for monasca-thresh (Meeting topic: monasca)" | 13:28 | |
| chaconpiza | Thanks Matthias | 13:28 |
| bandorf | Background: In our monasca-based product, we currently use storm 1.0.6 in monasca-thresh. | 13:28 |
| bandorf | So, we need to use a newer version since this one isn't maintained any longer. | 13:29 |
| bandorf | For results of my check, from agenda: | 13:29 |
| bandorf | Versions available: 2.x (latest: 2.2.0), 1.2.3 | 13:29 |
| bandorf | Versions used: devstack: 1.2.2 monasca/monasca-docker: 1.1.1 | 13:29 |
| bandorf | Since we will be executing quite some extensive tests (system test), my idea was to use a new version, if no issues occur - e.g. 2.2.0 | 13:30 |
| bandorf | My first questions: | 13:30 |
| bandorf | Anybody has experience with storm 2.x? | 13:31 |
| bandorf | Any pros and cons, trying to use it? | 13:31 |
| witek | no experience with new Storm from my side | 13:31 |
| bandorf | I was hoping for Doug... :-) | 13:32 |
| bandorf | Maybe, he's currently not in. | 13:32 |
| chaconpiza | dougsz is the one that upgrade Storm in devstack to 1.2.2 https://github.com/openstack/monasca-api/commit/4f62c1d318ebf1756424b7e308fdd037243f5f5c | 13:32 |
| chaconpiza | I assume that they are still using version 1.x.y | 13:33 |
| bandorf | Yes, I can ask him later. | 13:33 |
| bandorf | My 2nd topic: | 13:33 |
| bandorf | We are now using storm image, from which monasca-thresh image is constructed. | 13:33 |
| bandorf | In storm - from e.g. 1.2.3, they changed the base image: | 13:34 |
| bandorf | We are now using storm image, from which monasca-thresh image is constructed. | 13:34 |
| bandorf | storm 1.1.1: Alpine Linux 3.7 storm 1.2.3: Debian GNU/Linux 10 (buster) | 13:35 |
| bandorf | Thus, our Dockerfile doesn't fit any longer. | 13:35 |
| bandorf | Question 1: Is it acceptable for you, that there will be a Dockerfile for updated monasca-thresh that is not compatible with older Storm versions? | 13:36 |
| chaconpiza | This is the Docker file Matthias mentioned https://github.com/openstack/monasca-thresh/blob/master/docker/Dockerfile | 13:36 |
| bandorf | Next is not really a topic, but: Many things have to be changed: | 13:36 |
| bandorf | package mgr: apk -> apt-get | 13:37 |
| chaconpiza | it is possible to handle both? with kind of IF statement? | 13:37 |
| dougsz | sorry, meeting clash | 13:37 |
| bandorf | shell: ash -> bash | 13:37 |
| bandorf | Theoretically of course, it's possible. But it's a different structure, differnet package names, ... | 13:38 |
| bandorf | If there's no urgent reason, I'd like to avoid this | 13:38 |
| witek | ad Q1, I don't think it's a problem, the old version is not maintained anymore | 13:38 |
| bandorf | OK, great - at least some good news. | 13:39 |
| bandorf | Migration on its own is really tough, at least for me. | 13:39 |
| chaconpiza | if we decided to change the Dockerfile to handle the new Storm versions based on debian, it is ok to cherrypick the change to Ussuri? | 13:40 |
| *** k_mouza has quit IRC | 13:41 | |
| bandorf | Doesn't make a lot of sense to me. This would mean we will introduce new storm version for ussuri | 13:41 |
| bandorf | Are you asking because of CMM? Then, let's discuss separately | 13:42 |
| chaconpiza | ok | 13:42 |
| chaconpiza | sure | 13:42 |
| witek | why do we have to move to Debian image? Busybox seems avaialable for Alpine https://pkgs.alpinelinux.org/package/edge/main/x86_64/busybox | 13:43 |
| bandorf | storm image is based on Debian image. | 13:43 |
| chaconpiza | The official Strom image | 13:43 |
| bandorf | Other option: continue with old way, i.e. we build our own image, based on alpine | 13:43 |
| dougsz | bandorf: Apologies, no experience with Storm 2.x yet | 13:44 |
| bandorf | OK, thanks, Doug | 13:44 |
| witek | I see, yes, it makes sense to leverage the official image | 13:44 |
| chaconpiza | in the past we build the storm image from Alpine to later use it as a base for Thresh https://github.com/monasca/monasca-docker/blob/master/monasca-thresh/Dockerfile | 13:45 |
| bandorf | Well, yes, but the job seems to be tough. I'm not sure if it's the right way. The image is provided as "black box", regarding OS etc. | 13:45 |
| bandorf | But we are using the OS, java, ... | 13:45 |
| chaconpiza | now we use the official https://github.com/openstack/monasca-thresh/blob/master/docker/Dockerfile#L8 | 13:45 |
| bandorf | I can investigate a bit longer. Maybe, next week, I will know more. Then, we can discuss again | 13:46 |
| chaconpiza | Thanks Matthias | 13:47 |
| chaconpiza | lets go to next topic | 13:48 |
| chaconpiza | #openstack-discuss threads | 13:48 |
| witek | I've collected relevant threads from the mailing list | 13:48 |
| *** dougsz has quit IRC | 13:48 | |
| witek | the first one is related with the code audit related with the Gerrit outage in Oct | 13:49 |
| witek | http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018795.html | 13:49 |
| witek | then, there was an inquiry on monasca-analytics | 13:50 |
| chaconpiza | the audit means to check the commits/merges in this period for all Monasca repositories? | 13:50 |
| witek | no, there is more | 13:51 |
| witek | some data could be compromised | 13:51 |
| witek | here are all details | 13:51 |
| witek | http://lists.opendev.org/pipermail/service-announce/2020-October/000011.html | 13:51 |
| chaconpiza | Thanks for the link, #action I will go for this | 13:53 |
| witek | then, there was an inquiry on monasca-analytics | 13:54 |
| witek | http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018785.html | 13:54 |
| witek | just FYI | 13:54 |
| witek | finally, Telemetry project plans to meet and discuss next steps | 13:55 |
| witek | http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018685.html | 13:55 |
| witek | main topic seems to be Gnocchi support | 13:55 |
| chaconpiza | I am not sure where to redirect the inquiry about monasca-analytics | 13:55 |
| *** bandorf has quit IRC | 13:56 | |
| witek | well, I've answered that we didn't have anyone maintaining the project | 13:57 |
| chaconpiza | right | 13:57 |
| *** bandorf has joined #openstack-monasca | 13:58 | |
| chaconpiza | Ok, thanks for bringing the topics specially the one related about Gerrit outage | 13:58 |
| chaconpiza | #topic AOB | 13:58 |
| *** openstack changes topic to "AOB (Meeting topic: monasca)" | 13:58 | |
| chaconpiza | is there any other topic for today you like to discuss? | 13:59 |
| bandorf | not from me | 14:00 |
| chaconpiza | Thanks for the meeting today. Again, welcome to the Monasca community Yanos. | 14:00 |
| chaconpiza | See you next week same hour same channel. | 14:00 |
| chaconpiza | Bye | 14:00 |
| witek | thanks everyone | 14:00 |
| bandorf | Thanks, everybody, see you next week | 14:01 |
| chaconpiza | #endmeeting | 14:01 |
| *** openstack changes topic to "Monasca Wallaby PTG Topics and Attendance (Meeting topic: monasca)" | 14:01 | |
| openstack | Meeting ended Tue Nov 17 14:01:26 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:01 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/monasca/2020/monasca.2020-11-17-13.00.html | 14:01 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/monasca/2020/monasca.2020-11-17-13.00.txt | 14:01 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/monasca/2020/monasca.2020-11-17-13.00.log.html | 14:01 |
| *** bandorf has quit IRC | 14:01 | |
| *** adriancz has joined #openstack-monasca | 14:12 | |
| *** dougsz has joined #openstack-monasca | 14:17 | |
| *** dougsz has joined #openstack-monasca | 14:18 | |
| *** k_mouza has joined #openstack-monasca | 14:24 | |
| *** k_mouza has quit IRC | 14:24 | |
| *** k_mouza has joined #openstack-monasca | 14:24 | |
| *** dougsz has quit IRC | 15:11 | |
| *** dougsz has joined #openstack-monasca | 15:17 | |
| *** k_mouza has quit IRC | 16:07 | |
| *** k_mouza has joined #openstack-monasca | 16:23 | |
| *** nikparasyr has left #openstack-monasca | 16:49 | |
| *** witek has quit IRC | 17:21 | |
| *** k_mouza has quit IRC | 17:30 | |
| *** dougsz has quit IRC | 17:32 | |
| *** k_mouza has joined #openstack-monasca | 17:50 | |
| *** witek has joined #openstack-monasca | 18:00 | |
| *** witek has quit IRC | 18:09 | |
| *** k_mouza has quit IRC | 18:10 | |
| *** adriancz has quit IRC | 18:12 | |
| *** k_mouza has joined #openstack-monasca | 18:19 | |
| *** k_mouza has quit IRC | 18:56 | |
| *** jawad_axd has joined #openstack-monasca | 19:36 | |
| *** k_mouza has joined #openstack-monasca | 19:57 | |
| *** k_mouza has quit IRC | 20:01 | |
| *** k_mouza has joined #openstack-monasca | 20:16 | |
| *** k_mouza has quit IRC | 20:21 | |
| *** quasar` is now known as parallax | 23:03 | |
| *** parallax has left #openstack-monasca | 23:07 | |
| *** parallax has joined #openstack-monasca | 23:15 | |
| *** tosky has quit IRC | 23:58 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!