"Software trends have shifted dramatically — languages have come and gone, release cycles have shrunk from months to hours, architectures have evolved, and AI has taken the industry by storm. Yet the code that automates software deployment and infrastructure has remained largely unchanged.
“The state of infrastructure automation right now is roughly equivalent to the way the world looked before the CRM was invented,” says Jacob.
A skeptic might ask, why not use generative AI to do IaC? Well, according to Jacob, the issue is data — or rather, the lack of it. “Most people think LLMs are magic. They’re not. It’s a technology like anything else.”
LLM-powered agents need structured, relationally rich data to act — something traditional infrastructure tools don’t typically expose. System Initiative provides the high-fidelity substrate those models need, says Jacob. Therefore, System Initiative and LLMs could be highly complementary, bringing more AI into devops over time. “If we want that magical future, this is a prerequisite.”
System Initiative proposes a major overhaul to infrastructure automation. By replacing difficult-to-maintain configuration code with a data-driven digital model, System Initiative promises to both streamline devops and eliminate IaC-related headaches. But it still has gaps, like minimal cloud support, and few proven case studies.
There’s also the risk of locking into a proprietary execution model that replaces traditional IaC, which will be a hard pill for many organizations to swallow.
Still, that might not matter. If System Initiative succeeds, the use cases grow, and the digital-twin approach delivers the results, a new day may well dawn for devops."
https://www.infoworld.com/article/4021153/can-system-initiative-fix-devops.html
Stay ahead in IT Infrastructure & Development!
Follow me: @kevinveenbirkenbach@microblog.cymais.cloud for #CyMaIS news at https://cymais.cloud
Topics: #CloudComputing #DevOps #Microservices #Kubernetes #SoftwareDev #CyberSecurity #Automation #DigitalTransformation
Trends: #InfrastructureAsCode #CI #CD #Serverless #Agile #BusinessGrowth #StartupLife #DigitalStrategy
Connect & grow together!
IBM acquires HashiCorp: Terraform and Ansible to work together
Red Hat has been part of IBM since 2019, HashiCorp since February 2025. IBM has thus acquired Ansible and Terraform. It is now clear how the tools work together.
IBM übernimmt HashiCorp: Terraform und Ansible sollen zusammenarbeiten
Red Hat gehört seit 2019 zu IBM, HashiCorp seit Februar 2025. IBM hat damit Ansible und Terraform gekauft. Jetzt wird klar, wie die Werkzeuge zusammenarbeiten.
Discover how #PklLang is redefining Infrastructure as Code!
Unlike complex #YAML, Pkl uses schemas & constraints for robust configuration management, catching errors early and providing clear feedback.
Watch the video by Dan Chao (Software Engineer, Apple) - complete with demo & transcript: https://bit.ly/4jilS5u
Pulumi's Internal Developer Platform sets standards and relieves developers
Infrastructure-as-code provider Pulumi presents an internal developer platform that standardizes templates and simplifies the work of developers.
Internal Developer Platform von Pulumi setzt Standards und entlastet Entwickler
Infrastructure-as-Code-Anbieter Pulumi stellt eine interne Entwicklerplattform vor, die Vorlagen vereinheitlicht und die Arbeit der Entwickler erleichtern soll.
#Ansible vs #Terraform: Which is More Secure for Infrastructure Automation?
Ansible and Terraform are excellent tools for secure infrastructure automation. They can be used individually or together to maximize the benefits. Using both of them may not be cost-efficient, though. In deciding which one to use, it is important to carefully examine the operational goals and your #DevOps team’s security workflows.
https://hackread.com/ansible-vs-terraform-secure-infrastructure-automation/
#InfrastructureAsCode (#IaC)
Last Call zur Mastering GitOps: Von Continuous zu Progressive Delivery
Die Online-Konferenz am 30. April zeigt, wie sich komplexe Infrastrukturkonfigurationen nach GitOps-Manier umsetzen lassen und wie Progressive Delivery gelingt.
Mastering GitOps: So gelingt der Weg von Continuous zu Progressive Delivery
Die Online-Konferenz am 30. April zeigt, wie Progressive Delivery gelingt und sich komplexe Infrastrukturkonfigurationen nach GitOps-Manier umsetzen lassen.
Just a big shoutout to #Ansible and #AWX for being able to manage a AWX instance using Ansible.
The instance is running in #Kubernetes, managed by #ArgoCD. But the inner configuration of AWX (LDAP, Teams, Organisations, Permissions, Templates, Projects, Inventories, Credentials) needs to be managed,too. That is where Ansible comes in.
Next week I will once again have a AWX instance that manages itself by running a job on AWX. Nice, eh?
Dear #AWX users out there (AWX as in Ansible, not AWS as in Amazon...),
does anyone have good pointers on connecting AWX and #Hashicorp #Vault / #OpenBoa **without** having to define each secret/credential again in AWX?
I have set up a basic connection according to the documentation: https://ansible.readthedocs.io/projects/awx/en/24.6.1/userguide/credential_plugins.html#ug-credentials-hashivault
And I have created a credential using that lookup and could successfully output its value in a playbook run in AWX.
But having to define a AWX credential for each secret that I need to pull from Vault/OpenBoa sounds like a lot of unnecessary duplication.
(Yes, I know you can manage AWX via Ansible. We do that already. But still, you need to define the credentials in your code somewhere for the automation to create it in AWX)
OK, today I took some time and finally reworked the #semaphoreui package for @opensuse. I had it on my todo list for ages and never got around to it. It was already 90% finished but lacking some fine details.
Now I have properly cleaned it up and removed the "ansible-" from the name, as it is no longer just for executing #Ansible code. Apparently Semaphore can now execute #terraform #opentofu and #pulumi code as well.
I'll do more testing before I send it to #Tumbleweed.
In other words: new vagrant-libvirt setup incoming! :-)
Stay tuned.
Infrastructure-as-Code: Erweiterte Security und Kontrolle in der Pulumi Cloud
Role-Based Access Control und die Integration von GitHub Actions sollen die Zugangskontrolle und das Secrets-Management auf der IaC-Plattform verbessern.
Auf dem Weg zum zweiten Tag der #CLT2025
Wenn ihr euch für Infrastruktur- und Security-Tests interessiert - schaut doch mal um 11:00 in V4 vorbei: https://chemnitzer.linux-tage.de/2025/de/programm/beitrag/242
iX-Workshop für Entwickler und Architekten: IT-Management mit Terraform
Erstellen und verwalten Sie IT- und Cloud-Infrastrukturen als Code – Grundlagen, Installation und Nutzung von Terraform.
Amazon has introduced garbage collection in the AWS CDK (preview)!
This new feature automatically removes old assets from bootstrapped S3 buckets and ECR repositories, helping reduce maintenance and deployment costs.
Learn more on #InfoQ https://bit.ly/41Es3eu