Deployment

Cloud Robotics cluster

If you don’t have a Cloud Robotics cluster yet, follow the instructions given here for Kyma and here for Google flavor to set up your Robotics Core instance.

Container registry

You can use the default images for all apps we publish at ghcr.io/sap/ewm-cloud-robotics and skip this step.

• If you have modified the images and would like to use the GCR of your project you can use the predefined skaffold profile to build, test & push all images. The container registry is dynamically generated based upon your gcloud configuration (gcloud config get-value project - configurable via gcloud config set project <GCP_PROJECT>) and host eu.gcr.io. Consequently, images are pushed to eu.gcr.io/<GCP_PROJECT>/<IMAGE_NAME> (1).
• The second options is building images for single cloud robotics applications and push them to an arbitrary container registry defined in the file ~/.config/ewm-cloud-robotics-deployments/<PROJECT>/REGISTRY (2).
• You can also use a specific container registry (3).

It is assumed that access has been established beforehand.

# (1)
skaffold run --profile gcp

# (2a)
./deploy.sh --project=<PROJECT> build ewm-order-manager
# (2b)
export EWM_PROJECT=<PROJECT>
./deploy.sh build ewm-order-manager

# (3)
./deploy.sh --registry=eu.gcr.io/my-gcp-project build ewm-order-manager

Configuration

In order to customize the settings of any Cloud Robotics application, adjust the YAML of the AppRollout. It allows overwriting all variables of the underlying helm chart. By default the deploy.sh script uses the approllout.yaml/app.yaml files at ~/.config/ewm-cloud-robotics-deployments/<PROJECT>/<APP>/, thus one gets the best user experience by doing the following:

export EWM_PROJECT=my-project
# (1) create the dir
mkdir -p ~/.config/ewm-cloud-robotics-deployments/$EWM_PROJECT

# (2) copy the templates to the created dir
cp -R applayer-yaml/ ~/.config/ewm-cloud-robotics-deployments/$EWM_PROJECT

# (3) verify that app folders are in the correct place (expected print: 13 app directories)
ls ~/.config/ewm-cloud-robotics-deployments/$EWM_PROJECT

If you work on multiple projects, switch your EWM_PROJECT environment variable and repeat the steps above. This way you do not interfere with any of your previous configurations. Alternatively copy the AppRollout template files to adjust the values and continue using the copy within the installation process by specifying the path via the corresponding flag (./deploy.sh -f <path> rollout <APP>).

Installation

Installing the apps to your Cloud Robotics cluster is a two-step process (ref. Cloud Robotics Application Management):

1. Make your application available in the Google Cloud Robotics cluster by creating an App that describes which Helm charts should run in the respective cloud/robot targets.
2. Instantiate your application by creating an AppRollout referencing the previously created App. The AppRollout contains your specific configurations for your ewm-cloud-robotics deployment.

If you have complected the configuration steps, you can leverage the deploy.sh script as follows:

export EWM_PROJECT=my-project
# Example: ewm-order-manager

# (1) Register 'dev' version of the ewm-order-manager App
./deploy.sh push ewm-order-manager

# (2) Create a corresponding AppRollout
./deploy.sh rollout ewm-order-manager

Otherwise you need to specify approllout.yaml/app.yaml files for push and rollout. You can get examples and further information about this by running ./deploy.sh help.