Skip to content

Commit 8c6c053

Browse files
authored
Merge pull request #666 from acch/name_mapping_table
Add role name mapping table to migration guide
2 parents 9281000 + c9090dc commit 8c6c053

File tree

1 file changed

+103
-42
lines changed

1 file changed

+103
-42
lines changed

MIGRATING.md

+103-42
Original file line numberDiff line numberDiff line change
@@ -14,48 +14,109 @@ All playbooks using the Ansible roles provided by this project need to adapt thi
1414

1515
The following steps need to be taken in order to consume the `main` branch in your own projects:
1616

17-
- Repository contents need to be placed in a `collections/ansible_collections/ibm/spectrum_scale` directory, adjacent to your playbooks. The easiest way to do this is to clone the correct branch into the appropriate path:
18-
19-
```shell
20-
$ git clone -b main https://github.com/IBM/ibm-spectrum-scale-install-infra.git collections/ansible_collections/ibm/spectrum_scale
21-
```
22-
23-
The resulting directory structure should look similar to this:
24-
25-
```shell
26-
my_project/
27-
├── collections/
28-
│ └── ansible_collections/
29-
│ └── ibm/
30-
│ └── spectrum_scale/
31-
│ └── ...
32-
├── hosts
33-
└── playbook.yml
34-
```
35-
36-
- Once the repository contents are available in the appropriate path, roles can be referenced by using their Fully Qualified Collection Name (FQCN). A minimal playbook should look similar to this:
37-
38-
```yaml
39-
# playbook.yml:
40-
---
41-
- hosts: cluster01
42-
roles:
43-
- ibm.spectrum_scale.core_prepare
44-
- ibm.spectrum_scale.core_install
45-
- ibm.spectrum_scale.core_configure
46-
- ibm.spectrum_scale.core_verify
47-
```
48-
49-
Refer to the [Ansible User Guide](https://docs.ansible.com/ansible/latest/user_guide/collections_using.html#using-collections-in-a-playbook) for details on using collections, including alternate syntax with the `collections` keyword.
50-
51-
Note that all role names have changed:
52-
53-
- Old naming: `[component]/[precheck|node|cluster|postcheck]`
54-
- New naming: `[component]_[prepare|install|configure|verify]`
55-
56-
Refer to the examples in the [samples/](samples/) directory for a list of new role names.
57-
58-
- Some variables have been renamed for consistency as well, but it's expected that these changes only affect very few users. See [#590](https://github.com/IBM/ibm-spectrum-scale-install-infra/pull/590) for details, and refer to [VARIABLESNEW.md](VARIABLESNEW.md) for a complete listing of all available variables.
17+
- Repository contents need to be placed in a `collections/ansible_collections/ibm/spectrum_scale` directory, adjacent to your playbooks. The easiest way to do this is to clone the correct branch into the appropriate path:
18+
19+
```shell
20+
$ git clone -b main https://github.com/IBM/ibm-spectrum-scale-install-infra.git collections/ansible_collections/ibm/spectrum_scale
21+
```
22+
23+
The resulting directory structure should look similar to this:
24+
25+
```shell
26+
my_project/
27+
├── collections/
28+
│ └── ansible_collections/
29+
│ └── ibm/
30+
│ └── spectrum_scale/
31+
│ └── ...
32+
├── hosts
33+
└── playbook.yml
34+
```
35+
36+
- Once the repository contents are available in the appropriate path, roles can be referenced by using their Fully Qualified Collection Name (FQCN). A minimal playbook should look similar to this:
37+
38+
```yaml
39+
# playbook.yml:
40+
---
41+
- hosts: cluster01
42+
roles:
43+
- ibm.spectrum_scale.core_prepare
44+
- ibm.spectrum_scale.core_install
45+
- ibm.spectrum_scale.core_configure
46+
- ibm.spectrum_scale.core_verify
47+
```
48+
49+
Refer to the [Ansible User Guide](https://docs.ansible.com/ansible/latest/user_guide/collections_using.html#using-collections-in-a-playbook) for details on using collections, including alternate syntax with the `collections` keyword.
50+
51+
Note that all role names have changed:
52+
53+
- Old naming: `[component]/[precheck|node|cluster|postcheck]`
54+
- New naming: `[component]_[prepare|install|configure|verify]`
55+
56+
Refer to the [name mapping table](#role-name-mapping-table) for a list of new role names.
57+
58+
- Some variables have been renamed for consistency as well, but it's expected that these changes only affect very few users. See [#590](https://github.com/IBM/ibm-spectrum-scale-install-infra/pull/590) for details, and refer to [VARIABLESNEW.md](VARIABLESNEW.md) for a complete listing of all available variables.
59+
60+
## Role Name Mapping Table
61+
62+
| `master` branch | `main` branch |
63+
| -------------------------------- | ---------------------------------------- |
64+
| callhome/cluster | ibm.spectrum_scale.callhome_configure |
65+
| callhome/node | ibm.spectrum_scale.callhome_install |
66+
| callhome/postcheck | ibm.spectrum_scale.callhome_verify |
67+
| callhome/precheck | ibm.spectrum_scale.callhome_prepare |
68+
| core/cluster | ibm.spectrum_scale.core_configure |
69+
| core/common | ibm.spectrum_scale.core_common |
70+
| core/node | ibm.spectrum_scale.core_install |
71+
| core/postcheck | ibm.spectrum_scale.core_verify |
72+
| core/precheck | ibm.spectrum_scale.core_prepare |
73+
| core/upgrade | ibm.spectrum_scale.core_upgrade |
74+
| gui/cluster | ibm.spectrum_scale.gui_configure |
75+
| gui/node | ibm.spectrum_scale.gui_install |
76+
| gui/postcheck | ibm.spectrum_scale.gui_verify |
77+
| gui/precheck | ibm.spectrum_scale.gui_prepare |
78+
| gui/upgrade | ibm.spectrum_scale.gui_upgrade |
79+
| nfs/cluster | ibm.spectrum_scale.nfs_configure |
80+
| nfs/common | ibm.spectrum_scale.ces_common |
81+
| nfs/node | ibm.spectrum_scale.nfs_install |
82+
| nfs/postcheck | ibm.spectrum_scale.nfs_verify |
83+
| nfs/precheck | ibm.spectrum_scale.nfs_prepare |
84+
| nfs/upgrade | ibm.spectrum_scale.nfs_upgrade |
85+
| remote_mount/ | ibm.spectrum_scale.remotemount_configure |
86+
| scale_auth/upgrade | ibm.spectrum_scale.auth_upgrade |
87+
| scale_ece/cluster | ibm.spectrum_scale.ece_configure |
88+
| scale_ece/node | ibm.spectrum_scale.ece_install |
89+
| scale_ece/precheck | ibm.spectrum_scale.ece_prepare |
90+
| scale_ece/upgrade | ibm.spectrum_scale.ece_upgrade |
91+
| scale_fileauditlogging/cluster | ibm.spectrum_scale.fal_configure |
92+
| scale_fileauditlogging/node | ibm.spectrum_scale.fal_install |
93+
| scale_fileauditlogging/postcheck | ibm.spectrum_scale.fal_verify |
94+
| scale_fileauditlogging/precheck | ibm.spectrum_scale.fal_prepare |
95+
| scale_fileauditlogging/upgrade | ibm.spectrum_scale.fal_upgrade |
96+
| scale_hdfs/cluster | ibm.spectrum_scale.hdfs_configure |
97+
| scale_hdfs/node | ibm.spectrum_scale.hdfs_install |
98+
| scale_hdfs/postcheck | ibm.spectrum_scale.hdfs_verify |
99+
| scale_hdfs/precheck | ibm.spectrum_scale.hdfs_prepare |
100+
| scale_hdfs/upgrade | ibm.spectrum_scale.hdfs_upgrade |
101+
| scale_hpt/node | ibm.spectrum_scale.afm_cos_install |
102+
| scale_hpt/postcheck | ibm.spectrum_scale.afm_cos_verify |
103+
| scale_hpt/precheck | ibm.spectrum_scale.afm_cos_prepare |
104+
| scale_hpt/upgrade | ibm.spectrum_scale.afm_cos_upgrade |
105+
| scale_object/cluster | ibm.spectrum_scale.obj_configure |
106+
| scale_object/node | ibm.spectrum_scale.obj_install |
107+
| scale_object/postcheck | ibm.spectrum_scale.obj_verify |
108+
| scale_object/precheck | ibm.spectrum_scale.obj_prepare |
109+
| scale_object/upgrade | ibm.spectrum_scale.obj_upgrade |
110+
| smb/cluster | ibm.spectrum_scale.smb_configure |
111+
| smb/node | ibm.spectrum_scale.smb_install |
112+
| smb/postcheck | ibm.spectrum_scale.smb_verify |
113+
| smb/precheck | ibm.spectrum_scale.smb_prepare |
114+
| smb/upgrade | ibm.spectrum_scale.smb_upgrade |
115+
| zimon/cluster | ibm.spectrum_scale.perfmon_configure |
116+
| zimon/node | ibm.spectrum_scale.perfmon_install |
117+
| zimon/postcheck | ibm.spectrum_scale.perfmon_verify |
118+
| zimon/precheck | ibm.spectrum_scale.perfmon_prepare |
119+
| zimon/upgrade | ibm.spectrum_scale.perfmon_upgrade |
59120

60121
## Migration script
61122

0 commit comments

Comments
 (0)