Description :

This pipeline was designed to build a performance Bugfest-like environment.

1. HOW TO CREATE PERF ENV
2. HOW TO BUILD UI
3. HOW TO UPDATE PERF ENV
4. POSSIBILITY ISSUES AFTER UPDATE
5. HOW TO CHECK LOGS OF MODULES TO RANCHER

1. HOW TO CREATE PERF ENV

Link: https://jenkins-aws.indexdata.com/job/performance_framework/job/spin_up_perf_create/

Build with parameter

Available parameters:

release_version, teamName, UI_platform_complete, autoApprove, buildUI, pauseTime

Parameter Release_version

kiwi-bugfest-10-28-2021
juniper-bugfest-01-10-2021
ptf-iris-2-2021-07-08
bis1-v2-community-2021-04-01
ptf-kcp1-kiwi-01-18-2022

kcon-kiwi-sanitized-2022-02-14Module list of the latest release (KIWI):

Parameter teamName:

This parameter specifies the name of environment and access parameters in Rancher. Admin and members of github teamName team have access to Rancher to configure module deployment.

Values:

metadata, ptf, concorde, core-functional, core-platform, falcon, volaris, folijet, firebird, thunderjet, spitfire, vega

Also teamName specifies endpoint for: FOLIO, OKAPI, pgAdmin, edge modules

Parameters UI_platform_complete & buildUI:

By default, docker image docker.dev.folio.org/platform-complete:<teamName>-perf-latest is used. If buildUI = true then repo platform-complete/<UI_platform_complete> is used to build that docker image.

UI_paltform_complete values: master, R2-2021, R1-2021.
Note!!! Pipeline BUILD-UI only applicable for simple Rancher env

Parameter  pauseTime:

Specifies duration of work of environment.
Values: 1h, 2h, ..., 8h, week, infinity(not tested)
Env can be stoped in any time if there is no more activities with it.

Updates:
Date Changes:
28.10.2021
Rancher-46:

New option kiwi-bugfest-10-28-2021 is added.

New parameter added UI_platform_complete is added.

With Kiwi release new version of postgre is used. (10.4 => 12.7)

27.09.2021 Rancher-29:
New option juniper-bugfest-01-10-2021 is added.

2. HOW TO BUILD UI  ( if you need only ui-image)

link: https://jenkins-aws.indexdata.com/job/performance_framework/job/perf-env.ui/

Parameter teamName:

This parameter specifies the name of environment and access parameters in Rancher. Admin and members of github teamName team have access to Rancher to configure module deployment.

Values:

metadata, ptf, concorde, core-functional, core-platform, falcon, volaris, folijet, firebird, thunderjet, spitfire, vega

Parameter TenantName

add your tenant

Parameters UI_platform_complete & buildUI:

By default, docker image docker.dev.folio.org/platform-complete:<teamName>-perf-latest is used. If buildUI = true then repo platform-complete/<UI_platform_complete> is used to build that docker image.

for example :

docker.dev.folio.org/platform-complete docker.dev.folio.org/platform-complete:bulk-edit-34

UI_paltform_complete values: snapshot, master

How to use UI

1. go to rancher →choose your environment → apps → platform-complete

2. upgrate  module need to change image 

3. HOW TO UPDATE PERF ENV ( backend modules , ui moldules)

link: https://jenkins-aws.indexdata.com/job/performance_framework/job/spin_up_perf_migrate/

for example using perf-bulk-edit to update env 

1. choose release_version parameter 

        kcon-kiwi-sanitized-2022-02-14
        kiwi-bugfest-10-28-2021
        juniper-bugfest-01-10-2021
       ptf-iris-2-2021-07-08
       bis1-v2-community-2021-04-01
       ptf-kcp1-kiwi-01-18-2022

2.  choose branch ( build modules to https://github.com/folio-org/platform-complete)

snapshot - includes all  actually version testing modules

master - includes reliase versions to modules

3. TENANT_ID  - add your tenant for use

4.  autoApprove - choose if you want automatically run pipeline after plan

5. buildUI - it possible build UI into pipeline 

4. POSSIBILITY ISSUES AFTER UPDATE  ( for example using perf-builk-edit)

1. failed pipeline to start 

was found off problems with  subversions to postgres  :

• click on failed build
• replay 
• main script 
• if needs using  kiwi-bugfest-10-28-2021  should be change  7 --> 8 subversion
• run

was found off problems with size to versions of modules  ( local problems ) 

• click on failed build 
• replay
• script1
• find string 41-42 , need to change:
•         long numA = verA[i].toLong()
          long numB = verB[i].toLong()
• run

2.   issues connected with rancher 

• if not possible open UI for tenant :  need to check mod-permissions add more limits  to module (pods)    
• go to rancher → add your env
• apps → mod-permissions
• upgrate → add answer  "resources.limits.memory 2048Mi"
•  

if need to rebuild manually pod (module)

• apps → mod-permissions 
• click on module
• find option "config scale/ready scale"
• click on "-" one time / waiting when status "running" will change to "remove"
• click on "+" / wainting when module "running"

5. HOW TO CHECK LOGS OF MODULES TO RANCHER