| opendevreview | Joan Gilabert proposed openstack/watcher master: Handle missing dst_pool parameter in zone_migration https://review.opendev.org/c/openstack/watcher/+/950149 | 07:19 |
|---|---|---|
| opendevreview | David proposed openstack/watcher-tempest-plugin master: Update parameters on test_execute_workload_stabilization_strategy https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/950969 | 07:34 |
| opendevreview | David proposed openstack/watcher-tempest-plugin master: Update tests for host maintenance strategy https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/950851 | 07:44 |
| opendevreview | David proposed openstack/watcher-tempest-plugin master: Update tests for host maintenance strategy. https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/950851 | 07:54 |
| opendevreview | Alfredo Moralejo proposed openstack/watcher-tempest-plugin master: Enforce compute host in create_one_instance_per_host https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/950389 | 07:56 |
| opendevreview | Joan Gilabert proposed openstack/watcher master: Handle missing dst_pool parameter in zone_migration https://review.opendev.org/c/openstack/watcher/+/950149 | 07:57 |
| opendevreview | David proposed openstack/watcher-tempest-plugin master: Update tests for host maintenance strategy. https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/950851 | 08:07 |
| opendevreview | Takashi Kajinami proposed openstack/watcher-tempest-plugin master: Remove stable/2023.2 job https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/951241 | 08:30 |
| opendevreview | chandan kumar proposed openstack/watcher master: [WIP] host maintenance restore backup node https://review.opendev.org/c/openstack/watcher/+/951245 | 09:22 |
| opendevreview | Alfredo Moralejo proposed openstack/watcher-tempest-plugin master: Enforce compute host in create_one_instance_per_host https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/950389 | 09:30 |
| opendevreview | David proposed openstack/watcher-tempest-plugin master: Change timeframe of fake metrics uploaded to gnocchi. https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/950969 | 09:31 |
| opendevreview | David proposed openstack/watcher-tempest-plugin master: Change timeframe of fake metrics uploaded to gnocchi. https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/950969 | 09:32 |
| opendevreview | David proposed openstack/watcher-tempest-plugin master: Add tests for workload_balance with injected data https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/949722 | 09:33 |
| opendevreview | chandan kumar proposed openstack/watcher master: [WIP] host maintenance restore backup node https://review.opendev.org/c/openstack/watcher/+/951245 | 11:12 |
| rlandy | reminder - watcher IRC meeting here in ~10 mins | 11:51 |
| rlandy | pls add topics to https://etherpad.opendev.org/p/openstack-watcher-irc-meeting | 11:51 |
| rlandy | #startmeeting Watcher Meeting - 29 may 2025 | 12:01 |
| opendevmeet | Meeting started Thu May 29 12:01:26 2025 UTC and is due to finish in 60 minutes. The chair is rlandy. Information about MeetBot at http://wiki.debian.org/MeetBot. | 12:01 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 12:01 |
| opendevmeet | The meeting name has been set to 'watcher_meeting___29_may_2025' | 12:01 |
| rlandy | hi all .. who's around? | 12:01 |
| dviroel | o/ | 12:01 |
| chandankumar | o/ | 12:01 |
| jgilaber | o/ | 12:02 |
| amoralej_ | o/ | 12:02 |
| rlandy | Courtesy ping: sean-k-mooney | 12:02 |
| sean-k-mooney | o/ | 12:02 |
| mtembo | o/ | 12:02 |
| rlandy | ok - let's get started | 12:02 |
| sean-k-mooney | that working already :) | 12:02 |
| rlandy | Topics for today are on: | 12:03 |
| rlandy | #link https://etherpad.opendev.org/p/openstack-watcher-irc-meeting#L58 | 12:03 |
| rlandy | I start :) | 12:03 |
| rlandy | #topic: (rlandy) Strategies marked [POC] "This is a proof of concept that is not meant to be used in production" | 12:03 |
| rlandy | Two strategies that have active work on them are still marked POC in the doc: | 12:04 |
| rlandy | #link https://docs.openstack.org/watcher/latest/strategies/host_maintenance.html | 12:04 |
| rlandy | #link: https://docs.openstack.org/watcher/latest/strategies/workload_balance.html | 12:04 |
| rlandy | examples of strategies that are NOT POC are included in the notes ... | 12:04 |
| rlandy | #link https://docs.openstack.org/watcher/latest/strategies/zone_migration.html | 12:05 |
| rlandy | not POC | 12:05 |
| rlandy | so ... | 12:05 |
| rlandy | do we want to keep that label POC in the documentation if we have fully updated/tested/doc'ed a strategy? | 12:05 |
| rlandy | the doc for both host maintenance and balance is being worked on for updates | 12:06 |
| rlandy | and there are open bugs | 12:06 |
| sean-k-mooney | thats a good question | 12:06 |
| sean-k-mooney | so i want to move away form t he POC termonlogy in general and adopt experimental | 12:07 |
| sean-k-mooney | so i woudl prefer to update the docs to do that and again we need to loop back to the idea of adding a supprot level matix in the docs too | 12:07 |
| chandankumar | +1 to experimental | 12:07 |
| sean-k-mooney | i think we can remvoe the code level comment and perhaps the doc comment | 12:07 |
| sean-k-mooney | im not sure if we shoudl graduate it to fully supprot or not yet however | 12:08 |
| chandankumar | How a strategy graduate from experimental/poc to supported in upstream? | 12:08 |
| rlandy | what do we want to label zone migration as? | 12:08 |
| sean-k-mooney | both are good questions. | 12:09 |
| amoralej_ | I'd prefer a different term that supported for upstream, but i agree on the idea | 12:09 |
| sean-k-mooney | in most project we do not merge the code until we think its ready for production | 12:09 |
| *** amoralej_ is now known as amoralej | 12:09 | |
| sean-k-mooney | so we would not have merge thse poc impleation at all | 12:09 |
| sean-k-mooney | but since they exist | 12:09 |
| sean-k-mooney | to me its wether we think its mature enogh to run in production | 12:09 |
| sean-k-mooney | and are we happy that we can continue to test and maintain it going forward | 12:10 |
| chandankumar | since we have fixed the strategies, now it is working with ample test coverage but we have not data on usage Do we still want to mark them experimental? | 12:10 |
| sean-k-mooney | if we are happy with the level of testing and docs and the stragey is fucntioanl we can remvoe the experimental lable | 12:10 |
| jgilaber | we discussed at PTG to have an overview/status of the project, should the strategies state be documented there? | 12:10 |
| sean-k-mooney | yes we agreed to create a matrics in the docs that woudl docuemtn the testing and supprot level of all stragies | 12:11 |
| sean-k-mooney | like this https://docs.openstack.org/nova/latest/user/support-matrix.html | 12:11 |
| rlandy | so something like ... | 12:12 |
| rlandy | on the top level strategies page: | 12:12 |
| rlandy | strategy: test level experimental | 12:12 |
| rlandy | and we remove all references of support level in other places | 12:13 |
| rlandy | and we control it only there | 12:13 |
| chandankumar | +1 | 12:13 |
| sean-k-mooney | yes i think so so here https://docs.openstack.org/watcher/latest/strategies/ | 12:13 |
| sean-k-mooney | when we move something ebtween levels i think we shoud create a relese note for that as well | 12:13 |
| rlandy | as to which strategy gets what level, we can get feedback and agreement on the review | 12:14 |
| rlandy | +1 | 12:14 |
| sean-k-mooney | i.e. when it goes form experiemtal to production ready we have a short relese not for that | 12:14 |
| amoralej | +1 | 12:14 |
| sean-k-mooney | rlandy: yep we can do that in the review | 12:14 |
| rlandy | ok - thank you all for the discussion | 12:14 |
| rlandy | #action rlandy to put up a review with a table (removed from other places in the doc) for review | 12:15 |
| rlandy | ie: of strategies and test/experimental level | 12:15 |
| chandankumar | I have one more question | 12:15 |
| rlandy | go ahead | 12:15 |
| chandankumar | many strategies are not triggered via horizon UI | 12:15 |
| rlandy | good point | 12:16 |
| chandankumar | Do we want to document that also in each strategy doc? | 12:16 |
| rlandy | those requiring params | 12:16 |
| rlandy | yes! | 12:16 |
| rlandy | in the table? | 12:16 |
| jgilaber | +1, we can have an extra column with UI support | 12:16 |
| chandankumar | +1 for extra column | 12:17 |
| sean-k-mooney | we could | 12:17 |
| chandankumar | Do we want to put it in main strategy page? | 12:17 |
| mtembo | +1 extra column | 12:17 |
| sean-k-mooney | the columns i was thinking of are as follws | 12:17 |
| sean-k-mooney | name, testing level, supprot level(supproted, experimental, deprecation, removed) | 12:18 |
| sean-k-mooney | we can add horizon supprot | 12:18 |
| rlandy | removed? | 12:18 |
| sean-k-mooney | or we can encode that in a similar table in teh watcher-dashbaord repo | 12:18 |
| sean-k-mooney | and cross linked | 12:18 |
| sean-k-mooney | rlandy: so sometiems we docuemnt the release in which a feature is remvoed | 12:19 |
| sean-k-mooney | im not sure if we need that or not | 12:19 |
| sean-k-mooney | but that more for upgrades | 12:19 |
| sean-k-mooney | when you are upgrding to a new release you can review the matics to understand if all the stragies you use are still suprpoted. this would be captrued in an upgrades and deprecation release note as well | 12:20 |
| sean-k-mooney | so its not required | 12:20 |
| sean-k-mooney | we can defer the detail i think to the review | 12:20 |
| rlandy | agreed - let's start with the review and continue the conversation there. thank you all for your input | 12:20 |
| chandankumar | rlandy: thank you for bringing it! | 12:20 |
| rlandy | anything else on this topic? | 12:21 |
| rlandy | moving on ... | 12:21 |
| rlandy | #topic (dviroel) Eventlet Removal | 12:21 |
| dviroel | o/ | 12:22 |
| rlandy | dviroel, do you want to take this? | 12:22 |
| dviroel | yep, first, wrt to the email sent last week, the call for MAAS maintainers, no answers so far | 12:22 |
| rlandy | now what do we do? | 12:22 |
| dviroel | so I am planning to proceed with a patch to mark both MAAS and Ironic as experimental features, since they lack support, testing and docs | 12:22 |
| dviroel | the question is | 12:23 |
| dviroel | is enough just to update the docs (the plugins part) | 12:23 |
| dviroel | or should we also consider adding some log messages? | 12:23 |
| sean-k-mooney | we should likely add a log message and release note + a doc | 12:24 |
| sean-k-mooney | the log message shoudl only log on startup IMO | 12:25 |
| dviroel | ack, yeah, log once | 12:25 |
| sean-k-mooney | neutron did that when they made linux bridge experimental | 12:25 |
| dviroel | right, so I will proceed with a patch for that | 12:25 |
| dviroel | tks for the inputs | 12:26 |
| sean-k-mooney | just for consitency we likely shoudl havea support/testing matrics for datasouces and integrations as well | 12:26 |
| sean-k-mooney | looking at https://docs.openstack.org/watcher/latest/admin/index.html | 12:26 |
| sean-k-mooney | there is a high level page for datasouces https://docs.openstack.org/watcher/latest/datasources/index.html so that is simple | 12:26 |
| sean-k-mooney | but im not seeing anythin for mass/ironic there | 12:26 |
| sean-k-mooney | we might want to add an "services" section to the doc | 12:26 |
| sean-k-mooney | wehre we list integration with nova cinder ironic mass ectra | 12:27 |
| sean-k-mooney | i.e. the external services that watcher can interact with | 12:27 |
| sean-k-mooney | there we can follow the same patteern as we jsut dicssed for rlandy topic | 12:28 |
| dviroel | yep, i found mention to ironic only on change_node_power_state action doc | 12:28 |
| sean-k-mooney | ya so the name of that is a littel hard "services" works but it could also be "integrations" or similar | 12:29 |
| sean-k-mooney | maas makes it a littel werid because its not part of openstack | 12:29 |
| sean-k-mooney | the complete lack of docs about ironic and mass is part of why they are experimental so we probly shoudl have a "docs level" column on these as well | 12:31 |
| dviroel | yeah | 12:31 |
| dviroel | any other ideas? | 12:32 |
| rlandy | sounds right for now | 12:32 |
| dviroel | i will take a look on docs and see what we can do | 12:32 |
| dviroel | and we can chat more | 12:32 |
| sean-k-mooney | dviroel: back to your question i think we can proceed with marking them as experimental and i would suggest startign a patch to do that and we can revisit next week. | 12:32 |
| dviroel | and we can chat more | 12:32 |
| rlandy | dviroel: thank you for raising this ... anything more on the topic? | 12:33 |
| dviroel | next thing is about changes in BackgroundSchedulerService and Watcher Services | 12:33 |
| dviroel | still in progress but, the good news is that the patch with the new threading backend for oslo.service merged recently | 12:33 |
| dviroel | thread in ML: | 12:33 |
| dviroel | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/33EPOBRCGEKYUVDPFUZJZ2HENGDXVRE4/ | 12:33 |
| dviroel | i have a open pacth for initial evenlet move, but I still need to updated it from comments | 12:34 |
| dviroel | and that't what I have for this week | 12:35 |
| rlandy | ok- thank you - any more comments on anything dviroel raised? | 12:36 |
| dviroel | no, thanks | 12:36 |
| rlandy | #action dviroel to look at doc additions | 12:36 |
| rlandy | moving on ... | 12:37 |
| rlandy | #topic (sean): just an fyi we are going to use https://etherpad.opendev.org/p/grian-ui-status to track/drive developemt of the grian-ui plugin | 12:37 |
| rlandy | sean-k-mooney: ^^ would you like to take that? | 12:37 |
| sean-k-mooney | am the short verson is as follows | 12:38 |
| sean-k-mooney | durign the ptg we agreed with the telemery team to create a new horizon plugin for tenant metrics vizualisation | 12:38 |
| sean-k-mooney | over the last 2-3 weeks we have created the repo and started bootstraping it | 12:39 |
| sean-k-mooney | currently we are in the forming state choosing wehre we will host meeting, how we will track work ectra | 12:39 |
| sean-k-mooney | we have decied to use that ether pad to drive that for now simialr to howe we are suign the etherpad for this meeting | 12:39 |
| sean-k-mooney | we likely will use #openstack-telemetry to dicussion this topic going forward | 12:40 |
| rlandy | +1 do you need any additional support/resources? | 12:40 |
| sean-k-mooney | thats about it. for now no, we are hopign to have some intiall demos around m2 perhaps a littel later | 12:41 |
| sean-k-mooney | we will likely starte with create 2 example staic dashbaord 1 an admin only dashboard | 12:41 |
| sean-k-mooney | and a seocn that is tenatn facing to prove out both types | 12:42 |
| sean-k-mooney | those will evlove over time | 12:42 |
| sean-k-mooney | btu once we get to that initall pont we will likely ask for some user feedback | 12:42 |
| sean-k-mooney | i think that is where the wider team can help | 12:42 |
| sean-k-mooney | if you want to be more involed before that that fine too | 12:43 |
| rlandy | thank you sean-k-mooney | 12:43 |
| sean-k-mooney | anyway i think thats it unless there are any other questions? | 12:43 |
| amoralej | let us known where you have something that we can install and test | 12:44 |
| amoralej | i'd like to check the dashboards once ready | 12:44 |
| chandankumar | Do we need anything from devstack-plugin-prometheus for grian-ui? | 12:45 |
| sean-k-mooney | yep we will | 12:45 |
| sean-k-mooney | chandankumar: not currently | 12:45 |
| chandankumar | ok | 12:45 |
| sean-k-mooney | i have a basic devstack job ready | 12:45 |
| sean-k-mooney | it currently fails becasue we dont have a functial plugin yet | 12:45 |
| sean-k-mooney | so the install fails as a result | 12:45 |
| sean-k-mooney | but i have focused sofar on setign up the testing and jobs for the repo | 12:46 |
| sean-k-mooney | so now that that is mostly done we can start on buildign out actual fucntionaliy | 12:46 |
| rlandy | ok - anything more here? | 12:47 |
| chandankumar | thank you sean-k-mooney for sharing the progress here! | 12:48 |
| rlandy | moving on to give the other topics some time ... | 12:48 |
| rlandy | #topic: (jgilaber) Updated zone migration strategy etherpad with what I think are the relevant use cases | 12:48 |
| rlandy | #link https://etherpad.opendev.org/p/zone_migration_volume_migration_parameters | 12:49 |
| rlandy | jgilaber: ^^ do you want to take this? | 12:49 |
| jgilaber | yep | 12:49 |
| jgilaber | I have added a section on the same etherpad that I brought last week | 12:49 |
| jgilaber | with the few use cases for volume migration that I think the zone migration can support | 12:49 |
| jgilaber | with the help of amoralej | 12:50 |
| jgilaber | we came up with 3 scenarios | 12:50 |
| jgilaber | 1 that should work currently, and 2 other that will require some changes to the volume migration action | 12:50 |
| jgilaber | I also have a small sections with questions that I think we'll need to ask to cinder experts | 12:51 |
| jgilaber | let me know if you see anything that you think is wrong or is not clear | 12:51 |
| sean-k-mooney | what is the status of the vm migration part of this. is that still pending or did we merge the first two patches | 12:52 |
| jgilaber | vm migration seems to work well | 12:52 |
| jgilaber | we merged the path for the dst_node that I think is the only bug that affects that part | 12:53 |
| sean-k-mooney | i think its good to continue working on the cinder part in followups but we can likely merge the intall partcial fix if we ahve nto already done so | 12:53 |
| sean-k-mooney | ok good | 12:53 |
| sean-k-mooney | i jsut didnt recall if that part was merged or not | 12:53 |
| jgilaber | I've also changed the storage follow-up to that patch https://review.opendev.org/c/openstack/watcher/+/950149 | 12:54 |
| jgilaber | after the use cases review, I don't think it's great to have the dst_pool parameter mandatory | 12:54 |
| sean-k-mooney | so the 3 types fo volume migratoin are retype, migration between host in a pool and migration between backend host in different pools correct? | 12:54 |
| sean-k-mooney | jgilaber: yes i agree i talks to gmaan about this a litttle offline | 12:55 |
| jgilaber | I think that's right sean-k-mooney | 12:55 |
| sean-k-mooney | i think the way forward is to remvoe the required fields form the schema | 12:55 |
| sean-k-mooney | and move the validation to the api where we can encode the logic of which combintions of optiosn are valid more cleanly | 12:55 |
| sean-k-mooney | for example for retry neither the souce or dest pool shoudl eb requried as far as i am aware | 12:56 |
| sean-k-mooney | *retype | 12:56 |
| amoralej | wrt the cases, the one that should work currently, which is the retype (dst_pool empty) has some known bugs that we need to fix. There is a list at the end of the etherpad | 12:56 |
| jgilaber | src_pool is required currently as it is the only way it has to filter which volumes to migrate | 12:57 |
| jgilaber | that is a bug, because src_type is ignored | 12:57 |
| sean-k-mooney | hum ok | 12:57 |
| sean-k-mooney | that is perhaps unfortunate. it would be nice in the case wehre you are moving vms to be able to retype the volumes assocated with those vms and only those volumes | 12:58 |
| jgilaber | btw there is also a list on known bugs at the bottom of the etherpad | 12:58 |
| jgilaber | definitely we should fix that, we should be able to work with just the src_type | 12:59 |
| sean-k-mooney | i.e. please mvoe the vms on host A in az 1 to AZ2 and retype there voluems form mass_storage_az1 to mass_storage_az2 | 12:59 |
| amoralej | sean-k-mooney, actually there is the opossite, migrate or retype the volumes in a pool and the vms with volumes attached to them | 13:00 |
| amoralej | that exists already | 13:00 |
| amoralej | (with certain bugs) | 13:01 |
| sean-k-mooney | i htink oen of the bugs that is more impoant to fix is the lack of documenation | 13:01 |
| amoralej | but not the "migrate the VMs and their attached volumes" | 13:01 |
| sean-k-mooney | for such a complex stagy i think we will need to build out a set of usecase driven example | 13:02 |
| amoralej | yep | 13:02 |
| rlandy | (we are overtime but we can continue this discussion - will move the rest of the topics to next week) | 13:02 |
| jgilaber | +1, that's what we set out to do in the etherpad | 13:02 |
| sean-k-mooney | ack | 13:02 |
| jgilaber | those use cases can then serve as the backbone of the documentation | 13:02 |
| sean-k-mooney | ack | 13:03 |
| sean-k-mooney | ill try and fined time to review that with more detail over the next week | 13:03 |
| sean-k-mooney | thanks for writing this up | 13:03 |
| jgilaber | thanks! | 13:03 |
| rlandy | jgilaber: anything more on this topic? | 13:04 |
| jgilaber | nop, that is all from me | 13:04 |
| rlandy | ok - thank you | 13:04 |
| rlandy | I will move the bug triage to next week or we can take that on line ... | 13:04 |
| rlandy | pls note: | 13:04 |
| rlandy | Request for review: https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/949557 | 13:05 |
| rlandy | chandankumar: ^^ any comments on that for the reviewers? | 13:05 |
| chandankumar | It contains improvements from previous host maintenance tempest plugin patches | 13:05 |
| chandankumar | Please have a look, thank you! | 13:05 |
| rlandy | thank you chandankumar | 13:06 |
| rlandy | moving on ... | 13:06 |
| rlandy | volunteers to chair next week's meeting? | 13:06 |
| chandankumar | count me in for next week | 13:06 |
| rlandy | thank you chandankumar | 13:07 |
| rlandy | thanks all for attending and the good discussions | 13:07 |
| chandankumar | thank you rlandy ! | 13:07 |
| rlandy | pls take any topics we ran out of time for on to the channel or next week's agenda | 13:08 |
| rlandy | #endmeeting | 13:08 |
| opendevmeet | Meeting ended Thu May 29 13:08:20 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:08 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/watcher_meeting___29_may_2025/2025/watcher_meeting___29_may_2025.2025-05-29-12.01.html | 13:08 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/watcher_meeting___29_may_2025/2025/watcher_meeting___29_may_2025.2025-05-29-12.01.txt | 13:08 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/watcher_meeting___29_may_2025/2025/watcher_meeting___29_may_2025.2025-05-29-12.01.log.html | 13:08 |
| opendevreview | Alfredo Moralejo proposed openstack/watcher-tempest-plugin master: Enforce compute host in create_one_instance_per_host https://review.opendev.org/c/openstack/watcher-tempest-plugin/+/950389 | 16:28 |
| opendevreview | Joan Gilabert proposed openstack/watcher master: Enable storage model collector by default https://review.opendev.org/c/openstack/watcher/+/951323 | 16:45 |
| opendevreview | Ronelle Landy proposed openstack/watcher master: Update Workload Balance strategy documentation https://review.opendev.org/c/openstack/watcher/+/951025 | 19:04 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!