1. 21 May, 2025 1 commit
  2. 20 May, 2025 1 commit
  3. 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
  4. 15 May, 2025 1 commit
  5. 12 May, 2025 1 commit
  6. 09 May, 2025 1 commit
  7. 08 May, 2025 2 commits
  8. 07 May, 2025 2 commits
  9. 05 May, 2025 1 commit
  10. 01 May, 2025 1 commit
  11. 30 Apr, 2025 1 commit
  12. 28 Apr, 2025 1 commit
  13. 26 Apr, 2025 1 commit
  14. 25 Apr, 2025 2 commits
  15. 21 Apr, 2025 1 commit
  16. 18 Apr, 2025 1 commit
  17. 17 Apr, 2025 1 commit
  18. 15 Apr, 2025 1 commit
  19. 14 Apr, 2025 1 commit
  20. 12 Apr, 2025 1 commit
  21. 11 Apr, 2025 1 commit
  22. 10 Apr, 2025 2 commits
  23. 09 Apr, 2025 1 commit
  24. 07 Apr, 2025 1 commit
  25. 04 Apr, 2025 1 commit
  26. 31 Mar, 2025 1 commit
  27. 26 Mar, 2025 2 commits
  28. 24 Mar, 2025 1 commit
  29. 20 Mar, 2025 1 commit
  30. 19 Mar, 2025 3 commits
  31. 18 Mar, 2025 1 commit
  32. 17 Mar, 2025 2 commits