|
|
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.
|
|
|
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
|
|
|
|
... | ... | @@ -16,9 +16,9 @@ Our current abstractions include: |
|
|
We may want to restructure our abstractions, such as:
|
|
|
* Resources
|
|
|
* Applications
|
|
|
* Deployments
|
|
|
* Deployments (Application instances)
|
|
|
|
|
|
#### Sites
|
|
|
We may want to stick with our current abstractions for the first round of re-architecture, since we know that models works. We could then focus on getting the queue/engine implementation sorted out.
|
|
|
|
|
|
## Queue system
|
|
|
|
... | ... | |