FL Server Create
π‘ Overview
This guide walks you through creating a task and running the FL Server using the MNIST example.
Differences from FedOps 1.1.2
- In 1.1.2, the FL server ran as a Kubernetes Job, so it terminated when an FL run finished, making post-run management and log inspection difficult. Code was managed via Git, which made debugging and fixes harder. In 1.2, the server runs as a Pod with dedicated resources for the FL server, making code management, debugging, and log inspection much easier.
- In 1.1.2, there were no management features for the FL server, so resource scaling and file browsing were not possible. In 1.2, you can scale resources, browse files, and execute commands, making server management easier.
- When creating a task, options are collected from the user and applied automatically, preventing typos and missing required fields in the initial config.
Steps
To create an FL server, first create a task in the FedOps web UI.
.png)
- Click Task on the top navigation bar to open the Task management page.
- Click the + button in the top-right corner to open the create-task page.
On the create-task page, enter a title and click Create to make an FL task with default settings.
.png)
Click Create Scalable Server to create the FL server.
.png)
- By default, the Scalable Server is provisioned with 1 CPU and 2 Gi of memory. You can change these in Resource Scaling and apply them with Scale Resources.
Once server creation starts successfully, the FL Status will change. (Click Refresh Status to update the status.)
.png)
You can check the environment setup logs via Server Logs. When setup completes, the FL Status shows βFL Server created.β (Click Refresh Logs to update the logs.)
.png)
- The created serverβs file structure is as follows.
models.pyanddata_preparation.pyinclude default MNIST example code.conf/config.yamlis populated with the options you set when creating the task.app/code/ βββ client_main.py βββ client_manager_main.py βββ data_preparation.py βββ models.py βββ server_main.py βββ requirements.txt βββ conf βββ config.yaml Click Start FL Server to launch the FL Server.
.png)
- The FL serverβs runtime logs are saved to /app/data/logs/serverlog.txt. Use File Content to view the serverβs logs.
- Stop FL Server terminates the running FL Server process.