Provision and maintain AutoSD¶

After building your AutoSD image, you need to flash it onto your target hardware and keep the system up to date over its lifecycle.

Provision hardware¶

You can provision your OS image onto the following hardware platforms:

Note

For x86_64 targets, boot your image directly with air or QEMU. No hardware-specific flashing procedure is required.

Maintain deployed systems¶

AutoSD uses bootc update mechanisms for keeping deployed systems current. For details on how immutable updates work underneath, see Immutable system images with OSTree.

Important

AutoSD is the public preview of the Red Hat In-Vehicle Operating System (RHIVOS) product and contains all of the technology and tools necessary to run a mixed-criticality workload on that safety certified product. The documentation on this page presents the technology underlying and available in the product, but all safety requirements and documents are not covered here and are available only to RHIVOS customers. These safety documents impose some limitations and additional activities necessary for safety workloads.