After 19 weekly releases, we have built out 8 additional AWS services, going from 129 to 371 actions. EKS was certainly the biggest technical milestone, and also the largest unlock when it came to building Spinifex into something functional for supporting production-ready AWS workloads. Happy to answer questions and discuss specific implementation details.
Spinifex-created EBS volumes are fully portable across nodes. We use nbdkit for the networking side of that, allowing us to attach a volume to an instance on any node. Data in the EBS volumes is backed by our S3 implementation, Predastore, which allows any node to access the data if/when a volume gets relocated to a given node.
After 19 weekly releases, we have built out 8 additional AWS services, going from 129 to 371 actions. EKS was certainly the biggest technical milestone, and also the largest unlock when it came to building Spinifex into something functional for supporting production-ready AWS workloads. Happy to answer questions and discuss specific implementation details.
How does the project support volumes like Elastic Block Storage, across multiple nodes?
Spinifex-created EBS volumes are fully portable across nodes. We use nbdkit for the networking side of that, allowing us to attach a volume to an instance on any node. Data in the EBS volumes is backed by our S3 implementation, Predastore, which allows any node to access the data if/when a volume gets relocated to a given node.
Is ARM supported? Curious to try this on a NVIDIA GB10
ARM is indeed supported. Let us know how you go spinning this up on a GB10!
Pretty cool
Thanks!