Add instructions to run Ansible playbooks on remote machines (#5)

Part of [Automate testnet nitro deployments using Ansible](https://www.notion.so/Automate-testnet-nitro-deployments-using-Ansible-0d15579430204b8daba9a8aa31e07568)

Co-authored-by: Adw8 <adwaitgharpure@gmail.com>
Reviewed-on: cerc-io/testnet-ops#5
Co-authored-by: Prathamesh Musale <prathamesh@noreply.git.vdb.to>
Co-committed-by: Prathamesh Musale <prathamesh@noreply.git.vdb.to>
This commit is contained in:
Prathamesh Musale 2024-09-09 13:37:41 +00:00 committed by nabarun
parent 88e0b48540
commit 23f3a4c8ed
23 changed files with 336 additions and 82 deletions

8
.gitignore vendored
View File

@ -1,7 +1 @@
l2-setup/out hosts.ini
nitro-bridge-setup/out
nitro-bridge-setup/bridge-vars.yml
nitro-nodes-setup/nitro-vars.yml
nitro-nodes-setup/out
nitro-contracts-setup/out
nitro-contracts-setup/contract-vars.yml

View File

@ -8,7 +8,7 @@
- Set Locale Encoding to `UTF-8` - Set Locale Encoding to `UTF-8`
Ansible requires the locale encoding to be `UTF-8`. You can either use the `LANG` prefix when running Ansible commands or set the system-wide locale. Ansible requires the locale encoding to be `UTF-8`. You can either use the `LANG` prefix when running Ansible commands or set the system-wide locale
- Option 1: Use `LANG` Prefix in Commands - Option 1: Use `LANG` Prefix in Commands
@ -32,7 +32,7 @@
LANG="en_US.UTF-8" LANG="en_US.UTF-8"
``` ```
- Reboot your system or log out and log back in to apply the changes. - Reboot your system or log out and log back in to apply the changes
- Reference: <https://udhayakumarc.medium.com/error-ansible-requires-the-locale-encoding-to-be-utf-8-detected-iso8859-1-6da808387f7d> - Reference: <https://udhayakumarc.medium.com/error-ansible-requires-the-locale-encoding-to-be-utf-8-detected-iso8859-1-6da808387f7d>
@ -41,3 +41,4 @@
- [l2-setup](./l2-setup/README.md) - [l2-setup](./l2-setup/README.md)
- [nitro-node-setup](./nitro-nodes-setup/README.md) - [nitro-node-setup](./nitro-nodes-setup/README.md)
- [nitro-bridge-setup](./nitro-bridge-setup/README.md) - [nitro-bridge-setup](./nitro-bridge-setup/README.md)
- [nitro-contracts-setup](./nitro-contracts-setup/README.md)

2
hosts.example.ini Normal file
View File

@ -0,0 +1,2 @@
[deployment_host]
<host_name> ansible_host=<target_ip> ansible_user=<ssh_user> ansible_ssh_common_args='-o ForwardAgent=yes'

3
l2-setup/.gitignore vendored Normal file
View File

@ -0,0 +1,3 @@
out
l2-vars.yml
hosts.ini

View File

@ -4,13 +4,19 @@
To get started, follow the [installation](../README.md#installation) guide to setup ansible on your machine To get started, follow the [installation](../README.md#installation) guide to setup ansible on your machine
## Setup and Run Optimism ## Setup
The following commands have to be executed in [`l2-setup`](./) directory The following commands have to be executed in the [`l2-setup`](./) directory:
- Edit [`l2-vars.yml`](./l2-vars.yml) with the required values - Copy the `l2-vars.example.yml` vars file:
```bash ```bash
cp l2-vars.example.yml l2-vars.yml
```
- Edit [`l2-vars.yml`](./l2-vars.yml) with the required values:
```yaml
# L1 chain ID # L1 chain ID
l1_chain_id: "" l1_chain_id: ""
@ -34,44 +40,108 @@ The following commands have to be executed in [`l2-setup`](./) directory
l1_priv_key: "" l1_priv_key: ""
``` ```
- To setup and run L2, execute the `run-optimism.yml` Ansible playbook by running the following command. ## Run L2
NOTE: By default, deployments are created in the `l2-setup/out` directory. To change this location, update the `l2_directory` variable in the [setup-vars.yml](./setup-vars.yml) file. ### On Local Host
- To setup and run L2 locally, execute the `run-optimism.yml` Ansible playbook:
```bash ```bash
LANG=en_US.utf8 ansible-playbook -i localhost, --connection=local run-optimism.yml --extra-vars='{ "target_host": "localhost"}' -kK --user $USER LANG=en_US.utf8 ansible-playbook run-optimism.yml --extra-vars='{ "target_host": "localhost"}' --user $USER -kK
``` ```
- For skipping container build, set `"skip_container_build" : true` in the `--extra-vars` parameter: NOTE: By default, deployments are created in an `out` directory. To change this location, update the `l2_directory` variable in the [setup-vars.yml](./setup-vars.yml) file
```bash - For skipping container build, set `"skip_container_build" : true` in the `--extra-vars` parameter:
LANG=en_US.utf8 ansible-playbook -i localhost, --connection=local run-optimism.yml --extra-vars='{"target_host" : "localhost", "skip_container_build": true}' -kK --user $USER
```
- To run using existing contracts deployment ```bash
LANG=en_US.utf8 ansible-playbook run-optimism.yml --extra-vars='{"target_host" : "localhost", "skip_container_build": true}' --user $USER -kK
```
- To run using existing contracts deployment:
- Update `artifact_path` in [`setup-vars.yml`](./setup-vars.yml) file with path to data directory of the existing deployment - Update `artifact_path` in [`setup-vars.yml`](./setup-vars.yml) file with path to data directory of the existing deployment
- Run the ansible playbook with `"existing_contracts_deployment": true` in the `--extra-vars` parameter: - Run the ansible playbook with `"existing_contracts_deployment": true` in the `--extra-vars` parameter:
```bash ```bash
LANG=en_US.utf8 ansible-playbook -i localhost, --connection=local run-optimism.yml --extra-vars='{"target_host" : "localhost", "existing_contracts_deployment": true}' -kK --user $USER LANG=en_US.utf8 ansible-playbook run-optimism.yml --extra-vars='{"target_host" : "localhost", "existing_contracts_deployment": true}' --user $USER -kK
```
### On Remote Host
To run the playbook on a remote host:
- Create a new `hosts.ini` file:
```bash
cp ../hosts.example.ini hosts.ini
```
- Edit the [`hosts.ini`](./hosts.ini) file to run the playbook on a remote machine:
```ini
[<deployment_host>]
<host_name> ansible_host=<target_ip> ansible_user=<ssh_user> ansible_ssh_common_args='-o ForwardAgent=yes'
```
- Replace `<deployment_host>` with `l2_host`
- Replace `<host_name>` with the alias of your choice
- Replace `<target_ip>` with the IP address or hostname of the target machine
- Replace `<ssh_user>` with the SSH username (e.g., dev, ubuntu)
- Verify that you are able to connect to the host using the following command
```bash
ansible all -m ping -i hosts.ini -k
# Expected output:
# <host_name> | SUCCESS => {
# "ansible_facts": {
# "discovered_interpreter_python": "/usr/bin/python3.10"
# },
# "changed": false,
# "ping": "pong"
# }
```
- Execute the `run-optimism.yml` Ansible playbook for remote deployment:
```bash
LANG=en_US.utf8 ansible-playbook -i hosts.ini run-optimism.yml --extra-vars='{ "target_host": "l2_host"}' --user $USER -kK
```
- For skipping container build, set `"skip_container_build" : true` in the `--extra-vars` parameter:
```bash
LANG=en_US.utf8 ansible-playbook -i hosts.ini run-optimism.yml --extra-vars='{"target_host" : "l2_host", "skip_container_build": true}' --user $USER -kK
```
- To run using existing contracts deployment:
- Update `artifact_path` in [`setup-vars.yml`](./setup-vars.yml) file with path to data directory of the existing deployment
- Run the ansible playbook with `"existing_contracts_deployment": true` in the `--extra-vars` parameter:
```bash
LANG=en_US.utf8 ansible-playbook -i hosts.ini run-optimism.yml --extra-vars='{"target_host" : "l2_host", "existing_contracts_deployment": true}' --user $USER -kK
``` ```
## Check Deployment Status ## Check Deployment Status
- Run the following command in the directory where the optimism-deployment is created Run the following commands in the directory where the optimism-deployment is created:
- Follow optimism contracts deployment logs: - Follow optimism contracts deployment logs:
```bash ```bash
laconic-so deployment --dir optimism-deployment logs -f fixturenet-optimism-contracts laconic-so deployment --dir optimism-deployment logs -f fixturenet-optimism-contracts
``` ```
- Check L2 logs: - Check L2 logs:
```bash ```bash
laconic-so deployment --dir optimism-deployment logs -f op-geth laconic-so deployment --dir optimism-deployment logs -f op-geth
# Ensure new blocks are getting created # Ensure new blocks are getting created
``` ```

View File

@ -1,4 +1,4 @@
skip_container_build: false skip_container_build: false
l2_directory: "./out" l2_directory: "out"
existing_contracts_deployment: false existing_contracts_deployment: false
artifact_path: "" artifact_path: ""

3
nitro-bridge-setup/.gitignore vendored Normal file
View File

@ -0,0 +1,3 @@
out
bridge-vars.yml
hosts.ini

View File

@ -4,17 +4,19 @@
To get started, follow the [installation](../README.md#installation) guide to setup ansible on your machine To get started, follow the [installation](../README.md#installation) guide to setup ansible on your machine
## Run Nitro Bridge ## Setup
- Copy the `bridge-vars-example.yml` vars file The following commands have to be executed in the [`nitro-bridge-setup`](./) directory:
- Copy the `bridge-vars.example.yml` vars file:
```bash ```bash
cp bridge-vars-example.yml bridge-vars.yml cp bridge-vars.example.yml bridge-vars.yml
``` ```
- Edit [`bridge-vars.yml`](./bridge-vars.yml) and fill in the following values - Edit [`bridge-vars.yml`](./bridge-vars.yml) with the required values:
```bash ```yaml
# L1 WS endpoint # L1 WS endpoint
nitro_l1_chain_url: "" nitro_l1_chain_url: ""
@ -38,7 +40,7 @@ To get started, follow the [installation](../README.md#installation) guide to se
# Custom L2 token to be deployed # Custom L2 token to be deployed
token_name: "LaconicNetworkToken" token_name: "LaconicNetworkToken"
token_symbol: "LNT" token_symbol: "LNT"
intial_token_supply: "129600" initial_token_supply: "129600"
# Addresses of the deployed nitro contracts # Addresses of the deployed nitro contracts
na_address: "" na_address: ""
@ -49,19 +51,73 @@ To get started, follow the [installation](../README.md#installation) guide to se
l1_asset_address: "" l1_asset_address: ""
``` ```
- To run the nitro bridge, execute the `run-nitro-bridge.yml` Ansible playbook by running the following command: ## Run Nitro Bridge
NOTE: By default, deployments are created in the `nitro-nodes-setup/out` directory. To change this location, update the `nitro_directory` variable in the [setup-vars.yml](./setup-vars.yml) file. ### On Local Host
- To setup and run nitro bridge locally, execute the `run-nitro-bridge.yml` Ansible playbook:
```bash ```bash
LANG=en_US.utf8 ansible-playbook -i localhost, --connection=local run-nitro-bridge.yml --extra-vars='{ "target_host": "localhost"}' --user $USER -kK LANG=en_US.utf8 ansible-playbook run-nitro-bridge.yml --extra-vars='{ "target_host": "localhost"}' --user $USER -kK
``` ```
- For skipping container build, run with `"skip_container_build" : true` in the `--extra-vars` parameter: NOTE: By default, deployments are created in an `out` directory. To change this location, update the `nitro_directory` variable in the [setup-vars.yml](./setup-vars.yml) file
```bash - For skipping container build, set `"skip_container_build" : true` in the `--extra-vars` parameter:
LANG=en_US.utf8 ansible-playbook -i localhost, --connection=local run-nitro-bridge.yml --extra-vars='{ "target_host": "localhost", "skip_container_build": true }' --user $USER -kK
``` ```bash
LANG=en_US.utf8 ansible-playbook run-nitro-bridge.yml --extra-vars='{"target_host" : "localhost", "skip_container_build": true}' --user $USER -kK
```
### On Remote Host
To run the playbook on a remote host:
- Create a new `hosts.ini` file:
```bash
cp ../hosts.example.ini hosts.ini
```
- Edit the [`hosts.ini`](./hosts.ini) file to run the playbook on a remote machine:
```ini
[<deployment_host>]
<host_name> ansible_host=<target_ip> ansible_user=<ssh_user> ansible_ssh_common_args='-o ForwardAgent=yes'
```
- Replace `<deployment_host>` with `nitro_host`
- Replace `<host_name>` with the alias of your choice
- Replace `<target_ip>` with the IP address or hostname of the target machine
- Replace `<ssh_user>` with the SSH username (e.g., dev, ubuntu)
- Verify that you are able to connect to the host using the following command
```bash
ansible all -m ping -i hosts.ini -k
# Expected output:
# <host_name> | SUCCESS => {
# "ansible_facts": {
# "discovered_interpreter_python": "/usr/bin/python3.10"
# },
# "changed": false,
# "ping": "pong"
# }
```
- Execute the `run-nitro-bridge.yml` Ansible playbook for remote deployment:
```bash
LANG=en_US.utf8 ansible-playbook -i hosts.ini run-nitro-bridge.yml --extra-vars='{ "target_host": "nitro_host"}' --user $USER -kK
```
- For skipping container build, run with `"skip_container_build" : true` in the `--extra-vars` parameter:
```bash
LANG=en_US.utf8 ansible-playbook -i hosts.ini run-nitro-bridge.yml --extra-vars='{ "target_host": "nitro_host", "skip_container_build": true }' --user $USER -kK
```
## Check Deployment Status ## Check Deployment Status

View File

@ -7,7 +7,7 @@ optimism_url: ""
optimism_deployer_pk: "" optimism_deployer_pk: ""
token_name: "LaconicNetworkToken" token_name: "LaconicNetworkToken"
token_symbol: "LNT" token_symbol: "LNT"
intial_token_supply: "129600" initial_token_supply: "129600"
na_address: "" na_address: ""
vpa_address: "" vpa_address: ""
ca_address: "" ca_address: ""

View File

@ -1,3 +1,3 @@
target_host: "localhost" target_host: "localhost"
nitro_directory: ./out nitro_directory: out
skip_container_build: false skip_container_build: false

View File

@ -10,11 +10,11 @@ config:
OPTIMISM_DEPLOYER_PK: {{ optimism_deployer_pk }} OPTIMISM_DEPLOYER_PK: {{ optimism_deployer_pk }}
TOKEN_NAME: {{ token_name }} TOKEN_NAME: {{ token_name }}
TOKEN_SYMBOL: {{ token_symbol }} TOKEN_SYMBOL: {{ token_symbol }}
INITIAL_TOKEN_SUPPLY: {{ token_symbol }} INITIAL_TOKEN_SUPPLY: {{ initial_token_supply }}
NA_ADDRESS: {{ na_address }} NA_ADDRESS: "{{ na_address }}"
VPA_ADDRESS: {{ vpa_address }} VPA_ADDRESS: "{{ vpa_address }}"
CA_ADDRESS: {{ ca_address }} CA_ADDRESS: "{{ ca_address }}"
L1_ASSET_ADDRESS: {{ l1_asset_address }} L1_ASSET_ADDRESS: "{{ l1_asset_address }}"
network: network:
ports: ports:
nitro-bridge: nitro-bridge:

3
nitro-contracts-setup/.gitignore vendored Normal file
View File

@ -0,0 +1,3 @@
out
contract-vars.yml
hosts.ini

View File

@ -4,9 +4,9 @@
To get started, follow the [installation](../README.md#installation) guide to setup ansible on your machine To get started, follow the [installation](../README.md#installation) guide to setup ansible on your machine
## Deploy Nitro Contracts ## Setup
The following commands have to be executed in [`nitro-contracts-setup`](./) directory The following commands have to be executed in the [`nitro-contracts-setup`](./) directory:
- Copy the `contract-vars-example.yml` vars file - Copy the `contract-vars-example.yml` vars file
@ -29,22 +29,76 @@ The following commands have to be executed in [`nitro-contracts-setup`](./) dire
# Custom L1 token to be deployed # Custom L1 token to be deployed
token_name: "LaconicNetworkToken" token_name: "LaconicNetworkToken"
token_symbol: "LNT" token_symbol: "LNT"
intial_token_supply: "129600" initial_token_supply: "129600"
``` ```
- To deploy the L1 nitro contracts, execute the `deploy-contracts.yml` Ansible playbook by running the following command: ## Deploy Contracts
NOTE: By default, deployments are created in the `nitro-nodes-setup/out` directory. To change this location, update the `nitro_directory` variable in the [setup-vars.yml](./setup-vars.yml) file. ### On Local Host
- To deploy nitro contracts locally, execute the `deploy-contracts.yml` Ansible playbook:
```bash ```bash
LANG=en_US.utf8 ansible-playbook -i localhost, --connection=local deploy-contracts.yml --extra-vars='{ "target_host": "localhost"}' --user $USER -kK LANG=en_US.utf8 ansible-playbook deploy-contracts.yml --extra-vars='{ "target_host": "localhost"}' --user $USER -kK
``` ```
- For skipping container build, run with `"skip_container_build" : true` in the `--extra-vars` parameter: NOTE: By default, deployments are created in an `out` directory. To change this location, update the `nitro_directory` variable in the [setup-vars.yml](./setup-vars.yml) file
```bash - For skipping container build, set `"skip_container_build" : true` in the `--extra-vars` parameter:
LANG=en_US.utf8 ansible-playbook -i localhost, --connection=local deploy-contracts.yml --extra-vars='{ "target_host": "localhost", "skip_container_build": true }' --user $USER -kK
``` ```bash
LANG=en_US.utf8 ansible-playbook deploy-contracts.yml --extra-vars='{"target_host" : "localhost", "skip_container_build": true}' --user $USER -kK
```
### On Remote Host
To run the playbook on a remote host:
- Create a new `hosts.ini` file:
```bash
cp ../hosts.example.ini hosts.ini
```
- Edit the [`hosts.ini`](./hosts.ini) file to run the playbook on a remote machine:
```ini
[<deployment_host>]
<host_name> ansible_host=<target_ip> ansible_user=<ssh_user> ansible_ssh_common_args='-o ForwardAgent=yes'
```
- Replace `<deployment_host>` with `nitro_host`
- Replace `<host_name>` with the alias of your choice
- Replace `<target_ip>` with the IP address or hostname of the target machine
- Replace `<ssh_user>` with the SSH username (e.g., dev, ubuntu)
- Verify that you are able to connect to the host using the following command
```bash
ansible all -m ping -i hosts.ini -k
# Expected output:
# <host_name> | SUCCESS => {
# "ansible_facts": {
# "discovered_interpreter_python": "/usr/bin/python3.10"
# },
# "changed": false,
# "ping": "pong"
# }
```
- Execute the `deploy-contracts.yml` Ansible playbook for remote deployment:
```bash
LANG=en_US.utf8 ansible-playbook -i hosts.ini deploy-contracts.yml --extra-vars='{ "target_host": "nitro_host"}' --user $USER -kK
```
- For skipping container build, run with `"skip_container_build" : true` in the `--extra-vars` parameter:
```bash
LANG=en_US.utf8 ansible-playbook -i hosts.ini deploy-contracts.yml --extra-vars='{ "target_host": "nitro_host", "skip_container_build": true }' --user $USER -kK
```
## Check Deployment Status ## Check Deployment Status

View File

@ -3,4 +3,4 @@ geth_chain_id: ""
geth_deployer_pk: "" geth_deployer_pk: ""
token_name: "" token_name: ""
token_symbol: "" token_symbol: ""
intial_token_supply: "" initial_token_supply: ""

View File

@ -1,3 +1,3 @@
target_host: "localhost" target_host: "localhost"
nitro_directory: ./out nitro_directory: out
skip_container_build: false skip_container_build: false

View File

@ -6,7 +6,7 @@ config:
GETH_DEPLOYER_PK: {{ geth_deployer_pk }} GETH_DEPLOYER_PK: {{ geth_deployer_pk }}
TOKEN_NAME: {{ token_name }} TOKEN_NAME: {{ token_name }}
TOKEN_SYMBOL: {{ token_symbol }} TOKEN_SYMBOL: {{ token_symbol }}
INITIAL_TOKEN_SUPPLY: {{ intial_token_supply }} INITIAL_TOKEN_SUPPLY: {{ initial_token_supply }}
network: network:
ports: {} ports: {}
volumes: volumes:

3
nitro-nodes-setup/.gitignore vendored Normal file
View File

@ -0,0 +1,3 @@
out
nitro-vars.yml
hosts.ini

View File

@ -4,14 +4,22 @@
To get started, follow the [installation](../README.md#installation) guide to setup ansible on your machine To get started, follow the [installation](../README.md#installation) guide to setup ansible on your machine
## Run a nitro node ## Setup for Remote Host
To run the playbook on a remote host:
- Follow steps from [setup remote hosts](../README.md#setup-remote-hosts)
- Update / append the [`hosts.ini`](../hosts.ini) file for your remote host with `<deployment_host>` set as `nitro_host`
## Setup
The following commands have to be executed in [`nitro-nodes-setup`](./) directory The following commands have to be executed in [`nitro-nodes-setup`](./) directory
- Copy the `nitro-vars-example.yml` vars file - Copy the `nitro-vars-example.yml` vars file
```bash ```bash
cp nitro-vars-example.yml nitro-vars.yml cp nitro-vars.example.yml nitro-vars.yml
``` ```
- Edit [`nitro-vars.yml`](./nitro-vars.yml) and fill in the following values - Edit [`nitro-vars.yml`](./nitro-vars.yml) and fill in the following values
@ -56,19 +64,76 @@ The following commands have to be executed in [`nitro-nodes-setup`](./) director
nitro_l2_ext_multiaddr: "" nitro_l2_ext_multiaddr: ""
``` ```
- To run a nitro node, execute the `run-nitro-nodes.yml` Ansible playbook by running the following command. ## Run Nitro Node
NOTE: By default, deployments are created in the `nitro-nodes-setup/out` directory. To change this location, update the `nitro_directory` variable in the [setup-vars.yml](./setup-vars.yml) file. ### On Local Host
- To run a nitro node, execute the `run-nitro-nodes.yml` Ansible playbook by running the following command:
```bash ```bash
LANG=en_US.utf8 ansible-playbook -i localhost, --connection=local run-nitro-nodes.yml --extra-vars='{ "target_host": "localhost"}' -kK --user $USER LANG=en_US.utf8 ansible-playbook run-nitro-nodes.yml --extra-vars='{ "target_host": "localhost"}' --user $USER -kK
``` ```
- For skipping container build, run with `"skip_container_build" : true` in the `--extra-vars` parameter: NOTE: By default, deployments are created in a `out` directory. To change this location, update the `nitro_directory` variable in the [setup-vars.yml](./setup-vars.yml) file
- For skipping container build, run with `"skip_container_build" : true` in the `--extra-vars` parameter:
```bash
LANG=en_US.utf8 ansible-playbook -i hosts.ini run-nitro-nodes.yml --extra-vars='{ "target_host": "nitro_host", "skip_container_build": true }' --user $USER -kK
```
### On Remote Host
To run the playbook on a remote host:
- Create a new `hosts.ini` file:
```bash
cp ../hosts.example.ini hosts.ini
```
- Edit the [`hosts.ini`](./hosts.ini) file to run the playbook on a remote machine:
```ini
[<deployment_host>]
<host_name> ansible_host=<target_ip> ansible_user=<ssh_user> ansible_ssh_common_args='-o ForwardAgent=yes'
```
- Replace `<deployment_host>` with `nitro_host`
- Replace `<host_name>` with the alias of your choice
- Replace `<target_ip>` with the IP address or hostname of the target machine
- Replace `<ssh_user>` with the SSH username (e.g., dev, ubuntu)
- Verify that you are able to connect to the host using the following command
```bash
ansible all -m ping -i hosts.ini -k
# Expected output:
# <host_name> | SUCCESS => {
# "ansible_facts": {
# "discovered_interpreter_python": "/usr/bin/python3.10"
# },
# "changed": false,
# "ping": "pong"
# }
```
- Copy and edit the [`nitro-vars.yml`](./nitro-vars.yml) file as described in the [local setup](./README.md#run-nitro-node-on-local-host) section
- Execute the `run-nitro-nodes.yml` Ansible playbook for remote deployment:
```bash
LANG=en_US.utf8 ansible-playbook -i hosts.ini run-nitro-nodes.yml --extra-vars='{ "target_host": "nitro_host"}' --user $USER -kK
```
- For skipping container build, run with `"skip_container_build" : true` in the `--extra-vars` parameter:
```bash
LANG=en_US.utf8 ansible-playbook -i hosts.ini run-nitro-nodes.yml --extra-vars='{ "target_host": "nitro_host", "skip_container_build": true }' --user $USER -kK
```
```bash
LANG=en_US.utf8 ansible-playbook -i localhost, --connection=local run-nitro-nodes.yml --extra-vars='{ "target_host": "localhost", "skip_container_build": true }' -kK --user $USER
```
## Check Deployment Status ## Check Deployment Status

View File

@ -1,3 +1,3 @@
target_host: "localhost" target_host: "localhost"
nitro_directory: ./out nitro_directory: out
skip_container_build: false skip_container_build: false

View File

@ -1,8 +1,8 @@
NITRO_CHAIN_URL={{ nitro_l1_chain_url }} NITRO_CHAIN_URL={{ nitro_l1_chain_url }}
NITRO_SC_PK={{ nitro_sc_pk }} NITRO_SC_PK={{ nitro_sc_pk }}
NITRO_CHAIN_PK={{ nitro_chain_pk }} NITRO_CHAIN_PK={{ nitro_chain_pk }}
NA_ADDRESS={{ na_address }} NA_ADDRESS="{{ na_address }}"
VPA_ADDRESS={{ vpa_address }} VPA_ADDRESS="{{ vpa_address }}"
CA_ADDRESS={{ ca_address }} CA_ADDRESS="{{ ca_address }}"
NITRO_BOOTPEERS={{ nitro_l1_bridge_multiaddr }} NITRO_BOOTPEERS={{ nitro_l1_bridge_multiaddr }}
NITRO_EXT_MULTIADDR={{ nitro_l1_ext_multiaddr }} NITRO_EXT_MULTIADDR={{ nitro_l1_ext_multiaddr }}

View File

@ -1,10 +1,10 @@
NITRO_CHAIN_URL={{ nitro_l2_chain_url }} NITRO_CHAIN_URL={{ nitro_l2_chain_url }}
NITRO_SC_PK={{ nitro_sc_pk }} NITRO_SC_PK={{ nitro_sc_pk }}
NITRO_CHAIN_PK={{ nitro_chain_pk }} NITRO_CHAIN_PK={{ nitro_chain_pk }}
NA_ADDRESS={{ na_address }} NA_ADDRESS="{{ na_address }}"
VPA_ADDRESS={{ vpa_address }} VPA_ADDRESS="{{ vpa_address }}"
CA_ADDRESS={{ ca_address }} CA_ADDRESS="{{ ca_address }}"
BRIDGE_ADDRESS={{ bridge_contract_address }} BRIDGE_ADDRESS="{{ bridge_contract_address }}"
NITRO_BOOTPEERS={{ nitro_l2_bridge_multiaddr }} NITRO_BOOTPEERS={{ nitro_l2_bridge_multiaddr }}
NITRO_EXT_MULTIADDR={{ nitro_l2_ext_multiaddr }} NITRO_EXT_MULTIADDR={{ nitro_l2_ext_multiaddr }}
NITRO_L2=true NITRO_L2=true