Skip to content

Releases: NVIDIA/NVFlare

2.5.2

14 Dec 02:04
3276960
Compare
Choose a tag to compare

Contributions

Special thanks to all the contributors for this release (in git shortlog order):
@IsaacYangSLA, @yhwen @yanchengnv, @nvidianz @YuanTingHsieh

What's New

In this release, we have introduced several exciting new features and enhancements, building on the foundation of version 2.5.1. Key updates include:

Extended Python Version Support (2.5.1)

We now support a broader range of Python versions, from 3.9 to 3.12, ensuring greater compatibility and flexibility for your development needs.

Secure Federated XGBoost Enhancements

Please see this note

The Secure Federated XGBoost framework has been significantly improved with optimizations to the CUDA Paillier Plugin:

New Parallel CUDA-Based Reduction Algorithm:

Version 2 of the CUDA Paillier Plugin introduces a cutting-edge parallel reduction algorithm. This improvement:

  • Doubles the performance speed compared to version 1 on specific datasets (e.g., small feature sets with a large number of rows).
    Dramatically enhances efficiency in datasets with a wide number of features (over 2000 features).
  • Parameter Conversion Optimization: We have reduced unnecessary parameter conversions, streamlining the overall performance.

Performance Benchmarks:

Benchmarks conducted on the V100 GPU highlight the remarkable improvements achieved with these enhancements:

  • For small feature datasets, our solution is 30x to 36.5x faster compared to third-party CPU-based implementations.
  • For wide-feature datasets, we maintain a competitive edge, being 4.6x faster.
    The CPU-based plugin is also optimized to reduce the memory usage during ciphertext operations by utilizing shared memory.
Screen Shot 2024-12-13 at 8 43 28 PM

End-to-end fraud detection example enhancements

In addition to the existing manual feature engineering, we add example to use Graph Embedding to feed to XGBoost, the embedding as new features works better than manual feature enrichment
We also showed how to use Federated explainability for Fed XGBoost

Support Normal TLS & signed messages

By default NVIDIA FLARE supports mutual TLS (mTLS) connection. There is a need for some customers to use normal TLS. In this release, we added the normal TLS support

Description
Currently Flare's message security comes from mutual TLS: server and client authenticate each other when making connections. This means that only clients that have the right startup kits can make a connection to the server.
The requirement of one-way SSL between the server and clients breaks this assumption: the server could be exposed to the internet and any one could write a client to connect to the server. To ensure message security, explicit message authentication is required.
This PR implements message authentication: messages received by the server must have an auth token, and the token must be validated successfully to prove that it was issued by the server!

Here is how it works:
The client first tries to login to the server. The server/client authenticate each other explicitly with the credentials in their startup kits. This step is independent of how client/server is connected.
If the client credential is validated correctly, the server issues a token and a signature that binds the client name and token together. The signature is generated with the server's private key to prove that the signature can only be issued by the server.
When sending a message to the server, the client adds its client name, token and the signature as headers to the message.
When the message is received, the server validates the token and the signature. Messages that are missing these headers or fail to validate will be rejected.
Note that this mechanism is based on the security of the startup kits. All sites must protect their startup kits securely.

Bug fixes:

We fixed various bugs discovered by our users and customers

What's Changed

Full Changelog: 2.5.1...2.5.2

2.5.1: bug fixes and additional features

15 Oct 00:35
a5476ae
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.5.0...2.5.1

2.5.1rc2: bug fixes and document updates

11 Oct 00:32
139bc6a
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.5.1rc1...2.5.1rc2

2.5.1rc1: Bug fixes and more features

08 Oct 02:47
348ddb1
Compare
Choose a tag to compare
Pre-release

What's Changed

Full Changelog: 2.5.0...2.5.1rc1

2.5.0: Latest release with features and bug fixes

09 Sep 21:13
bff1d69
Compare
Choose a tag to compare

What's new

https://nvflare.readthedocs.io/en/main/whats_new.html
https://nvidia.github.io/NVFlare/

  • User Experience Improvements
    NVFlare 2.5.0 offers several new sets of APIs that allows for end-to-end ease of use that can greatly improve researcher and data scientists’ experience working with FLARE. The new API covers client, server and job construction with end-to-end pythonic user experience.

  • Model Controller API
    The new ModelController API greatly simplifies the experience of developing new federated learning workflows. Users can simply subclass the ModelController to develop new workflows. The new API doesn’t require users to know the details of NVFlare constructs except for FLModel class, where it is simply a data structure that contains model weights, optimization parameters and metadata.

You can easily construct a new workflow with basic python code, and when ready, the send_and_wait() communication function is all you need for communication between clients and server.

Using this in-process client API, we build a ScriptExecutor, which is directly used in the new Job API.

Compared with SubProcessLauncherClientAPI, the in-process client API offers better efficiency and is easier to configure. All the operations will be carried out within the memory space of the executor.

SubProcessLauncherClientAPI can be used for cases where a separate training process is required.

  • Job API
    The new Job API, or FedJob API, combined with Client API and Model Controller API, will give users an end-to-end pythonic user experience. The Job configuration, required prior to the current release, can now be directly generated automatically, so the user doesn’t need to edit the configuration files manually.

