1. 02 Jan, 2026 1 commit
  2. 05 Dec, 2025 1 commit
  3. 04 Dec, 2025 1 commit
  4. 26 Nov, 2025 1 commit
  5. 25 Nov, 2025 2 commits
  6. 21 Nov, 2025 1 commit
  7. 19 Nov, 2025 1 commit
  8. 17 Nov, 2025 1 commit
  9. 13 Nov, 2025 1 commit
  10. 11 Nov, 2025 1 commit
  11. 10 Nov, 2025 1 commit
  12. 08 Nov, 2025 1 commit
  13. 28 Oct, 2025 1 commit
  14. 24 Oct, 2025 1 commit
  15. 23 Oct, 2025 1 commit
  16. 21 Oct, 2025 1 commit
  17. 20 Oct, 2025 1 commit
  18. 17 Oct, 2025 1 commit
  19. 10 Oct, 2025 1 commit
  20. 07 Oct, 2025 1 commit
  21. 30 Sep, 2025 2 commits
  22. 04 Sep, 2025 1 commit
  23. 22 Aug, 2025 3 commits
  24. 19 Aug, 2025 1 commit
  25. 18 Aug, 2025 2 commits
  26. 15 Aug, 2025 1 commit
  27. 14 Aug, 2025 1 commit
  28. 23 Jul, 2025 1 commit
  29. 22 Jul, 2025 1 commit
  30. 11 Jun, 2025 1 commit
  31. 23 May, 2025 1 commit
  32. 21 May, 2025 1 commit
  33. 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
  34. 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
  35. 06 May, 2025 1 commit
    • Graham King's avatar
      feat: dynamo-run <-> python interop (#934) · 99cd9d85
      Graham King authored
      Adding this to a Python script makes it register on the network so that `dynamo-run` can discover it and send it requests:
      ```
      from dynamo.llm import register_llm
      
      MODEL = "Qwen/Qwen2.5-0.5B-Instruct"
      await register_llm(endpoint, MODEL, 3)
      ```
      
      Full vllm example, with pre-processing in dynamo:
      - `dynamo-run in=text out=dyn://dynamo.backend.generate`
      - `cd lib/bindings/python/examples/hello_world`
      - `python server_vllm.py`
      
      This builds on top of the work to move pre-processor to ingress side. It means we can decouple Rust and Python using NATS as the bus.
      
      The `register_llm` call does this:
      
      - Download the model from HF if necessary
      - Load the model deployment card from the HF folder or extract from GGUF
      - Push the tokenizer config etc into NATS object store so ingress can access it from a different machine
      - Publish the model deployment card to ETCD
      99cd9d85