1. 28 Jan, 2026 1 commit
  2. 02 Jan, 2026 1 commit
  3. 05 Dec, 2025 1 commit
  4. 04 Dec, 2025 1 commit
  5. 26 Nov, 2025 1 commit
  6. 25 Nov, 2025 2 commits
  7. 21 Nov, 2025 1 commit
  8. 19 Nov, 2025 1 commit
  9. 17 Nov, 2025 1 commit
  10. 13 Nov, 2025 1 commit
  11. 11 Nov, 2025 1 commit
  12. 10 Nov, 2025 1 commit
  13. 08 Nov, 2025 1 commit
  14. 28 Oct, 2025 1 commit
  15. 24 Oct, 2025 1 commit
  16. 23 Oct, 2025 1 commit
  17. 21 Oct, 2025 1 commit
  18. 20 Oct, 2025 1 commit
  19. 17 Oct, 2025 1 commit
  20. 10 Oct, 2025 1 commit
  21. 07 Oct, 2025 1 commit
  22. 30 Sep, 2025 2 commits
  23. 04 Sep, 2025 1 commit
  24. 22 Aug, 2025 3 commits
  25. 19 Aug, 2025 1 commit
  26. 18 Aug, 2025 2 commits
  27. 15 Aug, 2025 1 commit
  28. 14 Aug, 2025 1 commit
  29. 23 Jul, 2025 1 commit
  30. 22 Jul, 2025 1 commit
  31. 11 Jun, 2025 1 commit
  32. 23 May, 2025 1 commit
  33. 21 May, 2025 1 commit
  34. 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
  35. 15 May, 2025 1 commit
    • Graham King's avatar
      chore: Prevent duplicate components with different models. (#1103) · 641234cd
      Graham King authored
      Each namespace is for a single pipeline, so a component must be model-unique. The means we can have several components with the same name running the same model (data parallel), their traffic will be routed according to `--router-mode`, but we cannot have several components with the same name running different models.
      
      Add an `ensure_unique` check to prevent that happening.
      641234cd