QA01 & Local - Documentation

This Document includes all info we shared on issues, solutions and more and will be updated anytime we have major issue or workflow updates.

BOOST-BB-CI: Latest workflow:

This workflow was suggested in order to avoid conflicts when uploading code to dev/master:

Pull from master
Create new branch "fix-ro-feature_CV-XXXX_short-description"
Do task
Checkout branch from local branch (fix-or-feature_CV-XXXX_short-description...) to CV-XXX-dev
Commit and push from CV-XXX-dev
CR to dev branch and merge (resolved conflicts if exists)
QA check in qa01 environment and approved. (If QA pushback the task and some code changes needed, we delete

CV-XXX-dev branch and checking out back to "fix-or-feature_CV-XXXX_short-description" keep working and making the changes there and then doing gain step 4.

Go to local branch fix-or-feature_CV-XXXX_short-description and pull from master again
CR to master branch and merge to master.

Updating local env after deployment - including dump:

1. rm -rf docker-data/dump/* - deleting all files from dump folder

2. rm -rf docker-data/mongo/* - deleting all files from mongo folder

yarn update-db
yarn setup
yarn down
yarn docker

Create new template:

yarn create-group
Copy all the relevant files to your new template

Check services versions:

You can compare your local versions to versions in qa01/production in case something doesn't work for you after deployment or in order to see/use new abilities that were developed by BST team.

Boost Service:

Prod http://boost.naturalint.com/version

QA01 http://boost.qa01.corp.naturalint.com/version

CMS Service:

Prod http://cms-service.naturalint.com/version

QA01 http://cms-service.qa01.naturalint.com/version

Renderer:

Prod http://renderer.naturalint.com/deploy/version

QA01 http://renderer.qa01.corp.naturalint.com/deploy/version

Cirrus:

http://cirrus-bos.naturalint.com/healthcheck

Permission Service:

Prod http://permission-service.naturalint.com/version

QA01 http://permission-service.qa01.corp.naturalint.com/version

Product List Service:

Prod: http://product-list-service.naturalint.com/version

QA01: http://product-list-service.qa01.corp.naturalint.com/version

Check logs of Docker containers:

ssh docker-app01.qa01.corp.naturalint.com

sudo su

docker ps

docker logs -f {container id} (change the id number to the id of the relevant service)

in case you want to restart all containers: docker restart $(docker ps -a -q)
Get your public key (in case of permissions issue): ~/.ssh/id_rsa.pub | pbcopy

Working From Local straight to QA01

Now you can do you changes in Boost straight to QA01 from Local.

It means that during working on local all you changes will move to QA01.

Only in case we create new BB element (template) you will able see you changes in QA01 only after pushing them to QA01

(dev). But all you changes will be ready.

So for this you need update you docker-compose.yml file with new change in 3 places:

1) Change parameter (line ~ 67) CMS_SERVICE_URL:

# for local
#- CMS_SERVICE_URL=cms

# for qa01
- CMS_SERVICE_URL=cms-service.qa01.corp.naturalint.com

2) Change parameters settings (line ~ 83) CMS_SERVICE_MONGODB_HOST and CMS_SERVICE_MONGODB_DBNAME:

#local
#- CMS_SERVICE_MONGODB_HOST_01=mongo:27017
#- CMS_SERVICE_MONGODB_DBNAME=cms_service_development

#qa01
- CMS_SERVICE_MONGODB_HOST_01=mongo01.qa01.corp.naturalint.com:27017
- CMS_SERVICE_MONGODB_HOST_02=mongo02.qa01.corp.naturalint.com:27017
- CMS_SERVICE_MONGODB_HOST_03=mongo03.qa01.corp.naturalint.com:27017
- CMS_SERVICE_MONGODB_DBNAME=cms_service_qa

3) And (line ~ 147) CMS_SERVICE_URL here:

# for qa01
- CMS_SERVICE_URL=http://cms-service.qa01.corp.naturalint.com

# for local
#- CMS_SERVICE_URL=http://cms

Environments