Skip to content

VBMCTL: Tracking improvements to make it worthy of including in release artifacts #2751

@lentzi90

Description

@lentzi90

We currently use vbmctl for the e2e tests. It works well for this but there are several things we could improve on. I would like to make this tool useful also for development, especially with Tilt, or as a simple demo setup. Ideally it should be as simple to use as kind.

In addition to this, we may also need more features to make it more useful outside of BMO, for example in CAPM3 e2e tests.

This is a tracking issue for these improvements.

  • Support cleanup. We currently use a separate cleanup script. This should be handled by vbmctl instead.
  • Setup network. This is currently done in a script for CI. We should include this in vbmctl and also try to simplify it if possible.
  • Handle BMC emulators. It should be possible to setup sushy-tools (maybe also vbmc) using vbmctl directly instead of separately, as we do in CI.
  • Similarly, the image server would be handy to setup directly through vbmctl.
  • Make the VM volumes configurable.
  • Make the VM memory and CPU configurable.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/ciCategorizes issue or PR as related to CI or testing.triage/acceptedIndicates an issue is ready to be actively worked on.

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions