pyinfra VS Pulumi

There is https://pyinfra.com/

As a sidenote, I also made a small experiment a while ago : https://github.com/linkdd/tricorder/

But it's a bit of a chicken-and-egg problem. Without users, I don't know how it should be used, without features I won't get any users. So for now, it's in a state of "I'll address bug reports and feature requests, but I won't actively develop it".

I like https://github.com/pyinfra-dev/pyinfra. "pyinfra automates infrastructure using Python"

Only played with it for a little but it seems well designed an simpler alternative to ansible, chef and other such things.

Haven't used it in anger yet, but I have high hopes for PyInfra: https://github.com/pyinfra-dev/pyinfra

pyinfra - https://pyinfra.com/ - Pyinfra is simpler for me than Ansible. I completed the entire deployment in one afternoon, from installing and configuring the VPS server from scratch to deploying the application and automatically restoring the database from a backup.

I’ve replaced Ansible with PyInfra where ever possible. https://pyinfra.com/ is very clean, and fast but lacks the shear amount of automation that can be found with Ansible.

Some folks don't like YAML all that well, and I can understand where they are coming from. I wish Ansible provided a good Python API so that playbooks could be written in Python easier. But there is a project called PyInfra that is trying to do something similiar to Ansible, using Python as the configuration language. https://pyinfra.com/ It is still pretty new so not got nearly as many modules written for it yet.

If you are following this blog series, you should already know the benefits of using Terraform to define and deploy your AWS resources and configuration. Other IaC solutions such as AWS CloudFormation, AWS CDK, and Pulumi work the same way but differs in the programming or configuration language.

Infrastructure as Code (IaC) is an important part of any true hosting operation in the public cloud. Each of these platforms has their own IaC solution, e.g. AWS CloudFormation. But they also support popular open-source IaC tools like Pulumi or Terraform. A category of tools that also needs to be discussed is API gateways and other app-specific load balancers. There are applications for internal consumption, which can be called microservices if you have a lot of them. And often microservices use advanced networking options such as a service mesh instead of just the native private network offered by a VPC.

funny, to me systemd == no docker, no containers, just a VM.

it's my goto way to keep my programming running and have it be restarted if the vm reboots. I use VMs like "pods". I deploy code directly to the VM and run it there along with other programs. I scale up an scale down with: https://www.pulumi.com/

Pulumi — Modern infrastructure as a code platform that allows you to use familiar programming languages and tools to build, deploy, and manage cloud infrastructure.

A move like this may have an impact in other open source projects. Take Pulumi, for instance, people might avoid choosing it now that the Linux Foundation have its own IaC tool, and for newer, smaller projects it will probably be impossible to compete with a project under the Linux name.

Another alternative to writing an operator would be to rely on kustomize or https://www.pulumi.com/.

Pulumi

Would it make sense to say Dagger is to Pulumi [1], as Terraform is to Togomak?

[1]: https://www.pulumi.com/

Infrastructure as Code (IaC): Define your infrastructure using code (IaC) to automate the provisioning of resources such as virtual machines, load balancers, and databases. Tools like Terraform, Pulumi, and AWS CloudFormation can help.