Introduction
...
Environment name | Status | Rancher permissions | Purpose | Update type (Automated/Manual) Operational time (h/d) | Platform-core branch | Env. re-creation ticket | Development team status (optional) | Feedback | Log4j vulnerability fixing | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
metadata |
| Spitfire | platform-complete/master |
|
| Done
| |||||||||||||||||||||||||||||||||||||||
bulk-edit (old concorde) |
| Firebird |
|
| Done
| ||||||||||||||||||||||||||||||||||||||||
core-functional |
| prokopovych/core-functional | platform-complete/prokopovych-rancher |
|
or
| Done
| |||||||||||||||||||||||||||||||||||||||
volaris |
| Volaris |
|
| Done
| ||||||||||||||||||||||||||||||||||||||||
volaris-2nd |
| Volaris | platform-core/volaris-rancher |
|
| Done
| |||||||||||||||||||||||||||||||||||||||
core-platform |
| Core Platform | platform-complete/core-platform-rancher |
|
|
| |||||||||||||||||||||||||||||||||||||||
falcon |
| Falcon | platform-core/falcon-rancher |
|
| Done
| |||||||||||||||||||||||||||||||||||||||
firebird |
| Firebird | platform-core/firebird-rancher Latest release based on snapshot |
|
| Done
| |||||||||||||||||||||||||||||||||||||||
folijet |
| Folijet |
|
| Done
| ||||||||||||||||||||||||||||||||||||||||
vega |
| Vega |
|
| Done
| ||||||||||||||||||||||||||||||||||||||||
spanish |
| Spanish | platform-complete/master |
|
or
| Done
| |||||||||||||||||||||||||||||||||||||||
spitfire |
| Spitfire | platform-core/spitfire-rancher platform-core/snapshot-spitfire |
Please refer RANCHER-125 to re-provision env |
| Done
| |||||||||||||||||||||||||||||||||||||||
thor |
|
| Oleksandr | ||||||||||||||||||||||||||||||||||||||||||
thunderjet |
| thunderjet | platform-core/thunderjet-rancher |
|
| Done
| |||||||||||||||||||||||||||||||||||||||
unam | Used for testing config. |
or
|
...
- 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)
- need connection to database "pg-folio"
- 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))
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
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
- go to rancher → apps → pgadmin4 → shell
- 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