1. 20 Oct, 2025 1 commit
  2. 13 Oct, 2025 1 commit
  3. 30 Sep, 2025 1 commit
  4. 26 Sep, 2025 1 commit
  5. 24 Sep, 2025 1 commit
  6. 19 Sep, 2025 1 commit
  7. 16 Sep, 2025 1 commit
  8. 05 Sep, 2025 2 commits
  9. 02 Sep, 2025 1 commit
  10. 22 Aug, 2025 1 commit
  11. 21 Aug, 2025 1 commit
  12. 20 Aug, 2025 1 commit
  13. 19 Aug, 2025 1 commit
  14. 18 Aug, 2025 1 commit
  15. 15 Aug, 2025 2 commits
  16. 14 Aug, 2025 1 commit
  17. 13 Aug, 2025 1 commit
  18. 11 Aug, 2025 1 commit
  19. 07 Aug, 2025 2 commits
  20. 01 Aug, 2025 1 commit
  21. 30 Jul, 2025 1 commit
  22. 28 Jul, 2025 1 commit
  23. 25 Jul, 2025 1 commit
  24. 22 Jul, 2025 1 commit
  25. 16 Jul, 2025 1 commit
  26. 08 Jul, 2025 1 commit
  27. 07 Jul, 2025 1 commit
  28. 03 Jul, 2025 1 commit
  29. 13 Jun, 2025 1 commit
  30. 29 May, 2025 1 commit
  31. 23 May, 2025 1 commit
  32. 19 May, 2025 1 commit
    • Graham King's avatar
      feat: Support multiple models on single ingress node (#1127) · aeb79e62
      Graham King authored
      We can now do this:
      
      - Node 1:
      
      ```
      dynamo-run in=http out=dyn
      ```
      
      - Node 2 and 3, two instances of component 'backend' in the nemotron_ultra pipeline:
      
      ```
      dynamo-run in=dyn://nemotron_ultra.backend.generate out=vllm /data/models/NemotronUltra
      ```
      
      - Node 4 and 5, two instances of the 'backend' component in nemotron_super pipeline:
      
      ```
      dynamo-run in=dyn://nemotron_super.backend.generate out=vllm /data/models/NemotronSuper
      ```
      
      The ingress node will discover all four instances and route correctly. We have been planning for this for a long time now.
      
      As part of this auto-discovery is now always `out=dyn`, with no extra URL parts. Previously it could only route to a single pipeline.
      
      Also:
      - Refactor endpoint / instance naming now that I understand them
      - Fix removing models when their instance stops.
      aeb79e62
  33. 16 May, 2025 1 commit
  34. 09 May, 2025 2 commits
  35. 29 Apr, 2025 1 commit
    • Graham King's avatar
      chore: Split PushRouter from Client (#817) · a1a10365
      Graham King authored
      In a distributed system we don't know if the remote workers need pre-processing done ingress-side or not. Previously Client required us to decide this before discovering the remote endpoints, which was fine because pre-processing was worker-side.
      
      As part of moving pre-processing back to ingress-side we need to split this into two steps:
      - Client discovers the endpoints, and (later PR) will fetch their Model Deployment Card.
      - PushRouter will use the Model Deployment Card to decide if they need pre-processing or not, which affects the types of the generic parameters.
      
      Part of #743
      a1a10365
  36. 25 Apr, 2025 1 commit