We provide many examples to demonstrate the power of the new Job APIs making it very easy to experiment with new federated learning algorithms or create new applications.

  • Flower Integration
    Integration between NVFlare and the Flower framework aims to provide researchers the ability to leverage the strengths of both frameworks by enabling Flower projects to seamlessly run on top of NVFlare. Through the seamless integration of Flower and FLARE, applications crafted within the Flower framework can effortlessly operate within the FLARE runtime environment without necessitating any modifications. This initial integration streamlines the process, eliminating complexities and ensuring smooth interoperability between the two platforms, thus enhancing the overall efficiency and accessibility of FL applications. Please find details here. A hello-world example is available here.

  • Secure XGBoost
    The latest features from XGBoost introduced the support for secure federated learning via homomorphic encryption. For vertical federated XGBoost learning, the gradients of each sample are protected by encryption such that the label information will not be leaked to unintended parties; while for horizontal federated XGBoost learning, the local gradient histograms will not be learnt by the central aggregation server.

With our encryption plugins working with XGBoost, NVFlare now supports all secure federated schemes for XGBoost model training, with both CPU and GPU.

Please check federated xgboost with nvflare user guide https://nvflare.readthedocs.io/en/main/user_guide/federated_xgboost.html and the example

  • Tensorflow support

With community contributions, we add FedOpt, FedProx and Scaffold algorithms using Tensorflow. You can check the code here and the example

  • FOBS Auto Registration
    FOBS, the secure mechanism NVFlare uses for message serialization and deserialization, is enhanced with new auto registration features. These changes will reduce the number of decomposers that users have to register. The changes are:

Auto registering of decomposers on deserialization. The decomposer class is stored in the serialized data and the decomposers are registered automatically when deserializing. If a component only receives serialized data but it doesn’t perform serialization, decomposer registering is not needed anymore.

Data Class decomposer auto registering on serialization. If a decomposer is not found for a class, FOBS will try to treat the class as a Data Class and register DataClassDecomposer for it. This works in most cases but not all.

How to perform Kaplan-Meier survival analysis in a federated setting without and with secure features via time-binning and Homomorphic Encryption (HE).

How to use the Flare ModelController API to contract a workflow to facilitate HE under simulator mode.

BioNemo example for Drug Discovery
BioNeMo is NVIDIA’s generative AI platform for drug discovery. We included several examples of running BioNeMo in a federated learning environment using NVFlare:

The task fitting example includes a notebook that shows how to obtain protein-learned representations in the form of embeddings using the ESM-1nv pre-trained model.

The downstream example shows three different downstream tasks for fine-tuning a BioNeMo ESM-style model.

Federated Logistic Regression with NR optimization
The Federated Logistic Regression with Second-Order Newton-Raphson optimization example shows how to implement a federated binary classification via logistic regression with second-order Newton-Raphson optimization.

Hierarchical Federated Statistics
Hierarchical Federated Statistics is helpful when there are multiple organizations involved. For example, in the medical device applications, the medical devices usage statistics can be viewed from both device, device-hosting site, and hospital or manufacturers’ point of views. Manufacturers would like to see the usage stats of their product (device) in different sites and hospitals. Hospitals may like to see overall stats of devices including different products from different manufacturers. In such a case, the hierarchical federated stats will be very helpful.

FedAvg Early Stopping Example
The FedAvg Early Stopping example tries to demonstrate that with the new server-side model controller API, it is very easy to change the control conditions and adjust workflows with a few lines of python code.

Tensorflow Algorithms & Examples
FedOpt, FedProx, Scaffold implementation for Tensorflow.

FedBN: Federated Learning on Non-IID Features via Local Batch Normalization
The FedBN example showcases a federated learning algorithm designed to addr...

Read more

2.5.0rc12: Bug fixes

07 Sep 00:51
c278aff
Compare
Choose a tag to compare
2.5.0rc12: Bug fixes Pre-release
Pre-release

What's Changed

Full Changelog: 2.5.0rc11...2.5.0rc12

2.5.0rc11: Bug fixes

05 Sep 04:17
910179c
Compare
Choose a tag to compare
2.5.0rc11: Bug fixes Pre-release
Pre-release

What's Changed

Full Changelog: 2.5.0rc10...2.5.0rc11

2.5.0rc9: Bug fixes

04 Sep 01:11
d07b3f6
Compare
Choose a tag to compare
2.5.0rc9: Bug fixes Pre-release
Pre-release

What's Changed

Full Changelog: 2.5.0rc8...2.5.0rc9

2.5.0rc10: Feature improvements

04 Sep 01:20
60e722a
Compare
Choose a tag to compare
Pre-release

What's Changed

Full Changelog: 2.5.0rc9...2.5.0rc10

2.5.0rc8: Bug fixes

31 Aug 00:37
e3f195d
Compare
Choose a tag to compare
2.5.0rc8: Bug fixes Pre-release
Pre-release

What's Changed

Full Changelog: 2.5.0rc7...2.5.0rc8