Tags: kserve/modelmesh
Tags
feat: Add S390x support (#138) #### Modifications Added linux/s390x ( platform ) in the build github workflow #### Result https://github.com/modassarrana89/modelmesh/actions/runs/8688245342/job/23823937204 // Build operation run in local workflow is a success. Attached archieve log for refernece [logs_22763759557.zip](https://github.com/kserve/modelmesh/files/14978607/logs_22763759557.zip) --------- Signed-off-by: Modassar Rana <[email protected]>
feat: Add S390x support (#138) #### Modifications Added linux/s390x ( platform ) in the build github workflow #### Result https://github.com/modassarrana89/modelmesh/actions/runs/8688245342/job/23823937204 // Build operation run in local workflow is a success. Attached archieve log for refernece [logs_22763759557.zip](https://github.com/kserve/modelmesh/files/14978607/logs_22763759557.zip) --------- Signed-off-by: Modassar Rana <[email protected]>
feat: Add vModelId to PayloadProcessor Payload (#123) Add a vModelId field to the Payload class and correspondingly update built-in PayloadProcessor implementations where applicable. It may be null if the request was directed at a concrete modelId rather than a vModelId. ----- Signed-off-by: Nick Hill <[email protected]>
fix: Fix not reading limits when cgroup v2 used (#107) Docker image was not picking up memory limits when cgroup v2 was used. This lead to incorrect java heap memory limits that lead to crashes due to OOMKilled as described in #106. Add extra check for limits in cgroup v2 file for the image to correctly read memory limits with both cgroup v1 and cgroup v2. Resolves #106 --- Signed-off-by: funbiscuit <[email protected]>
chore: update dependencies to address CVEs (#101) #### Overview Update netty `4.1.94.Final` and guava `32.0.1-jre` Signed-off-by: Anh-Uong <[email protected]>
Let RemotePayloadProcessor send also gRPC call Metadata (#96) #### Motivation The `RemotePayloadProcessor` currently doesn't send gRPC call `Metadata` as part of its `PayloadContent` (to a remote endpoint). Such information might be important for many reasons, including debugging purposes. #### Modifications `RemotePayloadProcessor`'s `PayloadContent` now also features a `Map` that contains such `Metadata` information (when available). #### Result `RemotePayloadProcessor` sends also `Metadata` information (to a remote endpoint). Signed-off-by: Tommaso Teofili <[email protected]> Signed-off-by: Tommaso Teofili <[email protected]> Co-authored-by: Anish Asthana <[email protected]> Co-authored-by: Nick Hill <[email protected]>
feat: Allow custom prometheus info metric (#83) #### Motivation Allow the generation of an "info" metric by way of environment variables captured as `Gauge` metric set up during container startup #### Modifications - Added environment variable `MMESH_CUSTOM_ENV_VAR` in `ModelMeshEnvVars` - Added map `infoMetricParams` and logic to parse and pass the info to prometheus in `ModelMesh` - Added a `Gauge` using the parsed label names and values in `Metrics` - Added sample variables to `pom.xml` for testing and related test in `ModelMeshMetricsTest` #### Result - Support to pass information by via environment variables parsed as `<metricname>[;label1=envVarWithValueforLabel1,label2=envVarWithValueforLabel2,...,labelN=envVarWithValueforLabelN,]` if provided. Signed-off-by: Rafael Vasquez <[email protected]>
chore: Update dependencies (#78) grpc, netty, protobuf, thrift Signed-off-by: Nick Hill <[email protected]>
PreviousNext