Hey All!<p>OpenMetal came out of incubation late last year and I would love HN feedback and thoughts.<p>From a lot of early and current pushback, we are a company and business model that is going against the grain… but when we find a matching customer they love us!<p>We are an infrastructure company with a bit of scale already that competes - or is trying to at least - against the likes of AWS, GCP, etc. using open source private cloud technologies - OpenStack and Ceph at the core.<p>So, I already have thick skin... Feel free to tell me I am crazy but hopefully you also take a look!<p>Thanks!
Todd
The phrase "open source" is mentioned repeatedly here, and in your <a href="https://openmetal.io/about-openmetal/guiding-principles/" rel="nofollow">https://openmetal.io/about-openmetal/guiding-principles/</a> but <a href="https://github.com/openmetalio">https://github.com/openmetalio</a> seems to only be the docs and a simplistic search of them <<a href="https://github.com/openmetalio/openmetal-docs/search?q=git+clone">https://github.com/openmetalio/openmetal-docs/search?q=git+c...</a>> doesn't cough up the open source-ness of OpenMetal<p>Is your pitch that you <i>use</i> open source first, or that you <i>are</i> open source first?<p>ed: <strike>I would actually really enjoy if <a href="https://docs.openstack.org/devstack/zed/guides/single-vm.html" rel="nofollow">https://docs.openstack.org/devstack/zed/guides/single-vm.htm...</a> worked because moto only goes so far, whereas if I had the ability to actually do AWS-y stuff in a VM it would enable a lot more realistic tests than either localstack or moto offer</strike> I was inspired to actually try this again and it is now much better, and I'd go so far as to say it's now actually very cool<p>Which brings us back to your post: the website seems to be targeting so many different audiences, and at such differing levels of "hand waveiness" that it's hard to tell what problem paying you would solve. Is it just that you're taking the pain out of provisioning OpenStack and then good luck? Are you trying to take the localstack model of "open source, but operationalized" in order to add more surface area onto OpenStack (and then hopefully feeding those contributions back into OpenStack)?
While searching for any "git clone" instructions, seeing <a href="https://github.com/openmetalio/openmetal-docs/blob/main/docs/kubernetes-guides/deployment/kubespray.md#deploying-a-kubespray-cluster-to-openstack-using-terraform">https://github.com/openmetalio/openmetal-docs/blob/main/docs...</a> is a very bad sign since kubespray is <i>indescribably</i> slow and fragile. There are so many really great kubernetes bring-up tools nowadays, so using kubespray is a disservice<p>I guess if your business model is just enabling the customer to provision whatever they want onto their bare metal, or even OpenStack machines, ... I guess not your problem, but I still think either party could be more successful by picking a less fragile bring-up mechanism