JAAS Documentation¶

JAAS provides a single location to manage your Juju infrastructure by using the Dashboard or using the same Juju CLI commands to create a high-level overview and the ability to drill-in to the details when you need it.

JAAS is composed of the following components:

JIMM - Juju Intelligent Model Manager, which acts as a single point of contact for multiple Juju controllers,
Juju controllers - each controlling models in specific clouds or cloud regions,
Juju dashboard - providing a clear overview of your Juju real estate with the ability to drill down into details of your deploys.

JAAS is useful for customers that do not want to maintain their own controllers in public clouds. Canonical’s JAAS enables users to deploy their workloads in public clouds without the extra complexity and costs associated with running their own Juju controllers. JAAS is also useful for organisations running their own Juju infrastructure giving them a single point of contact for their entire real estate and, in combination with the Juju Dashboard, giving them a clear overview of their infrastructure.

In this documentation¶

Where to begin¶

We recommend starting with our JAAS overview and then our tutorial on deploying JAAS to MicroK8s.

This will help you understand the architecture of JAAS then guide you through its deployment with links to further docs on how to manage your environment.

Project and community¶

JAAS is a member of the Ubuntu family and warmly welcomes community contributions, suggestions, fixes and constructive feedback.