/
2025-03-13 Meeting Notes

2025-03-13 Meeting Notes

 Date

Mar 13, 2025

 Participants

  • @Eddy Fung@Konstantinos Antonakoglou @bibin Sebastian @Syed Mansoor.A @Gaurav Kumar

 Goals

  • Review any metrics / telemetry information from Porch

  • Review any code change required

 Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

 

 

1

 

@Eddy Fung

Presented some metrics information Porch and will share some of the key ones with the team

 



2

@Syed Mansoor.A

 

3

@Syed Mansoor.A

Porch Performance Testing Setup Guide

1. Set Up Development Environment

Run the following script to set up the development environment:

https://github.com/nephio-project/porch/blob/main/scripts/setup-dev-env.sh

2. Build and Deploy Porch

Execute the command below to build and deploy Porch in a Kubernetes Kind cluster:

make run-in-kind

Once deployment is complete, you should see the related pods running.

3. Create a Demo Namespace

Create a namespace for the demo setup:

kubectl create namespace porch-demo

4. Set Up Gitea Credentials

Create a secret to store Gitea credentials within the demo namespace:

kubectl create secret generic gitea \     --namespace=porch-demo \     --type=kubernetes.io/basic-auth \     --from-literal=username=nephio \     --from-literal=password=secret

5. Define Gitea Repositories in Porch

Apply the repository configuration file:

kubectl apply -f porch-repositories.yaml

6. Verify Repository Setup

Check the status of repositories in the porch-demo namespace:

kubectl get repositories -n porch-demo

Expected output:

NAME                  TYPE   CONTENT   DEPLOYMENT   READY   ADDRESS edge1                 git    Package   true         True    http://172.18.255.200:3000/nephio/edge1.git external-blueprints   git    Package   false        True    https://github.com/nephio-project/free5gc-packages.git management            git    Package   false        True    http://172.18.255.200:3000/nephio/management.git

7. Run Performance Tests

Navigate to the performance test directory:

cd porch/test/performance/

Execute the performance test command:

E2E=1 go test -v ./... -repos=4 -packages=4 -timeout 60m
  • repos: Number of repositories to test

  • packages: Number of package revisions in each repository

Once the tests begin, the metrics can be observed.

8. Verify Prometheus Targets

Check the Prometheus targets:

http://localhost:9090/targets

You should be able to run PromQL queries here.

9. Check Metrics Output

Retrieve the captured metrics using:

curl -k http://localhost:2113/metrics

This should return all the collected performance metrics from the test execution.

 Action items

Team will assess the Metrics provided by @Syed Mansoor.A

 Decisions

Related content