Allow CPU_RUNTIME_CACHE_CAPACITY in plugin_config

[andersendsa]

🛠 Summary

OpenVINO's CPU_RUNTIME_CACHE_CAPACITY is an internal parameter that isn't returned by get_property(pluginName, ov::supported_properties). This caused OVMS validation to fail when users attempted to configure it via plugin_config. This commit whitelists CPU_RUNTIME_CACHE_CAPACITY during validation (similar to ENABLE_MMAP) so that the configuration is passed down to OpenVINO Runtime, where it is supported.
Closes : #4299
JIRA/Issue if applicable.
Describe the changes.

1. Whitelisted CPU_RUNTIME_CACHE_CAPACITY in src/ov_utils.cpp

   • In the validatePluginConfiguration function, OVMS dynamically checks if the keys provided in plugin_config are supported by the target device.
   • I explicitly added pluginSupportedConfigKeys.insert("CPU_RUNTIME_CACHE_CAPACITY"); to bypass this validation failure for this specific key, similar to how it is handled for the ENABLE_MMAP configuration.
   • This ensures that OVMS allows the key and forwards it correctly to the OpenVINO Runtime, where it is functionally supported.

2. Added Unit Tests in src/test/ov_utils_test.cpp

   • I implemented a new test case TEST(OVUtils, ValidatePluginConfigurationAllowCPURuntimeCacheCapacity).
   • This test initializes a mock configuration with CPU_RUNTIME_CACHE_CAPACITY set to "0" and verifies that ovms::validatePluginConfiguration successfully executes without returning any errors (validating status.ok()).

🧪 Checklist

• Unit tests added.
• The documentation updated.
• Change follows security best practices.
  ``

[andersendsa]

Hi @atobiszei, @dtrawins pls let me know if this pr needs any changes or if it is good to merge

[Copilot]

Pull request overview

This PR updates OVMS’ OpenVINO plugin-config validation to allow passing the CPU plugin’s internal CPU_RUNTIME_CACHE_CAPACITY setting via plugin_config, addressing startup failures when users configure it (as reported in #4299).

Changes:

• Whitelists CPU_RUNTIME_CACHE_CAPACITY during plugin-config key validation (similar to the existing ENABLE_MMAP workaround).
• Adds a unit test asserting validation succeeds when CPU_RUNTIME_CACHE_CAPACITY is present in plugin_config.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
src/ov_utils.cpp	Extends validation allowlist to accept CPU_RUNTIME_CACHE_CAPACITY.
src/test/ov_utils_test.cpp	Adds a unit test covering the new allowlisted key.

[andersendsa]

Hi @dtrawins I have added the suggesteed changes pls let me know if this pr needs any changes or if it is good to merge

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

src/test/ov_utils_test.cpp:254

• The new test case is missing its closing } (and the file currently ends right after the compile_model line), which will cause a compilation failure.

    auto status = ovms::validatePluginConfiguration(pluginConfig, "CPU", ieCore);
    EXPECT_TRUE(status.ok());
    auto model = ieCore.read_model(std::filesystem::current_path().u8string() + "/src/test/dummy/1/dummy.xml", {}, pluginConfig);
    auto compiledModel = ieCore.compile_model(model, "CPU", pluginConfig);

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

src/ov_utils.cpp:144

• pluginSupportedConfigKeys is a std::set<std::string>, but the validation uses std::find(begin,end, ...), which is O(n) and less clear than using the set lookup. Prefer pluginSupportedConfigKeys.find(config.first) to keep the intent obvious and avoid linear scans.

    for (auto& config : pluginConfig) {
        if (std::find(pluginSupportedConfigKeys.begin(), pluginSupportedConfigKeys.end(), config.first) == pluginSupportedConfigKeys.end()) {
            SPDLOG_LOGGER_ERROR(modelmanager_logger, "Plugin config key: {} not found in supported config keys for device: {}.", config.first, targetDevice);