Title here
Summary here
FLOps Projects Overview
This Guide’s Goals
- Get you doing FL as quickly as possible
- Help you understand the basic FLOps project workflow
This guide uses predefined SLAs and ML Git repositories provided by the oak-cli to streamline the necessary steps. This base case is intended to run on a single machine to make it as easy as possible to follow along.
To create and use custom SLAs and ML Git repositories, please familiarize yourself with this base case and read the dedicated FLOps customization documentation.
What is a FLOps Project?
A FLOps project links all necessary FL and ML/DevOps components to power one FL user request.
A project contains information about:
- The user who requested it
- The target platforms that should be supported (e.g., ARM/AMD)
- What steps FLOps should perform after training.
- etc.
Projects are based on the SLA you use - they can vary in:
- ML Training Code (Git Repository)
- Requested Data (data-tags)
- FL Training Configuration
- Number of training rounds
- Number of Learners
- etc.
- FL Strategy (classic or clustered hierarchical)
- etc.
Running a basic FLOps Project
Requirements
- You have a running Oakestra deployment with at least one Worker Node with a registered NetManager.
- You have prepared your system to use FLOps.