Update Veriscope

The upgrade-veriscope.yaml playbook copies the version of the code on the controller machine onto the target Veriscope Server(s). It expects a value for the variable apps_to_update which is a list of veriscope components to update / reinstall, either api and/or dashboard (i.e. the web-application).

ansible-playbook -i infra/configure/inventory/veriscope-nodes.yaml --extra-vars '{"apps_to_update":["veriscope_ta_node", "veriscope_ta_dashboard"]}' infra/configure/playbooks/upgrade-veriscope.yaml

OR

Update a specific "app", e.g. --extra-vars '{"apps_to_update":["veriscope_ta_dashboard"]}'

ansible-playbook -i infra/configure/inventory/veriscope-nodes.yaml --extra-vars '{"apps_to_update":["veriscope_ta_dashboard"]}' infra/configure/playbooks/upgrade-veriscope.yaml

OR

Update a specific Veriscope Server, use the --limit flag as below. E.g. --limit "update-this-server.veriscope.org".

ansible-playbook -i infra/configure/inventory/veriscope-nodes.yaml infra/configure/playbooks/upgrade-veriscope.yaml --limit "<the-node-you-want-to-update>,localhost"

Run a specific Ansible playbook

Let’s say you want to create a new Admin User for your Veriscope dashboard. To do this, you can run the create-admin-user.yaml playbook as follows (the --limit flag is optional):

ansible-playbook -i infra/configure/inventory/veriscope-nodes.yaml infra/configure/playbooks/create-admin-user.yaml --limit "<the-node-you-want-to-update>"
A full list playbooks can be found /infra/configure/playbooks, from the root of the repository.

Update TA Account

Edit the veriscope-nodes.yaml file, and then use the ansible command to update or add more TA accounts in your veriscope_ta_node/.env:

ansible-playbook -i infra/configure/inventory/veriscope-nodes.yaml infra/configure/playbooks/update-ta-accounts.yaml -l "<Your Web Node>"
In the veriscope-node.yaml file, your address needs to be enclosed in single quotes and without any spaces.
Example 1. Single Ta Account
trust_anchors:
    - private_key: 672ce0b5212111e3508534449327440bdc98916be865706ab9ddc99e7f830f85
        address: '0xe33bC570102454BBA56B67A212172I2D64e8233d'
        preferred_name: TrustAnchorName
Example 2. Multiple Ta Accounts
trust_anchors:
    - private_key: 672ce0b5212111e3508534449327440bdc98916be865706ab9ddc99e7f830f85
        address: '0xe33bC570102454BBA56B67A212172I2D64e8233d'
        preferred_name: Trust_Anchor_1
    - private_key: 672ce0b5212111e35085d8e49327440bdc98916be865706ab9ddc99e7f830f85
        address: '0xe33bC570174354BBA56B67A212172I2D64e8233d'
        preferred_name: Trust_Anchor_2