Beta#
The beta is closed and invite-only.
What it is for#
One thing, mostly: the image has been booted on physical hardware, but a complete install to disk followed by a reboot into the installed system is not recorded on any real machine. Every end-to-end verification in the project names a virtual machine.
Seats go to operators willing to install on real hardware and report what breaks. That is the gap that stands between "demonstrated" and "deployable", and it cannot be closed from a bench.
What a useful report contains#
If you install on hardware, the information this project is missing is:
- the board or appliance model;
- the network controllers —
lspci -nn | grep -i net; - whether Secure Boot had to be turned off;
- whether every port appeared, and under which driver;
- whether the install completed and the machine came back up into the installed system.
That is exactly what turns "should work" into a list, and there is no list today.
What you would be running#
Read what is finished and what is not first, in full. The parts most likely to affect a beta installation:
- no rescue boot entry and no factory reset, so a lockout means a console session;
- no in-place upgrade on record;
- no release signature, so a checksum is the whole verification story;
- IPv6 configurable but not observable;
- app images on floating tags.
What is not decided#
In the meantime#
Install it in a virtual machine. That is the path with the evidence behind it, it exercises the same installer, the same units and the same first-boot sequence as the metal, and it will tell you within an hour whether the product is the shape you want.
Download an image What is finished, and what is not