Versions Compared

Old Version 1

changes.mady.by.user Michel El Hajj (Unlicensed)

Saved on

compared with

New Version 2

changes.mady.by.user Michel El Hajj (Unlicensed)

Saved on

Key

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

Objective

Become familiar with how the SOAJS Dashboard notifies you about catalog recipe updates for SOAJS services & daemons that are deployed in Dashboard Environment and learn how to pull and apply these updates in the Dashboard Environment.

Steps

  1. Understand what Catalog Recipe Updates mean and Locate the Update Notifications
  2. Apply the Code Update



Step 1

The Dashboard contains a notification system that informs you whenever new catalog recipe updates or upgrades.

Catalog Recipe updates happen after you deploy a service. Upon deploying a SOAJS cloud, the installer creates recipes for Nginx and the SOAJS services that were deployed in the Dashboard Environment.

These recipes can be modified under Develop → Catalog Recipes in the Dashboard. Whenever you change any of the recipes used by the installer to deploy the services in the dashboard environment, the dashboard notifies you so can apply these changes of these services.

These notifications appear Under Deploy pillar → Updates & Upgrades.

In Updates & Upgrades you will see notifications about new catalog recipes and which services were affected.



Step 2

Once a catalog recipe has been updated, you can apply it on the deployed services in the Dashboard environment and the environment you are using as follow:

  1. Go to Deploy pillar → High Availability
  2. Lookup the service you want to update
    1. Open the Service Operations menu
    2. Click Rebuild Service


Rebuild Service

This operation will load the catalog recipe again, if the catalog recipe has changed then the service will be affected then it redeploys the service with the new recipe changes.

The SOAJS deployer inside the SOAJS image will perform a git clone operation that will clone the latest code updates from branch master.

Once the code is pulled, the deployer will run an NPM INSTALL command to install the dependencies needed and will start your service.

While the deployer is running, your old service remains operational until the new service is flagged as running by either Docker Swarm or Kubernetes depending on which of the two drivers you have chosen to deploy your SOAJS cloud with.

When the new service becomes ready, then the old one will be terminated; your SOAJS Service is now updated and is using the catalog recipe.