| openstackgerrit | Merged openstack/python-masakariclient master: Remove usage of six https://review.opendev.org/757453 | 01:27 |
|---|---|---|
| *** vishalmanchanda has joined #openstack-masakari | 05:35 | |
| *** suzhengwei has joined #openstack-masakari | 06:45 | |
| yoctozepto | yoctozepto jopdorp suzhengwei - meeting in 8 minutes | 06:52 |
| jopdorp | Thanks for the reminder! | 06:54 |
| yoctozepto | #startmeeting masakari | 07:01 |
| openstack | Meeting started Tue Oct 13 07:01:00 2020 UTC and is due to finish in 60 minutes. The chair is yoctozepto. Information about MeetBot at http://wiki.debian.org/MeetBot. | 07:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 07:01 |
| *** openstack changes topic to " (Meeting topic: masakari)" | 07:01 | |
| openstack | The meeting name has been set to 'masakari' | 07:01 |
| yoctozepto | #topic Roll-call | 07:01 |
| *** openstack changes topic to "Roll-call (Meeting topic: masakari)" | 07:01 | |
| yoctozepto | o/ | 07:01 |
| jopdorp | 0/ | 07:01 |
| jopdorp | o/ | 07:01 |
| yoctozepto | (do note whatever you write in roll-call is fine; it's just to encourage ppl to announce their presence) | 07:02 |
| jopdorp | \m/ this then | 07:04 |
| yoctozepto | xD | 07:05 |
| yoctozepto | suzhengwei: around? | 07:05 |
| yoctozepto | #topic Agenda | 07:07 |
| *** openstack changes topic to "Agenda (Meeting topic: masakari)" | 07:07 | |
| yoctozepto | * Roll-call | 07:07 |
| yoctozepto | * Agenda | 07:07 |
| yoctozepto | * Announcements | 07:07 |
| yoctozepto | ** Victoria release this week! https://releases.openstack.org/victoria/schedule.html | 07:07 |
| yoctozepto | ** Virtual OpenStack Infrastructure Summit is right the next week: https://www.openstack.org/summit/2020/ | 07:08 |
| yoctozepto | ** Masakari Wallaby vPTG planned (in just two weeks! next masakari meeting cancelled): https://etherpad.opendev.org/p/masakari-wallaby-vptg | 07:08 |
| yoctozepto | * Review action items from the last meeting | 07:08 |
| yoctozepto | * CI status | 07:08 |
| yoctozepto | * Backports pending reviews | 07:08 |
| suzhengwei | I am | 07:08 |
| yoctozepto | * Critical Bugs and Patches | 07:08 |
| yoctozepto | * Release planning | 07:08 |
| yoctozepto | * Open discussion | 07:08 |
| yoctozepto | hi suzhengwei | 07:08 |
| suzhengwei | hi | 07:08 |
| yoctozepto | #topic Announcements | 07:08 |
| *** openstack changes topic to "Announcements (Meeting topic: masakari)" | 07:08 | |
| yoctozepto | #info Victoria release this week! https://releases.openstack.org/victoria/schedule.html | 07:08 |
| yoctozepto | so we made it with RC1 so far; the project is pretty dormant so that was not exactly unexpected | 07:09 |
| yoctozepto | any thoughts on the Victoria release? | 07:09 |
| jopdorp | what needs to be done for it still? | 07:10 |
| yoctozepto | jopdorp: release approved | 07:13 |
| yoctozepto | but if you are asking about masakari, then we have loads of ideas :-) | 07:14 |
| yoctozepto | just not enough hands/time to deliver | 07:14 |
| yoctozepto | #info Virtual OpenStack Infrastructure Summit is right the next week: https://www.openstack.org/summit/2020/ | 07:14 |
| yoctozepto | you can still register as far as I know | 07:14 |
| yoctozepto | it's a week-long online event | 07:15 |
| yoctozepto | you might find something interesting to you | 07:15 |
| jopdorp | yeah | 07:15 |
| yoctozepto | #info Masakari Wallaby vPTG planned (in just two weeks! next masakari meeting cancelled): https://etherpad.opendev.org/p/masakari-wallaby-vptg | 07:16 |
| yoctozepto | this is *the* most important announcement today | 07:17 |
| jopdorp | I'll be there | 07:17 |
| suzhengwei | me too | 07:17 |
| yoctozepto | \o/ | 07:18 |
| jopdorp | \m/ | 07:18 |
| yoctozepto | please add/review items on that page even before the sessions start | 07:19 |
| yoctozepto | it is more productive this way | 07:19 |
| yoctozepto | I did mine, I saw suzhengwei did as well | 07:20 |
| jopdorp | ok, I'll think about it | 07:21 |
| yoctozepto | thanks | 07:22 |
| yoctozepto | #topic Review action items from the last meeting | 07:22 |
| *** openstack changes topic to "Review action items from the last meeting (Meeting topic: masakari)" | 07:22 | |
| yoctozepto | let me find it | 07:22 |
| yoctozepto | oh, there were none | 07:23 |
| yoctozepto | so 100% success | 07:23 |
| yoctozepto | (beat it) | 07:23 |
| jopdorp | \m/ | 07:23 |
| yoctozepto | #CI status | 07:23 |
| yoctozepto | #topic CI status | 07:23 |
| *** openstack changes topic to "CI status (Meeting topic: masakari)" | 07:23 | |
| yoctozepto | not much happening; the last runs were green happy | 07:24 |
| yoctozepto | so GREEN | 07:24 |
| yoctozepto | #topic Backports pending reviews | 07:24 |
| *** openstack changes topic to "Backports pending reviews (Meeting topic: masakari)" | 07:24 | |
| yoctozepto | not only backports, but all stable pending changes: | 07:25 |
| yoctozepto | #link https://review.opendev.org/#/q/(project:openstack/masakari+OR+project:openstack/masakari-monitors+OR+project:openstack/python-masakariclient+OR+project:openstack/masakari-dashboard)+status:open+-branch:master | 07:25 |
| yoctozepto | ^ please review the above, they are one vote away from merging (I did my part!) | 07:25 |
| jopdorp | will do | 07:26 |
| yoctozepto | #topic Critical Bugs and Patches | 07:28 |
| *** openstack changes topic to "Critical Bugs and Patches (Meeting topic: masakari)" | 07:28 | |
| yoctozepto | and there are none - I will remove this point from the agenda next time if I can't hear any objections - I believe these can still be discussed during the open discussion (if they ever happen) | 07:29 |
| jopdorp | ok | 07:30 |
| suzhengwei | ok | 07:31 |
| yoctozepto | #topic Release planning | 07:35 |
| *** openstack changes topic to "Release planning (Meeting topic: masakari)" | 07:35 | |
| yoctozepto | well, it has been planned; for wallaby please remember about participating in the ptg :-) | 07:35 |
| suzhengwei | yoctozepto: Do we need reno for bugfix in V? | 07:40 |
| suzhengwei | There is no releasenote for bugfix patch. | 07:40 |
| yoctozepto | suzhengwei: if it went like this (e.g. this is backport) already, then we don't need it | 07:43 |
| yoctozepto | for all new ones we should strive to get renos because they increase the visibility of all (and others) efforts | 07:43 |
| yoctozepto | and show that the project is actively maintained | 07:43 |
| yoctozepto | #topic Open discussion | 07:44 |
| *** openstack changes topic to "Open discussion (Meeting topic: masakari)" | 07:44 | |
| yoctozepto | (I missed to switch the topic) | 07:44 |
| yoctozepto | please go on with any things you want | 07:44 |
| jopdorp | i was wondering what a ptg looks like | 07:45 |
| jopdorp | is like working together in a virtual office on the project for a couple of days | 07:45 |
| jopdorp | ? | 07:45 |
| jopdorp | like a hackathon or something? | 07:45 |
| suzhengwei | More like a project video meeting. | 07:47 |
| jopdorp | another thing is, we are looking into how to decrease failover times, to minimize downtime for our edge locations when they lose power | 07:47 |
| jopdorp | suzhengwei: okay | 07:47 |
| jopdorp | I'd be up for tha on a more regular basis too | 07:48 |
| suzhengwei | That is a good point which I study recently too. | 07:49 |
| jopdorp | it's a more direct way of communicating which is good for efficiency and motivation, and getting to know the team better | 07:50 |
| yoctozepto | suzhengwei, jopdorp: we can do video meetings regularly, yes; we do it with kolla as well; need to schedule right time though | 07:51 |
| jopdorp | both of you use kolla too? | 07:51 |
| jopdorp | maybe we could change the default config in kolla to make failover times faster | 07:52 |
| yoctozepto | jopdorp: I develop kolla but kolla should be discussed in #openstack-kolla ;-) | 07:52 |
| jopdorp | I was looking at this one https://review.opendev.org/#/c/732477/3/specs/victoria/approved/promotion-for-large-scale-hosts-failure.rst | 07:52 |
| jopdorp | I think it does make sense to prioritize instances | 07:53 |
| yoctozepto | yeah, suzhengwei has some nice ideas in specs already | 07:53 |
| jopdorp | or example if a client has a kubernetes cluster, prioritize failover for master over workers | 07:53 |
| jopdorp | what about adding hosts automtically back to pacemaker when they come back up? | 07:54 |
| jopdorp | I've been working with a test environment which is very unstable, to test out failover approach | 07:55 |
| jopdorp | and had to remove and re add the host from pacemaker every time we test a failover | 07:56 |
| jopdorp | also had to reenable it in nova and set on maintenance back to false | 07:57 |
| jopdorp | also I'm thinking about automatically moving instances back to the failed hosts they came from after a set period of time | 07:58 |
| yoctozepto | jopdorp: well, it's a protection measure against flops | 07:58 |
| yoctozepto | flops are worse | 07:58 |
| jopdorp | what is a flop? | 07:58 |
| yoctozepto | jopdorp: flaps* (/me broken) | 07:59 |
| jopdorp | haha | 07:59 |
| jopdorp | what is a flap? | 07:59 |
| yoctozepto | it is a situation where the instability causes the node to be repeated up/down | 07:59 |
| jopdorp | yeah | 07:59 |
| yoctozepto | causing the environment to recalculate each time | 07:59 |
| jopdorp | maybe the set period of time can fesolve that | 08:00 |
| yoctozepto | and wasting more time on constant moves rather than keeping it simple | 08:00 |
| jopdorp | resolve | 08:00 |
| jopdorp | wait 48 hours for example | 08:00 |
| yoctozepto | operator should really monitor the infrastructure and act accordingly | 08:00 |
| jopdorp | the main goal for me would be to have instances move back to the failed nodes after some time | 08:00 |
| yoctozepto | well, at least that's the common consensus | 08:00 |
| yoctozepto | (and it's more about pacemaker itself than masakari) | 08:00 |
| yoctozepto | (we can also consider consul for masakari) | 08:00 |
| jopdorp | because in our infrastructure failure is expected on leaf(edge) nodes | 08:00 |
| yoctozepto | but we are out of time today | 08:01 |
| jopdorp | which run at locations outside of regular datacenters | 08:01 |
| yoctozepto | jopdorp: add these points to the ptg discussion please | 08:01 |
| yoctozepto | thank you for coming, jopdorp, suzhengwei | 08:01 |
| jopdorp | will do! | 08:01 |
| jopdorp | thanks | 08:01 |
| yoctozepto | #endmeeting | 08:01 |
| *** openstack changes topic to "#openstack-masakari" | 08:01 | |
| openstack | Meeting ended Tue Oct 13 08:01:34 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 08:01 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/masakari/2020/masakari.2020-10-13-07.01.html | 08:01 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/masakari/2020/masakari.2020-10-13-07.01.txt | 08:01 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/masakari/2020/masakari.2020-10-13-07.01.log.html | 08:01 |
| *** priteau has joined #openstack-masakari | 08:34 | |
| *** suzhengwei has quit IRC | 08:53 | |
| *** vishalmanchanda has quit IRC | 09:44 | |
| *** vishalmanchanda has joined #openstack-masakari | 10:25 | |
| *** priteau has quit IRC | 10:30 | |
| *** devfaz has quit IRC | 12:11 | |
| *** openstackgerrit has quit IRC | 13:17 | |
| *** priteau has joined #openstack-masakari | 16:40 | |
| *** devfaz has joined #openstack-masakari | 17:35 | |
| *** priteau has quit IRC | 17:53 | |
| *** priteau has joined #openstack-masakari | 17:54 | |
| *** priteau has quit IRC | 18:01 | |
| *** vishalmanchanda has quit IRC | 22:34 | |
| *** watersj has joined #openstack-masakari | 23:20 | |
| *** samP has quit IRC | 23:21 | |
| *** samP has joined #openstack-masakari | 23:26 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!