Add steps to clean up service provider setup (#14)

Part of [Service Provider Setup](https://www.notion.so/Service-provider-setup-a09e2207e1f34f3a847f7ce9713b7ac5)
- Move user setup playbook to separate directory
- Remove unneeded variables

Co-authored-by: Adw8 <adwaitgharpure@gmail.com>
Reviewed-on: cerc-io/testnet-ops#14

nitro-bridge-setup/README.md

@@ -1,8 +1,10 @@
 # nitro-bridge-setup
 
-## Setup Ansible
+## Prerequisites
 
-To get started, follow the [installation](../README.md#installation) guide to setup ansible on your machine
+- Setup Ansible: To get started, follow the [installation](../README.md#installation) guide to setup ansible on your machine.
+
+- Setup user with passwordless sudo: Follow steps from [Setup a user](../user-setup/README.md#setup-a-user) to setup a new user
 
 ## Setup
 
@@ -40,33 +42,13 @@ The following commands have to be executed in the [`nitro-bridge-setup`](./) dir
 
 ## Run Nitro Bridge
 
-### On Local Host
-
-- To setup and run nitro bridge locally, execute the `run-nitro-bridge.yml` Ansible playbook:
-
-  ```bash
-  LANG=en_US.utf8 ansible-playbook run-nitro-bridge.yml --extra-vars='{ "target_host": "localhost"}'  --user $USER -kK
-  ```
-
-  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
-
-- For skipping container build, set `"skip_container_build" : true` in the `--extra-vars` parameter:
-
-  ```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
-   ```
+  ```bash
+  cp ../hosts.example.ini hosts.ini
+  ```
 
-- Edit the [`hosts.ini`](./hosts.ini) file to run the playbook on a remote machine:
+- Edit the [`hosts.ini`](./hosts.ini) file:
 
   ```ini
   [<deployment_host>]
@@ -76,12 +58,12 @@ To run the playbook on a remote host:
   - 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)
+  - Replace `<ssh_user>` with the username of the user that you set up on target machine (e.g. dev, ubuntu)
 
-- Verify that you are able to connect to the host using the following command
+- Verify that you are able to connect to the host using the following command:
 
   ```bash
-  ansible all -m ping -i hosts.ini -k
+  ansible all -m ping -i hosts.ini
 
   # Expected output:
 
@@ -94,25 +76,27 @@ To run the playbook on a remote host:
   # }
   ```
 
-- Execute the `run-nitro-bridge.yml` Ansible playbook for remote deployment:
+- Execute the `run-nitro-bridge.yml` Ansible playbook for deploying nitro bridge:
 
   ```bash
-  LANG=en_US.utf8 ansible-playbook -i hosts.ini run-nitro-bridge.yml --extra-vars='{ "target_host": "nitro_host"}'  --user $USER -kK
+  LANG=en_US.utf8 ansible-playbook -i hosts.ini run-nitro-bridge.yml --extra-vars='{ "target_host": "nitro_host"}'  --user $USER
   ```
 
+  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
+
 - 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
+  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
   ```
 
 ## Check Deployment Status
 
-- Run the following command in the directory where the bridge-deployment is created:
+Run the following command in the directory where the bridge-deployment is created:
 
-  - Check logs for deployments:
+- Check logs for deployments:
 
-    ```bash
-    # Check the bridge deployment logs, ensure that the node is running
-    laconic-so deployment --dir bridge-deployment logs nitro-bridge -f
-    ```
+  ```bash
+  # Check the bridge deployment logs, ensure that the node is running
+  laconic-so deployment --dir bridge-deployment logs nitro-bridge -f
+  ```

nitro-bridge-setup/setup-vars.yml

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