	\chapter{User Manual} \label{ch:summary}
	    \section{Rancher: Accessing the Containers}
	    After the containers have been deployed, there are a few steps that must be followed on the Rancher UI to access the containers. 
	    \begin{enumerate}
	        \item Login to the \href{https://cloud.cs.vt.edu/}{VT CS Cloud} website (Figure \ref{fig:CScloudWebsite}), then navigate to the group the containers reside on.
	        \begin{figure}[h!]
	            \centering
	            \includegraphics[scale = 0.4]{img/cluster.png}
	            \caption{CS Cloud Website}
	            \label{fig:CScloudWebsite}
	        \end{figure}
	        \item In the Workloads tab, select the container you wish to connect to
         (Figure \ref{fig:containerSelection}).
	        \begin{figure}[h!]
	            \centering
	            \includegraphics[scale = 0.5]{img/container.png}
	            \caption{Container selection}
	            \label{fig:containerSelection}
	        \end{figure}
	        \newpage
	        \item Once you have been brought to the container's settings page, navigate to the pod section and click on the menu icon, and then select ‘View Logs’ 
         (Figure \ref{fig:containersLogs}).
	        \begin{figure}[h!]
	            \centering
	            \includegraphics[scale = 0.5]{img/view_logs.png}
	            \caption{Containers logs}
	            \label{fig:containersLogs}
	        \end{figure}
	        \item Inside the terminal that will pop up, scroll until you can see a URL ending with ‘token=’ and a large string of characters
         (Figure \ref{fig:findingToken}). 
         Copy these characters, save them somewhere on your machine and then you can exit the terminal.
	        \begin{figure}[h!]
	            \centering
	            \includegraphics[scale = 0.5]{img/logs.png}
	            \caption{Finding the token}
	            \label{fig:findingToken}
	        \end{figure}
	        \item Next, navigate back to the workloads page that contains all of the containers. Select the ‘80/http’ option directly below the desired container.
	        \begin{figure}[h!]
	            \centering
	            \includegraphics[scale = 0.5]{img/http.png}
	            \caption{Container's HTTP Connection}
	            \label{fig:my_label}
	        \end{figure}
	        \item Finally, you will be brought to a new page with a Jupyter notebook page open. In the text box at the top of the page, paste the token in and then select login. 
	        \begin{figure}[h!]
	            \centering
	            \includegraphics[scale = 0.6]{img/jupyter-login.png}
	            \caption{Jupyter Login}
	            \label{fig:my_label}
	        \end{figure}
	        \item Now you will officially be connected to the container's Jupyter Notebook, and you will have access to the file system and be ready to develop.
	    \end{enumerate}
	    \begin{figure}[h!]
            \centering
            \includegraphics[scale = 0.6]{img/logged_in.png}
            \caption{Jupyter Homepage}
            \label{fig:my_label}
	    \end{figure}

        
        \section{Adding a new workflow automation entry}
        The steps to create a new workflow automation entry to the registry are as follows:

        % \subsection{Example workflow}
        % Let's take an example where we have the following workflow:

        % 1. Extract the URLs present in a .txt file 
        % 2. Model which topics the extracted URLs talk about 

        % For this example, let's assume that we have two Docker images that do these tasks taking as input any file that is present in the folder where they're run and saving the output in the same folder. Let's assume that the Docker images' tags are: 

        % \begin{enumerate}
        %     \item extract\_url:latest
        %     \item topic\_model:latest
        % \end{enumerate} 

        % Here is how we would add this scenario to the registry. 

        \begin{enumerate}
            \item Navigate to \url{https://frontend.discovery.cs.vt.edu/workflows} and log in.
            \item Create a goal(s)
                
            \begin{figure}[H]
	            \centering
	            \includegraphics[width=\textwidth]{img/user_manual/add_goal.png}
	            \caption{Add a goal}
	            \label{fig:add_a_goal}
	        \end{figure}
            \item Create a service(s)
            
         \begin{figure}[H]
	            \centering
	            \includegraphics[width=\textwidth]{img/user_manual/add_service.png}
	            \caption{Add a service}
	            \label{fig:add_a_service}
	        \end{figure}

            \item Link the created goals and services using the reasoner 
            

         \begin{figure}[H]
	            \centering
	            \includegraphics[width=\textwidth]{img/user_manual/add_reasoner.png}
	            \caption{Link goals and services together by creating a reasoner entry}
	            \label{fig:add_a_reasoner}
	        \end{figure}
        
        \end{enumerate}

        \subsection{Result}

        This will result in a new entry being created in the Registry database that houses all the data necessary to generate a workflow. This will result in an entry being created similar to the database entries shown below: 

        \begin{figure}[H]
            \centering
            \includegraphics[width=\textwidth]{img/user_manual/registry_created_goals.png}
            \caption{A sample list of goals created in the Registry database}
            \label{fig:registry_created_goals}
        \end{figure}

        \begin{figure}[H]
            \centering
            \includegraphics[width=\textwidth]{img/user_manual/registry_created_services.png}
            \caption{A sample service created in the Registry database}
            \label{fig:registry_created_services}
        \end{figure}

        \begin{figure}[H]
            \centering
            \includegraphics[width=\textwidth]{img/user_manual/registry_created_reasoner_metadata.png}
            \caption{A sample reasoner metadata entry created in the Registry database}
            \label{fig:registry_created_reasoner_metadata}
        \end{figure}
