Skip to content

RoboVAST 2.2.0

Choose a tag to compare

@fred-labs fred-labs released this 25 Sep 06:25
· 17 commits to main since this release
230d150
pip install robovast-client              # drive a RoboVAST service someone runs for you
pip install "robovast[nav,roqsim]"       # the core: configuration, results, the MCP server
pip install robovast-cluster             # deploy and run the service on a Kubernetes cluster

Then vast cluster setup deploys the service — into minikube on your own machine, or a cluster for a team. Container images for this version, tagged 2.2.0: ghcr.io/cps-test-lab/robovast and robovast-roqsim for linux/amd64 and linux/arm64, and robovast-controller and robovast-sidecar, which run only in the cluster, for linux/amd64.

What changed

  • Local Docker lane removed — campaigns run on a Kubernetes cluster, on one machine a minikube or kind; vast serve needs robovast-cluster
    (#675)
  • Settings refused — a .vast that sets execution.local or show_gui is refused, since nothing reads them
    (#675)
  • Navigation MCP tools retired — core answers them for any robot: pose_track_view, get_track_deviation, get_config_contribution, draw_config
    (#640)
  • Pinned deployments — the admin page offers Upgrade only on a tag CI moves; move a pinned version with vast service upgrade
    (#691)
  • Workspace archives — download, share and re-create a workspace as one archive
    (#657)
  • Simulator docs from the image — a simulator's documentation and spawnable components are read from the image that runs them
    (#521, #526, #683)
  • Campaign management — delete several campaigns at once, and sort the list by recency or size
    (#648, #646)
  • Stopping — a stop takes effect in every wait, and a campaign's auxiliary containers end with it
    (#616, #618)
  • Parallel postprocessing — a campaign's postprocessing is split across Jobs, per run where a plugin allows it
    (#601)
  • Simulator provenance — a campaign records which simulator commit it ran, and flags images built from different ones
    (#660)
  • Run view — a Run-view button on the campaign card, and the costmap panel drawn onto a rendered video
    (#643, #578)
  • TurtleBot 4 in the images — the roqsim image carries the Create 3 / TurtleBot 4 stack
    (#633, #664)