diff --git a/website/src/pages/about.md b/website/src/pages/about.md index b51f8a143a..2d4d07cc5f 100644 --- a/website/src/pages/about.md +++ b/website/src/pages/about.md @@ -1,50 +1,53 @@ # What is Agama? Agama is a new Linux installer born in the core of the [YaST](https://yast.opensuse.org/) team. It -is designed to offer re-usability, integration with third party tools and the possibility of -building advanced user interfaces over it. +is designed to offer re-usability, integration with third party tools and the possibility to +build advanced user interfaces over it. It offers an HTTP API to control and monitor the whole installation process and comes with two user interfaces: a modern web front-end and a powerful command-line tool. -Agama is capable of performing both interactive and unattended installations. Moreover, both -approaches can be combined in a single installation process driven by any combination of manual work -and automation, integrated or not into a bigger infrastructure. +Agama can perform interactive and unattended installations, making it possible even to mix both +approaches with any combination of manual work and automation. -Agama reuses many of the principles and internal components of (Auto)YaST, making sure it can handle -a similar number of architectures and technologies. +Agama reuses many of the principles and internal components of (Auto)YaST, ensuring it can handle +a similar number of architectures and technologies. It also offers a high level of backwards +compatibility with AutoYaST for unattended installations, being often able to act as a drop-in +replacement. -## A Linux installer? +## A Linux Installer... From a very simplistic and high level view, there are basically two methods to deploy a -Linux operating system: +Linux operating system - using a pre-built image and performing an installation. -- using a pre-built image, -- performing an installation. +The first method is direct and simple, but it cannot address all scenarios. On the other hand, +an installer can always be used to deploy a new Linux system through some general steps. -The first method is direct and simple, but there are scenarios that cannot be addressed just by -deploying an image. For those cases, you can use an installer to deploy the new system through some -general steps. - -- Perform some basic network configuration. -- Configure the storage setup for the target system (partitioning, LVM, encryption, etc.) -- Deploy the target system over that storage setup (eg. installing the appropriate set of RPM - packages). -- Customize the aspects of the system needed for the first boot (bootloader, kdump, authentication, - etc.). -- Give control to the new system (via kexec or hardware reboot). + - Configure the network and the storage setup, potentially including remote storage, partitioning, + LVM, encryption, etc. + - Deploy the target system over that storage setup, eg. installing the appropriate set of RPM + packages. + - Customize the aspects of the system needed for the first boot, like boot loader, kdump, + authentication, etc. + - Give control to the new system, via kexec or hardware reboot. Agama turns that process into a seamless experience. -## Just an installer - -Unlike its predecessor YaST, Agama... +## ... and Just an Installer -Focused on installation. Not present on the system after installation. +Unlike its predecessor YaST, known for been both a Linux installer and a general configuration +tool, Agama focuses on system installation. -Agama is a deployment tool, taking care of those aspects that: +As a pure deployment tool, Agama takes care of those aspects that: + - can only be handled during installation itself or + - are needed to get a minimal functional system that can be booted and configured in a secure way. -- can only be handled during installation itself or -- are needed to get a minimal functional system that can be booted and configured in a secure way. +As such, Agama is not present at the final installed system and minimizes overlapping with more +general configuration tools. ![Deploy and configuration tools](/img/deploy-configure.png) + +## More Details + +If you need more information about what Agama can do, the plans for the future, how it compares to +YaST or the level of compatibity with AutoYaST, check the [Frequenly Asked Questions](/faq). diff --git a/website/src/pages/faq.md b/website/src/pages/faq.md index 016847ccd6..97b82942a6 100644 --- a/website/src/pages/faq.md +++ b/website/src/pages/faq.md @@ -1,6 +1,11 @@ # Frequently Asked Questions -## Why a New Installer +## What is Agama? + +Short answer - a Linux installer intended as the evolution of YaST. For a longer answer, check +the [About](/about) section. + +## Why a new installer? This new project follows two main motivations: to overcome some of the limitations of YaST and to serve as installer for new projects, like those based on SUSE Linux Framework One. @@ -14,3 +19,23 @@ cases. But time goes by, and the good old YaST is starting to show its age in so - Sharing logic with other tools like Salt or Ansible is very difficult. - Some in-house solutions like [libyui](https://github.com/libyui/libyui) make more difficult to contribute to the project. + +## How is Agama different from YaST? + +TBD. + +## Will Agama replace YaST as the main installer for SUSE Linux or openSUSE distributions? + +TBD. + +## What can I configure with Agama? + +TBD. + +## Where is the nCurses interface? + +TBD. + +## Can I use my existing AutoYaST profiles and infrastructure? + +TBD. diff --git a/website/static/img/deploy-configure.png b/website/static/img/deploy-configure.png index 13541187e3..89830fe788 100644 Binary files a/website/static/img/deploy-configure.png and b/website/static/img/deploy-configure.png differ