Installation workflow review

Embedding applications requires a similar workflow to embedding MicroShift into a RHEL for Edge image.

  • The following image shows how system artifacts such as RPMs, containers, and files are added to a blueprint and used by the image composer to create an ostree commit.

  • The ostree commit then can follow either the ISO path or the repository path to edge devices.

  • The ISO path can be used for disconnected environments, while the repository path is often used in places were the network is usually connected.

Embedding MicroShift workflow

468 RHbM install workflow 1023 1

Reviewing these steps can help you understand the steps needed to embed an application:

  1. To embed MicroShift on RHEL for Edge, you added the MicroShift repositories to image builder.

  2. You created a blueprint that declared all the RPMs, container images, files and customizations you needed, including the addition of MicroShift.

  3. You added the blueprint to image builder and ran a build with the image builder CLI tool (composer-cli). This step created rpm-ostree commits, which were used to create the container image. This image contained RHEL for Edge.

  4. You added the installer blueprint to image builder to create an rpm-ostree image (ISO) to boot from. This build contained both RHEL for Edge and MicroShift.

  5. You downloaded the ISO with MicroShift embedded, prepared it for use, provisioned it, then installed it onto your edge devices.

↑ Up: Embed application RPMs tutorial | ⌂ Home: Red Hat build of MicroShift | Next: Embed application RPMs workflow →