Skip to content

docs: update blueprint_framework.md #89

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pdp2shirts wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: update blueprint_framework.md #89

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions Docs/blueprint_framework.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,12 +8,12 @@ Josh Brooks, Chief Solutions Architect | josh\@worldtechit.com
## What is an OPI Blueprint (Intent and Goals)?

An OPI Blueprint is an example architecture that shows how to
operationalize an open-source component within the OPI ecosystem. Rather
operationalize an open source component within the OPI ecosystem. Rather
than presenting raw code, APIs, or RFC specifications, a Blueprint takes an
OPI-supported technology and demonstrates a practical, real-world
deployment pattern that an enterprise customer or systems integrator could
replicate. **The intent is to:** **Accelerate adoption** by bridging the
gap between OPI’s open-source projects and production-ready deployments.
gap between OPI’s open source projects and production-ready deployments.
Customers don’t buy RFC adoption—they buy outcomes. **Showcase the value of
DPU/IPU technology** in offloading complex networking, security, and
storage functions to dedicated hardware, freeing host CPU cores for
Expand Down Expand Up @@ -73,13 +73,13 @@ company?”*
## How do Blueprints tie-in to OPI?

Blueprints are the adoption arm of the OPI Project. The OPI Project’s core
mission is to create a vendor-neutral, open-source framework of APIs and
mission is to create a vendor-neutral, open source framework of APIs and
tools for managing IPUs and DPUs. That work produces standardized
interfaces, reference implementations, and tested integrations—but it
doesn’t inherently show an enterprise customer how to operationalize those
components. Blueprints close that gap by: **Consuming OPI APIs and tools**
in validated, end-to-end architectures that prove multi-vendor
interoperability. **Providing the “last mile”** between OPI’s open-source
interoperability. **Providing the “last mile”** between OPI’s open source
projects (opi-api, sztp, DPU Operator) and what a customer actually needs
to stand up in their data center. **Creating a feedback loop** where
real-world deployment patterns surface gaps or enhancements needed in the
Expand Down
Loading