-After some seconds, we should see some log messages informing about
-the progress of the deployment.
-If you now open another terminal and connect to the host through SSH,
-you should find some directories created by NEPI.
-You should see a directory named \emph{nepi-exp}, and under that directory
-you will find another with the identifier you gave when you created the
-experiment controller (the <exp-id>).
-Under the experiment directory, you will find directories for each of the
-resources deployed (e.g. \emph{node-1}, \emph{app-2}).
-The resource directories are named with a short string that identifies the
-type of resource (e.g. 'node', 'app', etc), followed by a unique number that
-uniquely identifies a given resource within the experiment,
-the global unique identifier (guid).
-
-From the ipython console, we can check the deployment status of each resource
-by querying the EC with the method \emph{state}.
-The argument \emph{hr} stand for `human readable`, and will return a string
-state instead of a state number.
+After some seconds, we should see some output messages informing us about the
+progress in the host deployment.
+If you now open another terminal and you connect to the host using
+SSH (as indicated below), you should see that a directory for your experiment
+has been created in the host. In the remote host you will see that two NEPI
+directories were created in the \$HOME directory: \emph{nepi-src} and \emph{nepi-exp}.
+The first one is where NEPI will store files that might be re used by many
+experiments (e.g. source code, input files) . The second directory \emph{nepi-exp},
+is where experiment specific files (e.g. results, deployment scripts) will be stored.
+
+\begingroup
+ \fontsize{10pt}{12pt}\selectfont
+
+\begin{verbatim}
+
+$ ssh -i identity username@hostname
+
+\end{verbatim}
+
+\endgroup
+
+Inside the \emph{nepi-exp} directory, you will find another directory with
+the <exp-id> assigned to your EC, and inside that directory you should find
+one directory named node-1 which will contain the files (e.g. result traces)
+associated to the LinuxNode reosurce you just deployed.
+In fact for every resource deployed associated to that host (e.g. each
+linux::Application), NEPI will create a directory to place files related to it.
+The name of the directory identifies the type of resources (e.g. 'node',
+'app', etc) and it is followed by the global unique identifier (guid).
+
+We can see if a resource finished deploying by querying its state through the EC
git://git.onelab.eu / nepi.git / blobdiff