...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
INTRODUCTION : - LOGGING, PROJECT DESCRIPTION, RUNNING MODULES
CREATE NEW SCRATCH ENV FOR TEAM
- BUILD UI MODULE FROM BRANCH
- BUILD BACKEND MODULE FROM BRANCH
- REGISTERING MODULES IN OKAPI
- CREATE ELASTICSEARCH INDEX SNAPSHOT
HOW TO ADD NEW MODULE FOR RANCHER
HOW CONNECTION TO DATABASE
HOW TO CREATE DUMP DATABASE USING RANCHER ( backUp)
HOW TO CREATE RESTORE DUMP TO NEW ENV
Table of Contents
1.INTRODUCTION
Each development team has access to a “developer scratch environment” to ensure that their changes are ready to be finalised.
...
For general assistance use the Slack channel #scratch-environments and help via your team-specific channel.
The Kitfox DevOps team wiki page has further resources regarding Rancher scratch environments.
...
teamName, Action, TenantName, Repo, Plan, Change, Register, branch, platform_image
Parameter teamName:
Specifies the name of environment and access parameters in Rancher. For most values admin and members of github teamName team have access to Rancher to configure module
...
deployment.
| 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 |
|
| OleksandrDone | ||||||||||||||||||||||||||||||||||||||||||
| 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.
...
- go to rancher → apps → launch
- search needs module
- choose namespase for modules ( by default name of module) , should be choose your team name
- add parameters for using module
- launch
8.HOW CONNECTION TO DATABASE
...
password: (don't forget enter to password ( db_password)) --→ how to find db_password ( resourses → secrets → db_connetcion_modules → 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)
...