🎯 Goal: having the automation create and start the zdm-ansible-container, in which you will then launch the Ansible playbook that provisions and starts the ZDM Proxy.
It's time to download and run zdm-util, which creates
the Ansible container that, in turn, will deploy the ZDM proxies.
Download and extract the utility:
### {"terminalId": "host", "backgroundColor": "#C5DDD2"}
cd /workspace/zdm-scenario-katapod/running_zdm_util
wget https://github.com/datastax/zdm-proxy-automation/releases/download/v2.2.0/zdm-util-linux-amd64-v2.2.0.tgz
tar -xvf zdm-util-linux-amd64-v2.2.0.tgz
rm zdm-util-linux-amd64-v2.2.0.tgzNote: commands on a background of a colour like the one above are part of the "core" migration process, as opposed to the setup/context commands you encountered so far.
Before going through the configuration utility, you may find it useful to check the IP addresses you will momentarily need. For your convenience, this interactive lab provides a handy script that retrieves and prints exactly that information: execute it (on the still-unused "zdm-proxy-logs" console) with
### logs
. /workspace/zdm-scenario-katapod/scenario_scripts/find_addresses.shNote: in this learning environment we are using a single host for all containers (including Origin!). In a production setup, you would most likely have the proxy containers run each on a separate host machine.
The configuration utility that you are about to launch will ask you a few questions along the way. Please supply the answers as summarized in this table (see also the Documentation page):
| Request | Answer |
|---|---|
| Private key location | ../zdm_host_private_key/zdm_deploy_key |
| Network prefix for ZDM host | If, for example, your ZDM host is 172.17.0.1, you can provide 172.17.0.* here |
| Do you have an inventory file? | No, not yet |
| Is this for testing? | Yes (so as to allow for a single ZDM host instead of the required three) |
| Address for the ZDM hosts | the IP for the ZDM host, that is, ZDM_HOST_IP in the output of find_addresses.sh. There is just one and you have to input a blank line afterwards to signal you're done |
| Address for the monitoring instance | the same IP as above for the monitoring instance (in this setup, it will be the same machine) |
What does the utility do? (click to expand)
The zdm-util interactively collects a few configuration values from the user,
then uses these to create a ready-to-use Ansible Control Host container
tailored to the settings for this specific migration.
The container thus created features Ansible playbooks that you can launch with simple one-line commands to provision the ZDM Proxies themselves, the associated monitoring stack, and perform other maintenance operations (such as restarts or upgrades).
Start the config utility with:
### {"terminalId": "host", "backgroundColor": "#C5DDD2"}
cd /workspace/zdm-scenario-katapod/running_zdm_util
./zdm-util-v2.2.0Once you are done, answer "Yes" when asked "Do you wish to proceed?": a zdm-ansible-container is created and started
on the host machine's Docker (this will take ten seconds or so).
Once you get the prompt back, check with
### {"terminalId": "host", "backgroundColor": "#C5DDD2"}
docker ps