Hitachi

JP1 Version 13 JP1/Integrated Management 3 - Manager Configuration Guide


10.3.1 How to create a Docker image and Podman image

Organization of this subsection

(1) Prepare the followings under the working directory

The files to be prepared under the working directory are the same as for JP1/IM - Agent. Place the configuration files for an add-on program of IM Exporter under the conf directory. When monitoring script exporter targets in a container, include them in the image in the same way.

Here, type the files to be added to the JP1/IM - Agent directory structure.

working directory/
  + conf/
      + jpc_process_exporter.yml#1
      + jpc_script_exporter.yml#2
      + promitor/#3
          + scraper/#4
              + runtime.yaml#5
              + metrics-declaration.yaml#6
          + resource-discovery/#7
              + runtime.yaml#8
              + resource-discovery-declaration.yaml#9

#1: process exporter configuration file(If changing the settings)

#2: script exporter configuration file(If changing the settings)

#3: promitor configuration file directory(If changing the settings)

#4: promitor scraper configuration file directory(If changing the settings)

#5: promitor scraper configuration file (If changing the settings)

#6: promitor scraper configuration file (If changing the settings)

#7: promitor resource discovery configuration file directory (If changing the settings)

#8: promitor resource discovery configuration file (If changing the settings)

#9: promitor resource discovery configuration file (If changing the settings)

The build procedure to connect to Azure with ServicePrincipal is as follows.

  1. In the build procedure described in Building a container environment for integrated agents for JP1/IM - Agent, perform the steps other than step 4 in 10.1.2(6) Setting up Promitor > (b) Configuring authentication information for connecting to Azure and then create the files under the working directory.

  2. After starting the container, perform step 4 in 10.1.2(6) Setting up Promitor > (b) Configuring authentication information for connecting to Azure.

  3. Start the Promitor service. For details, see Building a container environment for integrated agents for service control.

The following is an example of a Docker file.

FROM oraclelinux:8
:
ENV JP1IMAGENT_ADDON_PROMITOR_ACTIVE "no"#
ENV JP1IMAGENT_ADDON_PROCESS_EXPORTER_ACTIVE "yes" 
ENV JP1IMAGENT_ADDON_SCRIPT_EXPORTER_ACTIVE "no" 
:
CMD [ "/bin/bash", "-c", "/opt/start.sh" ] 
#

If "yes", after the container starts, the following log will be output and the service will have a failure status. If you specify the authentication information and restart, the service will start normally.

Validation failed: Azure authentication is not configured correctly - No identity secret was configured for service principle authentication

The following is an example of a service definition file.

[unix_http_server]
file=/tmp/supervisor.sock   ; the path to the socket file
 :
[program:process_exporter]
command=command-line
directory=/opt/jp1ima/bin
autostart=true
stopwaitsecs=180