More 2FA work is on the roadmap, added another thumps up for TOTP - team has a pretty big backlog though.
I am pretty sure I found your account on our side - sent you an email from the system in case I can help.
The Ansible playbooks are held inside a system called Semaphore for each customer's deployment. Playbooks are specific to the servers selected. Configurations for a cluster made up of 3 X single CPU box with 128GB of RAM with a single worker drive vs 3X a dual CPU box, 1TB RAM, and 4 worker drives. We copy it to the servers for now as we are still working on making Semaphore accessible from the Central interface.
For the root@ - thanks! Will pass that to the dev team - I found some with it and some without it, makes sense to have it on all since it is root keys.
I'll take that back to the engineering group - I don't think they formed a specific opinion so the feedback is really helpful. For Kubernetes, we validated OpenShift/OKD, Rancher, Kubespray as you mentioned, and kOps on our "pin" of OpenStack. We also use an OpenStack system with something call Magnum - though this one is up for discussion as Magnum may have a limited span in front of it. Check this if interested:
Our model does encourage them to go the way they want as it is a full root level OpenStack/etc. but absolutely we do want to give good guidance when they don't have their systems already going.
Thanks for looking! and you got all the way to our guiding principles! Awesome.
Our spot in the OpenStack/Open Source ecosystem isn't code - and looks like it isn't clear enough - it is that we make the full open source version of OpenStack and Ceph available in an environment that is suited to those systems - not a test system, but a real multi server system.
It lets people experience OpenStack and Ceph before every having to take on architecting it - and the Ansible we used is available to them to either carry forward on our systems or for using it as the basis of anything they want to build.
These are both for paying customers and for people learning - we have set aside resources and in our business model to allow people to spin up and use the clusters so they can learn.
OpenStack and Ceph in real production is pretty hard to pull off - failure is really common and so what we are hoping is we can at least ease some of that.
We also help OpenStack itself by providing hardware for the Zuul dev pipelines.
As for who we sell to/make money/solve - these are usually mid-size companies spending between $30k and $100k per month on Cloud and we handle part of that spend. Usually because we can tune the cloud to their workload for better performance or because we are a better deal with better support than the local mega cloud...
The guy behind this has a Ph.D. - fusion energy - and is clearly a brilliant engineer. He is building on our current systems and generations that came before.
He is just making a choice to not turn it into a product to be sold but a skill to be shared. Teaching us to fish.
I say awesome and we need more of these open source, go your own way, people in this world!
Has anyone here become a donor? How is the project doing?
That statement is counter to how "vCPUs" related to "CPU" since early cloud implementation. AWS not taking advantage of the much more efficient "oversubscription ratio" versus thread pinning - unlikely.
I just watched a couple of your video on participating in Open Source - like https://youtu.be/GU_ISkNml-A - and just read a ton of really nice things about you below and read your story.
And honestly I really have no idea how SerenityOS would relate to me or my company – but I do know that everything under the hood of our hosting and our clouds is Open Source.
So for sure I can say for just being an Open Source champion and an all around nice guy, for the next year at least, count on me personally at $100 a month (just did it in Github) and my company InMotion Hosting for another $100 month (just did it on Patreon).
Open Source constantly struggles with needing super talented professional but also struggles on how to make sure they make a good living. I know $200/mo isn't a lot when it comes to life, but hopefully it helps you know others out here believe in this kind of work and taking this kind of chance!
I am pretty sure I found your account on our side - sent you an email from the system in case I can help.
The Ansible playbooks are held inside a system called Semaphore for each customer's deployment. Playbooks are specific to the servers selected. Configurations for a cluster made up of 3 X single CPU box with 128GB of RAM with a single worker drive vs 3X a dual CPU box, 1TB RAM, and 4 worker drives. We copy it to the servers for now as we are still working on making Semaphore accessible from the Central interface.
For the root@ - thanks! Will pass that to the dev team - I found some with it and some without it, makes sense to have it on all since it is root keys.