first done

content/docs/federated-core-platform/management/_index.md

@@ -0,0 +1,10 @@
+---
+weight: 120
+title: "Management"
+description: ""
+icon: "article"
+date: "2025-08-26T14:35:18-06:00"
+lastmod: "2025-08-26T14:35:18-06:00"
+draft: false
+toc: true
+---

content/docs/federated-core-platform/management/core-scanner.md

@@ -0,0 +1,18 @@
+---
+weight: 121
+title: "Core Scanner"
+description: ""
+icon: "article"
+date: "2025-08-25T12:34:24-06:00"
+lastmod: "2025-08-25T12:34:24-06:00"
+draft: false
+toc: true
+---
+
+Core Scanner is a utility to examine and manage each Core on a given installation of Federated Core Platform. It allows a customer service person to examine the Core, look at all the configuration files, see any anomalies in the files, track usage of resources (CPU, RAM, storage, network), and perform tightly managed actions on the Core to take remedial steps as needed.
+
+Each installation of Core Scanner includes user and group priveleges so that the owner of the Federated Core Platform can look at all Cores running, but also partners can examine and manage the Cores of their customers. For example, a managed service provider may have a number of Cores for which they will want to be able to provide monitor and fix service3. Core Scanner allows them to see those Cores, only.
+
+Core Scanner provides the ability to "take action" on a Core with a large library of pre-defined "actions" for each Core depending on the applications installed and the reality of the Core at the time of inspection. If a Core needs more storage, for example, "actions" are brought forward suggesting remedial action to the support person. There are also actions available to compare a given Core to normative Cores.
+
+Core Scanner is supported by the "machine learning" functions in the [Update and Upgrade](update-and-upgrade.md) and [Monitor and Fix](monitor-and-fix.md) systems.

content/docs/federated-core-platform/management/monitor-and-fix.md

@@ -0,0 +1,16 @@
+---
+weight: 123
+title: "Monitor and Fix"
+description: ""
+icon: "article"
+date: "2025-08-25T12:35:43-06:00"
+lastmod: "2025-08-25T12:35:43-06:00"
+draft: false
+toc: true
+---
+
+Every Core running on an installation of Federated Core Platform, every application running on every Core, and every service not an application running on every Core, is monitored in real time to ensure it runs, has the system resources needed, and provides customers with the best experience. If there are anomalies detected, alerts are created and can be sent to the local Matrix server, and Federated Monitor and Fix system attempts to solve the problem using patterns and the service definitions in place.
+
+For example, if a customer with a 500GB storage limit for their Files service decides to upload 3TB of files, the File service will fail, and Monitor and Fix will attempt to fix the problem by adding for block storage (if that service is available AND the service definition allows that to happen without customer "approval").
+
+The Monitor and Fix system continues to get better and better as we see more patterns and improve the paths to successful amelioration of problems.

content/docs/federated-core-platform/management/update-and-upgrade.md

@@ -0,0 +1,16 @@
+---
+weight: 122
+title: "Update and Upgrade"
+description: ""
+icon: "article"
+date: "2025-08-25T12:36:19-06:00"
+lastmod: "2025-08-25T12:36:19-06:00"
+draft: false
+toc: true
+---
+
+Each Federated Core Platform installation has a Gitea respository where the software (OS, utilities, platform, open source SaaS) for the entire system is tracked. The operator of each installation is able to package those updates into regular upgrades pushed out to some/all Cores on the system, push them out individually for testing to some Cores, or schedule updates for a given list of Cores.
+
+Since the nature of the Federated Core Platform is delivering open source SaaS to customers, there needs to be a testing protocol set up to ensure updates are in fact needed/wanted. Federated Computer does this centrally, so operators using Federated Core Platform can know the software will "work". However, there may be additional concerns with respect to security, other customizations that need to be tested, etc.
+
+While Federated Core Platform draws much of the software from DockerHub, there are container images maintained by Federated Computer and, over time, more of the container images will come from Federated Computer rather than DockerHub. The principle reason for this is to add an additional step for quality and security.