diff --git a/README.md b/README.md index 13207ed..18996e5 100644 --- a/README.md +++ b/README.md @@ -28,27 +28,29 @@ The solution uses a sophisticated multi-agent orchestration pattern where specia This solution enables enterprise-grade Kubernetes migration with the following capabilities: -• **Enterprise Batch Processing Architecture** -Complete solution including React web application for file upload, validation, and queue management coupled with intelligent multi-agent processing engine + - **Enterprise Batch Processing Architecture**
+ Complete solution including React web application for file upload, validation, and queue management coupled with intelligent multi-agent processing engine -• **Intelligent Platform Detection** -Automatically identifies source Kubernetes platform (GKE/EKS) through configuration analysis and applies platform-specific migration strategies + - **Intelligent Platform Detection**
+ Automatically identifies source Kubernetes platform (GKE/EKS) through configuration analysis and applies platform-specific migration strategies -• **Multi-Agent Expert Orchestration** -Specialized agents (Technical Architect, Azure Expert, Platform Experts, QA Engineer) collaborate through Semantic Kernel GroupChat orchestration patterns + - **Multi-Agent Expert Orchestration**
+ Specialized agents (Technical Architect, Azure Expert, Platform Experts, QA Engineer) collaborate through Semantic Kernel GroupChat orchestration patterns -• **Process Framework Integration** -Each migration step (analysis, design, conversion, documentation) is built using Semantic Kernel Process Framework with event routing and step orchestration + - **Process Framework Integration**
+ Each migration step (analysis, design, conversion, documentation) is built using Semantic Kernel Process Framework with event routing and step orchestration -• **MCP Server Tool Integration** -Agents access intelligent tools through Model Context Protocol servers for file operations, knowledge search, and specialized functions without direct model training + - **MCP Server Tool Integration**
+ Agents access intelligent tools through Model Context Protocol servers for file operations, knowledge search, and specialized functions without direct model training -• **Azure Well-Architected Framework Compliance** -Configurations transformed according to Azure security, reliability, performance, cost optimization, and operational excellence principles + - **Azure Well-Architected Framework Compliance**
+ Configurations transformed according to Azure security, reliability, performance, cost optimization, and operational excellence principles + + - **Comprehensive Migration Reporting**
+ Detailed reports capturing expert analysis, transformation decisions, and recommendations from multiple specialized agents -• **Comprehensive Migration Reporting** -Detailed reports capturing expert analysis, transformation decisions, and recommendations from multiple specialized agents ### Agentic Architecture + ## If you want to get know more detail about Agentic Architecture, please take a look at this document: [Agentic Architecture](docs/AgenticArchitecture.md) @@ -231,6 +233,23 @@ Have questions, find a bug, or want to request a feature? [Submit a new issue](h ## Responsible AI Transparency FAQ Please refer to [Transparency FAQ](./TRANSPARENCY_FAQ.md) for responsible AI transparency details of this solution accelerator. +## Data Collection + +The software may collect information about you and your use of the software and send it to Microsoft. Microsoft may use this information to provide services and improve our products and services. You may turn off the telemetry as described in the repository. There are also some features in the software that may enable you and Microsoft to collect data from users of your applications. If you use these features, you must comply with applicable law, including providing appropriate notices to users of your applications together with a copy of [Microsoft’s privacy statement](https://go.microsoft.com/fwlink/?LinkID=824704). You can learn more about data collection and use in the help documentation and our privacy statement. Your use of the software operates as your consent to these practices. + +### Telemetry Configuration + +This repository uses telemetry to track and monitor usage. There are two means of telemetry being used for this purpose: [Azure Developer CLI (AZD)](https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/overview?tabs=windows) and using [Azure Verified Modules (AVM)](https://azure.github.io/Azure-Verified-Modules/) for provisioning resources. Telemetry collection in this solution is enabled by default. + +To opt out, perform the following steps: + +1. Set the environment variable `AZURE_DEV_COLLECT_TELEMETRY` to `no` in your environment prior to deploying. +2. Set the `enableTelemetry` parameter value in `main.parameters.json` to `false` prior to deploying. + +## Trademarks + +This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft’s Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party’s policies. + ## Disclaimers To the extent that the Software includes components or code used in or derived from Microsoft products or services, including without limitation Microsoft Azure Services (collectively, “Microsoft Products and Services”), you must also comply with the Product Terms applicable to such Microsoft Products and Services. You acknowledge and agree that the license governing the Software does not grant you a license or other right to use Microsoft Products and Services. Nothing in the license or this ReadMe file will serve to supersede, amend, terminate or modify any terms in the Product Terms for any Microsoft Products and Services. diff --git a/src/backend-api/src/tests/test_files/EKS/ebs-kc-classes.yaml b/data/eks/ebs-kc-classes.yaml similarity index 100% rename from src/backend-api/src/tests/test_files/EKS/ebs-kc-classes.yaml rename to data/eks/ebs-kc-classes.yaml diff --git a/src/backend-api/src/tests/test_files/EKS/ebs-kc-restore.yaml b/data/eks/ebs-kc-restore.yaml similarity index 100% rename from src/backend-api/src/tests/test_files/EKS/ebs-kc-restore.yaml rename to data/eks/ebs-kc-restore.yaml diff --git a/src/backend-api/src/tests/test_files/EKS/ebs-kc-snapshot.yaml b/data/eks/ebs-kc-snapshot.yaml similarity index 100% rename from src/backend-api/src/tests/test_files/EKS/ebs-kc-snapshot.yaml rename to data/eks/ebs-kc-snapshot.yaml diff --git a/src/backend-api/src/tests/test_files/EKS/ebs-kc.yaml b/data/eks/ebs-kc.yaml similarity index 100% rename from src/backend-api/src/tests/test_files/EKS/ebs-kc.yaml rename to data/eks/ebs-kc.yaml diff --git a/src/backend-api/src/tests/test_files/GKE/axolotl-training-job.yaml b/data/gke/axolotl-training-job.yaml similarity index 100% rename from src/backend-api/src/tests/test_files/GKE/axolotl-training-job.yaml rename to data/gke/axolotl-training-job.yaml diff --git a/src/backend-api/src/tests/test_files/GKE/model-export.yaml b/data/gke/model-export.yaml similarity index 100% rename from src/backend-api/src/tests/test_files/GKE/model-export.yaml rename to data/gke/model-export.yaml diff --git a/src/backend-api/src/tests/test_files/GKE/model-storage-pvc.yaml b/data/gke/model-storage-pvc.yaml similarity index 100% rename from src/backend-api/src/tests/test_files/GKE/model-storage-pvc.yaml rename to data/gke/model-storage-pvc.yaml diff --git a/src/backend-api/src/tests/test_files/GKE/tensorboard.yaml b/data/gke/tensorboard.yaml similarity index 100% rename from src/backend-api/src/tests/test_files/GKE/tensorboard.yaml rename to data/gke/tensorboard.yaml diff --git a/docs/DeploymentGuide.md b/docs/DeploymentGuide.md index 1092500..1cb736c 100644 --- a/docs/DeploymentGuide.md +++ b/docs/DeploymentGuide.md @@ -170,7 +170,9 @@ Once you've opened the project in [Codespaces](#github-codespaces), [Dev Contain > #### Important Note : Before accessing the application, ensure that all **[Post Deployment Steps](#post-deployment-steps)** are fully completed, as they are critical for the proper configuration of **Data Ingestion** and **Authentication** functionalities. -6. After exploring the application, you can delete the resources by running `azd down` command. +6. Use the application by uploading other GKE or EKS container workload configuration YAML files. [Sample input files can be found in the data folder](/data/). + +7. After exploring the application, you can delete the resources by running `azd down` command. ### Post Deployment Steps diff --git a/docs/images/readme/agentic_architecture.png b/docs/images/readme/agentic_architecture.png index 1476fbf..a138dab 100644 Binary files a/docs/images/readme/agentic_architecture.png and b/docs/images/readme/agentic_architecture.png differ diff --git a/docs/images/readme/architecture.png b/docs/images/readme/architecture.png index 332fa00..9b04455 100644 Binary files a/docs/images/readme/architecture.png and b/docs/images/readme/architecture.png differ diff --git a/infra/main.parameters.json b/infra/main.parameters.json index 9da5290..e9929f3 100644 --- a/infra/main.parameters.json +++ b/infra/main.parameters.json @@ -28,6 +28,9 @@ }, "aiModelCapacity": { "value": "${AZURE_AI_MODEL_CAPACITY}" + }, + "enableTelemetry": { + "value": true } } }