Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

...

Environment nameStatusRancher permissionsPurpose

Update type (Automated/Manual)

Operational time (h/d)

Platform-core branchEnv. re-creation ticketDevelopment team status (optional)FeedbackLog4j vulnerability fixing
metadata

Status
colourGreen
titleChecked
Available to use.

Spitfire

platform-complete/master

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-31

Status
colourGreen
titleKeep it


Done

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-101

bulk-edit

(old concorde)

Status
colourGreen
titleChecked
Available to use.

Firebird

platform-core/firebird-rancher

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-70

Status
colourGreen
titleKeep it



Done

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-150

core-functional

Status
colourYellow
titleIn review

prokopovych/core-functional

platform-complete/prokopovych-rancher

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-54

Status
colourGreen
titleKeep it

or

Status
colourRed
titleShut down


Done

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-141

volaris

Status
colourGreen
titleChecked
Available to use.

Volaris

platform-core/volaris-rancher

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-75

Status
colourGreen
titleKeep it


Done

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-127

volaris-2nd

Status
colourYellow
titleIn review
Available to use.

Volaris

platform-core/volaris-rancher

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-78

Status
colourGreen
titleKeep it


Done

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-127

core-platform

Status
colourGreen
titleChecked
Available to use.

Core Platform

platform-complete/core-platform-rancher

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-53

Status
colourRed
titleShut down


Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-188

falcon

Status
colourGreen
titleChecked
Available to use.

Falcon

platform-core/falcon-rancher

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-56

Status
colourGreen
titleKeep it


Done

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-120

firebird

Status
colourGreen
titleChecked
Available to use.

Firebird

platform-core/firebird-rancher

Latest release based on snapshot

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-49

Status
colourGreen
titleKeep it



Done

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-122

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-149

folijet

Status
colourGreen
titleChecked
Available to use.

Folijet

platform-core/folijet-rancher

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-47

Status
colourGreen
titleKeep it


Done

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-130

vega

Status
colourGreen
titleChecked
Available to use.

Vega

platform-core/vega-rancher

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-55

Status
colourGreen
titleKeep it


Done

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-157

spanish

Status
colourGreen
titleChecked
Available to use.

Spanish

platform-complete/master

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyFOLIO-3320

Status
colourGreen
titleKeep it

or

Status
colourRed
titleShut down


Done

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-153

spitfire

Status
colourGreen
titleCHECKED
Available to use.

Spitfire

platform-core/spitfire-rancher

platform-core/snapshot-spitfire

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-48

Please refer RANCHER-125 to re-provision env

Status
colourGreen
titleKeep it


Done

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-125

thor

Status
titleInitial






Status
colourYellow
titleUpgrade


Oleksandr
thunderjet

Status
colourGreen
titleCHECKED
Available to use.

thunderjet

platform-core/thunderjet-rancher

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-52

Status
colourGreen
titleKeep it


Done

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-134

unamUsed for testing config.




Status
colourGreen
titleKeep it

or

Status
colourRed
titleShut down



...

  • Registering a particular module (backend or UI module)
    docker run --rm -e TENANT_ID=diku -e OKAPI_URL=https://<project name>-okapi.ci.folio.org -e MODULE_NAME=<module name> docker.dev.folio.org/folio-okapi-registration
    
  • Registering all modules (backend and UI from ‘platform-complete’ list)
    docker run --rm -e TENANT_ID=diku -e OKAPI_URL=https://<project name>-okapi.ci.folio.org -e MODULE_NAME='' docker.dev.folio.org/folio-okapi-registration
    
  • Registering all UI modules only
    docker run --rm -e TENANT_ID=diku -e OKAPI_URL=https://<project name>-okapi.ci.folio.org -e MODULE_NAME='platform-complete' docker.dev.folio.org/folio-okapi-registration

    for example:
    docker run --rm -e TENANT_ID=diku -e OKAPI_URL=https://core-platform-okapi.ci.folio.org -e MODULE_VERSION=24.0.0-SNAPSHOT.999 -e MODULE_NAME=mod-inventory-storage docker.dev.folio.org/folio-okapi-registration

Apply module permissions

The last step after modules registration is to apply permissions for modules to the admin user.

...

if we have env with old database 

1. go to  UI pgadmin4  ( for example folio_modules bd) 

2. should be download file backup  to this pgadmin pod for restore

3. click on create a new database  Image Added   Image Added 



4. next point needs to scale  working modules to state 0 "-", this options help delete parameters old database ( !!!   not scale apps → elasticsearch, kafka, pgadmin4, postgres)



Image AddedImage AddedImage Added



5. after was modules scaled ,  should be go to UI pgadmin4 → choose new database →   using psl command line for sure that all old database will drop correct  



 

Image Added


have to execute 3 command  ( for check that database haven't active datname those database which need drop)  

SELECT * FROM pg_stat_activity WHERE datname = '<database_name>';

SELECT pg_terminate_backend (pid) FROM pg_stat_activity WHERE pg_stat_activity.datname = '<database_name>';        

DROP DATABASE <database_name>;


Image AddedImage AddedImage Added


5. after DROP database , not leaving commandline → execute CREATE DATABASE <name database> 


Image Added


  6. go to pgadmin4 → execute shell → commanline → need to do a restore for database "folio_modules"


/usr/local/pgsql-12/pg_restore --host=pg-folio --port=5432 --username=postgres  --dbname=<< name database>>   --section=pre-data --section=data --section=post-data -s --verbose /var/lib/pgadmin/storage/user_folio.org/<<name file backup>>


7. check how to restore  database


  1.   modules must have owner ( name modules)     

Image Added


8.  after success restore need scale all modules  again  to " + "


Image Added


9.  modules not active now → should be do manipulate for registration modules, check  table " discovery modules", anable modules for okapi