general/occlum
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[readthedoc] supplement pytorch tutorials

Browse Source
This commit is contained in:
Qi Zheng 2023-10-17 11:49:47 +08:00 committed by volcano
parent fe59284e3d
commit d2f2c3ca04
2 changed files with 19 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
docs/readthedocs/docs/source/images/distributed_pytorch.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 121 KiB

20
docs/readthedocs/docs/source/tutorials/distributed_pytorch.md
View File

@ -1,3 +1,21 @@
# Distributed PyTorch # Distributed PyTorch
To be Added [PyTorch](https://pytorch.org/) is well supported in Occlum. Unmodified distributed PyTorch training (such as fasion-MNIST dataset training) could be enabled running in TEE by simple steps.
## Overview
![Flow](../images/distributed_pytorch.png)
Above is the flow chart which could be break down as below.
1. Client starts the PyTorch Occlum instances, such as one master and two worker nodes.
2. Every PyTorch Occlum instance starts, get required keys from one remote attestation based KMS. The keys could be for data decryption, result encryption or Pytorch nodes TLS certs.
3. PyTorch nodes set up rendezvous.
4. Loading dataset, training started.
5. Encrypt and save result if necessary.
For step 2, users could use the Occlum [init-ra AECS](https://occlum.readthedocs.io/en/latest/remote_attestation.html#init-ra-solution) solution which has no invasion to the PyTorch application.
More details please refer to [pytorch demo](https://github.com/occlum/occlum/tree/master/demos/pytorch/distributed).
Note, the demo has not involved KMS and data encryption or decryption. Users could add them accordingly.