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