From: Luis Chamberlain <mcgrof@kernel.org>
To: Chuck Lever <cel@kernel.org>, Daniel Gomez <da.gomez@kruces.com>,
kdevops@lists.linux.dev
Cc: Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH 4/5] ai milvus: add monitoring support
Date: Thu, 4 Sep 2025 02:13:20 -0700 [thread overview]
Message-ID: <20250904091322.2499058-5-mcgrof@kernel.org> (raw)
In-Reply-To: <20250904091322.2499058-1-mcgrof@kernel.org>
Add monitoring framework integration to the AI Milvus workflow to
track performance during vector database benchmarks.
Generated-by: Claude AI
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
playbooks/ai_benchmark.yml | 14 ++++++++++++++
playbooks/roles/milvus/tasks/install_docker.yml | 2 ++
.../roles/monitoring/tasks/monitor_collect.yml | 2 ++
workflows/ai/Makefile | 5 +++++
4 files changed, 23 insertions(+)
diff --git a/playbooks/ai_benchmark.yml b/playbooks/ai_benchmark.yml
index 85fc117c8ba7..7e681328e2bc 100644
--- a/playbooks/ai_benchmark.yml
+++ b/playbooks/ai_benchmark.yml
@@ -3,6 +3,20 @@
hosts: ai
vars:
ai_vector_db_milvus_benchmark_enable: true
+ tasks:
+ # Start monitoring services before running benchmarks
+ - ansible.builtin.import_tasks: roles/monitoring/tasks/monitor_run.yml
+ when:
+ - enable_monitoring|default(false)|bool
+ tags: ["monitoring", "monitor_run"]
+
roles:
- role: milvus
tags: ['ai', 'vector_db', 'milvus', 'benchmark']
+
+ post_tasks:
+ # Collect monitoring data after benchmarks complete
+ - ansible.builtin.import_tasks: roles/monitoring/tasks/monitor_collect.yml
+ when:
+ - enable_monitoring|default(false)|bool
+ tags: ["monitoring", "monitor_collect"]
diff --git a/playbooks/roles/milvus/tasks/install_docker.yml b/playbooks/roles/milvus/tasks/install_docker.yml
index e1e1d911aee0..8c3a80430cd7 100644
--- a/playbooks/roles/milvus/tasks/install_docker.yml
+++ b/playbooks/roles/milvus/tasks/install_docker.yml
@@ -14,6 +14,7 @@
- python3-pip
- python3-setuptools
- python3-packaging
+ - python3-bpfcc
state: present
become: true
when:
@@ -35,6 +36,7 @@
- docker-compose
- python3-pip
- python3-setuptools
+ - python3-bcc
state: present
become: true
when:
diff --git a/playbooks/roles/monitoring/tasks/monitor_collect.yml b/playbooks/roles/monitoring/tasks/monitor_collect.yml
index 9662f827301f..83193ed459b6 100644
--- a/playbooks/roles/monitoring/tasks/monitor_collect.yml
+++ b/playbooks/roles/monitoring/tasks/monitor_collect.yml
@@ -119,6 +119,8 @@
{{ topdir_path }}/workflows/mmtests/results/monitoring
{%- elif kdevops_workflow_enable_sysbench|default(false)|bool -%}
{{ topdir_path }}/workflows/sysbench/results/monitoring
+ {%- elif kdevops_workflow_enable_ai|default(false)|bool -%}
+ {{ topdir_path }}/workflows/ai/results/monitoring
{%- else -%}
{{ topdir_path }}/results/monitoring
{%- endif -%}
diff --git a/workflows/ai/Makefile b/workflows/ai/Makefile
index 7e9b8af236b7..2ffa64c727fa 100644
--- a/workflows/ai/Makefile
+++ b/workflows/ai/Makefile
@@ -101,6 +101,11 @@ ai-results-baseline:
ai-results-dev:
$(Q)$(MAKE) ai-results HOSTS="dev"
+monitor-results: $(KDEVOPS_EXTRA_VARS)
+ $(Q)ansible-playbook $(ANSIBLE_VERBOSE) \
+ playbooks/monitor-results.yml \
+ --extra-vars=@./extra_vars.yaml
+
ai-setup:
$(Q)ansible-playbook $(ANSIBLE_VERBOSE) \
-i hosts \
--
2.45.2
next prev parent reply other threads:[~2025-09-04 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 9:13 [PATCH 0/5] add memory fragmentation automation testing Luis Chamberlain
2025-09-04 9:13 ` [PATCH 1/5] monitoring: add memory fragmentation eBPF monitoring support Luis Chamberlain
2025-09-04 9:13 ` [PATCH 2/5] mmtests: add monitoring framework integration Luis Chamberlain
2025-09-04 9:13 ` [PATCH 3/5] sysbench: " Luis Chamberlain
2025-09-04 9:13 ` Luis Chamberlain [this message]
2025-09-04 9:13 ` [PATCH 5/5] minio: add monitoring support Luis Chamberlain
2025-09-19 3:49 ` [PATCH 0/5] add memory fragmentation automation testing Luis Chamberlain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250904091322.2499058-5-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=cel@kernel.org \
--cc=da.gomez@kruces.com \
--cc=kdevops@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox