From 2da6642faf46b5da940a63c860f6dc4be23f8f3c Mon Sep 17 00:00:00 2001 From: boneyard93501 Date: Thu, 12 Aug 2021 00:35:01 +0000 Subject: [PATCH] GitBook: [2.0.0] 23 pages modified --- tutorials_tutorials/recipes_setting_up.md | 6 +- .../tutorial_run_local_node.md | 127 +++++++++++++----- 2 files changed, 96 insertions(+), 37 deletions(-) diff --git a/tutorials_tutorials/recipes_setting_up.md b/tutorials_tutorials/recipes_setting_up.md index 87e4013..4440a59 100644 --- a/tutorials_tutorials/recipes_setting_up.md +++ b/tutorials_tutorials/recipes_setting_up.md @@ -1,6 +1,10 @@ # Setting Up Your Environment -In order to develop within the Fluence solution, [Rust](https://www.rust-lang.org/tools/install) and small number of tools are required. +In order to develop within the Fluence solution, [Node](https://nodejs.org/en/), [Rust](https://www.rust-lang.org/tools/install) and small number of tools are required. + +### NodeJs + +Download the \[installer\]\([https://nodejs.org/en/download/](https://nodejs.org/en/download/)\) for your platform and follow the instructions. ### Rust diff --git a/tutorials_tutorials/tutorial_run_local_node.md b/tutorials_tutorials/tutorial_run_local_node.md index 306e60f..f7fbfeb 100644 --- a/tutorials_tutorials/tutorial_run_local_node.md +++ b/tutorials_tutorials/tutorial_run_local_node.md @@ -12,9 +12,13 @@ where the `-d` flag runs the container in detached mode, `-e` flag sets the envi Once the container is up and running, we can tail the log \(output\) with -```bash +```text docker logs -f fluence +``` +Which gives os the logged output: + +```bash [2021-03-11T01:31:17.574274Z INFO particle_node] +-------------------------------------------------+ | Hello from the Fluence Team. If you encounter | @@ -36,6 +40,8 @@ docker logs -f fluence ``` + + For future interaction with the node, we need to retain the server peer id 12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx. And if you feel the need to snoop around the container: ```bash @@ -51,20 +57,33 @@ Now that we have a local node, we can use the `fldist` tool to interact with it. Let's inspect our node and check for any available modules and interfaces: -```bash -fldist get_modules --node-id 12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx --node-addr /ip4/127.0.0.1/tcp/9999/ws/p2p/12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx -client seed: 43PmCycRqLt9h3t5Dbmkc3vpNjF9qrNDEVLvQhjCQYSj -client peerId: 12D3KooWQXTe2aFzUsYFf9mBHe4poey45nmAoa8PQwCc2iy9BLMW -node peerId: 12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx -[[]] +```text +fldist get_modules \ + --node-id 12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx \ + --node-addr /ip4/127.0.0.1/tcp/9999/ws/p2p/12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx \ + --pretty +``` -fldist get_interfaces --node-id 12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx --node-addr /ip4/127.0.0.1/tcp/9999/ws/p2p/12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx -client seed: DGf3E48yr73tJbxXpfxyNiRNFsoeRgxKUCpUDYafkXaN -client peerId: 12D3KooWEY37spzSbrg1GTFEo67p9X8cFqmYDHuzaBWWJ9aRT1G2 -node peerId: 12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx +Let's us check on available modules and gives us: + +```bash +[[]] +``` + +And checking on available interfaces: + +```text +fldist get_interfaces \ + --node-id 12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx \ + --node-addr /ip4/127.0.0.1/tcp/9999/ws/p2p/12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx + --expand +``` + +Results in: + +```text 60000 [ [] ] -to expand interfaces, use get_interfaces --expand ``` Since we just initiated the node, we expect no modules and no interfaces and the `fldist` queries confirm our expectations. To further explore and validate the node, we can create a small [greeting](https://github.com/fluencelabs/fce/tree/master/examples/greeting) service. @@ -77,49 +96,80 @@ cd fluence-greeeter echo '{ "name":"greeting"}' > greeting_cfg.json ``` -We just grabbed the greeting wasm file from the Fluence repo and created a service configuration file, greeting\_cfg.json, which allow us to create a new GreetingService: +We just grabbed the greeting Wasm file from the Fluence repo and created a service configuration file, `greeting_cfg.json`, which allow us to create a new GreetingService: ```bash -fldist --node-id 12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx --node-addr /ip4/127.0.0.1/tcp/9999/ws/p2p/12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx new_service --ms /Users/bebo/localdev/fce/examples/greeting/artifacts/greeting.wasm:greeting_cfg.json -n GreetingService +fldist --node-id 12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx \ + --node-addr /ip4/127.0.0.1/tcp/9999/ws/p2p/12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx \ + new_service \ + --ms examples/greeting/artifacts/greeting.wasm:greeting_cfg.json \ + -n GreetingService +``` + +Which gives us the service id: + +```text client seed: 7VtMT7dbdfuU2ewWHEo42Ysg5B9KTB5gAgM8oDEs4kJk client peerId: 12D3KooWRSmoTL64JVXna34myzAuKWaGkjE6EBAb9gaR4hyyyQDM node peerId: 12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx -uploading blueprint GreetingService to node 12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx via client 12D3KooWRSmoTL64JVXna34myzAuKWaGkjE6EBAb9gaR4hyyyQDM -NON-CONSTANT BLUEPRINT ID: Expected blueprint id to be predefined as 88b9b328-7c2b-44fe-8f2c-01b52db12fd9, but it was generated by node as 94d02dfe696549a98e23c5de8713e7c6d6f91694e823790a2f6dcfcc93843be3 service id: 64551400-6296-4701-8e82-daf0b4e02751 service created successfully ``` -We now have a greeting service running on our node. As always, make a note of the service id, 64551400-6296-4701-8e82-daf0b4e02751. +We now have a greeting service running on our node. As always, take note of the service id. ```bash -fldist get_modules --node-id 12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx --node-addr /ip4/127.0.0.1/tcp/9999/ws/p2p/12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx -client seed: HXoV5UfoBAtT8vM2zibm6oiTt7ecFBbP3xSF2dec4RTF -client peerId: 12D3KooWGJ8crCtYy4es835v5dVhTbD7snyLxCQupuiq2sLSXMyA -node peerId: 12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx -[[{"config":{"logger_enabled":true,"logging_mask":null,"mem_pages_count":100,"mounted_binaries":null,"wasi":{"envs":null,"mapped_dirs":null,"preopened_files":[]}},"hash":"80a992ec969576289c61c4a911ba149083272166ffec2949d9d4a066532eec1d","name":"greeting"}]] +fldist get_modules \ + --node-id 12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx \ + --node-addr /ip4/127.0.0.1/tcp/9999/ws/p2p/12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx \ + --pretty +``` + +Which now lists our uploaded module: + +```text +[ + { "config": { + "logger_enabled":true, + "logging_mask":null, + "mem_pages_count":100, + "mounted_binaries":null, + "wasi":{ + "envs":null, + "mapped_dirs":null, + "preopened_files":[] + }, + "hash":"80a992ec969576289c61c4a911ba149083272166ffec2949d9d4a066532eec1d", + "name":"greeting" + } +] ``` Yep, checking once again for modules, the output confirms that the greeting service is available. Writing a small AIR script allows us to use the service: ```text -(xor - (seq - (call relay (service "greeting") [name] result) - (call %init_peer_id% (returnService "run") [result]) - ) - (call %init_peer_id% (returnService "run") [%last_error%]) -) +service GreetingService("service-id"): + greeting: string -> string + +func greeting(name:string, node:string, greeting_service_id: string) -> string: + on node: + GreetingService greeting_service_id + res <- GreetingService.greeting(name) + <- res ``` -Copy and save the script to greeting.clj and we can use our trusted `fldist` tool: +Compile the script with [`aqua-cli`](https://doc.fluence.dev/aqua-book/getting-started/quick-start) and use the resulting file with the`fldist` tool: + +```text +fldist --node-id 12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx \ + --node-addr /ip4/127.0.0.1/tcp/9999/ws/p2p/12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx \ + run_air \ + -p greeting.greeting.air \ + -d '{"service": "64551400-6296-4701-8e82-daf0b4e02751", "name":"Fluence"}' +``` ```bash -fldist --node-id 12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx --node-addr /ip4/127.0.0.1/tcp/9999/ws/p2p/12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx run_air -p greeting.clj -d '{"service": "64551400-6296-4701-8e82-daf0b4e02751", "name":"Fluence"}' -client seed: 8eXzEhypvkYST82sakeS4NeGFSyxqyCSpv2GQj3tQK5E -client peerId: 12D3KooWLFqJwuHNe2kWF8SMgX6cm24L83JUADFcbrj5fC1z3b21 -node peerId: 12D3KooWLFCmDq4vDRfaxW2GA6kYnorxAiie78XzQrVDVoWEZnPx -Particle id: 14db3aff-b1a9-439e-8890-d0cdc9a0bacd. Waiting for results... Press Ctrl+C to stop the script. + =================== [ "Hi, Fluence" @@ -141,13 +191,18 @@ Yep, our node and the tools are working as expected. Going back to the logs, we ```bash docker logs -f fluence +``` + +And check from the bottom up: + +```text [2021-03-12T02:42:51.041267Z INFO aquamarine::particle_executor] Executing particle 14db3aff-b1a9-439e-8890-d0cdc9a0bacd [2021-03-12T02:42:51.041927Z INFO particle_closures::host_closures] Executed host call "64551400-6296-4701-8e82-daf0b4e02751" "greeting" (96us 700ns) [2021-03-12T02:42:51.046652Z INFO particle_node::network_api] Sent particle 14db3aff-b1a9-439e-8890-d0cdc9a0bacd to 12D3KooWLFqJwuHNe2kWF8SMgX6cm24L83JUADFcbrj5fC1z3b21 @ [/ip4/172.17.0.1/tcp/61636/ws] ``` -Looks like our node container and logging is up and running and ready for your development use. As the Fluence team is rapidly developig, make sure you stay up to date. Check the repo or [Docke rhub](https://hub.docker.com/r/fluencelabs/fluence) and update with `docker pull fluencelabs/fluence:latest`. +Looks like our node container and logging is up and running and ready for your development use. As the Fluence team is rapidly developing, make sure you stay up to date. Check the repo or [Docker hub](https://hub.docker.com/r/fluencelabs/fluence) and update with `docker pull fluencelabs/fluence:latest`. Happy composing!