Support internal_ip
for SSH fleet clusters
It's now possible to specify instance IP addresses used for communication inside SSH fleet clusters using the internal_ip
property:
type: fleet
name: my-ssh-fleet
placement: cluster
ssh_config:
user: ubuntu
identity_file: ~/.ssh/dstack/key.pem
hosts:
- hostname: "3.79.203.200"
internal_ip: "172.17.0.1"
- hostname: "18.184.67.100"
internal_ip: "172.18.0.2"
If internal_ip
is not specified, dstack
automatically detects internal IPs by inspecting network interfaces. This works when all instances have IPs belonging to the same subnet and are accessible on those IPs. The explicitly specified internal_ip
enables networking configurations when the instances are accessible on IPs that do not belong to the same subnet.
UX enhancements for dstack apply
The dstack apply
command gets many improvements including more concise and consistent output and better error reporting. When applying run configurations, dstack apply
now prints a table similar to the dstack ps
output:
✗ dstack apply
Project main
User admin
...
Submit a new run? [y/n]: y
NAME BACKEND RESOURCES PRICE STATUS SUBMITTED
spicy-tiger-1 gcp 2xCPU, 8GB, $0.06701 running 14:52
(us-central1) 100.0GB (disk)
spicy-tiger-1 provisioning completed (running)
What's Changed
- [UX]: live table when provisioning dstack configuration runs #1978 by @Tob-iee in #2036
- Fix returning metrics from deleted runs by @jvstme in #2038
- [UI] Migrate the chat components to the new CloudScape chat componets by @olgenn in #2044
- Recover unreachable instances by @un-def in #2043
- UX enhancements for
dstack apply
by @jvstme in #2045 - Implement /api/fleets/list endpoint by @r4victor in #2050
- Remove padding in
dstack apply
live tables by @jvstme in #2048 - Fix typo in
dstack attach --help
by @jvstme in #2054 - Support specifying internal_ip for SSH fleet hosts by @r4victor in #2056
New Contributors
Full Changelog: 0.18.28...0.18.29