From 4a240fb342c5d166584b64d48ae97a0a86a46548 Mon Sep 17 00:00:00 2001 From: Teodora Mihoc Date: Tue, 14 Jan 2025 08:50:37 +0100 Subject: [PATCH] docs: update homepage intro (#79) --- .custom_wordlist.txt | 1 + index.rst | 38 +++++++++++++++++++++----------------- 2 files changed, 22 insertions(+), 17 deletions(-) diff --git a/.custom_wordlist.txt b/.custom_wordlist.txt index d71ec65..cc0977a 100644 --- a/.custom_wordlist.txt +++ b/.custom_wordlist.txt @@ -34,6 +34,7 @@ IAM IdP init installable +jaas JAAS jimm jimmctl diff --git a/index.rst b/index.rst index a4851bb..1a625e4 100644 --- a/index.rst +++ b/index.rst @@ -5,23 +5,27 @@ 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. +JAAS is an enterprise layer on top of `Juju `__. + +JAAS provides: + +- The Juju Infinite Model Manager, JIMM (and its `backing charm `__): A Juju enterprise-level controller. + +- JIMM-specific extensions to existing Juju machinery, including + + * the `Juju CLI `__ (enhanced with `jimmctl`, for JIMM admins, and `jaas`, for regular JIMM users), + + * the `Juju dashboard `__ (and its `backing charm `__), and + + * the `Terraform Provider for Juju `__. + +When you use an existing Juju on Kubernetes controller to deploy JIMM and its dependencies, and then connect your Juju controllers to JIMM, you gain the ability to: + +- use OIDC authentication for integration with your existing identity provider for federated login, service accounts and other features offered by identity providers; +- use ReBAC for authorisation; +- use the Juju CLI, Juju Dashboard, and the Terraform Provider for Juju to interact with multiple Juju controllers from a single point of contact. + +If you want to take Juju to the enterprise level, you need JAAS. ---------