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

compute: Build VM images suitable for lauching with neonvm-guest #10456

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

hlinnaka
Copy link
Contributor

The 'legacy-vm-builder-image' Dockerfile target can still be used to
build an old-style VM image, for use with vm-builder. And that's still
the default target. However, there are now ano other target,
'compute-node-bootable', that can be used to build an image that
includes systemd unit files to launch the services, and
'compute-node-neonvm-payload' to package that as a QCOW2 image that
can be used with the new neon-vm launcher.

See neondatabase/autoscaling#1211 for the new
launcher. That's a requirement for using the new-style images.

This avoids the slow recompilation of the docker layers, if some
unrelated files are modified.
I don't see the point of that, postgres itself and many of the
extensions are already built dynamically.

The immediate reason to make the switch is that I intend to add the
--with-systemd flag, and there don't seem to be a static version of
that (at least not on Debian).
…guest

The 'legacy-vm-builder-image' Dockerfile target can still be used to
build an old-style VM image, for use with vm-builder. And that's still
the default target. However, there are now ano other target,
'compute-node-bootable', that can be used to build an image that
includes systemd unit files to launch the services, and
'compute-node-neonvm-payload' to package that as a QCOW2 image that
can be used with the new neon-vm launcher.

See neondatabase/autoscaling#1211 for the new
launcher.
Copy link

7359 tests run: 6979 passed, 0 failed, 380 skipped (full report)


Flaky tests (3)

Postgres 17

Postgres 15

Postgres 14

Code coverage* (full report)

  • functions: 33.6% (8442 of 25114 functions)
  • lines: 49.2% (70793 of 143970 lines)

* collected from Rust tests only


The comment gets automatically updated with the latest test results
ed5efbd at 2025-01-20T22:39:20.845Z :recycle:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant