https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/automation/index.html Recent content in 3.10 Automation on JP1 Cloud Service/Operations Integration User's Guide Hugo -- gohugo.io en https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/automation/auth_reg/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/automation/auth_reg/index.html The authentication information registered in Automation manages the secret information of the target host where the job is executed. This section describes how to register the following authentication information. Authentication information for accessing credentials in GitLab and Ops I Authentication information using PAT (1) Authentication information for accessing credentials in GitLab and Ops I Because Playbooks are stored in GitLab, it is necessary to access GitLab from AWX. This section describes how to register authentication information for accessing credentials in GitLab and Ops I from AWX. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/automation/project/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/automation/project/index.html A project is the directory where the Playbook is stored. In a project, you can set the organization that will use the created project, as well as authentication information for accessing the GitLab repository where “Playbookβ.yaml” is registered, etc. Only users belonging to the organization set here can access this project or the job template that set this project. [Procedure for setting projects] 1. Select the Automation application and then select " https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/automation/inventory/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/automation/inventory/index.html Inventory manages the hosts where jobs can be executed. Only users belonging to the organization set here can execute jobs using this inventory or an inventory. [Registering inventory] 1. Select the Automation application, then select "Inventories" in the "Resources" category on the AWX window displayed in the contents area. 2. When the Inventories window appears, click the "Add" button and then select "Add inventory". The Create new inventory window will be displayed. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/automation/job_template/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/automation/job_template/index.html A job template is a set of definitions combining authentication information, projects, inventories, etc., for executing a job. Through a project, you can link to a Playbook by specifying “Playbookβ.yaml” from the repository set for the project. In addition, by defining the provided Ops I component “awx.run_job_template” in the action of the Task model in the Workflow YAML file, a job template can be automatically executed from the workflow. For details on the provided Ops I component “awx. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/automation/job_confirm/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/automation/job_confirm/index.html 1. Select the Automation application and then select "Jobs" in the "Views" category on the AWX window displayed in the contents area. 2. From the job list, select the name of the job whose results you would like to check. 3. When the job detail window appears, check the execution results from the Details tab or the Output tab. (Figure) Automation Details window