https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/operation/opsi_vup/index.html Recent content in 5.3 Actions required when upgrading Ops I version on JP1 Cloud Service/Operations Integration User's Guide Hugo -- gohugo.io en https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/operation/opsi_vup/ticketcustom_incorporate/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/operation/opsi_vup/ticketcustom_incorporate/index.html This section explains the tasks required to upgrade Ops I while preserving Ops I features and incorporating the latest features added in the Ops I upgrade. Users can edit customizable YAML definitions from Ops I to customize Ops I features. For details on customizable YAML files, see “Customizing the default YAML files”. For details on customizing the ticket window, see “Customizing the ticket window”. For details about customizing the workflow window, see “Customizing the workflow window”. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/operation/opsi_vup/ee_update/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/operation/opsi_vup/ee_update/index.html AWX for Ops I has OpsI Automation EE (for execution on Ops I’s SaaS infrastructure) and OpsI Outpost EE (for execution of relay servers) registered. In addition, the base image for the custom execution environment is registered in GitLab by default. When upgrading Ops I, a new version of the OpsI Automation EE execution environment is added to the [Execution Environment] of AWX displayed from the automation application. The sample project “system/awx-ee” for the custom execution environment and the base image for the custom execution environment defined in that project may be updated when Ops I is upgraded.