Chapter 8. Generating platform assets for application deployment

Procedure

1. Open the terminal application and navigate to the <MTA_HOME>/ directory.

2. List the supported platforms for the discovery process:

   $ mta-cli discover --list-platforms

   Copy to Clipboard Toggle word wrap

3. Generate the discovery manifest for a CF application as an output file:

   $ mta-cli discover cloud-foundry \ --input <path_to_application-manifest> \ --output <path_to_discovery-manifest>\

   Copy to Clipboard Toggle word wrap

Procedure

1. Open the terminal application and navigate to the <MTA_HOME>/ directory.

2. Generate the deployment manifest as an output file:

   $ mta-cli generate helm --chart-dir helm_sample \ --input <path_to_discovery-manifest> \ --output-dir <location_of_deployment_manifest> \

   Copy to Clipboard Toggle word wrap

3. Verify the ConfigMap:

   $ mta-cli cd <location_of_deployment_manifest> \
   $ cat configmap.yaml
   $ cat Dockerfile

   Copy to Clipboard Toggle word wrap

4. Verify the Dockerfile:

   $ mta-cli cd <location_of_deployment_manifest> \
   $ cat Dockerfile

   Copy to Clipboard Toggle word wrap

Procedure

1. Open the terminal application and navigate to the <MTA_HOME>/ directory.

2. Verify the content of the CF Node.js application manifest:

   $ cat cf-nodejs-app.yaml
   name: cf-nodejs
   lifecycle: cnb
   buildpacks:
     - docker://my-registry-a.corp/nodejs
     - docker://my-registry-b.corp/dynatrace
   memory: 512M
   instances: 1
   random-route: true

   Copy to Clipboard Toggle word wrap

3. Generate the discovery manifest:

   $ mta-cli discover cloud-foundry \ --input cf-nodejs-app.yaml \ --output discover.yaml \

   Copy to Clipboard Toggle word wrap

4. Verify the content of the discover manifest:

   $ cat discover.yaml
   name: cf-nodejs
   randomRoute: true
   timeout: 60
   buildPacks:
   - docker://my-registry-a.corp/nodejs
   - docker://my-registry-b.corp/dynatrace
   instances: 1

   Copy to Clipboard Toggle word wrap

5. Generate the deployment manifest in the newDir directory by using the discover.yaml file:

   $ mta-cli generate helm \ --chart-dir helm_sample \ --input discover.yaml --output-dir newDir

   Copy to Clipboard Toggle word wrap

6. Check the contents of the Dockerfile in the newDir directory:

   $ cat ./newDir/Dockerfile
   FROM busybox:latest
   
   RUN echo "Hello cf-nodejs!"

   Copy to Clipboard Toggle word wrap

7. Check the contents of the ConfigMap in the newDir directory:

   $ cat ./newDir/configmap.yaml
   apiVersion: v1
   kind: ConfigMap
   metadata:
     name: cf-nodejs-config
   data:
     RANDOM_ROUTE: true
     TIMEOUT: "60"
     BUILD_PACKS: |
       - docker://my-registry-a.corp/nodejs
       - docker://my-registry-b.corp/dynatrace
     INSTANCES: "1"

   Copy to Clipboard Toggle word wrap

8. In the ConfigMap, override the name to nodejs-app and INSTANCES to 2 :

   $ mta-cli generate helm \ --chart-dir helm_sample \ --input discover.yaml --set name="nodejs-app" \ --set instances=2 \ --output-dir newDir \

   Copy to Clipboard Toggle word wrap

9. Check the contents of the ConfigMap again:

   $ cat ./newDir/configmap.yaml
   apiVersion: v1
   kind: ConfigMap
   metadata:
     name: nodejs-app
   data:
     RANDOM_ROUTE: true
     TIMEOUT: "60"
     BUILD_PACKS: |
       - docker://my-registry-a.corp/nodejs
       - docker://my-registry-b.corp/dynatrace
     INSTANCES: "2"

   Copy to Clipboard Toggle word wrap