Skip to content

Latest commit

 

History

History
66 lines (49 loc) · 4.38 KB

README.md

File metadata and controls

66 lines (49 loc) · 4.38 KB
Raw

Building a Docker image of Dell EMC OpenManage Ansible Modules

Build a docker image for Dell EMC OpenManage Ansible Modules by using the Docker Engine and the docker file for OpenManage Ansible Modules. Download the OpenManage Ansible Modules docker file from here.

For more information about the Docker Engine and how to install the Docker Engine, see https://docs.docker.com/engine/.

The docker file for OpenManage Ansible Modules contains the following packages:

Disclaimer: You use the docker image for Dell EMC OpenManage Ansible Modules and any underlying image source packages at your own risk. The docker image for Dell EMC OpenManage Ansible Modules and any underlying image source packages may not meet your requirements or expectations. It could include quality, technical or other mistakes, inaccuracies or typographical errors. Dell makes no express warranties, and disclaims all implied warranties, including merchantability, fitness for a particular purpose, title, and non-infringement as well as any warranty arising by statute, operation of law, course of dealing or performance or usage of trade regarding the docker image for Dell EMC OpenManage Ansible Modules and any underlying image source packages. Dell has no liability to you for any damages that arise out of or relate to your use of the docker image for Dell EMC OpenManage Ansible Modules and any underlying image source packages.

How to build the Docker image

To build the docker image, do the following:

  1. Download and install Docker Engine on your system.

  2. Download and save the OpenManage Ansible modules docker file from here. Ensure that this docker file is downloaded on the same system where the Docker Engine is installed.

  3. Run the following Command:

    docker build -t dellemc/openmanage-ansible-modules .

    A docker image is created with the name specified in the command. That is, dellemc/openmanage-ansible-modules. The size of this image is around 379 MB.

    Note:

    • Run the command from the same directory where the Dockerfile is downloaded. If not use the option --file to specify the path to the Dockerfile.
    • The OpenManage Enterprise docker file uses the official docker image python:3-slim as a base.
    • Ensure that the docker.io registry search path is enabled on the system if the Docker Engine fails to download the base image.

  4. To verify if the image is created successfully, run the following command:

    docker image ls

    If the image is created successfully, this command lists the image created in step 3. That is, dellemc/openmanage-ansible-modules.

Add playbook, variable files and inventory

The Docker image of OpenManage Ansible Modules does not contain the playbook and the required configuration to run a task.

The latest sample playbooks and examples are available in the playbooks directory.

After creating the playbook, bind mount the folder containing the playbook, variable and inventory files to the target mount point /dellemc using the option -v.

Running a playbook

Run the playbook using the following command after the playbook, inventory and optional variable files are added to the current working directory.

docker run --rm \
    -v $(pwd):/dellemc dellemc/openmanage-ansible-modules:latest \
    -v playbook.yml -i inventory -t getlcstatus

Note:

  • To allow access to mounted shares in the Docker container, use the volume or bind mount option when running export or import server configuration profile tasks.
  • The playbook may fail if Security-Enhanced Linux (SELinux) is configured on the system. Refer the Docker documentation on how to bind mount folders using SELinux label.

Running ad-hoc commands

Ansible ad-hoc commands can also be used. The following example command shows how to to view the status of a Lifecycle Controller.

docker run --rm \
    --entrypoint '/usr/local/bin/ansible' \
    dellemc/openmanage-ansible-modules:latest localhost \
    -m idrac_lifecycle_controller_status_info -a "idrac_ip=192.168.10.1 idrac_user=user idrac_pwd=password"