Pelorus Demo
Assumptions
- Github SSH key is setup on the machine where the demo will run.
- Ansible is installed
- oc command line tools installed
- Logged into OCP Cluster
Goal
In this demo, you will get a taste of how Pelorus captures a change going through the application's delivery cycle.
- Initializing Pelorus sets the baseline by looking at existing, stored data
- Running the demo script will create a new commit to go through the pipeline
- Watch as the metrics and trends change as new versions roll out
Pelorus should be used as a conversation tool to read the trends in metrics and react by making informed investments in the software delivery process.
Prerequisites
Pelorus is up and running
Clone the pelorus repo.
Fork the RedHat COP Container Pipeline Repo, then clone (using ssh).
The location of the repo will be passed as an argument to the pelorus demo script (i.e. /home/
The second argument the script takes is the url of the forked repo, so for example ,"https://github.com/kenwilli/container-pipelines.git".
Flow
- Deploy sample application (basic-nginx)
- Make changes to the application (adding a line to index.html)
- commit changes to source control
- redeploy application with the changes to be captured by pelorus
Execution
An "idle" state could resemble:
>:mag: **Note**<br/>
>Dashboard can be found by going to grafana which url can found with:
>`oc get route grafana-route -o json | jq -r '.spec.host'`
>
> And navigating Home(top left) -> pelorus -> Softare Delivery Performance
Run the demo script
pelorus/demo/demo.sh <path to container-pipelines> <url to forked repo>
The script will start and will begin to run the ansible-applier on the
A prompt will appear on the screen waiting for user input, the user can "rerun" the script. What this will do is create a change in the index.html file, git commit and push it to the