To setup the demo, you will need to run 2 shell scripts.
First, clone this repo to your local disk that will be able to use oc command to access to your OCP server.
Then, changed path to bin folder and run ./init.sh script to initialize the demo environment. This script will create a few OCP projects to represent dev, test, prod environments. A tools project will be created to keep the CI/CD tools such as jenkins, gogs and etc.
Once the demo environments have been provisioned. Make sure all the PODs under the tools project are all ready running without error. Run the ./initDemoData.sh script to initilize the required demo data.
There are some manual steps required before running the initDemoData.sh script. Please run ./initDemoData.sh -h for more details.
- You may want to increase the resource limits for Jenkins and Nexus. Especially Nexus will need minimum 3GB RAM to run properly. These resource limits can be changed from the init.sh script using parameters before provisioning. Allocation of 4GB will be the best for smooth demo experience. With lower memory allocation, Jenkins build will always fail caused by Nexus keep restarting in the background. Higher memory ensure maven/build are cached once the first built has been done, which helps to cut down a lot of build time for all the subsequence builds. If you restarted the POD or server, make sure you have done a first build before the actual demo.
- Do a chmod +x init.sh if the script is without execution permission.
- Do a chmod +x initDemoData.sh if the script is without execution permission.
To be updated.
