8 ms·

Show HN: Open-source tool to deploy infrastructure in any cloud

14 points by goncaloo 4y ago

We have been working on multy.dev, an open-source cloud agnostic API that makes it easy to deploy the same infrastructure to any cloud provider using native managed services. The motivation was the realisation that, even when using Terraform, migrating infrastructure code requires an end-to-end re-write. Even though most core resources are the same in any major cloud, developers need to learn a new provider to deploy the same infrastructure when moving providers. We are still in early days of development and currently support the core services from AWS and Azure: - Networking (virtual_network, subnet, route_table, security_group, network_interface, public_ip) - Compute (virtual_machine, managed kubernetes) - Database (managed MySQL databases) - Vault (managed secrets) - Storage (managed storage) - Abstraction of cloud differences (Azure VM public vs AWS EC2 private by default) - Deployment through Terraform We’re looking for feedback from other developers about our approach. Let us know your thoughts! GitHub: https://github.com/multycloud/multy https://github.com/multycloud/multy

abdouls 4y ago
This is a really good idea! I've worked with both Azure and AWS - we've mainly used Powershell scripts and both their SDKs to deploy resources. For AWS we were still using the sdks / cli to deploy but for Azure we went to bicep (Azure's api really sucked as it kept being updated very often and caused the Az module to stop working). I can see value in this as it grows!
- goncaloo 4y ago
  Thank you! We're focusing on a terraform provider for now but we want to also provide an SDK and a portal in the future.
eurasiantiger 4y ago
The use of the word ”agnostic” implies skepticism towards cloud solutions and that your stack knows nothing about any cloud provider. I don’t think that’s the way either is.
- goncaloo 4y ago
  That's a good point. Our approach is to embrace cloud native services instead of avoiding them and still not be locked in to a single cloud provider. We use cloud agnostic to convey that the user can write code that works for any cloud, and we'll translate it to the cloud specific services. I'll think of different messages - thank you for the feedback!
ifokeev 4y ago
I'm trying to make this live too here: https://github.com/cloudytool/cloudy https://github.com/cloudytool/cloudy. My idea is to give a user cloud-specific javascript templates with a production-ready cluster infrastructure. Looking for contributors :)
- goncaloo 4y ago
  Cool project! Why did you choose Pulumi?

14 points by goncaloo 4y ago

abdouls 4y ago

This is a really good idea! I've worked with both Azure and AWS - we've mainly used Powershell scripts and both their SDKs to deploy resources. For AWS we were still using the sdks / cli to deploy but for Azure we went to bicep (Azure's api really sucked as it kept being updated very often and caused the Az module to stop working). I can see value in this as it grows!

goncaloo 4y ago
Thank you! We're focusing on a terraform provider for now but we want to also provide an SDK and a portal in the future.

eurasiantiger 4y ago

The use of the word ”agnostic” implies skepticism towards cloud solutions and that your stack knows nothing about any cloud provider. I don’t think that’s the way either is.

goncaloo 4y ago
That's a good point. Our approach is to embrace cloud native services instead of avoiding them and still not be locked in to a single cloud provider. We use cloud agnostic to convey that the user can write code that works for any cloud, and we'll translate it to the cloud specific services. I'll think of different messages - thank you for the feedback!

ifokeev 4y ago

I'm trying to make this live too here: https://github.com/cloudytool/cloudy https://github.com/cloudytool/cloudy. My idea is to give a user cloud-specific javascript templates with a production-ready cluster infrastructure. Looking for contributors :)

goncaloo 4y ago
Cool project! Why did you choose Pulumi?