Public | Automated Build

Last pushed: a year ago
Short Description
Dell OpenManage to manage and monitor your hardware.
Full Description

Dell OpenManage

Dockerized OpenManage Server Administrator (OMSA), built on top of official CentOS images.

Configuration

  • container has to run in privilged mode so that the host hardware can be exposed to it.
  • specifying --net=host exposes the host's network interfaces to the container, otherwise they will not be available.
  • default command: /opt/dell/srvadmin/sbin/srvadmin-services.sh restart so that services can start cleanly in case container is stopped and then restarted.
  • login credentials: root / password

Where this image has been tested (some more than others)

  • RHEL 7
  • SLES 12
  • CentOS 7
  • Ubuntu Server 12.04 & 14.04
  • Debian 7 / 8

Run example

$ docker run --privileged -d -p 1311:1311 --restart=always \
    --net=host -v /lib/modules/`uname -r`:/lib/modules/`uname -r` \
    --name=omsa82 jdelaros1/openmanage

Testing without volume mounting /lib/modules resulted in mixed results across different servers, so I added this requirement back.

Once the container starts, give it about 20-25 seconds for all the OpenManage services to start inside the container.

Usage examples

You can monitor your server by going to https://your-server:1311. Use the login credentials given above. You can also run commands from a command console:

$ docker exec omsa82 omreport chassis bios
BIOS Information

Manufacturer : Dell Inc.
Version      : 1.2.6
Release Date : 06/08/2015

$ docker exec omsa82 omreport chassis processors
Processors Information

Health : Ok

Index             : 0
Status            : Ok
Connector Name    : CPU1
Processor Brand   : Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz
Processor Version : Model 63 Stepping 2
Current Speed     : 2400  MHz
State             : Present
Core Count        : 8

Index             : 1
Status            : Ok
Connector Name    : CPU2
Processor Brand   : Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz
Processor Version : Model 63 Stepping 2
Current Speed     : 2400  MHz
State             : Present
Core Count        : 8

SNMP support

This image does not have support for SNMP. To create an image with SNMP support, look here for an updated Dockerfile. When running this image, don't forget to open port 161/udp.

$ docker run --privileged -d -p 161:161/udp -p 1311:1311 --restart=always \
    -v /lib/modules/`uname -r`:/lib/modules/`uname -r` \
    --name=omsa82 jdelaros1/openmanage

Known Issues

  • OS information reported is for the container, not the host.

Support

Please note this image is provided as-is and not supported by Dell in any shape or form.

Report problems or provide feedback

If you run into any problems or would like to provide feedback, please open an issue here or send a note to the Linux-PoweEdge mailing list.

Docker Pull Command
Owner
jdelaros1
Source Repository

Comments (7)
jdelaros1
a year ago

Thanks @ungoliant for your interest and comments. As far as volume-mounting /etc/passwd, sure that is possible but should up to each user to implement. I personally think that having a separate /etc/passwd is better since it keeps the container environment as isolated as possible. And as far as the SSL connection, that will be a "feature" for the OMSA development team to decide, although I think we can all agree that security is paramount these days and not something that is optional.

ungoliant
a year ago

"The root that you create with container creation" means "The root user you create with container creation"

ungoliant
a year ago

Hello Jose!

Thank you very much for your efforts creating this Docker image.
I come here after I see that Dell isn't supporting Debian/Ubuntu anymore in their apt repository.
As it is, your Dockerfile is a great example on how somebody may create their own docker container, but I think is not advisable to just use this docker container in production.
The issues I see:

  • The root that you create with container creation. I would try something like bind mounting /etc/passwd and /etc/shadow in ro instead, to get the previous behaviour of using the local users.
  • The SSL configuration. It would be good if by default SSL came disabled, and enabled only on request if we provide the needed files as another volume. Why SSL disabled by default? Because it may be easier to run an apache reverse proxy in front to finish the SSL connections instead of dealing with the configuration of another application.
    Cheers!
jdelaros1
a year ago

@rocketraman, image was not tested against Fedora, only enterprise distributions. I tried months ago just for fun and run into several issues, but did not pursue it further.

rocketraman
a year ago

Does not work on Fedora 23. Attempts to build DKS modules at startup and fails.

jdelaros1
a year ago

Yup issue has been fixed in latest build. Thanks to mfischer-zd for his pull request in github.

shulin
a year ago

Not working.

:~# docker run --privileged -d -p 1311:1311 --restart=always -v /lib/modules/uname -r:/lib/modules/uname -r --name=omsa81 jdelaros1/openmanage:latest
WARNING: Your kernel does not support memory swappiness capabilities, memory swappiness discarded.
fa0f4c4138ea3c69abe6c37e764c172616de0a45506cf58fcf04f397b4859c68

:~# docker logs omsa81
Failed to get D-Bus connection: No connection to service manager.
Stopping dsm_om_shrsvc (via systemctl): [FAILED]
Failed to get D-Bus connection: No connection to service manager.
Stopping dsm_om_connsvc (via systemctl): [FAILED]
Failed to get D-Bus connection: No connection to service manager.
Stopping dataeng (via systemctl): [FAILED]
Failed to get D-Bus connection: No connection to service manager.
Stopping instsvcdrv (via systemctl): [FAILED]
Failed to get D-Bus connection: No connection to service manager.
Starting instsvcdrv (via systemctl): [FAILED]
Failed to get D-Bus connection: No connection to service manager.
Starting dataeng (via systemctl): [FAILED]

:~# docker images
jdelaros1/openmanage latest 03f95bb52aae 2 weeks ago 926.6 MB