Skip to content

OCI AI Blueprints v1.0.3

Choose a tag to compare

View all tags
@grantneumanoracle grantneumanoracle released this 16 Jun 18:05
· 26 commits to main since this release
v1.0.3
30323e3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

🚨🚨 BREAKING CHANGE – READ THIS FIRST! 🚨🚨
Upgrading to v1.0.3 will destroy all existing deployments created with earlier versions of oci-ai-blueprints.
The upgrade replaces the Autonomous Database backend with a brand-new PostgreSQL instance, wiping the current database in the process.

Before you upgrade:

  1. Undeploy every active blueprint
  2. Back up any critical data you still need.
  3. Proceed with the v1.0.3 installation only after the cluster is clean.

Release Change Audit Report

New Version: v1.0.3
Previous Version: v1.0.2
Generated: 2025-06-16 10:51:07

Repositories Analyzed

  • Quickstarts (oci-ai-blueprints)
  • Control Plane (corrino)
  • Portal (oci_ai_blueprints_portal)

Release v1.0.3 delivers our most significant infrastructure overhaul to date.
PostgreSQL becomes the default backend everywhere, a fully-fledged Llama Stack sample debuts, vLLM is bumped to 0.9.1, security & contribution guidance tighten up, and several deployment/networking issues are resolved.
The sections below give a concise—but comprehensive—overview of what changed, how the parts fit together, and what to know before you upgrade.

1 · Executive Summary

  • Default Database Migration – Autonomous Database (ADB) is replaced by PostgreSQL across Quickstarts and Control Plane.
  • Llama Stack Blueprint – New end-to-end sample that combines ChromaDB, Jaeger, PostgreSQL, and the Llama Stack application.
  • vLLM Upgrade – All API docs, workflows, and blueprints now pin to vLLM 0.9.1.
  • Documentation & Security – Added SECURITY.md, CONTRIBUTING.md, richer install/verification steps, FAQs, and JSON-schema clarifications.
  • Bug Fixes & UX – Fixed endpoint exposure, restored proper Postgres SSL settings, added host-port overrides, improved install notes.
  • Portal Repo – No changes in v1.0.3.

2 · Repository-Specific Changes

Quickstarts Repo

Category Highlights
New Features Llama Stack Blueprint
• Lives under docs/sample_blueprints/llama-stack
• Bundles ChromaDB, Jaeger, PostgreSQL, and the main app
• Includes deployment order & structured JSON blueprint files
Improvements • vLLM bumped to 0.9.1 everywhere
• Added SECURITY.md & CONTRIBUTING.md
• Polished Installation Notes: clearer env-vars, tooling, test cmds, FAQ section
Bug Fixes • Corrected ingress.tf, cert-manager.tf, cluster-tools modules, policies.tf so endpoints expose correctly
Technical Changes • Swapped ADB ➜ PostgreSQL (postgres_db.tf, random-string creds)
• Removed ADB code; updated locals.tf, outputs.tf, schema.yaml
Documentation • Top-level README spotlights Llama Stack blueprint
• Synced sample_blueprints/README.md with new structure
• Reflected vLLM bump in docs/api_documentation.md & model workflows

Control Plane Repo

Category Highlights
New Features PostgreSQL Support
• Swapped Oracle DB config for PostgreSQL in project/settings.py
• Added references/postgres_db.yaml (ConfigMap, PVC, Deployment, Service)

Host-Port Customization
• New override in recipe_service_template.yaml
• api/control_plane/digest.py now respects custom host ports
Improvements • Enriched combined_schema.json descriptions (recipe_container_port, recipe_host_port)
Bug Fixes • Re-enabled Postgres SSL connectivity & removed unintended public LB in postgres_db.yaml
Technical Changes • Rolled back faulty commit f16dd51ea7f; restored correct DB settings

Portal Repo

No changes in this release.

3 · Cross-Repository Impact

  • Unified Postgres Backend – Both Quickstarts & Control Plane deploy PostgreSQL natively; blueprints share the same manifests.
  • Llama Stack Deployment – New Quickstarts blueprint spins up the full stack and leverages Control Plane’s postgres_db.yaml.
  • Consistent vLLM Versioning – Every repo now targets vLLM 0.9.1.
  • Security & Contribution Alignment – SECURITY.md & CONTRIBUTING.md set standards that will propagate to other repos.

4 · Upgrade Considerations

Area Action Items
Database Migration • If you are upgrading from a previous release, please make sure to undeploy all deployments before upgrading.
Docs & Workflows • Follow the revamped Installation Notes & FAQs in Quickstarts README.
• View new documentation (updated JSON schema & API docs) regarding host/container ports.
Security & Contribution • Review SECURITY.md and CONTRIBUTING.md for new processes.

Thank You for Upgrading to v1.0.3 🎉

This release lays the groundwork for a more secure, flexible, and consistent developer experience.
Encounter an issue or have feedback? Please consult SECURITY.md and CONTRIBUTING.md for next steps.

Assets 4
Loading