You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/overview.md
+43-29Lines changed: 43 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,17 +9,27 @@ This page provides an overview of Ansible, the project structure and the compone
9
9
10
10
## Ansible Overview
11
11
12
-
[Ansible](https://www.ansible.com/overview/how-ansible-works) models your IT infrastructure by describing how all of your systems inter-relate, rather than just managing one system at a time.
12
+
[Ansible](https://www.ansible.com/overview/how-ansible-works) models your IT
13
+
infrastructure by describing how all of your systems inter-relate, rather than
14
+
just managing one system at a time.
13
15
14
-
It doesn't use any agents nor additional custom security infrastructure, so it's easy to deploy - and most importantly, it uses a very simple language, YAML, in the form of Ansible Playbooks that allow you to describe your automation jobs in a way that approaches plain English.
16
+
It doesn't use any agents nor additional custom security infrastructure, so it's
17
+
easy to deploy - and most importantly, it uses a very simple language, YAML, in
18
+
the form of Ansible Playbooks that allow you to describe your automation jobs in
19
+
a way that approaches plain English.
15
20
16
-
An Ansible playbook contains one or more roles. A role is an independent component which allows reuse of common configuration steps. It consists of a set of tasks used to configure a host to serve a certain purpose, for example, configuring a service. This is depicted in the diagram below.
21
+
An Ansible playbook contains one or more roles. A role is an independent
22
+
component which allows reuse of common configuration steps. It consists of a set
23
+
of tasks used to configure a host to serve a certain purpose, for example,
24
+
configuring a service. This is depicted in the diagram below.
17
25
18
26
Roles are defined using YAML files with a predefined directory structure.
19
27
20
-
A role directory structure contains directories: defaults, vars, tasks, files, templates, meta, and handlers.
28
+
A role directory structure contains directories: defaults, vars, tasks, files,
29
+
templates, meta, and handlers.
21
30
22
-
***defaults** contains default variables for the role. Variables in defaults have the lowest priority so they are easy to override
31
+
***defaults** contains default variables for the role. Variables in defaults
32
+
have the lowest priority so they are easy to override
23
33
***vars** contains variables for the role. Variables in vars have higher priority than variables in the defaults directory
24
34
***tasks** contains the main list of steps to be executed by the role
25
35
***files** contains files which we want to be copied to the remote host. We don’t need to specify a path of resources stored in this directory
@@ -31,7 +41,10 @@ A role directory structure contains directories: defaults, vars, tasks, files, t
31
41
32
42
The project contains a playbook and multiple roles.
33
43
34
-
The ACS playbook can be found in the _playbooks_ directory. Because the project makes use of Ansible role structure, the playbook contains only definitions of the roles, and all the logic is performed by them, thus making the project both granular and easy to maintain.
44
+
The ACS playbook can be found in the _playbooks_ directory. Because the project
45
+
makes use of Ansible role structure, the playbook contains only definitions of
46
+
the roles, and all the logic is performed by them, thus making the project both
47
+
granular and easy to maintain.
35
48
36
49
The playbook uses the following roles:
37
50
@@ -64,36 +77,37 @@ set of instructions.
64
77
## Versioning
65
78
66
79
To understand which Operating System the Alfresco Ansible playbook can work
67
-
against (on the target nodes), please refer to the [Supported
> Support for ACS 7.0 has been deprecated since April 2024, but you can still use the latest playbook that supported it ([v2.6.0](https://github.com/Alfresco/alfresco-ansible-deployment/releases/tag/v2.6.0))
99
113
> Support for ACS 6.2 has been deprecated since November 2022, but you can still use the latest playbook that supported it ([v2.2.0](https://github.com/Alfresco/alfresco-ansible-deployment/releases/tag/v2.2.0))
0 commit comments