bertha/demoassets repository overview

⁠Latest Tags

Use these images together:

• ppm-dev-9.52_d-2-octane12.60.35.186_dis-jira8.1.0 integrated with Octane and Jira
• octane12.60.35.186_dis-ppm9.52_d-2-2 integrated with PPM [and Jira]
• jira8.1.0-ppm-dev-9.52_d-2 integrated with PPM

Use these images together:

• ppm-dev-9.52_d-2-octane12.60.35.186_dis integrated with Octane
• octane12.60.35.186_dis-ppm9.52_d-2 integrated with PPM

⁠PPM

⁠Run Statement

$ docker run --name ppm -d --shm-size=2g --hostname=ppm.aos.com -p 8087:8080 -p 8088:80 -p 1098:1099 -p 1522:1521 --net demo-net --add-host nimbusserver.aos.com:172.50.0.1 --ip 172.50.10.20 admpresales/ppm:${TAG}

--- Memory footprint at idle: 1.4 GB

⁠Container Usage

URL: http://nimbusserver.aos.com:8087⁠

Username: admin

Password: Password1

Launch Pages URL: http://nimbusserver.aos.com:8088⁠

⁠Adding the demo-net docker network

In order for multiple containers to be visible to one another, they must be attached to a Docker network. This is already done on the NimbusServer VM You can also do this yourself with the following command:

$ docker network create --subnet 172.50.0.0/16 --gateway 172.50.0.1 demo-net

⁠Additional Information

By setting different environment using the variables (-e NAME=VALUE), you can control certain aspects of the application during the run statement.

⁠Dockerfile

https://github.houston.softwaregrp.net/AMSPreSales-Demos/ppm-docker⁠

⁠Octane

⁠Run Statement

$ docker run -d -p 1099:1099 -p 8085:8080 -p 9081:9081 -p 9082:9082 --name octane --hostname octane.aos.com --net demo-net -e OCTANE_HOST=nimbusserver.aos.com --add-host nimbusserver.aos.com:172.50.0.1 --shm-size=2g admpresales/octane:$TAG

--- Memory footprint at idle: 7.5 GB

⁠Container Usage

URL: http://nimbusserver.aos.com:8085⁠

Username: sa@nga

Password: Password1

⁠NOTES

• You MUST use the FQDN nimbusserver.aos.com since nimbusserver alone will cause problems with the ALM Synchronizer and elsewhere.
• You can specify either the IP address of your nimbusserver environment or the nimbusserver alias referenced in your local hosts file. You must specify port 8085 as shown.
• Changing your browser language may have adverse affects on Octane (specifically, you may not be able to add CI servers).
• The Client ID and Client Secret for a given image can be found inside the container in the directory /opt/octane/apikeys

⁠ALM Synchronization

Octane 12.60.10.90 and beyond now allows synchronization with ALM 12.60 images

⁠Adding the demo-net docker network

ALM Octane requires a network which can be built with the following command (preconfigured on the NimbusServer VM):

docker network create --subnet 172.50.0.0/16 --gateway 172.50.0.1 demo-net

⁠Jira

⁠Run Statement

$ docker run -d -p 8099:8080 --name jira --hostname jira.aos.com --add-host nimbusserver.aos.com:172.50.0.1 --net demo-net admpresales/jira:TAG Container Usage

The URL for Jira along with the recommended default username and password, is shown below: http://nimbusserver.aos.com:8099⁠

Username = admin Password = Password1

⁠NOTES

The Jira image is completely non-configured, and will need to be setup by each individual. Instructions are forthcoming. Adding the demo-net docker network

Jira requires a network which can be built with the following command (preconfigured on the NimbusServer VM):

$ docker network create --subnet 172.50.0.0/16 --gateway 172.50.0.1 demo-net

⁠Additional Information

The purpose of making Jira Software available in the Nimbus demo platform is to show integrations from our portfolio to Jira Software environments that many of our customers currently also own and use. This image is not intended to provide the ability to deliver software comparisons, nor is it to be used in any other context other than demonstrating the integrations with our software portfolio.

Jira is manufactured and sold by Atlassian Software, and should not, under any circumstances, be distributed to anyone not in Micro Focus ADM Presales. This is an extremely limited distribution audience and must remain so in order to ensure license compliance for demonstration purposes.

The Jira instance is going to be run using either a permanent license key purchased by each individual SA, or via an evaluation license key that is renewable. Instructions on how to renew an evaluation license key can be found here:

https://confluence.atlassian.com/purchasing/how-can-i-extend-my-evaluation-321257637.html⁠

Jira Software terms of use are important to understand. Failure to follow these terms and conditions can result in termination of your employment and legal liability for Micro Focus. Please ensure that you read and adhere to all of the stated terms and conditions in their license agreement, which can be found here:

Acceptable Use Policy: https://www.atlassian.com/legal/acceptable-use-policy⁠ Customer Agreement: https://www.atlassian.com/legal/customer-agreement⁠