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-nodes-setup/README.md

@@ -1,8 +1,10 @@
 # nitro-nodes-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 with passwordless sudo
 
 ## Setup
 
@@ -52,33 +54,13 @@ The following commands have to be executed in [`nitro-nodes-setup`](./) director
 
 ## Run Nitro Node
 
-### On Local Host
-
-- To run a nitro node, execute the `run-nitro-nodes.yml` Ansible playbook by running the following command:
-
-  ```bash
-  LANG=en_US.utf8 ansible-playbook run-nitro-nodes.yml --extra-vars='{ "target_host": "localhost"}' --user $USER -kK
-  ```
-
-  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": "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:
+- Edit the [`hosts.ini`](./hosts.ini) file:
 
   ```ini
   [<deployment_host>]
@@ -88,12 +70,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
 
   ```bash
-  ansible all -m ping -i hosts.ini -k
+  ansible all -m ping -i hosts.ini
 
   # Expected output:
 
@@ -108,31 +90,32 @@ To run the playbook on a remote host:
 
 - 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:
+- Execute the `run-nitro-nodes.yml` Ansible playbook to deploy nitro nodes:
 
   ```bash
-  LANG=en_US.utf8 ansible-playbook -i hosts.ini run-nitro-nodes.yml --extra-vars='{ "target_host": "nitro_host"}' --user $USER -kK
+  LANG=en_US.utf8 ansible-playbook -i hosts.ini run-nitro-nodes.yml --extra-vars='{ "target_host": "nitro_host"}' --user $USER
   ```
 
+  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
+  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
   ```
 
-
 ## Check Deployment Status
 
-- Run the following command in the directory where the deployments are created
+Run the following command in the directory where the deployments are created
 
-  - Check L1 nitro node logs:
+- Check L1 nitro node logs:
 
-    ```bash
-    laconic-so deployment --dir l1-nitro-deployment logs nitro-node -f
-    ```
+  ```bash
+  laconic-so deployment --dir l1-nitro-deployment logs nitro-node -f
+  ```
 
-  - Check L2 nitro node logs:
+- Check L2 nitro node logs:
 
-    ```bash
-    laconic-so deployment --dir l2-nitro-deployment logs nitro-node -f
-    ```
+  ```bash
+  laconic-so deployment --dir l2-nitro-deployment logs nitro-node -f
+  ```

nitro-nodes-setup/setup-vars.yml

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