Merge branch 'main' into ITEP-78714-install-completion-output

Author: yockgen

.github/workflows/boot_tester.yml

@@ -0,0 +1,54 @@
+name: Boot Tester
+on:
+  schedule:
+    # Run twice a week: Tuesdays at 02:00 UTC and Fridays at 02:00 UTC
+    - cron: '0 2 * * 2'  # Tuesday at 2 AM UTC
+    - cron: '0 2 * * 5'  # Friday at 2 AM UTC
+  workflow_dispatch: {}
+    # Allow manual triggering of the workflow
+permissions:
+  contents: read
+jobs:
+  boot-test:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+        with:
+          persist-credentials: false
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v3
+
+      - name: Install Earthly
+        uses: earthly/actions-setup@v1
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          version: "latest" # or pin to a specific version like "v0.8.0"
+
+      - name: Install system deps
+        run: |
+          sudo apt-get update
+          sudo apt-get install -y qemu-system-x86 ovmf tree jq systemd-ukify mmdebstrap systemd-boot
+
+      - name: Set up Go
+        uses: actions/setup-go@v5
+        with:
+          go-version: stable  # or a pinned version you know exists
+
+      - name: Copy tester script
+        run: |
+          if [ ! -f validate.sh ]; then
+            echo "validate.sh not found!"
+            exit 1
+          fi
+          chmod +x validate.sh
+
+      - name: Run build-tester
+        run: |
+          echo "Starting validate.sh..."
+          # Ensure script has access to docker group for Earthly
+          sudo usermod -aG docker $USER
+          # Run the validation script
+          ./validate.sh --qemu-test
+          echo "Build and tests completed."

docs/architecture/architecture.md

@@ -70,7 +70,17 @@ The following diagram shows the network context of the OS Image Composer tool:
 ![OS Image Composer Network Diagram](assets/os-image-composer-network-diagram.drawio.svg).
 
 The diagram illustrates how different components of the product's system
-architecture communicate with each other.
+architecture communicate with each other as well as the flow of setup and
+deployment process:
+
+1. Clone image composer tool repository from Intel Open Edge Platform
+2. Install or Build the Image Composer Tool to the target architecture.
+3. Use the Image Composer Tool to compose your custom OS Image for the desired
+   OS distribution. The remote package repositories perform server side
+   validation on the HTTPS requests from the image composer tool. Integrity of
+   each downloaded package is verified using authenticated GPG keys.
+4. Deploy the composed OS Image on edge node using your preferred
+   deployment method.
 
 ### Network Security Considerations
 
@@ -94,16 +104,16 @@ the OS Image Composer tool:
 
 The tools for composing an image are grouped under following components:
 **Provider**, **Chroot**, **Image**, **OsPackage**, and **Config**.
-For modularity, each group contains a set of the components for
-the OS Image Composer tool's functions.
+For modularity, each group contains a set of the components for the
+OS Image Composer tool's functions.
 
 The **provider** component takes data from *config* as its input, then calls
-**chroot**, **image** and **OsPackage** components to set up buidling the image.
+**chroot**, **image** and **OsPackage** components to set up building the image.
 **Chroot** libraries are used to create ChrootEnv for building the OS Image.
 The **image** libraries provide the general functions for building OS images.
-The **OsPackage** libraries include utilities for handling debian and
-rpm packages. The **config** component contains configuration data for the image
-that will be created.
+The **OsPackage** libraries include utilities for handling debian and rpm packages.
+The **config** component contains configuration data for the image that will be
+created.
 
 ### Chroot
 
@@ -139,15 +149,15 @@ distribution-specific functionality from the core and common business logic.-->
 
 ![components - package](assets/components.drawio.OsPackage.svg)
 
-*Package* groups the libraries that provide the unified interface of the
+*OsPackage* groups the libraries that provide the unified interface of the
 operating system vendors' remote package repositories. It analyzes given
 package lists and downloads all the packages and dependencies from the target
 operating system's remote package repository to a local cache.
 
 It also verifies signatures of the downloaded packages to ensure they are
-authenticated and from certified source. It also provides the unified interface
-to install the packages and the dependencies in the correct order into the
-image rootfs directory.
+authenticated and from a certified source. It also provides the unified
+interface to install the packages and the dependencies in the correct order
+into the image rootfs directory.
 
 ## Operational Flow