Skip to content

README.md

Latest commit

 

History

History
61 lines (48 loc) · 3.11 KB

README.md

File metadata and controls

61 lines (48 loc) · 3.11 KB

controlm_toolset

Docker examples

Please let me know of improvements you think would be useful

For future

  • test the STOPSIGNAL dockerfile command and use it in the run_register to test for non-usual stop signals.

Comments

  • Purpose: create docker image to show possibility of agent running in docker
  • Files
    • build_docker_image.sh: Builds the docker image
    • check_docker_container.sh: uses docker inspect to get the return code and log of the container execution.
    • clean_docker_container.sh: Clean orphan images
    • conn2_docker_container.sh: allows for connecting to the container for verifications
    • remove_docker_container.sh: use docker stop to stop the container
      • Sends SIGTERM and SIGKILL after timeout.
      • Timeout changed to 60 secs to allow for orderly termination.
    • run_docker_container.sh: runs the container
      • Ensure you change the endpoint and token for the build process.
      • Check the variables to install plugins as required
      • Exit codes
        • 0 = exited normally. Agent deleted successfully
        • 13 = deletion of agent from hostgroup failed. Agent may still be registered and member of the hostgroup.
        • 14 = deletion of agent failed. Agent may still be registered.
    • signal_docker_container.sh: sends a signal for the container to process
      • Sends SIGUSR1 by default. Other signals (SIGTERM, SIGHUP, SIGKILL) can also be sent. SIGTERM is trapped in addition to SIGUSR1, but no others. SIGKILL will terminate the container immediatly. Others may be ignored.
      • images/dockerfile
      • images/run_register_controlm.sh: is the CMD that is being executed for the container work.
      • images/deploy_test_jobs.json: test jobs. Not required, but will need to change the dockerfile and the run_register_controlm.sh
      • Other files as needed

Helix Control-M

  • Note: this is an old release. Likely works with new releases, but customization and changes may be needed.
  • Find the files here
  • There are two dockerfiles in the images directory
  • Copy the dockerfile you need to "dockerfile" and run the build.

Self-Hosted (a.k.a. On-Premise)

  • Note: Updated to 9.0.21.300
  • Find the files here
  • The Dockerfile is based on AlmaLinux:latest
    • You will need to pull from the Docker Hub to your repositoryCopy the dockerfile you need to "dockerfile" and run the build.
  • The Dockerfile and other required files are in the images directory
    • Note that the dockerfile also implements patches. You need to download them from EPD.
    • The dockerfile installs the GCP Composer plugin as an example. Follow the appropriate documentation to install the plugins on your specific Control-M environment.

Information about Kubernetes

For the Kubernetes best practice information see here. This implementation is NOT supported by BMC.

See in the link following the **Control-M for Kubernetes **supported implementation.