Skip to content

Latest commit

 

History

History
146 lines (86 loc) · 5.27 KB

MINI-SETUP.MD

File metadata and controls

146 lines (86 loc) · 5.27 KB

The Prevail 2021 setup

Find your RHOCP user

Find your user:

oc whoami

Example output:

IAM#[email protected]

A) Setup the tools namespace

Edit the configuration file:

# if you like vi
vi ~/config.bc-full

# if you like nano (use ctl O to save, and ctl X to exit)
nano ~/config.bc-full

If you prefer a graphical environment then you could login to the VNC console. This is not preferred as the API tokens that we have to edit later during the lab are long and cannot be pasted through VNC.

Notes:

  • Set your User as value in OCP_ADMIN (example value IAM#[email protected]). Your user has the cluster-role in the IBM Lab Environment;
  • Set your User as value in OCP_USER (example value IAM#[email protected]). This user will become project admin for various projects on your RHOCP cluster;
  • Modify SLACK_URL and SLACK_CHANNEL when you have a slack channel that you can post to (optional).

Install the tools:

bash tools/setup.sh

Note:

  • it will take about 10 to 15 minutes until the setup completes on the IBM Lab Environment.
  • there will be the occasional warning. These can be ignored.

Inspect the tools namespace:

Deploy

Inspect the tools and see if you can login

Aspect Description Default Credentials
sonarqube source vulnerability scanner admin / admin
nexus3 maven artifact repository for builds admin / admin123
silver-platter maven site reports for dependency vulnerability scanning aot-user / ibm-prevail-2021
grafana jmeter performance dashboard root / secret (anonymous access enabled), go to dashboard, manage, tools

B) Setup the tools-images namespace

bash scripts/tools-images/setup.sh

C) Setup the pipelines namespace

Setup port-forwarding:

bash tools/sonarqube/port-forward.sh

Login to sonarqube via the forwarded port ("right-click and open this link"). Default username and password are both admin

It may take half a minute to get connected.

Make a SONAR_QUBE_PAT via create new project and generate a key.

Edit the configuration file, and modify SONAR_QUBE_PAT:

vi ~/config.bc-full

Initialize the pipeline project / namespace:

bash scripts/pipeline/mini-setup.sh

Checkpoint

Login to the pipelines project and see that you have access to the pipelines.

Via the GUI:

Deploy

Or via the CLI:

tkn pipeline list

Example Output

NAME                                  AGE            LAST RUN   STARTED   DURATION   STATUS
vailability-pipeline-prevail-2021     1 minute ago   ---        ---       ---        ---
functionality-pipeline-prevail-2021   1 minute ago   ---        ---       ---        ---
image-intake-pipeline-prevail-2021    1 minute ago   ---        ---       ---        ---
performance-pipeline-prevail-2021     1 minute ago   ---        ---       ---        ---
security-pipeline-prevail-2021        1 minute ago   ---        ---       ---        ---

Inspect the persistent volume claims and see them transition from state Pending to Bound:

oc get pvc

Example Output

NAME                 STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS      AGE
clone-1-pvc          Bound    pvc-51999dec-00f3-466d-82f2-1901a70e8570      20Gi       RWO            ibmc-block-gold   3m21s
clone-2-pvc          Bound    pvc-e0bbda9e-80eb-4f71-a176-c8f3a4bbd120      20Gi       RWO            ibmc-block-gold   3m20s
maven-repo-pvc       Bound    pvc-bf804d58-56aa-46c7-9f78-b2ee4e92de7a      20Gi       RWO            ibmc-block-gold   3m20s
maven-settings-pvc   Bound    pvc-ac96c2dc-3e50-4c13-a64b-7ccd577f3e0f      20Gi       RWO            ibmc-block-gold   3m20s
maven-source-pvc     Bound    pvc-d9b83f9f-0cba-4e60-833c-05a2c422cc41      20Gi       RWO            ibmc-block-gold   3m20s
owasp-repo-pvc       Bound    pvc-8a4a3d68-e82e-48c1-9f99-92bfeb093bfc      20Gi       RWO            ibmc-block-gold   3m20s
sonar-repo-pvc       Bound    pvc-1a3f9162-e48b-47ed-9019-e7a963fa3c51      20Gi       RWO            ibmc-block-gold   3m20s

Inspect the images in the tools namespace:

if [ $(oc get is -n tools | grep 5000 | wc -l) -eq 3 ] ; then echo OK ; else echo NoK ; fi

There must be 3 images. If there are less then inspect:

oc get is -n tools

Example Output

jmeter-prevail-2021   image-registry.openshift-image-registry.svc:5000/tools/jmeter-prevail-2021   latest   26 minutes ago
silver-platter        image-registry.openshift-image-registry.svc:5000/tools/   silver-platter     2.4      
stackrox-ubi          image-registry.openshift-image-registry.svc:5000/tools/   stackrox-ubi       latest   25 minutes ago

And repair if necessary:

cd tools/stackrox/
tools/stackrox/build_stackrox_image.sh
cd -

cd tools/jmeter-performance-test/
tools/jmeter-performance-test/build_jmeter_image.sh
cd -

Trivia

This repo was developed on Redhat CRC where 2 users exist (kubeadmin and developer).

On CRC the setup is run under kubeadmin. On that environment you can make distinction between a cluster-admin and a project admin.

It is not possible to add additional users on the IBM Lab environment.