verita84 2020-12-18 17:52:15 +00:00
parent b339ff4325
commit 283b6e2766

@ -1,11 +1,10 @@
![Pic](https://verita84.com/git/verita84/picluster/raw/branch/master/images/faas-0.png)
With this new feature, applications can spin up containers themselves and retrieve data from the PiCluster server. Lets explore how this works.
With this feature, applications can spin up containers themselves and retrieve data from the PiCluster server. Lets explore how this works.
![Pic](https://verita84.com/git/verita84/picluster/raw/branch/master/images/faas-1.png)
![Pic](https://verita84.com/git/verita84/picluster/raw/branch/master/images/faas-0.png)
When a function is finished running, the container is automatically deleted and the output is stored on the server. When the application requests the data from the server, the data is removed as well.
![Pic](https://verita84.com/git/verita84/picluster/raw/branch/master/images/faas-1.png)
In the screenshot above, you can see the current functions running on the cluster where the data is not retrieved yet. There is also another option under the functions category to remove all the functions and the output data stored.
In the screenshot below, you can see the function viewer. From here, you can select a function where the output was not retrieved yet by an application and view the output. You will also notice that there is a curl command in the Data Retrieval text box. For testing, you can copy and paste the contents into a terminal to see the output from the function.