Public Repository

Last pushed: 2 years ago
Short Description
HP Operations Orchestration Community Edition
Full Description

########################################################################
Please Note!
We have created a new repo for HP Software images, and we will maintain the OOCE image there.

From now on, please pull from hpsoftware/ooce:

https://registry.hub.docker.com/u/hpsoftware/ooce/

########################################################################

HP Operations Orchestration Community Edition images

The images in the repository include HP Operations Orchestration Community Edition Central Server with deployed content for orchestrating Docker, Puppet, Nexus, Jenkins and more.
It uses a Postgres 9.3 DB.

Volumes:
"/etc/postgresql", "/var/log/postgresql", "/var/lib/postgresql"

Exposed Ports:
8080(http),8443(https),5432(Postgres)

HP OO Central logs are located in /usr/local/hp/oo/central/var/logs

The documentation for the deployed content packs is saved in /usr/local/hp/oo/content

Database Administrator credentials:
User: postgres
Password: foobar

Usage:

sudo docker run -t -i --name ooce -p 0000:8080 -p 0000:8443 -p 0000:5432 -d hpoo/ooce:latest

Then run the docker ps command in order to see which ports on your docker host were allocated. It takes about two minutes until Central is up. To access Central, open a browser to http://<docker host ip>:<allocated http port>

The images are tagged in the following format: <OOCE version>.<image version>
e.g. The first image for OOCE 10.20 is tagged as 10.20.1

In case you want to create new flows and operations, you will need the Windows based HP Operations Orchestration Studio.
In order to install OO Studio and develop your own content:

  1. Copy the studio installation and the content packs from your container (named ooce in this example) to your Docker host: docker cp ooce:/usr/local/hp/oo/content/. .

  2. Copy the files from your Docker host to you Windows desktop.

  3. Install HP OO Studio (community-installer-win64-studio.exe).

  4. Open Studio and deploy the content packs.

For more details, guides and documentation of HP Operations Orchestration, visit us at https://hpln.hp.com/group/operations-orchestration

Docker Pull Command
Owner
hpoo

Comments (5)
hpoo
2 years ago

Hi All.
We have created a new new repo for HP Software images, and we will maintain the OOCE image there.

From now on, please pull from hpsoftware/ooce:

https://registry.hub.docker.com/u/hpsoftware/ooce/

Thanks,
Tal.

ophintor
2 years ago

Great job!! :-)

hpoo
3 years ago

fixed the "--name" thing with html encoding
you can copy and it will work

hpoo
3 years ago

Hi.
Thanks for the feedback.
The --name was changed to -name by the web site editor.just amatter of http encoding issue.

Regarding the port mapping: 000:5432 automatically mapped a free port on your Docker host. This is valid syntax. another option is to use a port number you know is free. eg 7000:5432
This is actually my favorite option.

Regards,
Tal.

evkruining
3 years ago

Great stuff!

Only thing is that I had to modify the docker command slightly. The -name option is depreciated and in above example, the port mapping doesn't seem right (but that might just be me). The command that worked perfectly for me is:

 docker run -t -i –name=“ooce” -p 8080:8080 -p 8443:8443 -p 5432:5432 -d hpoo/ooce:latest

I already have OO Studio installed on a windows box so I didn't need to copy it from the container but I think the copy content code should look like this (at least that worked for me):

 docker cp ooce:/usr/local/hp/oo/content/. /tmp/