1. 26 Feb, 2026 1 commit
  2. 19 Feb, 2026 1 commit
  3. 11 Feb, 2026 1 commit
  4. 29 Jan, 2026 1 commit
  5. 14 Jan, 2026 1 commit
  6. 06 Jan, 2026 1 commit
  7. 02 Jan, 2026 1 commit
  8. 10 Dec, 2025 1 commit
  9. 03 Dec, 2025 1 commit
  10. 13 Nov, 2025 1 commit
  11. 07 Nov, 2025 1 commit
  12. 12 Oct, 2025 1 commit
  13. 26 Sep, 2025 1 commit
  14. 19 Sep, 2025 1 commit
  15. 16 Sep, 2025 1 commit
  16. 28 Aug, 2025 1 commit
  17. 26 Aug, 2025 1 commit
  18. 22 Aug, 2025 1 commit
  19. 18 Aug, 2025 1 commit
  20. 25 Jul, 2025 1 commit
  21. 10 Jul, 2025 1 commit
  22. 13 Jun, 2025 1 commit
  23. 11 Jun, 2025 1 commit
  24. 05 Jun, 2025 1 commit
  25. 04 Jun, 2025 1 commit
  26. 30 May, 2025 1 commit
  27. 28 May, 2025 1 commit
  28. 27 May, 2025 1 commit
  29. 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
  30. 07 May, 2025 1 commit
  31. 02 May, 2025 1 commit