remove old analyst
This commit is contained in:
parent
847f2f5b8a
commit
28a5cc9448
3 changed files with 43 additions and 6 deletions
|
|
@ -26,6 +26,11 @@ spec:
|
|||
- name: ollama-sidecar
|
||||
image: ollama/ollama:latest
|
||||
restartPolicy: Always # This is the magic
|
||||
env:
|
||||
- name: OLLAMA_DEBUG
|
||||
value: "2"
|
||||
- name: OLLAMA_LOG_LEVEL
|
||||
value: "DEBUG"
|
||||
ports:
|
||||
- containerPort: 11434
|
||||
volumeMounts:
|
||||
|
|
@ -34,11 +39,10 @@ spec:
|
|||
resources:
|
||||
limits:
|
||||
nvidia.com/gpu: 1
|
||||
|
||||
|
||||
containers:
|
||||
- name: analyst
|
||||
image: siriussec/summarizer:latest
|
||||
image: siriussec/summarizerlocal:1.1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: DB_PASSWORD
|
||||
valueFrom:
|
||||
|
|
@ -47,7 +51,7 @@ spec:
|
|||
key: password
|
||||
envFrom:
|
||||
- configMapRef:
|
||||
name: news-app-config
|
||||
name: gemma-config
|
||||
# Make sure your summarizer script talks to http://localhost:11434
|
||||
# (or http://127.0.0.1:11434)
|
||||
|
||||
|
|
|
|||
33
apps/base/customer1/news_bot/gemma-configmap.yaml
Normal file
33
apps/base/customer1/news_bot/gemma-configmap.yaml
Normal file
|
|
@ -0,0 +1,33 @@
|
|||
apiVersion: v1
|
||||
kind: ConfigMap
|
||||
metadata:
|
||||
name: gemma-config
|
||||
namespace: customer1
|
||||
data:
|
||||
DB_HOST: "customer1-pgdb-rw"
|
||||
DB_NAME: "news_app_db"
|
||||
DB_USER: "news_app"
|
||||
DB_PORT: "5432"
|
||||
LLM_URL: "http://localhost:11434"
|
||||
MODEL_NAME: "gemma2"
|
||||
SUMMARY_PROMPT: |
|
||||
You are an expert news analyst working for DARPA. Your task is to deliver thorough, insightful analysis of the provided news articles.
|
||||
|
||||
ARTICLES:
|
||||
{data}
|
||||
|
||||
Instructions:
|
||||
- Identify the 3–6 most impactful events or developments (prioritize geopolitical, technological, military, economic, or security implications).
|
||||
- For each impactful event: Write a detailed 4–6 sentence summary, including key facts, context, potential consequences, and why it matters strategically.
|
||||
- For all remaining/lesser articles: Write 2–4 cohesive paragraphs synthesizing them into broader themes or trends (do NOT list them individually unless critical).
|
||||
- Aim for a total output length of 400–800 words. Be comprehensive but concise.
|
||||
- Always produce substantial content — even if articles seem minor, extract value, implications, or connections.
|
||||
- Use neutral, professional, analytical tone with precise language.
|
||||
- Structure your response clearly with headings like:
|
||||
## Most Impactful Events
|
||||
### Event 1: [Brief Title]
|
||||
[4–6 sentences...]
|
||||
...
|
||||
## Synthesis of Lesser Developments
|
||||
[Paragraphs...]
|
||||
- Output ONLY the structured report — no introductions, apologies, or meta-comments like "no major events found".
|
||||
|
|
@ -3,7 +3,6 @@ apiVersion: kustomize.config.k8s.io/v1beta1
|
|||
kind: Kustomization
|
||||
namespace: customer1
|
||||
resources:
|
||||
- analyst-gemini-cronjob.yaml
|
||||
- configmap.yaml
|
||||
- gemini-apikey.yaml
|
||||
- news-user-db-secret.yaml
|
||||
|
|
@ -12,4 +11,5 @@ resources:
|
|||
- scrapy-configmap.yaml
|
||||
- telebot-cronjob.yaml
|
||||
- telebot-secret.yaml
|
||||
|
||||
- gemma-configmap.yaml
|
||||
- analyst-cronjob.yaml
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue