DSO and Cache Configurator Migration Guide
If you used Data Streams Optimizer or Cache Configurator 2021.2 or earlier versions, this guide help you easily migrate to the new 2021.3 version and versions going forward.
This migration is required for existing TCC environment file(s), otherwise Data Streams Optimizer or Cache Configurator will not function.
Changing your environment file is the first step in configuring connections to your systems manually.
- Update your environment file:The default location of your environment files is:${TCC_TOOLS_PATH}/demo/environment
- Remove theconnection_settingsfield:{ "targets": { "target_name_1": { "target_info": "...", "connection_settings": { "hostname": "...", "username": "...", "password": "...", "port": 22, "connection_timeout":5, "reconnection_timeout":10, "reconnection_attempts":10 }, "capsule_settings": { ... }, ... ... ... } } }Your environment file should now look like this:{ "targets": { "target_name_1": { "target_info": "...", "capsule_settings": { ... }, ... ... ... } } }
- Update thecapsule_apply_scriptfield:If you didn’t customize the default field or script, change:"capsule_apply_script": "bash /usr/share/tcc_tools/tools/target_scripts/capsule_apply_uefi.sh",To the new version of the script:"capsule_apply_script": "bash ./host_scripts/capsule_upload_apply_uefi.sh",If you customized the script for your systems, update your script to support the new functionality.To update the script, follow Capsule Upload and Apply Script.
- Updatescriptsfield:If you didn’t customize this default field or script, change the entire field:"scripts": { "register_verification": "python3 /usr/share/tcc_tools/tools/target_scripts/registers_checker.py", "bdf": "python3 /usr/share/tcc_tools/tools/target_scripts/bdf_converter.py", "processor_checker": "python3 /usr/share/tcc_tools/tools/target_scripts/processor_checker.py", "rtct_reader": "python3 /usr/share/tcc_tools/tools/target_scripts/rtct_reader.py", "reboot_command": "reboot" }To the new version of scripts:"scripts": { "register_verification": "bash ./host_scripts/target_runner.sh python3 /usr/share/tcc_tools/tools/target_scripts/registers_checker.py", "bdf": "bash ./host_scripts/target_runner.sh python3 /usr/share/tcc_tools/tools/target_scripts/bdf_converter.py", "processor_checker": "bash ./host_scripts/target_runner.sh python3 /usr/share/tcc_tools/tools/target_scripts/processor_checker.py", "rtct_reader": "bash ./host_scripts/target_runner.sh python3 /usr/share/tcc_tools/tools/target_scripts/rtct_reader.py", "reboot_command": "bash ./host_scripts/target_reboot.sh" }If you customized the script for your systems or use other scripts, addbash ./host_scripts/target_runner.shat the beginning of each script. However, you need to change``reboot_command`` to the new version of the script.
- Update${TCC_TOOLS_PATH}/host_scripts/target_connection_settings.shwith your connection settings:Field NameDescriptionHOSTNAMEReplacehostnamewith the IP address or hostname of the target system.USERReplaceuserwithroot.SSH_EXTRAAdd any additional SSH command line options.This file contains the hostname and username to connect to the target board through SSH.Here’s an example of the target connection settings file:HOSTNAME='hostname' USER='user' SSH_EXTRA=''
- Setup a password-less connection between the host and target machines.
- Generate a key with an empty passphrase:ssh-keygen -t rsa
- Copy the key to the target system:ssh-copy-id <user>@<target>If you do not havessh-copy-idon your host system, use the command:cat .ssh/id_rsa.pub | ssh <user>@<target> 'cat >> .ssh/authorized_keys'
- Verify that a password is no longer required. For example:ssh <user>@<target> ls