Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: tio can run without NATS or ETCD #203

Merged
merged 1 commit into from
Feb 18, 2025
Merged

bug: tio can run without NATS or ETCD #203

merged 1 commit into from
Feb 18, 2025

Conversation

grahamking
Copy link
Contributor

Previously tio wouldn't run unless etcd and nats were present in the environment, even though it doesn't use them yet.

This makes it easier to use tio.

ryanolson
ryanolson previously approved these changes Feb 18, 2025
Previously `tio` wouldn't run unless etcd and nats were present in the
environment, even though it doesn't use them yet.

This makes it easier to use `tio`.
Comment on lines +80 to +82
//let dt_config = triton_distributed::distributed::DistributedConfig::from_settings();
// Wraps the Runtime (which wraps two tokio runtimes) and adds etcd and nats clients
let d_runtime = triton_distributed::DistributedRuntime::new(runtime, dt_config).await?;
//let d_runtime = triton_distributed::DistributedRuntime::new(runtime, dt_config).await?;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you elaborate a bit on the implications of this? For example, with the distributed_runtime included, would you be able to hook up components exposed run by tio with llmctl or other tooling, and with these commented out, would they no longer be discoverable? Looking for high level ideas to learn more about how the moving parts relate to each other

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are no implications. We were creating a DistributedRuntime but not using any parts of it.

Currently there are no components and no discovery. Once we start doing out=nats we will want the distributed runtime, so I left it in commented out.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, thanks Graham!

@grahamking grahamking merged commit 424129d into main Feb 18, 2025
6 checks passed
@grahamking grahamking deleted the gk-offline-tio branch February 18, 2025 18:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants