Uploaded image for project: 'AI Platform Core Components'
  1. AI Platform Core Components
  2. AIPCC-3257

build DeepGEMM for llm-d cluster scale MoE serving

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Accelerator Enablement
    • llm-d: build DeepEP
    • False
    • Hide

      The Git repository lacks both version tags and formal releases, which makes it impossible to pin the project to a specific version with any reliability. 
      Git repo changed

      Show
      The Git repository lacks both version tags and formal releases, which makes it impossible to pin the project to a specific version with any reliability.  Git repo changed
    • False
    • In Progress
    • AIPCC-3181 - Support for llm-d
    • AIPCC-3181Support for llm-d
    • 0% To Do, 0% In Progress, 100% Done
    • Hide

      23/July/25 - Green
      In review State with enhancement needed as the wheel is build from midstream and automatic versioning is introduced

      11/July/25 - Green
      In review State.

      Show
      23/July/25 - Green In review State with enhancement needed as the wheel is build from midstream and automatic versioning is introduced 11/July/25 - Green In review State.

      Feature Overview (mandatory - Complete while in New status)

      DeepGEMM is a required dependency for cluster scale serving of deepseek models, 

      Build instructions: https://github.com/deepseek-ai/DeepGEMM.git

      Goals (mandatory - Complete while in New status)
      Provide high-level goal statement, providing user context and expected user outcome(s) for this Feature

      • Build deepEP as a wheel

       

      Requirements (mandatory -_ Complete while in Refinement status):
      A list of specific needs, capabilities, or objectives that a Feature must deliver to satisfy the Feature. Some requirements will be flagged as MVP. If an MVP gets shifted, the Feature shifts. If a non MVP requirement slips, it does not shift the feature.

      Requirement Notes isMVP?
      Wheel build   Yes
      Builder image update   Yes

       

      Done - Acceptance Criteria (mandatory - Complete while in Refinement status):
      Acceptance Criteria articulates and defines the value proposition - what is required to meet the goal and intent of this Feature. The Acceptance Criteria provides a detailed definition of scope and the expected outcomes - from a users point of view

      A wheel collection owner can add a supported version of nixl to their collection. Runtime image is updated to support minimal working config deepEP.

      Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):

      vllm-d builds will include this package

      Out of Scope {}{}(Initial completion while in Refinement status):
      High-level list of items or persona’s that are out of scope.
      <your text here>

      Documentation Considerations {}{}(Initial completion while in Refinement status):
      Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation..
      <your text here>

       

      Questions to Answer {}{}(Initial completion while in Refinement status):
      Include a list of refinement / architectural questions that may need to be answered before coding can begin.
      <your text here>

      Background and Strategic Fit (Initial completion while in Refinement status):
      Provide any additional context is needed to frame the feature.

      https://github.com/deepseek-ai/DeepEP

      Customer Considerations {}{}(Initial completion while in Refinement status):
      Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.
      <your text here>

      Team Sign Off (Completion while in Refinement status)

      • All required Epics (known at the time) are linked to the this Feature
      • All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
      • Add - Reviewers name, Team Name
      • Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
      • Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone

      *An engineer or tech lead from the product requesting this feature is required for the signoff below.

      Reviewed By Team Name Accepted Notes
             
             
             
             

       

              rh-ee-vshaw Vikash Shaw
              rhn-support-weaton Will Eaton
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: