|
|
Aegir is made up of several components. First off, there is a front-end built on Drupal 8. This user interface passes configuration variables into a distributed task queue, built on Celery. Finally, queue workers receive these tasks, and run various operations, based on the variables passed into the task from the front-end. A command-line client, built on Drupal Console, can also post tasks to the queue, allowing for relatively simple scripting. |
|
|
\ No newline at end of file |
|
|
Aegir is made up of several components. First off, there is a front-end built on Drupal 8. This user interface passes configuration variables into a distributed task queue, built on Celery. Finally, queue workers receive these tasks, and run various operations, based on the variables passed into the task from the front-end. A command-line client, built on Drupal Console, can also post tasks to the queue, allowing for relatively simple scripting.
|
|
|
|
|
|
## Front-end
|
|
|
|
|
|
The front-end is written in Drupal 8. It consists of some base entities and traits, along with basic admin interfaces for creating and managing fields and bundles.
|
|
|
|
|
|
## Queue system
|
|
|
|
|
|
The queue is implemented using Celery, a full-featured task queue written in Python.
|
|
|
|
|
|
## Back-end (queue worker)
|
|
|
|
|
|
The back-end will consume tasks from the queue, and run various commands. The initial engine is `ansible-playbook`, but Kubernetes is also likely to follow. |
|
|
\ No newline at end of file |