diff --git a/docs/developer-guide/assets/emt-luks-setup.drawio.svg b/docs/developer-guide/assets/emt-luks-setup.drawio.svg index 4fe96415fe..304cad5327 100644 --- a/docs/developer-guide/assets/emt-luks-setup.drawio.svg +++ b/docs/developer-guide/assets/emt-luks-setup.drawio.svg @@ -1,4 +1,4 @@ -
Edge MIcrovisor Setup
Edge Manageability Framework
Set up
Edge Manageability Framework
Trusted Platform Module
LUKS key access denied
Edge Device
in ready state
Partition
physical discs
Enable LUKS on all partitions
Install Edge Microvisor
Deploy Application
Enable LUKS
Reboot
Generate and store LUKS key
Retrieve LUKS key
Lock-out LUKS key access
\ No newline at end of file +
Edge MIcrovisor Toolkit Setup
Edge MIcrovisor Toolkit Setup
Edge Manageability Framework
Edge Manageability F...
Set up
Edge Manageability Framework
Set up...
Trusted Platform Module
Trusted Platform Mod...
LUKS key access denied
LUKS key access denied
Edge Device
in ready state
Edge Device...
Partition
physical discs
Partition...
Enable LUKS on all partitions
Enable LUKS on all p...
Install Edge Microvisor Toolkit
Install Edge Microvi...
Deploy Application
Deploy Application
Enable LUKS
Enable LUKS
Reboot
Reboot
Generate and store LUKS key
Generate and store LUKS key
Retrieve LUKS key
Retrieve LUKS key
Lock-out LUKS key access
Lock-out LUKS key access
Text is not SVG - cannot display
\ No newline at end of file diff --git a/docs/developer-guide/emt-bootkit.md b/docs/developer-guide/emt-bootkit.md index 0b8f9b22b2..ffddae7c86 100644 --- a/docs/developer-guide/emt-bootkit.md +++ b/docs/developer-guide/emt-bootkit.md @@ -54,7 +54,7 @@ root=tmpfs rootflags=mode=0755 rd.skipfsck noresume modules-load=nbd The generated `initramfs` and `vmlinuz` images can be used for implementing required customizations in [Edge Manageability Framework](#orchestrator-build-with-bootkit-new-workflow) -or [Edge Microvisor Toolkit Standalone Node](#microvisor-build-with-bootkit-new-workflow) builds. +or [Edge Microvisor Toolkit Standalone Node](#edge-microvisor-toolkit-build-with-bootkit-new-workflow) builds. ## Integration with Edge Manageability Framework and Edge Microvisor Toolkit Standalone Node @@ -119,7 +119,7 @@ file during the building process: ## Edge Microvisor Toolkit Standalone Node Specific Builds -### Microvisor Build with HookOS (previous workflow) +### Edge Microvisor Toolkit Build with HookOS (previous workflow) In [Edge Microvisor Toolkit Standalone Node](https://github.com/open-edge-platform/edge-microvisor-toolkit-standalone-node), HookOS sources, separate from the ones in Edge Manageability Framework, were implemented to @@ -132,7 +132,7 @@ The customized HookOS `initramfs` and `vmlinuz` were then used to generate the r ISO for the USB installer of [Edge Microvisor Toolkit Standalone Node](https://github.com/open-edge-platform/edge-microvisor-toolkit-standalone-node). -### Microvisor Build with Bootkit (new workflow) +### Edge Microvisor Toolkit Build with Bootkit (new workflow) When using Edge Microvisor Bootkit in the build workflow, the following components are added to run as native systemd services in the `initramfs` image: diff --git a/docs/developer-guide/get-started/emt-build-and-deploy.md b/docs/developer-guide/get-started/emt-build-and-deploy.md index b079718c31..bf8ac685b0 100644 --- a/docs/developer-guide/get-started/emt-build-and-deploy.md +++ b/docs/developer-guide/get-started/emt-build-and-deploy.md @@ -9,11 +9,11 @@ meet specific edge deployment needs. You can choose between: - **Edge Microvisor Toolkit Non-Real-Time image** (default) - **Edge Microvisor Toolkit Desktop Virtualization image** -- **Custom immutable Edge Microvisor Toolkit created using** [Build Instructions](#1-build-the-microvisor) +- **Custom immutable Edge Microvisor Toolkit created using** [Build Instructions](#1-build-the-edge-microvisor-toolkit) **Table of contents:** -1. [Build a custom image of Edge Microvisor Toolkit.](#1-build-the-microvisor) +1. [Build a custom image of Edge Microvisor Toolkit.](#1-build-the-edge-microvisor-toolkit) 2. [Create a bootable USB installer.](#2-create-a-bootable-usb-installer) 3. [Install the toolkit on an edge device.](#3-install-the-toolkit-on-an-edge-device) 4. [Deploy AI solution.](#4-deploy-ai-solution) @@ -23,11 +23,11 @@ meet specific edge deployment needs. You can choose between: Make sure your machine meets the [minimum hardware configuration](../emt-system-requirements.md#minimum-hardware-configuration-for-building-os-image). -## 1. Build the microvisor +## 1. Build the Edge Microvisor Toolkit If you want to create your own custom standalone node, follow the instructions below to build -the Edge Microvisor from scratch. If you wish to use the default, non-real-time image of Edge Microvisor -skip to [Create a bootable USB installer](#2-create-a-bootable-usb-installer). +the Edge Microvisor Toolkit from scratch. If you wish to use the default, non-real-time image +of Edge Microvisor Toolkit skip to [Create a bootable USB installer](#2-create-a-bootable-usb-installer). All available image configurations are stored in JSON files, located in the `imageconfigs` folder. If you want to configure any additional kernel command line arguments, follow the instructions in @@ -363,7 +363,7 @@ Replace `/dev/sdX` with the device name of your USB drive. If you want to use the default non-RT image, [proceed with installation](#3-install-the-toolkit-on-an-edge-device), as the `usb-bootable-files.tar.gz` file already includes this image. - To install [custom build image](#1-build-the-microvisor), or the image with desktop + To install [custom build image](#1-build-the-edge-microvisor-toolkit), or the image with desktop virtualization features (DV) you need to copy it manually to the 5th partition of the USB drive, replacing the default non-RT one. Follow the instructions below: diff --git a/docs/developer-guide/security-considerations/emt-sb-howto.md b/docs/developer-guide/security-considerations/emt-sb-howto.md index ed76c811f9..afa8c9808f 100644 --- a/docs/developer-guide/security-considerations/emt-sb-howto.md +++ b/docs/developer-guide/security-considerations/emt-sb-howto.md @@ -7,11 +7,11 @@ it is protected against advanced attacks. Here are the steps required to do so, generating local signing certificates, rebuilding packages, and testing the secure boot functionality. - [RAW or VHD/X](#raw-and-vhd-image) - configure BIOS with signed production keys of -a RAW/VHD Edge Microvisor image. +a RAW/VHD Edge Microvisor Toolkit image. ## RAW and VHD Image -Production images of Edge Microvisor are signed by Intel. Secure Boot prevents +Production images of Edge Microvisor Toolkit are signed by Intel. Secure Boot prevents unauthorized bootloaders and operating systems from starting, ensuring that only code signed with a trusted key is executed. For custom signed OS images, you need to enroll your certificate into the firmware’s trusted key database.