What is the difference between juju and puppet

Product Deployment. Build Tools. Other Infrastructure Tools. DevOps Tools. Reviews These are some of the external sources and on-site user reviews we've used to compare Puppet Enterprise and Juju.

The client machines provide the platforms for running Puppet clients as agents. In addition, the requirement of signing a certificate between the master machine and the agent adds complexity. Source: www. Source: blog. Puppet — Puppet also has a master-agent architecture. Puppet server runs on the master machine and Puppet clients runs as an agent on each client machine. You need to install a master server and a client agent in the target nodes. It also includes the option for a standalone client.

This is the equivalent of Chef-solo. You can install deployment modules via Puppet commands. Just like Chef, it has a paid Enterprise edition that comes with additional features that include orchestration and reporting.

Chef and Puppet differ in their approaches to their basic functions. Chef is more monolithic and integrated, while Puppet has multiple services. This makes Chef much easier to set up, run, and manage. Puppet is arguably the most popular in this list. It happens to be the most complete tool in terms of modules, available actions, and user interfaces. The tool represents a whole picture of data center orchestration, which encompasses almost every operating system.

It comes with deep tools for all the major operating systems. This is an open-source orchestration tool from Canonical, the developers of Ubuntu OS. This tool enables enterprises to deploy, scale, and manage software and services residing in the cloud. Moreover, some of its modules are cloud-specific which makes a potential migration from one platform to the other difficult. Finally, due to its imperative nature, Ansible does not scale in large environments consisting of various interconnected applications.

It allows users to provision and manage cloud, infrastructure, and service resources using simple, human-readable configuration language called HCL HashiCorp Configuration Language. The resources are delivered by so-called providers. Terraform uses a declarative DevOps paradigm which means that instead of defining exact steps to be executed, the ultimate state is defined. This is a huge progress compared to the traditional configuration management tools. The applications being deployed still have to be installed and configured using traditional scripts and tools.

Of course, pre-built images can be used too, when deploying applications in cloud environments. In addition to the initial deployment, Terraform can also be used to orchestrate deployed workloads. This functionality is provided by its execution plans and resource graphs. Thanks to the execution plans users can define exact steps to be performed and the order in which they will be executed. In turn, resource graphs allow to visualise those plans.

Again, this is much more than what Ansible can do. Contrary to both Ansible and Terraform, Juju is an application modelling tool, developed and maintained by Canonical. You can use it to model and automate deployments of even very complex environments consisting of various interconnected applications.

Examples of such environments include OpenStack , Kubernetes or Ceph clusters. Puppet Open Source is a flexible, customizable framework available under the Apache 2. As a declarative, model-based approach to IT automation, it lets you define the desired state - or the "what" - of your infrastructure using the Puppet configuration language.

If you have an external puppetmaster, note that you will have to use some method to classify nodes automatically. The yaml from 'juju status' should be parsable into an external node classifier.