Snapshotting Configuration in Docker

If you deploy a Docker container with the ZEUS_BASE_CONFIG environment variable set, the Traffic Manager creates a configuration snapshot after the base configuration has been applied. Any additional configuration imported from the directory specified in the ZEUS_WATCHED_CONFIG environment variable is layered on top of this base configuration.

In practice, this is relevant only if the base configuration and watched configuration directories are different, such that the watched configuration is applied on top of the base configuration. For example:.

/base/config/system-settings.yaml
`version: 6.1` `global_settings:` `properties:` `session:` `ip_cache_size: 65535` `web_cache:` `size: 2GB` `max_file_size: 50MB`

/watched/config/my-service.yaml
`version: 6.1` `virtual_servers:` `- name: example-service` `properties:` `basic:` `enabled: true` `port: 80` `protocol: http` `pool: discard` `request_rules: [ basic-response ]` `rules:` `- name: basic-response` `content: \|` `http.sendResponse("200 OK", "text/plain", "Hello World\n", "X-Served-By: Ivanti vTM");`

/watched/config/my-service.yaml

version: 6.1

virtual_servers:

- name: example-service

  properties:

    basic:

      enabled: true

      port: 80

      protocol: http

      pool: discard

      request_rules: [ basic-response ]

rules:

- name: basic-response

  content: |

    http.sendResponse("200 OK", "text/plain", "Hello World\n", "X-Served-By: Ivanti vTM");

Deploying a container in Docker using these configuration documents results in the base configuration in "system-settings.yaml" being applied to the Traffic Manager initially, the base configuration snapshot being updated, and then the configuration in "my-service.yaml" being applied on top of that base configuration. Any changes to configuration in the "watched" directory are applied on top of the base configuration. However, changes to configuration in the "base" directory after the container is launched have no effect as that directory is not being watched for changes.

To deploy the container, use the following command

Deploy container with base and watched configuration
`# Assumes the sample configuration documents shown above are saved as ./base/config/system-settings.yaml and ./watched/config/my-service.yaml` `docker run --name=vtm-config-example \` -v `pwd`/base:/base \ -v `pwd`/watched:/watched \ `-p 8080:80 \` `-p 9090:9090 \` `-e ZEUS_BASE_CONFIG=/base \` `-e ZEUS_WATCHED_CONFIG=/watched \` `-e ZEUS_EULA=accept \` `-e ZEUS_PASS=admin \` `--privileged \` `--init \` `-t \` `-d \` `pulsesecure/vtm:<version>`

Deploy container with base and watched configuration

# Assumes the sample configuration documents shown above are saved as ./base/config/system-settings.yaml and ./watched/config/my-service.yaml

docker run --name=vtm-config-example \

            -v `pwd`/base:/base \

            -v `pwd`/watched:/watched \

            -p 8080:80 \

            -p 9090:9090 \

            -e ZEUS_BASE_CONFIG=/base \

            -e ZEUS_WATCHED_CONFIG=/watched \

            -e ZEUS_EULA=accept \

            -e ZEUS_PASS=admin \

            --privileged \

            --init \

            -t \

            -d \

            pulsesecure/vtm:<version>

Snapshotting Configuration in Other Deployments

For other deployment types, take a snapshot after the Traffic Manager has been deployed to create a new base configuration snapshot.

To snapshot the current Traffic Manager configuration, run the following command:

$ZEUSHOME/zxtm/bin/config-snapshot