Persistent storage for the tftservices

threefoldfoundation / tft-stellar

Threefoldtoken on the stellar network

Apache License 2.0

7 stars 5 forks source link

Persistent storage for the tftservices #439

Closed robvanmieghem closed 2 years ago

robvanmieghem commented 2 years ago

[x] Check which services need it the unlock_service is the only one, the migration service model is only to prevent concurrent calls for the same address
[x] think about the best way
[x] Modify the helm chart to configure this
[x] Test it
[x] Configure a k8s PVC and configure the appropriate values for the tftservices
[x] Redeploy
[x] Restore data

Let's wait a bit with redeploying since it's the beginning of the month so locked tokens will be released now

robvanmieghem commented 2 years ago

the model is stored in root's home .config/jumpscale/secureconfig/models/UnlockhashTransaction I suggest to map only this folder to the PVC instead of the entire secureconfig to prevent impact on ephemeral data that is also stored there and might not be handled well if it changes.

robvanmieghem commented 2 years ago

blocked on #442

robvanmieghem commented 2 years ago

unblocked, initial test shows the unlock tx is written to the persistent volume and retreivable but is no longer available after a pod restart

robvanmieghem commented 2 years ago

After a write to unlockservice, both transactions are available again so it must be a js-sdk caching thing.

robvanmieghem commented 2 years ago

a complete helm uninstall, waiting for the pod to be completely removed and an install does not solve the problem so I don't think it's volume readwriteonce k8s problem.

robvanmieghem commented 2 years ago

After a short while the js-sdk picks them up again