Skip to content

made es optional and log to local system#90

Open
Balatripura587 wants to merge 7 commits into
quay:masterfrom
Balatripura587:es-optional
Open

made es optional and log to local system#90
Balatripura587 wants to merge 7 commits into
quay:masterfrom
Balatripura587:es-optional

Conversation

@Balatripura587
Copy link
Copy Markdown
Contributor

ES server configuration is made optional and when ES is not configured, all per-image push/pull results (with summary stats) and Vegeta timeseries data are written to local JSON files on a PVC.

Signed-off-by: Bala Tripura Kumari Bodapati <bbodapat@redhat.com>
Signed-off-by: Bala Tripura Kumari Bodapati <bbodapat@redhat.com>
@Balatripura587 Balatripura587 marked this pull request as ready for review May 13, 2026 19:44
Balatripura587 and others added 2 commits May 13, 2026 15:49
Signed-off-by: Bala Tripura Kumari Bodapati <bbodapat@redhat.com>
Comment thread deploy/test.job.yaml Outdated
imagePullPolicy: Always
volumes:
- name: test-results
emptyDir: {}
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will disappear with the pod. Looks like we might need a PVC based approach, but something that doesn't pre-allocate the memory, instead just on demand (.i.e maybe NFS?). And then a cp can be done on this.

Copy link
Copy Markdown
Contributor Author

@Balatripura587 Balatripura587 May 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. I have identified an issue with current approach. Worker pods are mounted the same PVC directly — this worked because all pods anded on the same node, but breaks at scale when pods land on different nodes since they can't write to same PVC. So modified the approach where worker pods push per-image results to Redis , and the orchestrator collects all results from Redis after jobs finish and writes the aggregated JSON to its local volume.
  2. For PVC based approach,I think PVC would be better as NFS would require deploying and maintaining a separate NFS server. So I think this approach might be better. let me know your thoughts

Comment thread main.py Outdated
'%s_pull_results.json' % env_config["test_uuid"])

# Write results to Elasticsearch (if configured)
if env_config["es_host"] and Elasticsearch:
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have a similar block above as well. Do you think this can be modularized and reused?

Signed-off-by: Bala Tripura Kumari Bodapati <bbodapat@redhat.com>
Signed-off-by: Bala Tripura Kumari Bodapati <bbodapat@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants