-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
.Net: OpenAI V2 & Assistants V2 - GA (#7151)
Accumulation of incremental changes that were reviewed separately. This change fundamentally grapples with updating the Azure AI OpenAI SDK from V1 to V2. This involves: - Including the OpenAI SDK dependency - Refactoring the OpenAI Connector - Introducing an Azure OpenAI Connector - Update the experimental `Agents.OpenAI` to support V2 assistant features (breaking change) --------- Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: Roger Barreto <[email protected]> Co-authored-by: SergeyMenshykh <[email protected]> Co-authored-by: SergeyMenshykh <[email protected]> Co-authored-by: Dmytro Struk <[email protected]> Co-authored-by: Roger Barreto <[email protected]> Co-authored-by: Dr. Artificial曾小健 <[email protected]> Co-authored-by: westey <[email protected]> Co-authored-by: Mark Wallace <[email protected]> Co-authored-by: Tao Chen <[email protected]> Co-authored-by: Evan Mattson <[email protected]> Co-authored-by: Maurycy Markowski <[email protected]> Co-authored-by: gparmigiani <[email protected]> Co-authored-by: Atiqur Rahman Foyshal <[email protected]> Co-authored-by: Eduard van Valkenburg <[email protected]> Co-authored-by: Andrew Desousa <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Marcelo Garcia <[email protected]> Co-authored-by: Marcelo Garcia 🛸 <[email protected]> Co-authored-by: Eirik Tsarpalis <[email protected]>
- Loading branch information
20 people
authored
Sep 4, 2024
1 parent
0bee1c1
commit cc63d56
Showing
364 changed files
with
15,290 additions
and
12,136 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,196 @@ | ||
| # OpenAI Connector Migration Guide | ||
|
|
||
| This manual prepares you for the migration of your OpenAI Connector to the new OpenAI Connector. The new OpenAI Connector is a complete rewrite of the existing OpenAI Connector and is designed to be more efficient, reliable, and scalable. This manual will guide you through the migration process and help you understand the changes that have been made to the OpenAI Connector. | ||
|
|
||
| ## 1. Package Setup when Using Azure | ||
|
|
||
| If you are working with Azure and or OpenAI public APIs, you will need to change the package from `Microsoft.SemanticKernel.Connectors.OpenAI` to `Microsoft.SemanticKernel.Connectors.AzureOpenAI`, | ||
|
|
||
| > [!IMPORTANT] | ||
| > The `Microsoft.SemanticKernel.Connectors.AzureOpenAI` package depends on the `Microsoft.SemanticKernel.Connectors.OpenAI` package so there's no need to add both to your project when using `OpenAI` related types. | ||
| ```diff | ||
| - // Before | ||
| - using Microsoft.SemanticKernel.Connectors.OpenAI; | ||
| + After | ||
| + using Microsoft.SemanticKernel.Connectors.AzureOpenAI; | ||
| ``` | ||
|
|
||
| ### 1.1 AzureOpenAIClient | ||
|
|
||
| When using Azure with OpenAI, before where you were using `OpenAIClient` you will need to update your code to use the new `AzureOpenAIClient` type. | ||
|
|
||
| ### 1.2 Services | ||
|
|
||
| All services below now belong to the `Microsoft.SemanticKernel.Connectors.AzureOpenAI` namespace. | ||
|
|
||
| - `AzureOpenAIAudioToTextService` | ||
| - `AzureOpenAIChatCompletionService` | ||
| - `AzureOpenAITextEmbeddingGenerationService` | ||
| - `AzureOpenAITextToAudioService` | ||
| - `AzureOpenAITextToImageService` | ||
|
|
||
| ## 2. Text Generation Deprecated | ||
|
|
||
| The latest `OpenAI` SDK does not support text generation modality, when migrating to their underlying SDK we had to drop the support and removed `TextGeneration` specific services but the existing `ChatCompletion` ones still supports (implements `ITextGenerationService`). | ||
|
|
||
| If you were using any of the `OpenAITextGenerationService` or `AzureOpenAITextGenerationService` you will need to update your code to target a chat completion model instead, using `OpenAIChatCompletionService` or `AzureOpenAIChatCompletionService` instead. | ||
|
|
||
| > [!NOTE] | ||
| > OpenAI and AzureOpenAI `ChatCompletion` services also implement the `ITextGenerationService` interface and that may not require any changes to your code if you were targeting the `ITextGenerationService` interface. | ||
| tags: | ||
| `OpenAITextGenerationService`,`AzureOpenAITextGenerationService`, | ||
| `AddOpenAITextGeneration`,`AddAzureOpenAITextGeneration` | ||
|
|
||
| ## 3. ChatCompletion Multiple Choices Deprecated | ||
|
|
||
| The latest `OpenAI` SDK does not support multiple choices, when migrating to their underlying SDK we had to drop the support and removed `ResultsPerPrompt` also from the `OpenAIPromptExecutionSettings`. | ||
|
|
||
| tags: `ResultsPerPrompt`,`results_per_prompt` | ||
|
|
||
| ## 4. OpenAI File Service Deprecation | ||
|
|
||
| The `OpenAIFileService` was deprecated in the latest version of the OpenAI Connector. We strongly recommend to update your code to use the new `OpenAIClient.GetFileClient()` for file management operations. | ||
|
|
||
| ## 5. SemanticKernel MetaPackage | ||
|
|
||
| To be retro compatible with the new OpenAI and AzureOpenAI Connectors, our `Microsoft.SemanticKernel` meta package changed its dependency to use the new `Microsoft.SemanticKernel.Connectors.AzureOpenAI` package that depends on the `Microsoft.SemanticKernel.Connectors.OpenAI` package. This way if you are using the metapackage, no change is needed to get access to `Azure` related types. | ||
|
|
||
| ## 6. Contents | ||
|
|
||
| ### 6.1 OpenAIChatMessageContent | ||
|
|
||
| - The `Tools` property type has changed from `IReadOnlyList<ChatCompletionsToolCall>` to `IReadOnlyList<ChatToolCall>`. | ||
|
|
||
| - Inner content type has changed from `ChatCompletionsFunctionToolCall` to `ChatToolCall`. | ||
|
|
||
| - Metadata type `FunctionToolCalls` has changed from `IEnumerable<ChatCompletionsFunctionToolCall>` to `IEnumerable<ChatToolCall>`. | ||
|
|
||
| ### 6.2 OpenAIStreamingChatMessageContent | ||
|
|
||
| - The `FinishReason` property type has changed from `CompletionsFinishReason` to `FinishReason`. | ||
| - The `ToolCallUpdate` property has been renamed to `ToolCallUpdates` and its type has changed from `StreamingToolCallUpdate?` to `IReadOnlyList<StreamingToolCallUpdate>?`. | ||
| - The `AuthorName` property is not initialized because it's not provided by the underlying library anymore. | ||
|
|
||
| ## 6.3 Metrics for AzureOpenAI Connector | ||
|
|
||
| The meter `s_meter = new("Microsoft.SemanticKernel.Connectors.OpenAI");` and the relevant counters still have old names that contain "openai" in them, such as: | ||
|
|
||
| - `semantic_kernel.connectors.openai.tokens.prompt` | ||
| - `semantic_kernel.connectors.openai.tokens.completion` | ||
| - `semantic_kernel.connectors.openai.tokens.total` | ||
|
|
||
| ## 7. Using Azure with your data (Data Sources) | ||
|
|
||
| With the new `AzureOpenAIClient`, you can now specify your datasource thru the options and that requires a small change in your code to the new type. | ||
|
|
||
| Before | ||
|
|
||
| ```csharp | ||
| var promptExecutionSettings = new OpenAIPromptExecutionSettings | ||
| { | ||
| AzureChatExtensionsOptions = new AzureChatExtensionsOptions | ||
| { | ||
| Extensions = [ new AzureSearchChatExtensionConfiguration | ||
| { | ||
| SearchEndpoint = new Uri(TestConfiguration.AzureAISearch.Endpoint), | ||
| Authentication = new OnYourDataApiKeyAuthenticationOptions(TestConfiguration.AzureAISearch.ApiKey), | ||
| IndexName = TestConfiguration.AzureAISearch.IndexName | ||
| }] | ||
| }; | ||
| }; | ||
| ``` | ||
|
|
||
| After | ||
|
|
||
| ```csharp | ||
| var promptExecutionSettings = new AzureOpenAIPromptExecutionSettings | ||
| { | ||
| AzureChatDataSource = new AzureSearchChatDataSource | ||
| { | ||
| Endpoint = new Uri(TestConfiguration.AzureAISearch.Endpoint), | ||
| Authentication = DataSourceAuthentication.FromApiKey(TestConfiguration.AzureAISearch.ApiKey), | ||
| IndexName = TestConfiguration.AzureAISearch.IndexName | ||
| } | ||
| }; | ||
| ``` | ||
|
|
||
| ## 8. Breaking glass scenarios | ||
|
|
||
| Breaking glass scenarios are scenarios where you may need to update your code to use the new OpenAI Connector. Below are some of the breaking changes that you may need to be aware of. | ||
|
|
||
| #### 8.1 KernelContent Metadata | ||
|
|
||
| Some of the keys in the content metadata dictionary have changed, you will need to update your code to when using the previous key names. | ||
|
|
||
| - `Created` -> `CreatedAt` | ||
|
|
||
| #### 8.2 Prompt Filter Results | ||
|
|
||
| The `PromptFilterResults` metadata type has changed from `IReadOnlyList<ContentFilterResultsForPrompt>` to `ContentFilterResultForPrompt`. | ||
|
|
||
| #### 8.3 Content Filter Results | ||
|
|
||
| The `ContentFilterResultsForPrompt` type has changed from `ContentFilterResultsForChoice` to `ContentFilterResultForResponse`. | ||
|
|
||
| #### 8.4 Finish Reason | ||
|
|
||
| The FinishReason metadata string value has changed from `stop` to `Stop` | ||
|
|
||
| #### 8.5 Tool Calls | ||
|
|
||
| The ToolCalls metadata string value has changed from `tool_calls` to `ToolCalls` | ||
|
|
||
| #### 8.6 LogProbs / Log Probability Info | ||
|
|
||
| The `LogProbabilityInfo` type has changed from `ChatChoiceLogProbabilityInfo` to `IReadOnlyList<ChatTokenLogProbabilityInfo>`. | ||
|
|
||
| #### 8.7 Finish Details, Index, and Enhancements | ||
|
|
||
| All of above have been removed. | ||
|
|
||
| #### 8.8 Token Usage | ||
|
|
||
| The Token usage naming convention from `OpenAI` changed from `Completion`, `Prompt` tokens to `Output` and `Input` respectively. You will need to update your code to use the new naming. | ||
|
|
||
| The type also changed from `CompletionsUsage` to `ChatTokenUsage`. | ||
|
|
||
| [Example of Token Usage Metadata Changes](https://github.com/microsoft/semantic-kernel/pull/7151/files#diff-a323107b9f8dc8559a83e50080c6e34551ddf6d9d770197a473f249589e8fb47) | ||
|
|
||
| ```diff | ||
| - Before | ||
| - var usage = FunctionResult.Metadata?["Usage"] as CompletionsUsage; | ||
| - var completionTokesn = usage?.CompletionTokens ?? 0; | ||
| - var promptTokens = usage?.PromptTokens ?? 0; | ||
|
|
||
| + After | ||
| + var usage = FunctionResult.Metadata?["Usage"] as ChatTokenUsage; | ||
| + var promptTokens = usage?.InputTokens ?? 0; | ||
| + var completionTokens = completionTokens: usage?.OutputTokens ?? 0; | ||
|
|
||
| totalTokens: usage?.TotalTokens ?? 0; | ||
| ``` | ||
|
|
||
| #### 8.9 OpenAIClient | ||
|
|
||
| The `OpenAIClient` type previously was a Azure specific namespace type but now it is an `OpenAI` SDK namespace type, you will need to update your code to use the new `OpenAIClient` type. | ||
|
|
||
| When using Azure, you will need to update your code to use the new `AzureOpenAIClient` type. | ||
|
|
||
| #### 8.10 Pipeline Configuration | ||
|
|
||
| The new `OpenAI` SDK uses a different pipeline configuration, and has a dependency on `System.ClientModel` package. You will need to update your code to use the new `HttpClientPipelineTransport` transport configuration where before you were using `HttpClientTransport` from `Azure.Core.Pipeline`. | ||
|
|
||
| [Example of Pipeline Configuration](https://github.com/microsoft/semantic-kernel/pull/7151/files#diff-fab02d9a75bf43cb57f71dddc920c3f72882acf83fb125d8cad963a643d26eb3) | ||
|
|
||
| ```diff | ||
| var clientOptions = new OpenAIClientOptions | ||
| { | ||
| - // Before: From Azure.Core.Pipeline | ||
| - Transport = new HttpClientTransport(httpClient), | ||
|
|
||
| + // After: From OpenAI SDK -> System.ClientModel | ||
| + Transport = new HttpClientPipelineTransport(httpClient), | ||
| }; | ||
| ``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.