This repository was archived by the owner on Jan 15, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 85
This repository was archived by the owner on Jan 15, 2025. It is now read-only.
Orchestrator recognizer plugin for Adaptive Runtime #492
Copy link
Copy link
Closed
Labels
Area: PackagesRelating to bot component packages.Relating to bot component packages.Area: Runtime HostRelating to the project runtime bot hostRelating to the project runtime bot hostfeature-requestA request for new functionality or an enhancement to an existing one.A request for new functionality or an enhancement to an existing one.needs-triageThe issue has just been created and it has not been reviewed by the team.The issue has just been created and it has not been reviewed by the team.
Milestone
Description
Background
Per microsoft/BotFramework-Composer#5471, the decision was made to not include the Orchestrator language recognizer by default in the runtime due to the large size of the underlying language model, as well as due to the fact that the Orchestrator runtime only supports x64 architecture.
Ask
In alignment with this decision, an ask has been made to support an Orchestrator extension for the new adaptive runtime. To support this, the following requirements need to be met:
- An external Orchestrator recognizer plugin should be defined as a valid NuGet package that can be consumed by the adaptive runtime.
- The plugin needs to register the recognizer present in Microsoft.Bot.Builder.AI.Orchestrator using the available ComponentRegistrations API within the Bot Framework SDK.
- The runtime host application needs to ensure that, when built, declarative files with the *.blu suffix are copied to the build output location alongside other supported declarative files.
- The 'generated' folder built by Composer contains recognizer-specific settings that need to be picked up by the runtime and added as a configuration source into IConfigurationBuilder. As such, the runtime should make sure to copy the generated folder to the build output directory, and at a minimum include 'generated/orchestrator.settings.json'. (N.B.: since other generated settings are added this way, we should probably just include all *settings.json files from the generated directory)
Additional Notes
- Orchestrator team is working on producing a version of the runtime that supports x86 target platform. There is a known limitation that this will only support smaller language models.
- We do not need to concern ourselves with handling excluding the onnxruntime.pdb. Orchestrator team is working on repackaging the recognizer runtime to exclude the *.pdb files due to their large size.
Metadata
Metadata
Assignees
Labels
Area: PackagesRelating to bot component packages.Relating to bot component packages.Area: Runtime HostRelating to the project runtime bot hostRelating to the project runtime bot hostfeature-requestA request for new functionality or an enhancement to an existing one.A request for new functionality or an enhancement to an existing one.needs-triageThe issue has just been created and it has not been reviewed by the team.The issue has just been created and it has not been reviewed by the team.