Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »


Purpose 

The purpose of this document is to provide a detailed overview of AI Services Deployment. The document consists of a detailed process, with procedures for Infrastructure Deployment, and Configuration with AC5.x Professional.


Scope

This process covers aspects of the deployment of AI Services in the production environment and its connectivity to AC 5.x Professional.


Infrastructure Deployment in Azure

 Create a “Resource Group” with required “Tags”

  1. Create “App Service Plan” with required “Tags”

  1. Once “App Service Plan” is created, it will show the overview as below:

  1. Create “Web App” with the steps below:

Put name, Publish Type, Runtime Stack, Java Web Server Stack, OS and Region

   Select Pricing Plan, as per recommendation from Product Team

Give reference from where the image will be pulled

Select Networking Options, keep public access as “ON” and Network Injection as “OFF”

Select “Monitoring” option as follow for Application Insight

Give the Tag

Once a Web App is created it will show like this, we can hit the URL to test the default page.

Add environment vairables in app service

Deploy through pipeline - Build Pipeline

Release Pipeline

  1. Create “API Management Service”.

  1. Configure API’s 

Add required policy

Update backend

Create GET & PUT operation 

  1. App Reg and integration 

Create new App reg 

Configure certificate and secret

Add the client id in previous created application 

Add JWT Token in API management 

Update values according to the Application created

Create Log analytics Workspace

Create application Insight

Integrated application insight into api management 

Add the required configuration to send logs to application insight 

Update the inbound policy for extract unstructured data async  and change the client id according to the created details 

  1. Create AKS Cluster

  1. Configure Milvus

attu:

  enabled: true

  service:

    type: LoadBalancer



extraConfigFiles:

  user.yaml: |+

    common:

      security:

        authorizationEnabled: true



service:

  type: LoadBalancer

 

minio:

  persistence:

    size: 50Gi



pulsar:

  bookkeeper:

    volumes:

      journal:

        size: 50Gi

      ledgers:

        size: 50Gi
kafka:

  persistence:

    size: 50Gi

Default username and password

Username - root

Password- jpQfSvbKUkZG

Create new user and password to use in application

Also change the password of root user

Login using Attu loadbalancer: 

Create new database -  Database name should be start with underscore "_" with client key ,  Like  "_<<Clientkey>>" where all the dash"-" needed to be replaced by underscore "_"

Here: Client key / id = The app reg client id 

To onboard new clients we need to add new clients in app reg and also create the database of the same. 

  1. Configure AI Service 

Go to manage deployment

Create new model deployment

Increase the token limit to max for all

Create Content filter

Requested decreased restriction on open ai content filtering

https://customervoice.microsoft.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR7en2Ais5pxKtso_Pz4b1_xUMlBQNkZMR0lFRldORTdVQzQ0TEI5Q1ExOSQlQCN0PWcu

Request Quota increase:

  1. Document Intelligence 

Create document intelligence service 

Go to document intelligence Studio

Use postman to migrate studio from sandbox to production

https://drive.google.com/file/d/1gcq2Fp0QrfMHAG_gCmPi0cBcH-oJ7c1E/view?usp=drive_link

Get the Model after migration using below 

https://learn.microsoft.com/en-us/rest/api/aiservices/document-models/list-models?view=rest-aiservices-v4.0%20(2024-07-31-preview)&tabs=HTTP

Security: 

  1. API Manamagent: Only allow IP address of AC5 professional AKS cluster in api management 

  1. App Service : Only allow request from api management

  2. Document Intelligence: Only allow request from with the Vnet

  3. OpenAI : Only allow the request from within the Vnet

Patching and Upgrade:

  1. Below process will be used for application upgrade

  1. Add slot in prod

  2. Update version / patch in different slot 

  1. Swap the prod with prod-02

  • No labels