---
# System prepended metadata

title: OSTree plugin use cases

---

# OSTree plugin use cases

Epic with an overview of the ecosystem: https://pulp.plan.io/issues/8924
*  Clients don't have to download the whole commit when updating. If the repository provides a `static delta` between the clients current commit and the commit of interest, the client can download the `static delta` instead.
*  The `static delta` is an additional content type that a Pulp OSTree repository version can contain. Pulp would need to compute the `static delta`. The `static delta` is most useful to be calculated when you know for sure that there are clients using a specific commit and they will be updating to another specific commit. This content type is not needed for the initial implementation. 
*  RPM OSTree provides a lot more useful information to administrators. It can show which RPMs have changed between two commits. Pulp should probably show this information to users. 

Initial upload of a Fedora IoT commit archive: https://pulp.plan.io/issues/8918
* Can the same commit be shared by multiple refs?
    * Yes

Upload of Fedora IoT update commit archives: https://pulp.plan.io/issues/8919
*     

Mirroring of a Fedora IoT repository: https://pulp.plan.io/issues/8921
    * Use libostree to `pull` a repository.
    * Could possibly only sync `static deltas` instead of full commits. 
