Barani
Barani
@peternied @davidlago Do you have any inputs on this issue? This seems to be related to https://github.com/opensearch-project/security/issues/1941
+1 to the idea of creating release issue for OpenSearch benchmark release. Pre-planning the releases along with well defined code freeze date would help prioritize the changes in timely manner.
@gkamat @IanHoang Do we need to open an issue in OpenSearch core to investigate this behavior? CC: @dblock @nknize
Overall documentation including [developer guide](https://github.com/opensearch-project/opensearch-benchmark/blob/main/DEVELOPER_GUIDE.md) and [readme.md](https://github.com/opensearch-project/opensearch-benchmark/blob/main/README.md) needs to be updated to reflect the current status. We will be working on closing these gaps soon.
@gkamat @rishabhmaurya Can we look in to https://github.com/opensearch-project/opensearch-migrations/blob/main/TrafficCapture/README.md#traffic-replayer?
@rishabh6788 @gkamat @IanHoang Can we use opensearch-cluster-cdk for this purpose?
OpenSearch EOL policy is documented [here](https://opensearch.org/releases.html).
@praveensameneni the framework to on-board workloads exist already but plugin teams need to provide appropriate workload to automate the benchmark runs. This can be completed only after plugin teams provide...
@gauravruhela Can you please provide your inputs?
Thanks for opening an issue. We will look in to it when we have bandwidth. CCR is a unique use case hence I would appreciate if your team can contribute...