1. 25 Aug, 2025 1 commit
  2. 22 Aug, 2025 2 commits
  3. 21 Aug, 2025 1 commit
  4. 19 Aug, 2025 2 commits
  5. 18 Aug, 2025 1 commit
  6. 15 Aug, 2025 1 commit
  7. 14 Aug, 2025 1 commit
  8. 13 Aug, 2025 1 commit
  9. 11 Aug, 2025 1 commit
  10. 07 Aug, 2025 1 commit
  11. 05 Aug, 2025 1 commit
  12. 28 Jul, 2025 1 commit
  13. 23 Jul, 2025 1 commit
  14. 22 Jul, 2025 1 commit
  15. 15 Jul, 2025 1 commit
  16. 08 Jul, 2025 1 commit
  17. 11 Jun, 2025 1 commit
  18. 23 May, 2025 1 commit
  19. 07 Apr, 2025 1 commit
    • Graham King's avatar
      feat(dynamo-run): Basic routing choice (#524) · ec2e7307
      Graham King authored
      As a first step towards KV routing:
      - introduce a `--router-mode` in dynamo-run that only does random and round-robin right now. Not that interesting yet.
      - Make the vllm engine publish the KV events received from our patched vllm.
      
      Now we "just" need to connect the two. Easy right?
      ec2e7307
  20. 04 Apr, 2025 1 commit
    • Graham King's avatar
      feat: Python decorator dynamo_worker takes optional `static` parameter without etcd (#494) · 88ad3425
      Graham King authored
      Adds `@dynamo_worker(static = True)` to create a static worker which has a predictable name and hence does not require discovery or `etcd` to be running. There can only be a single static worker per namespace / component / endpoint trio.
      
      This contrasts with the default dynamic `dynamo_worker` endpoints we have now, which get a unique random name (based on namespace/component/endpoint), and are discovered by ingress components using etcd.
      
      Also change the hello_world example to use `dynamo_worker(static = True)` so that it is exercised and demonstrated somewhere.
      
      For NIM.
      88ad3425
  21. 25 Feb, 2025 1 commit
  22. 18 Feb, 2025 2 commits
  23. 05 Feb, 2025 1 commit
  24. 04 Feb, 2025 1 commit