Coober Netease, Seth Roka, Rook discussed on Software Engineering Daily
We did a show about Cooper Nettie. Snapshot ING, and it was with a vendor that does does this as part of their service offering. And there are a lot of vendors that are filling in the gaps of the storage world in coober Netease. Where there are these all of these little frictions that exist in managing state and Cooper, Netease. There are vendors that provide solutions to some of these things why is it that vendors are able to build solutions to this. But it's not easy to snap your fingers and get it into the cougar Netease. API? That's a great question and the answer to that is that vendors work at a very with a very tight set of like they control the full stack essentially, they control the storage system, and they can choose an interface that will work nicely with their system when we introduce one of those operations into coober net. As we need to ensure that it works not just with a single vendor. But that it works across vendors, and we need to do. So in a way that doesn't end up being the lowest common denominator interface. Right. We don't want to stifle the innovation. That's going on at the storage layer with these storage vendors, we want them to be able to expose the full power of their storage system. But at the same time do so in a way that is going to be portable for application developers and doing so requires a lot of care and a lot of thoughtful consideration on what those API primitives are going to look like. And so you're going to see storage vendors actually, be far ahead of where Kuban as itself is. And what we do is. We look at the storage vendors, and we figure out what are the common set of operations that would be useful to expose application developers. And then thoughtfully work with the storage vendors as well. As end users and everyone in our community to try to come up with an interface that will work for everyone. There are open source projects related to orchestrating storage. While I guess I should say specifically rook is an orchestration system for storage that is deeply integrated with Cooper nineties. Explain what rook does sure the way that. I see it as rookies an operator for Seth. Seth is a storage system that can be deployed on top of existing discs and provides it's a software defined storage system. So it's one way to be able to pull the the underlying disks that you have and expose a a storage systems to your cluster running. Seth manually has been very challenging for those who are familiar with Steph. And so what rook did was come up with an operator for deploying Steph on top of coober Netease. I tried to decouple the consumption of storage from the making available of storage and rook is squarely in the domain of making a specific type of storage system. Available to a cluster to us where Kuban the. The storage say is interested is kind of the line outside of that. Which is some storage system. Exists could be Seth via rook could be an facet could be something else. How do I actually consume that and make that available to application application developers? I understand correctly. Seth offers file object and block stores through its API. And if rook is on top of Seth Roka's a layer into Seth and rook provides a Kuban eighties friendly interface to working with Steph. What else do you need?.