Creating local_state directory, and saving state to it

[cloudnoize]

No description provided.

[teoparvanov]

LGTM, with one comment:

[MasterSkepticista]

Why not reuse save?

[cloudnoize]

Why not reuse save?

Save is prepopulated with proto files, which eliminates the option to mount it as an encrypted fs under Gramine.
Furthermore, we need a directory to store the final models that the model owner can retrieve through the file server, and it should not be mounted as an encrypted fs, the save directory meet those requirements.

[MasterSkepticista]

Why not encrypt the state before writing under save/?

[cloudnoize]

Why not encrypt the state before writing under save/?

Gramine uses proprietary encryption protocol, you can't mount the save directory as encrypted fs with files in it and then read them, so it's either you start with those files in a different path and then rewrite them to save or present a new directory as done here.
In each case you need a directory that is outside of the encrypted fs to host the final models (which are encrypted but not via Gramine), so the save can act both as the initial model and the final model location that is outside of the encrypted fs.

[MasterSkepticista]

Why not encrypt the state before writing under save/?

Gramine uses proprietary encryption protocol, you can't mount the save directory as encrypted fs with files in it and then read them, so it's either you start with those files in a different path and then rewrite them to save or present a new directory as done here. In each case you need a directory that is outside of the encrypted fs to host the final models (which are encrypted but not via Gramine), so the save can act both as the initial model and the final model location that is outside of the encrypted fs.

I was referring to standard encryption that does not require enclaves