Skip to content

ci(tests): run the Docker driver as an external service in tmachine conformance #5602

Closed

Description

@elezar

User Story

As a maintainer moving the compute drivers out of this repository (#5200), I want
OpenShell CI to run a driver as an external service against the packaged gateway
on tmachine, so that external drivers are tested the way operators run them.

Problem Statement

docker-external-driver-e2e runs the Docker conformance tests against a
driver-free gateway and a driver that e2e/with-docker-gateway.sh starts from a
shell. That lane:

  • does not use the packaged gateway, its service, or its TLS setup;
  • needs its own copy of the gateway and driver wiring in the shell wrapper;
  • cannot be reused by a driver built elsewhere, which is where drivers are going.

tmachine already installs the packaged gateway and runs the conformance family,
but it has no way to run a compute driver as a separate service.

Proposed Design

  • Add a tmachine role that installs a driver binary and a system service, waits
    for its socket, and points the packaged gateway at it by name.
  • Have the packaged gateway role start it after the runtime images load and
    before the gateway starts.
  • Add a deb-external-docker-driver installer and run the conformance family
    with it on ubuntu-docker-rootful.
  • Build the driver in build-external-drivers and pass it to tmachine through
    the integration inputs, opt-in so the release workflows are unchanged.
  • Remove docker-external-driver-e2e once the tmachine row replaces it.

Acceptance Criteria

  • The conformance family passes on tmachine with openshell-driver-docker running
    as an external service against the packaged gateway.
  • docker-external-driver-e2e and its task and wrapper branches are removed.
  • The Podman and Kubernetes external-driver lanes are unchanged; they follow in
    separate changes.

Alternatives Considered

  • Keep the shell-wrapper lanes. They duplicate gateway setup and don't exercise
    the packaged gateway.
  • Run external drivers only from their own repositories. This still needs a way
    to run them in tmachine, and the in-tree lane is the reference for it.

Related: #5200, #4848.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions