mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
45 lines
3.3 KiB
Plaintext
45 lines
3.3 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// microshift_running_applications/embedding-apps-tutorial.adoc
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="microshift-embed-app-rpms-tutorial_{context}"]
|
|
= Embed application RPMs tutorial
|
|
|
|
The following tutorial reviews the {microshift-short} installation steps and adds a description of the workflow for embedding applications. If you are already familiar with `rpm-ostree` systems such as {op-system-ostree-first} and {microshift-short}, you can go straight to the procedures.
|
|
|
|
[id="microshift-installation-workflow-review_{context}"]
|
|
== Installation workflow review
|
|
Embedding applications requires a similar workflow to embedding {microshift-short} into a {op-system-ostree} 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-short} workflow
|
|
image:468_RHbM_install_workflow_1023_1.png[title="Embedding MicroShift in a RHEL for Edge image workflow."]
|
|
|
|
Reviewing these steps can help you understand the steps needed to embed an application:
|
|
|
|
. To embed {microshift-short} on {op-system-ostree}, you added the {microshift-short} repositories to Image Builder.
|
|
|
|
. You created a blueprint that declared all the RPMs, container images, files and customizations you needed, including the addition of {microshift-short}.
|
|
|
|
. 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 {op-system-ostree}.
|
|
|
|
. You added the installer blueprint to Image Builder to create an `rpm-ostree` image (ISO) to boot from. This build contained both {op-system-ostree} and {microshift-short}.
|
|
|
|
. You downloaded the ISO with {microshift-short} embedded, prepared it for use, provisioned it, then installed it onto your edge devices.
|
|
|
|
[id="microshift-embed-app-rpms-workflow_{context}"]
|
|
== Embed application RPMs workflow
|
|
|
|
After you have set up a build host that meets the Image Builder requirements, you can add your application in the form of a directory of manifests to the image. After those steps, the simplest way to embed your application or workload into a new ISO is to create your own RPMs that include the manifests. Your application RPMs contain all of the configuration files describing your deployment.
|
|
|
|
The following "Embedding applications workflow" image shows how Kubernetes application manifests and RPM spec files are combined in a single application RPM build. This build becomes the RPM artifact included in the workflow for embedding {microshift-short} in an ostree commit.
|
|
|
|
.Embedding applications workflow
|
|
image:468_RHbM_install_workflow_1023_2.png[title="Embedding applications workflow."]
|
|
|
|
The following procedures use the `rpmbuild` tool to create a specification file and local repository. The specification file defines how the package is built, moving your application manifests to the correct location inside the RPM package for {microshift-short} to pick them up. That RPM package is then embedded in the ISO.
|