Juju (software)

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages) This article contains promotional content. Please help improve it by removing promotional language and inappropriate external links, and by adding encyclopedic text written from a neutral point of view. (March 2014) (Learn how and when to remove this message) This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Juju" software – news · newspapers · books · scholar · JSTOR (September 2014) (Learn how and when to remove this message) (Learn how and when to remove this message)

Juju

Original author(s)	Canonical
Initial release	May 5, 2011; 13 years ago (2011-05-05)
Stable release	3.5.4[1] / 1 October 2024; 2 months ago (1 October 2024)
Repository	github.com/juju/juju
Written in	Go
Operating system	Ubuntu, macOS, CentOS
Type	Orchestration
License	GNU Affero General Public License
Website	juju.is

Juju is a free and open-source application modeling tool developed by Canonical Ltd.^[2] Juju is an application management system. It was built to reduce the operation overhead of software by facilitating, deploying, configuring, scaling, integrating, and performing operational tasks on public and private cloud services along with bare-metal servers and local container-based deployments.

Juju aims to provide a modeling language that abstracts the specifics of operating complex software topologies to reduce the cost of operations and provide flexibility. A Juju model is an environment to manage and operate a set of software applications. Models can be operated on a variety of public clouds.

A Juju controller is a service that tracks the events, state, and user activity across multiple models. A database server tool and databases available on a server are an example of a Juju controller and its models. Each model can have different configurations, sets of operating software, and users with various levels of access. Examples of models include a web application, load balancer, and database in a "web-app" model. Models allow deployments to be isolated into logical solutions and managed separately.

The central mechanism behind Juju is called charms. Charms can be written in any programming language that can be executed from the command line. A charm is a collection of YAML configuration files and a selection of hooks. A hook is an executable file that can be used to install software, start or stop a service, manage relationships with other charms, upgrade charms, scale charms, configure charms, etc. Charms can have many properties. Using charm helpers, boiler-plate code is automatically generated, thereby speeding up charm creation.

Juju has two components: a client and a bootstrap node. After installing the client, one or more environments can be bootstrapped. Juju environments can be bootstrapped on various clouds. By creating a Juju Provider, additional cloud environments can be supported.

Juju can also be bootstrapped on bare-metal servers. Large deployments can use Canonical's Metal as a Service. Small deployments can use the manual provider, which allows any SSH-accessible Ubuntu machine to be converted into a Juju-managed machine. Juju can also be installed on a local Ubuntu machine via LXC operating system–level virtualization and the local provider.

Juju has both command line and GUI access. Automatically available on every controller, the Juju GUI allows users to visually see what software is currently running in which models. Users can also search the Charm Store [see below] and browse results with detailed charm information. Complex software stacks can be deployed via drag-and-drop.

Juju also has a concept of bundles. A bundle is a portable specification for a model with charms, configuration, and relations, all specified in a declarative YAML format. A bundle YAML file can later be imported into another Juju model and shared with others. Bundles can also be uploaded to the Charm Store, allowing others to deploy them.

In this example bundle, two applications are modeled: MediaWiki and MySQL. Users can modify attributes declared in the bundle to customize their deployment:

services:
  mediawiki:
    charm: mediawiki
    num_units: 1
    options:
      debug: false
      name: Please set name of wiki
      skin: vector
  mysql:
    charm: mysql
    num_units: 1
    options:
      binlog-format: MIXED
      dataset-size: 80%
      tuning-level: safest
series: trusty
relations:
- - mediawiki:db
  - mysql:db

The Juju Charm Store launched on April 3, 2012.^[3] The Charm Store regularly tests charms to notify charm authors when code breaks, in addition to ensuring that Juju users have access to the latest versions of charms.

Juju is available on the Ubuntu Server, with agents available for Ubuntu, CentOS,^[4] and Microsoft Windows.^[5] Support for both CentOS and Windows has been contributed by Cloudbase Solutions.