5 ms·
Disclaimer: I work on Ubicloud. Wow, it is exciting to see what we are working on at HN. We only shared it with our professional circle so far, but it seems it
by pwmtr 3y ago
Disclaimer: I work on Ubicloud.
Wow, it is exciting to see what we are working on at HN. We only shared it with our professional circle so far, but it seems it found its way to HN .
Happy to answer any questions, but in summary we are building an open cloud, an alternative to existing hyperscalers, because we believe that you shouldn't have to give up power and lock yourself in to be able to have the ease of use of cloud.
You can use the managed version of Ubicloud or you can host it yourself. You can also use any bare metal provider such as Hetzner or OVH (currently we only support Hetzner because... well.. we are just starting , and support for other providers are on the way), thus benefit from their low prices and many available locations.
- alsjdfnasljfkh 3y ago[flagged]
- esperent 3y agoI think you could improve this section of the Readme to make this more accessible: > Today, AWS offers about two hundred cloud services. Ultimately, we will implement 10% of the cloud services that make up 80% of that consumption. > Example workloads and reasons to use Ubicloud today include: > You have an ephemeral workload like a CI/CD pipeline (we're integrating with GitHub Actions), or you'd like to run compute/memory heavy tests. Our managed cloud is ~3x cheaper than AWS, so you save on costs. > You want a portable and simple app deployment service like MRSK. We're moving Ubicloud's control plane from Heroku to MRSK; and we want to provide open and portable services for MRSK's dependencies in the process. > You have bare metal machines sitting somewhere. You'd like to build your own cloud for portability, security, or compliance reasons. This seems needlessly wordy. Instead you might assume that readers already have expertise or can look up terms themselves and simply list like this: Currently Available Features * CI/CD * MRSK app deployment * Etc. Coming soon * X * Y * Z * Etc.
- pwmtr 3y agoThanks for the feedback. We iterated few times on our README already and we will iterate on it many more times. These will definitely come in handy.
- amne 3y agoI work for Ubisoft and I initially thought we published our internal cloud platform which is named "Ubisoft Cloud".
- dijit 3y agoI used to work for Ubisoft; thought the same thing when reading the name. Unfortunately Ubisoft Cloud wasn't (likely still isn't) anything special; thus there's nothing really to open source Ubisoft cloud itself is a combination of openstack, a deprecated array of vmware clusters and kubernetes (Named: UKS). When I was there the storage system of these components kept disconnecting because there was a core switch without redundancy. The director of infrastructure for Central IT (GNS) sent a strongly worded email to all the stakeholders stating that we should be implementing failure domains.. when pressed on what failure domains we had he said... "one". Blows my mind. Ubisoft IT (GNS) has weird incentives. They chronically underinvest in themselves, offer half-baked and ill-fitting solutions and then wonder why people don't want to use them. It's peverse because the on-prem stuff Ubisoft has is consistently underinvested in yet we have 7 figure contracts with all three major cloud providers- paying well over 5x what we would have paid if we just invested properly.
- notpushkin 3y agoCongrats on the (soft-)launch! Have you considered other licensing options, like BSL?
- pwmtr 3y agoThanks. Indeed we did. Actually we asked HN crowd about this few days ago to get some input. https://news.ycombinator.com/item?id=36998888 https://news.ycombinator.com/item?id=36998888 Eventually, we decided to go with more restrictive one as it is easier to make it more permissive without upsetting our users.