TAD are available as git repositories.
These documents describe silos or application blocks in LNAGORA deployments. That includes the block Software architecture, a description of the Software components, the multi-tenancy strategy, an inventory of the hardware stack (IP addresses, Openstack servers…) and the main procedures for operations.
Every TAD should be associated with a feature team.
Both the SREs and the feature team in charge of the TAD must work together and maintain the information. Adding or removing Software dependencies or network flows should get a validation from the CoTECH.
Here is the association table.
| TAD | Feature Team |
|---|---|
| Emaily | |
| Identity | ??? |
| Trinity | Calendar (as Inbox is moving to Emaily) |
| LinShare | LinShare |
| Twake | Twake |
| Twake Console | Twake Console |
| Commons | ??? |
Assuming there is a core team in charge of common services (architecture, identity, accounts management, administration - which includes the Twake Console), then this team would be in charge of the Commons and Identity parts.
TADs are written in Markdown.
The repositories contain an automated mechanism to generate PDF files.
The last version of the file can be downloaded directly from the repository’s landing page. Older versions can be retrieved from the Intégration et Livraison Continues > Pipelines menu (artifacts icon on the right).