<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Devices &amp; SPEKTRA Edge OS on SPEKTRA Edge</title>
    <link>https://docs.edgelq.com/learn/devices/</link>
    <description>Recent content in Devices &amp; SPEKTRA Edge OS on SPEKTRA Edge</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://docs.edgelq.com/learn/devices/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Overview</title>
      <link>https://docs.edgelq.com/learn/devices/overview/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.edgelq.com/learn/devices/overview/</guid>
      <description>This section explains the ideas you need before configuring a device: how the OS is structured, how persistence works, and which platforms are supported.&#xA;A managed, reconciled operating system SPEKTRA Edge OS is designed to be operated remotely and at scale. Instead of logging into each device to make changes by hand, you describe the desired state of a device on the SPEKTRA Edge platform, and the device continuously reconciles itself to match.</description>
    </item>
    <item>
      <title>Device setup &amp; provisioning</title>
      <link>https://docs.edgelq.com/learn/devices/provisioning/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.edgelq.com/learn/devices/provisioning/</guid>
      <description>This section takes a device from blank hardware to a managed device: creating an install image, onboarding the device so it joins your project, setting the administrator password, and confirming it is online.&#xA;Setup at a glance Create an install image for the target device type, with the defaults you want baked in (encryption, network, storage, time). Write the image to installation media and boot the device from it. Onboard the device so it obtains an identity and joins your project.</description>
    </item>
    <item>
      <title>Install the droplet agent (.deb package)</title>
      <link>https://docs.edgelq.com/learn/devices/install-agent-deb/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.edgelq.com/learn/devices/install-agent-deb/</guid>
      <description>Most fleets run the purpose-built SPEKTRA Edge OS image. If instead you want to bring an existing Debian/Ubuntu Linux under management, you can install the droplet agent from a .deb package. The machine then joins your project and runs managed workloads, while you keep your own operating system.&#xA;This page walks you through the whole flow: install the package, create a provisioning policy and a service account, grant the service account a role, download its key, convert the key into a project_config.</description>
    </item>
    <item>
      <title>Storage</title>
      <link>https://docs.edgelq.com/learn/devices/storage/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.edgelq.com/learn/devices/storage/</guid>
      <description>This section describes how device storage is laid out by default and how to add your own partitions and mounts or expand storage to use the whole disk.&#xA;Default disk layout A device&amp;rsquo;s primary disk is divided into a small number of areas, each with a distinct role:&#xA;Area Role Persistent Encrypted by default Boot Files required to start the device Yes No Configuration Device settings, identity, administrator password, hooks Yes Yes (when encryption is enabled) System images The OS image(s) used to boot, including the version you can roll back to Yes No Data Container images, workload data, and logs Yes Yes (when encryption is enabled) The data area takes the remaining space on the disk, so most of the disk is available to your workloads.</description>
    </item>
    <item>
      <title>Troubleshooting</title>
      <link>https://docs.edgelq.com/learn/devices/troubleshooting/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.edgelq.com/learn/devices/troubleshooting/</guid>
      <description>Playbooks for the problems you are most likely to hit. Each lists the usual causes in the order worth checking.&#xA;A device will not come online Connectivity. Confirm outbound TCP 443 to the platform is allowed (directly or via proxy). See Connectivity &amp;amp; ports. Time. A badly wrong clock breaks secure connections and attestation. Ensure the device can reach an NTP source — see Time synchronization. Network configuration. A recent network change may have broken connectivity; the device should fall back to its image network settings unless fallback is disabled.</description>
    </item>
  </channel>
</rss>
