4 ms·

Kick ass project, been following bcantril since before Joyent and as a (server/infra + sysadmin nerd this really hits home): Are there plans to build some publi

Kick ass project, been following bcantril since before Joyent and as a (server/infra + sysadmin nerd this really hits home): Are there plans to build some public-cloud-esque software add-ons to offer cloud-native equivalents to s3, serverless-functions, message queues, etc? I feel like the "running your own datacenter" complexity of on prem is a big part of why companies go to the cloud in the first place - but that a good amount of cloud lock-in is actually in the software/service stack and reliance on it. I know there is a competent open source option for most of these services (and in fact most are repackaged open source software...), but they do seem pretty disparate and require quite a fair bit of knowledge and expertise to deploy and run at scale. Secondary question in the same thread: What about "accounting"? Running infrastructure at large-scale companies (such that would look at a rack-level solution) usually entails budgeting and accounting of resources - how does oxide simplify this for infrastructure ops trying to keep the various IT consumers honest?

bcantrill 3y ago
Great questions. We are careful about new service exposure -- object storage certainly makes sense (though having built one in the past, very mindful about trade-offs between cost/performance/availability/durability) but some higher level services may not (do not expect an Elastic Beanstalk equivalent!). There's a big gray area in the middle, where we will be customer- and demand-driven. On accounting: yes! This is something that we have designed abstractions for from the start with respect to tenancy with our silo and project abstraction[0], and we are actively adding resource allocation and monitoring; stay tuned! [0] https://docs.oxide.computer/guides/key-entities-and-concepts https://docs.oxide.computer/guides/key-entities-and-concepts

bcantrill 3y ago

Great questions. We are careful about new service exposure -- object storage certainly makes sense (though having built one in the past, very mindful about trade-offs between cost/performance/availability/durability) but some higher level services may not (do not expect an Elastic Beanstalk equivalent!). There's a big gray area in the middle, where we will be customer- and demand-driven. On accounting: yes! This is something that we have designed abstractions for from the start with respect to tenancy with our silo and project abstraction[0], and we are actively adding resource allocation and monitoring; stay tuned! [0] https://docs.oxide.computer/guides/key-entities-and-concepts https://docs.oxide.computer/guides/key-entities-and-concepts