@@ -410,7 +410,8 @@ machine. The supported features are:
410
410
can be installed during the contextualization of the virtual machine if it
411
411
is not installed.
412
412
413
- There are some **special ** type of application that starts with ``ansible.modules. `` or ``ansible.collections. ``.
413
+ There are some **special ** type of application that starts with ``ansible.roles. ``
414
+ (``ansible.modules. `` in < IM 1.14 ) or ``ansible.collections. ``.
414
415
These applications installs `ansible roles <https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_reuse_roles.html >`_ or
415
416
`ansible collections <https://docs.ansible.com/ansible/latest/collections_guide/index.html >`_
416
417
that can be used in the ``configure `` sections of the RADL.
@@ -420,14 +421,14 @@ machine. The supported features are:
420
421
421
422
There are three type of ansible modules/roles:
422
423
423
- * `Ansible Galaxy <https://galaxy.ansible.com/ >`_ roles: ``ansible.modules .micafer.hadoop ``: The user
424
- specifies the name of the galaxy role afther the string ``ansible.modules . ``
425
- * HTTP URL: ``ansible.modules .https://github.com/micafer/ansible-role-hadoop/archive/master.tar.gz|hadoop ``: The user
426
- specifies an HTTP URL afther the string ``ansible.modules . ``. The file must be compressed.
424
+ * `Ansible Galaxy <https://galaxy.ansible.com/ >`_ roles: ``ansible.roles .micafer.hadoop ``: The user
425
+ specifies the name of the galaxy role afther the string ``ansible.roles . ``
426
+ * HTTP URL: ``ansible.roles .https://github.com/micafer/ansible-role-hadoop/archive/master.tar.gz|hadoop ``: The user
427
+ specifies an HTTP URL afther the string ``ansible.roles . ``. The file must be compressed.
427
428
It must contain the ansible role content. Furthermore the user can specify the rolename using
428
429
a ``| `` afther the url, as shown in the example.
429
- * Git Repo: ``ansible.modules .git+https://github.com/micafer/ansible-role-hadoop|hadoop ``: The user specifies a Git repo
430
- (using the git scheme in the URL) afther the string ``ansible.modules . ``. Furthermore the
430
+ * Git Repo: ``ansible.roles .git+https://github.com/micafer/ansible-role-hadoop|hadoop ``: The user specifies a Git repo
431
+ (using the git scheme in the URL) afther the string ``ansible.roles . ``. Furthermore the
431
432
user can specify the rolename using a ``| `` afther the url, as shown in the example.
432
433
433
434
``nat_instance = yes|no ``
@@ -592,7 +593,7 @@ Including roles or collections of Ansible Galaxy
592
593
-------------------------------------------------
593
594
594
595
To include a role available in Ansible Galaxy a special application requirement
595
- must be added: it must start with: "ansible.modules " as shown in the following
596
+ must be added: it must start with: "ansible.roles " as shown in the following
596
597
example. In this case the Ansible Galaxy role called "micafer.hadoop" will be installed::
597
598
598
599
network net (outbound = 'yes')
@@ -603,7 +604,7 @@ example. In this case the Ansible Galaxy role called "micafer.hadoop" will be in
603
604
net_interface.0.connection = "net" and
604
605
disk.0.os.name = "linux" and
605
606
disk.0.os.flavour = "ubuntu" and
606
- disk.0.applications contains (name="ansible.modules .micafer.hadoop")
607
+ disk.0.applications contains (name="ansible.roles .micafer.hadoop")
607
608
)
608
609
609
610
Then the configuration section of the RADL can use the role as described in the role's
@@ -620,7 +621,7 @@ documentation. In the particular case of the "micafer.hadoop" role is the follow
620
621
621
622
You can request an specific version/tag/branch of a galaxy role using the following format::
622
623
623
- disk.0.applications contains (name="ansible.modules .micafer.hadoop,v1.0.0")
624
+ disk.0.applications contains (name="ansible.roles .micafer.hadoop,v1.0.0")
624
625
625
626
Similarly, to include a collection available in Ansible Galaxy it must start with:
626
627
"ansible.collections" as shown in the following example. In this case the Ansible Galaxy
0 commit comments