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.

...

HOW TO CREATE DUMP DATABASE USING RANCHERRANCHER  ( backup)

  1. need connection to database "pg-folio"
  2. apps → pgadmin4 

...

3. using shell , pg_dump command


/usr/local/pgsql-12/pg_dump --file "/var/lib/pgadmin/storage/user_folio.org/<<name file backup>>" --host "pg-folio" --port "5432" --username "postgres"  --verbose --format=c --blobs --section=pre-data --section=data --section=post-data "folio_modules"

password:         (don't forget enter to password ( db_password))


Image Added


4. after dump was created, should be create a copy to your local machine  ( usecase:  copy to  env which to use for restore dump) 

how to cp from pgadmin backup postgres into local mashine:

from

rancher kubectl -n thor cp pgadmin4-<<number pod with backup>>:/var/lib/pgadmin/storage/user_folio.org/<< name file backup>>   /<< your home directory/file backup>>

 to 

rancher kubectl -n unam cp /<< your home directory/file backup>>   pgadmin4-<<number pod where need restore>>:/var/lib/pgadmin/storage/user_folio.org/<<name file backup>>


how to using rancher CLI to local machine 

1. install tar.gz rancher cli https://github.com/rancher/cli/releases
2. tar -xvf tar 
3. needs add racnher execute file in /bin/
4. rancher login https://rancher.dev.folio.org --token (how create token)  
    - go to rancher (under account foto click on api key ) 
    - create api key your temporapy token
for example : rancher login https://rancher.dev.folio.org --token token-tlrgx:w4xt8q496pjlqfdtsd8hwdkkv7j8c97tp8tzj7ll8fwzx86bwdqm6n

Image AddedImage AddedImage Added


5. rancher cluster
6. rancher cluster kubeconfig  c-479xv  (your using cluster id)
7. rancher cluster kubeconfig  c-479xv > /home/.kube/config  (add your path to .kube if you need use kubectl)



HOW TO CREATE RESTORE DUMP TO NEW ENV 

if we have new env & empty database  

  1.  go to rancher → apps → pgadmin4 → shell
  2. execute next command to restore dump

/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>> 

password:

3. go to ui pgadmin4 →check restore

---------------------------------------------------------------------------------------------------

if we have env with old database 

1. go to