diff --git a/docs/latex/references.bib b/docs/latex/references.bib
index 7b7bf2e88419fed2f12eed25055aa15a555a1904..0d6ba89d1781570f15fea72f3e8869a08d9ba533 100644
--- a/docs/latex/references.bib
+++ b/docs/latex/references.bib
@@ -2,42 +2,42 @@
 @Misc{802.1Q,
 title = {{802.1Q-2014 - Bridges and Bridged Networks}},
 howpublished = {\url{http://www.ieee802.org/1/pages/802.1Q-2014.html}},
-note = {Accessed: 2019-06-15}
+note = {Accedido: 2019-06-15}
 }
 
 @Misc{openstack-basic-networking,
 title = {{Basic networking}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/mitaka/networking-guide/intro-basic-networking.html}},
-note = {Accessed: 2019-06-15}
+note = {Accedido: 2019-06-15}
 }
 
 @Misc{openstack-networking-concepts,
 title = {{Networking concepts}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/arch-design/design-networking/design-networking-concepts.html}},
-note = {Accessed: 2019-06-15}
+note = {Accedido: 2019-06-15}
 }
 
 @Misc{openstack-history,
 title = {{Introduction}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/project-team-guide/introduction.html}},
-note = {Accessed: 2019-06-15}
+note = {Accedido: 2019-06-15}
 }
 
 @Misc{openstack-software,
 title = {{Software}},
 author = {{Openstack}},
 howpublished = {\url{https://www.openstack.org/software/}},
-note = {Accessed: 2019-06-15}
+note = {Accedido: 2019-06-15}
 }
 
 @Misc{openstack-keystone-architecture,
 title = {{Keystone Architecture}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/keystone/latest/getting-started/architecture.html}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @book{openstack-idm-book,
@@ -107,254 +107,252 @@ note = {Accessed: 2019-06-20}
 title = {{Design}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/arch-design/design.html}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{openstack-control-plane,
 title = {{Control plane architecture}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/arch-design/design-control-plane.html}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{openstack-conductor,
 title = {{Conductor as a place for orchestrating tasks}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/nova/rocky/user/conductor.html}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{openstack-compute-overview,
 title = {{Compute service overview}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/nova/latest/install/get-started-compute.html}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{openstack-memcached,
 title = {{Memcached}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/mitaka/install-guide-ubuntu/environment-memcached.html}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{openstack-messaging,
 title = {{Message queuing}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/security-guide/messaging.htmll}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{openstack-lvm,
 title = {{LVM}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/cinder/latest/configuration/block-storage/drivers/lvm-volume-driver.html}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{openstack-volume-drivers,
 title = {{Volume drivers}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/cinder/latest/configuration/block-storage/volume-drivers.html}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{openstack-inventory,
 title = {{Iventory}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/openstack-ansible/rocky/reference/inventory/inventory.html}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{openstack-user-config,
 title = {{openstack\_user\_config settings reference}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/openstack-ansible/queens/reference/inventory/openstack-user-config-reference.html}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{openstack-image-properties-1,
 title = {{Common Image Properties}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/glance/queens/user/common-image-properties.html}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{openstack-image-properties-2,
 title = {{Useful image properties}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/glance/latest/admin/useful-image-properties.html}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{openstack-images-instances,
 title = {{Images and instances}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/glance/queens/admin/troubleshooting.html}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{openstack-storage-api,
 title = {{Object Storage API overview}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/swift/latest/api/object_api_v1_overview.html}},
-note = {Accessed: 2019-07-05}
+note = {Accedido: 2019-07-05}
 }
 
 @Misc{openstack-storage-characteristics,
 title = {{Object Storage characteristics}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/swift/latest/admin/objectstorage-characteristics.html}},
-note = {Accessed: 2019-07-05}
+note = {Accedido: 2019-07-05}
 }
 
 @Misc{openstack-storage-intro,
 title = {{Introduction to Object Storage}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/swift/latest/admin/objectstorage-intro.html}},
-note = {Accessed: 2019-07-05}
+note = {Accedido: 2019-07-05}
 }
 
 @Misc{openstack-storage-components,
 title = {{Components}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/swift/latest/admin/objectstorage-components.html}},
-note = {Accessed: 2019-07-05}
+note = {Accedido: 2019-07-05}
 }
 
 @Misc{openstack-storage-architect,
 title = {{Swift Architectural Overview}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/swift/latest/overview_architecture.html}},
-note = {Accessed: 2019-07-05}
+note = {Accedido: 2019-07-05}
 }
 
 @Misc{openstack-puppet,
 title = {{Welcome to the Puppet OpenStack Guide!}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/puppet-openstack-guide/latest/}},
-note = {Accessed: 2019-07-05}
+note = {Accedido: 2019-07-05}
 }
 
 @Misc{openstack-ansible,
 title = {{OpenStack-Ansible Documentation}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/openstack-ansible/latest/}},
-note = {Accessed: 2019-07-05}
+note = {Accedido: 2019-07-05}
 }
 
 @Misc{openstack-marketplace,
 title = {{The OpenStack Marketplace}},
 author = {{Openstack}},
 howpublished = {\url{https://www.openstack.org/marketplace/distros/}},
-note = {Accessed: 2019-07-05}
+note = {Accedido: 2019-07-05}
 }
 
 @Misc{openstack-nova-architecture,
 title = {{Nova System Architecture}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/nova/latest/user/architecture.html}},
-note = {Accessed: 2019-07-05}
+note = {Accedido: 2019-07-05}
 }
 
 @Misc{openstack-glance-architecture,
 title = {{Basic architecture}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/glance/queens/contributor/architecture.html}},
-note = {Accessed: 2019-07-05}
+note = {Accedido: 2019-07-05}
 }
 
 @Misc{openstack-container-networking,
 title = {{Container networking}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/openstack-ansible/rocky/reference/architecture/container-networking.html}},
-note = {Accessed: 2019-07-05}
+note = {Accedido: 2019-07-05}
 }
 
 @Misc{openstack-networking-architecture,
 title = {{Network architectures}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/openstack-ansible/stein/user/network-arch/example.html}},
-note = {Accessed: 2019-07-05}
+note = {Accedido: 2019-07-05}
 }
 
-@Misc{openstack-container-networking,
+@Misc{openstack-appendix-e,
 title = {{Appendix E: Container networking}},
 author = {{Openstack}},
 howpublished = {\url{https://docs.openstack.org/project-deploy-guide/openstack-ansible/ocata/app-networking.html#network-diagrams}},
-note = {Accessed: 2019-07-05}
+note = {Accedido: 2019-07-05}
 }
 
-
-
 @Misc{openstack-selinux-fix-1,
 title = {{AIO Build Fails on SELinux File Context Tasks}},
 author = {{Openstack}},
 howpublished = {\url{https://bugs.launchpad.net/openstack-ansible/+bug/1782798}},
-note = {Accessed: 2019-07-05}
+note = {Accedido: 2019-07-05}
 }
 
 @Misc{openstack-selinux-fix-2,
 title = {{Drop SELinux support for CentOS 7}},
 author = {{Openstack}},
 howpublished = {\url{https://review.opendev.org/#/c/603860/}},
-note = {Accessed: 2019-07-05}
+note = {Accedido: 2019-07-05}
 }
 
 @Misc{ansible-modules,
 title = {{Module Index}},
 author = {{Ansible}},
 howpublished = {\url{https://docs.ansible.com/ansible/latest/modules/modules_by_category.html}},
-note = {Accessed: 2019-07-05}
+note = {Accedido: 2019-07-05}
 }
 
 @Misc{redhat-virtualization,
 title = {{What is virtualization?}},
 author = {{Red Hat}},
 howpublished = {\url{https://www.redhat.com/en/topics/virtualization/what-is-virtualization}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{redhat-kvm,
 title = {{What is KVM?}},
 author = {{Red Hat}},
 howpublished = {\url{https://www.redhat.com/en/topics/virtualization/what-is-KVM}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{redhat-lxc,
 title = {{What's a Linux container}},
 author = {{Red Hat}},
 howpublished = {\url{https://www.redhat.com/en/topics/containers/whats-a-linux-container}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{redhat-conductor,
 title = {{Conductor}},
 author = {{Red Hat}},
 howpublished = {\url{https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/4/html/Configuration_Reference_Guide/section_conductor.html}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{redhat-cinder,
 title = {{Openstack Block Storage (Cinder)}},
 author = {{Red Hat}},
 howpublished = {\url{https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/6/html/Component_Overview/section-blockStorage.html}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{arch-lxc,
 title = {{Linux Containers}},
 author = {{ArchLinux}},
 howpublished = {\url{https://wiki.archlinux.org/index.php/Linux_Containers}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{vmware-virtualization,
 title = {{Virtualization}},
 author = {{VMware}},
 howpublished = {\url{https://www.vmware.com/solutions/virtualization.html}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @TechReport{vmware-whitepaper,
@@ -369,21 +367,21 @@ title = {{Containers on Virtual Machines or Bare Metal?}},
 title = {{What are Hypervisors?}},
 author = {{Oracle}},
 howpublished = {\url{https://docs.oracle.com/cd/E50245_01/E50249/html/vmcon-hypervisor.html}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{docker-containers,
 title = {{What is a Container?}},
 author = {{Docker}},
 howpublished = {\url{https://www.docker.com/resources/what-container}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @Misc{cisco-datacenter,
 title = {{What is a Data Center}},
 author = {{Cisco}},
 howpublished = {\url{https://www.cisco.com/c/en/us/solutions/data-center-virtualization/what-is-a-data-center.html}},
-note = {Accessed: 2019-06-20}
+note = {Accedido: 2019-06-20}
 }
 
 @TechReport{sp800-145,
diff --git a/docs/latex/report.pdf b/docs/latex/report.pdf
index 9c6ea17c669cc3963ec2391e362f3dec00a3afe3..6667c7910243a74bd2ecd3e375f3478ac05d5bce 100644
Binary files a/docs/latex/report.pdf and b/docs/latex/report.pdf differ
diff --git a/docs/latex/report.tex b/docs/latex/report.tex
index a66eadb250d50992831e2d69ff9d51157d374c62..09c202cb5467ceb36b8176670494db727b1268f1 100644
--- a/docs/latex/report.tex
+++ b/docs/latex/report.tex
@@ -49,7 +49,6 @@
 			Universidad de la República, Montevideo, Uruguay. \\
 			Email: \href{mailto:matias.capucho@fing.edu.uy}{matias.capucho@fing.edu.uy}, \href{mailto:selizondo@fing.edu.uy}{selizondo@fing.edu.uy} }
 
-
 \date{4 de Junio de 2019}
 
 \pagestyle{fancy}
@@ -514,7 +513,7 @@ A continuación se presenta un diseño que ilustra servicios desplegados en cont
 \begin{figure}[H]
 	\centering
 		\includegraphics[width=1.0\columnwidth]{containers-deploy}
-	\caption{Despliegue de servicios Openstack en contenedores. Extraída de \cite{openstack-container-networking}.}
+	\caption{Despliegue de servicios Openstack en contenedores. Extraída de \cite{openstack-appendix-e}.}
 	\label{containers-deploy}
 \end{figure}
 
@@ -537,14 +536,14 @@ Como se menciona anteriormente los contenedores que corren servicios de Openstac
 \section{Configuración OSA}
 En esta sección se presentan las configuraciones y conceptos más relevantes del nodo Deploy a tener en cuenta durante un despliegue de Openstack utilizando Ansible. Estas incluyen las convenciones de directorios empleadas, la configuración estándar y el significado del contenido de los archivos que deben ser modificados.
 
-\subsubsection{Convenciones}
+\subsection{Convenciones}
 \begin{itemize}
 	\item El repositorio de OSA se clona generalmente en el directorio \path{/opt/openstack-ansible}.
 	\item Los roles de Ansible utilizados por defecto se encuentran en el directorio \path{/etc/ansible/roles} los cuales son generados a partir del archivo \path{/opt/openstack-ansible/ansible-role-requirements.yml} mediante la ejecución del \path{script bootstrap-ansible.sh}. 
 	\item Las configuraciones realizadas por el administrador son indicadas en el directorio \path{/etc/openstack_deploy}.
 \end{itemize}
 
-\subsubsection{Inventario}
+\subsection{Inventario}
 Define las especificaciones de los hosts y contenedores dentro del ambiente actual de Openstack. Esta información se encuentra en el archivo \path{/etc/openstack-ansible/openstack_inventory.json}, generado a partir de los host groups, containers groups y components indicados en:
 \begin{itemize}
 	\item La estructura por defecto almacenada en \path{/opt/openstack-ansible/inventory/env.d}
@@ -559,22 +558,310 @@ Define las especificaciones de los hosts y contenedores dentro del ambiente actu
 Este archivo es considerado como referencia en cualquiera de los comandos asociados al despliegue de OSA por lo tanto nunca debe ser eliminado o modificado en un ambiente de producción.\\
 
 Los components hacen referencia a los diferentes servicios que serán instalados durante el despliegue de Openstack, tanto en contenedores virtuales como directamente en los target host. Los containers groups agrupan estos components, determinando los potenciales contenedores a ser creados junto con sus especificaciones. 
-En las configuraciones realizadas en ambos directorios env.d/ se asocian los containers groups anteriores con los hosts groups, los cuales agrupan diversos target hosts. De esta forma se determina qué servicio debe ser instalado en qué target host.\\
+En las configuraciones realizadas en ambos directorios env.d/ se asocian los containers groups anteriores con los hosts groups, los cuales agrupan diversos target hosts. De esta forma se determina qué servicio debe ser instalado en qué target host.
 
-\subsubsection{openstack\_user\_config.yml}
+\subsection{openstack\_user\_config.yml}
 Es el principal archivo de configuración, creado por el operador de Openstack. Las especificaciones de cada sección se detallan en \cite{openstack-user-config}.
 
 \chapter{Instalación}
 
 \section{Ambiente de trabajo}
+
+\subsection{Hardware utilizado}
+Para realizar la instalación de Openstack se utilizó un servidor físico (denominado renata) alojado en el Instituto de Computación de la Facultad de Ingeniería (InCo). El mismo cuenta con una amplia cantidad de recursos destacando sus 40 procesadores virtuales, 128 GB de RAM y 40 TB de disco duro. Se aloja en una red privada del InCo en donde para salir a Internet se debe pasar por un proxy, provocando algunas limitaciones que luego se mencionan.\\
+
+En el servidor fueron necesarias las siguientes configuraciones de red:
+\begin{enumerate}
+	\item Creación de un bridge el cual será utilizado por la interfaz física del servidor y por los distintos NAT que se deben crear con KVM para la arquitectura que se virtualiza.
+Para esto se creo la interfaz br-mgmt con la siguiente configuración:
+	\begin{lstlisting} 
+	DEVICE="br-mgmt"
+	BOOTPROTO="none"
+	IPADDR="192.168.60.242"
+	PREFIX="24"
+	GATEWAY="192.168.60.1"
+	DNS1="192.168.60.230"
+	ONBOOT="yes"
+	TYPE="Bridge"
+	NM_CONTROLLED="no"
+	\end{lstlisting}
+	
+	\item En la interfaz eno2 la cual tenía configurada la IP del bridge quedó de la siguiente forma:
+	\begin{lstlisting}
+	BOOTPROTO=none
+	NAME=eno2
+	UUID=824cd835-662a-4d47-a148-512aec3dd237
+	DEVICE=eno2
+	ONBOOT=yes
+	BRIDGE="br-mgmt"
+	NM_CONTROLLED="no"
+	\end{lstlisting}
+\end{enumerate}
+
+\subsection{Conexión remota hacia el servidor renata}
+Dado que el servidor se encuentra en una red privada del InCo, para conectarse al mismo de forma remota se deben establecer algunas conexiones SSH. A continuación se detallan las conexiones y comandos utilizados.
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=1.0\columnwidth]{acceso-renata}
+	\caption{}
+	\label{acceso-renata}
+\end{figure}
+
+\begin{enumerate}
+	\item Como el servidor se encuentra en una red privada del InCo solo se puede acceder desde un host que se encuentre en una red interna de la FIng, por ej: lulu.fing.edu.uy. Para esto ejecutar:
+	\begin{lstlisting}
+	$ ssh usuario_fing@lulu.fing.edu.uy
+	\end{lstlisting}
+	 
+	\item Desde el host lulu para conectarse al servidor renata se debe ejecutar: 
+	\begin{lstlisting}
+	$ ssh openstack@192.168.60.242
+	\end{lstlisting}
+\end{enumerate}
+
+\subsection{Virtualización con KVM}
+Para crear la arquitectura de nodos se utilizó el virtualizador KVM, debido a que es la tecnología de virtualización utilizada normalmente en los servidores del InCo. Con el fin de facilitar la interacción con KVM a través de una interfaz gráfica, se utilizó el programa virt-manager.
+
+\subsubsection{Utilización virt-manager}
+Dentro del virt-manager lo primero a realizar es configurar una nueva conexión desde el menú Archivo -> Añadir conexión... de la siguiente forma:
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=0.6\columnwidth]{virt-nueva-conexion}
+	\caption{Nueva conexión en virt-manager.}
+	\label{virt-nueva-conexion}
+\end{figure}
+
+Como un host remoto está a dos conexiones SSH del servidor Renata, la configuración que se muestra en la figura X no será suficiente. Para el correcto funcionamiento se debe crear una regla de forwarding que envíe todas las acciones realizadas por el virt-manager hacia el host lulu.fing.edu.uy el cual tiene acceso al servidor. Para lograr esto se debe ejecutar: 
+
+\begin{lstlisting}[gobble=0]
+ssh -L 5900:192.168.60.242:22 <usuario_fing>@lulu.fing.edu.uy
+\end{lstlisting}
+
+El número de puerto utilizado puede ser cualquiera que no esté siendo utilizado y no sea privilegiado.\\
+
+El orden adecuado para conectarse al servidor mediante virt-manager es:
+
+\begin{enumerate}
+	\item Crear la conexión ssh indicada.
+	\item Iniciar virt-manager.
+	\item Inicializar la conexión. En este paso se puede llegar a requerir la contraseña del usuario del servidor renata desde la consola que esté ejecutando el manager.
+\end{enumerate}
+
+Lo siguiente a realizar es crear con KVM las redes virtuales que se natean al bridge br-mgmt del servidor físico. Es necesario crear 4 redes, donde cada una se corresponde con las redes necesarias para el funcionamiento de Openstack. Estas redes son:
+
+\begin{itemize}
+	\item NAT-Open (Red management Subred 10.0.1.0/24).
+	\item NAT-Open-Storage (Red storage Subred 10.0.10.0/24).
+	\item NAT-Open-Vxlan (Red vxlan Subred 10.0.2.0/24).
+	\item NAT-Open-Vlan (Red vlan Subred 10.0.4.0/24).
+\end{itemize}
+
+Para crear estas redes se debe ir al menú Editar -> Detalles de la conexión.
+Luego como se muestra en la imagen en la pestaña de redes virtuales seleccionar el icono (+).
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=0.6\columnwidth]{virt-conf-red}
+	\caption{Configuración de redes virtuales en virt-manager.}
+	\label{virt-conf-red}
+\end{figure}
+
+Al presionar el botón para agregar un nueva red, desplegará en pantalla un wizard. A continuación se muestra el paso a paso de la creación de la red NAT-Open a modo de ejemplo:
+
+\begin{enumerate}
+	\item Seleccionar el nombre de la red
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=0.6\columnwidth]{virt-red-1}
+	\label{virt-red-1}
+\end{figure}
+
+	\item Seleccionar la subred y el rango para el DHCP
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=0.6\columnwidth]{virt-red-2}
+	\label{virt-red-2}
+\end{figure}	
+
+	\item No habilitar direcciones IPv6
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=0.6\columnwidth]{virt-red-3}
+	\label{virt-red-3}
+\end{figure}	
+
+	\item Seleccionar el tipo de red virtual
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=0.6\columnwidth]{virt-red-4}
+	\label{virt-red-4}
+\end{figure}		
+	
+\end{enumerate}
+
+El mismo procedimiento se deberá repetir con el resto de las redes listadas.\\
+
+Lo último que es necesario crear con KVM son las nodos virtuales que se utilizaron para instalar Openstack. En la instalación realizada se utilizan 5 nodos con las especificaciones detalladas a continuación:
+
+\begin{itemize}
+	\item \textbf{Nodo deploy}:
+		\begin{itemize}
+			\item 1 interfaz en NAT-Open
+			\item 2 CPUs
+			\item 200 GB de disco
+			\item 8 GB de RAM
+		\end{itemize}
+
+	\item \textbf{Nodo haproxy1}:
+		\begin{itemize}
+			\item 2 interfaces: una en NAT-Open y otra conectada al bridge br-mgmt de renata
+			\item 4 CPUs
+			\item 200 GB de disco
+			\item 32 GB de RAM
+		\end{itemize}
+
+	\item \textbf{Nodo infra1}:
+		\begin{itemize}
+			\item 4 interfaces: una en cada NAT creada
+			\item 8 CPUs
+			\item 200 GB de disco
+			\item 32 GB de RAM
+		\end{itemize}
+
+	\item \textbf{Nodo compute1}:
+		\begin{itemize}
+			\item 4 interfaces: una en cada NAT creada
+			\item 8 CPUs
+			\item 200 GB de disco
+			\item 32 GB de RAM
+		\end{itemize}
+
+	\item \textbf{Nodo storage1}:
+		\begin{itemize}
+			\item 2 interfaces: una en NAT-Open y otra en NAT-Open-Storage
+			\item 4 CPUs
+			\item 2 discos: uno de 40 GB para el SO y otro de 200 GB para el volumen de cinder
+			\item 32 GB de RAM
+		\end{itemize}
+
+\end{itemize}
+
+A continuación se detalla paso a paso cómo crear el nodo deploy, el resto se realiza de forma análoga salvando las diferencias de recursos e interfaces de red.
+
+\begin{enumerate}
+	\item En el presente ejemplo se crea una VM suponiendo que se instalará el SO.
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=0.6\columnwidth]{virt-nodo-1}
+	\label{virt-nodo-1}
+\end{figure}
+
+	\item Seleccionar la imagen a utilizar y el tipo de SO. La misma deberá estar en un directorio del servidor físico.
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=0.8\columnwidth]{virt-nodo-2}
+	\label{virt-nodo-2}
+\end{figure}
+
+	\item Seleccionar RAM y CPUs.
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=0.6\columnwidth]{virt-nodo-3}
+	\label{virt-nodo-3}
+\end{figure}
+
+	\item Para el almacenamiento se deberá crear un nuevo volumen de la siguiente forma:
+	\begin{enumerate}[label*=\arabic*.]
+		\item Elegir la segunda opción y presionar Administrar.
+	\begin{figure}[H]
+		\centering
+			\includegraphics[width=0.6\columnwidth]{virt-nodo-4a}
+		\label{virt-nodo-4a}
+	\end{figure}
+
+		\item Esto desplegará una ventana mostrando directorios del sistema de archivos de renata. Se puede elegir un volumen existente o crear uno nuevo con el botón (+).
+	\begin{figure}[H]
+		\centering
+			\includegraphics[width=1.0\columnwidth]{virt-nodo-4b}
+		\label{virt-nodo-4b}
+	\end{figure}
+
+		\item Al crearlo se debe especificar el nombre, el tipo y la capacidad.
+	\begin{figure}[H]
+		\centering
+			\includegraphics[width=0.8\columnwidth]{virt-nodo-4c}
+		\label{virt-nodo-4c}
+	\end{figure}
+	
+	\end{enumerate}
+
+	\item Luego se debe ingresar el nombre de la máquina y seleccionar la red que conecta el host directamente al bridge del servidor físico en lugar de la red NAT-Open para que el host tenga conexión a internet durante la instalación y poder realizar las primeras configuraciones en el mismo.
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=0.7\columnwidth]{virt-nodo-5}
+	\label{virt-nodo-5}
+\end{figure}
+
+	\item Se debe verificar en la opción IDE CDROM 1 que esté correctamente seteado la imagen a utilizar para instalar el SO.
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=1.0\columnwidth]{virt-nodo-6}
+	\label{virt-nodo-6}
+\end{figure}
+
+	\item Verificar en las opciones de arranque que el IDE CDROM 1 esté en primer lugar para que la máquina bootee con la imagen seleccionada.
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=0.8\columnwidth]{virt-nodo-7}
+	\label{virt-nodo-7}
+\end{figure}
+
+	\item Finalmente al confirmar todos los cambios se lanzará la VM creada y se instalará el SO.
+
+\end{enumerate}
+
+\subsection{Especificaciones servidor renata}
+La red en la que se encuentra el servidor Renata no cuenta con acceso a internet. Para solucionar este problema se realizó un túnel ssh reverso desde el host lulu.fing.edu.uy al servidor Renata para establecer como proxy de Renata el host proxy.fing.edu.uy, siendo este último el proxy de la FING.
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=0.8\columnwidth]{redes-renata}
+	\caption{Túnel reverso y esquema de servidores.}
+	\label{redes-renata}
+\end{figure}
+
+El funcionamiento de esta configuración se detalla a continuación:
+
 \begin{itemize}
-	\item virtualización con KVM
-	\item configuración de redes en KVM (virt-manager)
-	\item limitaciones de red
-	\item diagrama renata, lulu, VMS, DNS
-	\item túneles SSH, reversos, proxys, etc
+	\item El host lulu.fing.edu.uy inicia una conexion SSH con renata en donde indica que cree una conexión inversa con el proxy de la FIng.
+
+	\item Al establecer la conexión, el servidor renata crea el túnel inverso en donde envía todos los paquetes destinados al puerto 3128 al servidor proxy en el puerto 3128.
+
+	\item Finalmente para que renata tenga acceso a Internet se setean las variables de entorno http\_proxy y https\_proxy con el valor http://localhost:3128. De esta forma todo el tráfico http será enviado al puerto 3128 local y gracias al túnel reverso todos los pedidos http serán enviados al proxy logrando tener acceso a Internet.	
 \end{itemize}
 
+Para lograr esto se debe ejecutar el siguiente comando al iniciar la conexión SSH desde lulu hacia renata:
+
+\begin{lstlisting}[gobble=0]
+$ ssh -R 3128:proxy.fing.edu.uy:3128 openstack@192.168.60.242
+\end{lstlisting}
+
+Como se muestra en la figura \ref{redes-renata} el servidor DNS utilizado se encuentra en la misma red local.
+
+\subsection{Acceso al exterior desde nodos}
+Los nodos virtualizados en el servidor renata con la configuración por defecto no tendrán acceso a Internet. Esto sucede por que al realizar un pedido http o https será enviado al gateway de estos nodos virtuales que es la IP 10.0.1.1 de la interfaz virtual de renata, en donde solamente forwardea los paquetes recibidos en el puerto 3128 al proxy de la FIng. Para solucionar esto basta con configurar las variables de entorno http\_proxy y https\_proxy en los nodos virtualizados con el siguiente valor: http://10.0.1.1:3128. Esto aplica para los 5 nodos utilizados en la instalación.
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=1.0\columnwidth]{internet-nodos}
+	\caption{Salida a Internet en los nodos de Openstack.}
+	\label{internet-nodos}
+\end{figure}
+
+% ------------------------------------------------------
+
 \section{Diseño de arquitectura}
 
 \section{Preparación de nodos}
diff --git a/docs/latex/report.toc b/docs/latex/report.toc
index cc6d80167b651e12d82122df45da1fe311135b91..9d3209dd55e3f89b54bff0a97173353b3a09f1f6 100644
--- a/docs/latex/report.toc
+++ b/docs/latex/report.toc
@@ -1,83 +1,89 @@
 \babel@toc {spanish}{}
-\contentsline {chapter}{\numberline {1}Introducci\IeC {\'o}n}{2}{chapter.1}
-\contentsline {chapter}{\numberline {2}Marco te\IeC {\'o}rico}{3}{chapter.2}
-\contentsline {section}{\numberline {2.1}Cloud computing}{3}{section.2.1}
-\contentsline {section}{\numberline {2.2}Virtualizaci\IeC {\'o}n}{4}{section.2.2}
-\contentsline {subparagraph}{KVM}{5}{section*.3}
-\contentsline {section}{\numberline {2.3}Contenerizaci\IeC {\'o}n}{5}{section.2.3}
-\contentsline {subparagraph}{LXC}{6}{section*.5}
-\contentsline {section}{\numberline {2.4}Datacenters}{6}{section.2.4}
-\contentsline {section}{\numberline {2.5}Redes}{6}{section.2.5}
-\contentsline {subparagraph}{Flat}{7}{section*.6}
-\contentsline {subparagraph}{VLAN}{7}{section*.7}
-\contentsline {subparagraph}{VXLAN}{7}{section*.8}
-\contentsline {chapter}{\numberline {3}Openstack}{8}{chapter.3}
-\contentsline {section}{\numberline {3.1}Origen y definici\IeC {\'o}n}{8}{section.3.1}
-\contentsline {section}{\numberline {3.2}M\IeC {\'o}dulos Core}{9}{section.3.2}
-\contentsline {subsection}{\numberline {3.2.1}Keystone}{9}{subsection.3.2.1}
-\contentsline {subsection}{\numberline {3.2.2}Nova}{10}{subsection.3.2.2}
-\contentsline {subparagraph}{API}{11}{section*.12}
-\contentsline {subparagraph}{Scheduler}{11}{section*.13}
-\contentsline {subparagraph}{Compute}{11}{section*.14}
-\contentsline {subparagraph}{Conductor}{12}{section*.15}
-\contentsline {subparagraph}{Placement}{12}{section*.16}
-\contentsline {subsection}{\numberline {3.2.3}Neutron}{12}{subsection.3.2.3}
-\contentsline {subparagraph}{Neutron-server}{13}{section*.19}
-\contentsline {subparagraph}{Plugins y agentes}{13}{section*.20}
-\contentsline {subparagraph}{Cola de mensajes}{13}{section*.21}
-\contentsline {subsection}{\numberline {3.2.4}Glance}{14}{subsection.3.2.4}
-\contentsline {subparagraph}{Creaci\IeC {\'o}n de una VM}{15}{section*.23}
-\contentsline {subsection}{\numberline {3.2.5}Cinder}{16}{subsection.3.2.5}
-\contentsline {subsection}{\numberline {3.2.6}Swift}{17}{subsection.3.2.6}
-\contentsline {subparagraph}{Principales componentes}{18}{section*.27}
-\contentsline {section}{\numberline {3.3}Tipos de nodos}{19}{section.3.3}
-\contentsline {subparagraph}{Nodo de control}{19}{section*.28}
-\contentsline {subparagraph}{Nodo de red}{19}{section*.29}
-\contentsline {subparagraph}{Nodo de c\IeC {\'o}mputo}{19}{section*.30}
-\contentsline {subparagraph}{Nodo de almacenamiento}{19}{section*.31}
-\contentsline {subparagraph}{Nodo de balanceamiento de carga}{19}{section*.32}
-\contentsline {section}{\numberline {3.4}Servicios de infraestructura}{19}{section.3.4}
-\contentsline {subparagraph}{Galera - MariaDB}{19}{section*.33}
-\contentsline {subparagraph}{Message queue}{19}{section*.34}
-\contentsline {subparagraph}{Memcached}{20}{section*.35}
-\contentsline {section}{\numberline {3.5}M\IeC {\'e}todos de instalaci\IeC {\'o}n}{20}{section.3.5}
-\contentsline {subsection}{\numberline {3.5.1}Ansible}{20}{subsection.3.5.1}
-\contentsline {subparagraph}{Nodo de control}{21}{section*.36}
-\contentsline {subparagraph}{Inventario}{21}{section*.37}
-\contentsline {subparagraph}{M\IeC {\'o}dulos}{21}{section*.38}
-\contentsline {subparagraph}{Tarea}{21}{section*.39}
-\contentsline {subparagraph}{Playbook}{21}{section*.40}
-\contentsline {section}{\numberline {3.6}Arquitectura}{21}{section.3.6}
-\contentsline {subsection}{\numberline {3.6.1}Arquitectura de red}{22}{subsection.3.6.1}
-\contentsline {subparagraph}{Management Network}{22}{section*.42}
-\contentsline {subparagraph}{Overlay Network}{22}{section*.43}
-\contentsline {subparagraph}{Storage Network}{22}{section*.44}
-\contentsline {subsubsection}{Interfaces de red}{22}{section*.45}
-\contentsline {section}{\numberline {3.7}Configuraci\IeC {\'o}n OSA}{26}{section.3.7}
-\contentsline {subsubsection}{Convenciones}{26}{section*.51}
-\contentsline {subsubsection}{Inventario}{26}{section*.52}
-\contentsline {subsubsection}{openstack\_user\_config.yml}{26}{section*.53}
-\contentsline {chapter}{\numberline {4}Instalaci\IeC {\'o}n}{27}{chapter.4}
-\contentsline {section}{\numberline {4.1}Ambiente de trabajo}{27}{section.4.1}
-\contentsline {section}{\numberline {4.2}Dise\IeC {\~n}o de arquitectura}{27}{section.4.2}
-\contentsline {section}{\numberline {4.3}Preparaci\IeC {\'o}n de nodos}{27}{section.4.3}
-\contentsline {subsubsection}{Deploy}{27}{section*.54}
-\contentsline {subsubsection}{Infra1}{29}{section*.56}
-\contentsline {subsubsection}{Compute1}{31}{section*.57}
-\contentsline {subsubsection}{Storage1}{31}{section*.58}
-\contentsline {subsubsection}{HAproxy1}{32}{section*.59}
-\contentsline {section}{\numberline {4.4}Configuraci\IeC {\'o}n}{33}{section.4.4}
-\contentsline {subsection}{\numberline {4.4.1}Configuraci\IeC {\'o}n claves SSH}{33}{subsection.4.4.1}
-\contentsline {subsection}{\numberline {4.4.2}Archivos de configuraci\IeC {\'o}n OSA}{33}{subsection.4.4.2}
-\contentsline {subsubsection}{openstack\_user\_config.yml}{33}{section*.60}
-\contentsline {subsubsection}{user\_variables.yml}{36}{section*.61}
-\contentsline {subsubsection}{cinder.yml}{37}{section*.62}
-\contentsline {subsection}{\numberline {4.4.3}Generaci\IeC {\'o}n de claves}{37}{subsection.4.4.3}
-\contentsline {subsection}{\numberline {4.4.4}Correcciones}{37}{subsection.4.4.4}
-\contentsline {subsubsection}{SELinux}{37}{section*.63}
-\contentsline {section}{\numberline {4.5}Ejecuci\IeC {\'o}n de playbooks}{38}{section.4.5}
-\contentsline {subsubsection}{setup-hosts.yml}{38}{section*.64}
-\contentsline {subsubsection}{install-haproxy.yml}{38}{section*.65}
-\contentsline {subsubsection}{setup-infrastructure.yml}{38}{section*.66}
-\contentsline {subsubsection}{setup-openstack.yml}{38}{section*.67}
-\contentsline {section}{\numberline {4.6}Verificaci\IeC {\'o}n}{39}{section.4.6}
+\contentsline {chapter}{\numberline {1}Introducci\IeC {\'o}n}{3}{chapter.1}
+\contentsline {chapter}{\numberline {2}Marco te\IeC {\'o}rico}{4}{chapter.2}
+\contentsline {section}{\numberline {2.1}Cloud computing}{4}{section.2.1}
+\contentsline {section}{\numberline {2.2}Virtualizaci\IeC {\'o}n}{5}{section.2.2}
+\contentsline {subparagraph}{KVM}{6}{section*.3}
+\contentsline {section}{\numberline {2.3}Contenerizaci\IeC {\'o}n}{6}{section.2.3}
+\contentsline {subparagraph}{LXC}{7}{section*.5}
+\contentsline {section}{\numberline {2.4}Datacenters}{7}{section.2.4}
+\contentsline {section}{\numberline {2.5}Redes}{7}{section.2.5}
+\contentsline {subparagraph}{Flat}{8}{section*.6}
+\contentsline {subparagraph}{VLAN}{8}{section*.7}
+\contentsline {subparagraph}{VXLAN}{8}{section*.8}
+\contentsline {chapter}{\numberline {3}Openstack}{9}{chapter.3}
+\contentsline {section}{\numberline {3.1}Origen y definici\IeC {\'o}n}{9}{section.3.1}
+\contentsline {section}{\numberline {3.2}M\IeC {\'o}dulos Core}{10}{section.3.2}
+\contentsline {subsection}{\numberline {3.2.1}Keystone}{10}{subsection.3.2.1}
+\contentsline {subsection}{\numberline {3.2.2}Nova}{11}{subsection.3.2.2}
+\contentsline {subparagraph}{API}{12}{section*.12}
+\contentsline {subparagraph}{Scheduler}{12}{section*.13}
+\contentsline {subparagraph}{Compute}{12}{section*.14}
+\contentsline {subparagraph}{Conductor}{13}{section*.15}
+\contentsline {subparagraph}{Placement}{13}{section*.16}
+\contentsline {subsection}{\numberline {3.2.3}Neutron}{13}{subsection.3.2.3}
+\contentsline {subparagraph}{Neutron-server}{14}{section*.19}
+\contentsline {subparagraph}{Plugins y agentes}{14}{section*.20}
+\contentsline {subparagraph}{Cola de mensajes}{14}{section*.21}
+\contentsline {subsection}{\numberline {3.2.4}Glance}{15}{subsection.3.2.4}
+\contentsline {subparagraph}{Creaci\IeC {\'o}n de una VM}{16}{section*.23}
+\contentsline {subsection}{\numberline {3.2.5}Cinder}{17}{subsection.3.2.5}
+\contentsline {subsection}{\numberline {3.2.6}Swift}{18}{subsection.3.2.6}
+\contentsline {subparagraph}{Principales componentes}{19}{section*.27}
+\contentsline {section}{\numberline {3.3}Tipos de nodos}{20}{section.3.3}
+\contentsline {subparagraph}{Nodo de control}{20}{section*.28}
+\contentsline {subparagraph}{Nodo de red}{20}{section*.29}
+\contentsline {subparagraph}{Nodo de c\IeC {\'o}mputo}{20}{section*.30}
+\contentsline {subparagraph}{Nodo de almacenamiento}{20}{section*.31}
+\contentsline {subparagraph}{Nodo de balanceamiento de carga}{20}{section*.32}
+\contentsline {section}{\numberline {3.4}Servicios de infraestructura}{20}{section.3.4}
+\contentsline {subparagraph}{Galera - MariaDB}{20}{section*.33}
+\contentsline {subparagraph}{Message queue}{20}{section*.34}
+\contentsline {subparagraph}{Memcached}{21}{section*.35}
+\contentsline {section}{\numberline {3.5}M\IeC {\'e}todos de instalaci\IeC {\'o}n}{21}{section.3.5}
+\contentsline {subsection}{\numberline {3.5.1}Ansible}{21}{subsection.3.5.1}
+\contentsline {subparagraph}{Nodo de control}{22}{section*.36}
+\contentsline {subparagraph}{Inventario}{22}{section*.37}
+\contentsline {subparagraph}{M\IeC {\'o}dulos}{22}{section*.38}
+\contentsline {subparagraph}{Tarea}{22}{section*.39}
+\contentsline {subparagraph}{Playbook}{22}{section*.40}
+\contentsline {section}{\numberline {3.6}Arquitectura}{22}{section.3.6}
+\contentsline {subsection}{\numberline {3.6.1}Arquitectura de red}{23}{subsection.3.6.1}
+\contentsline {subparagraph}{Management Network}{23}{section*.42}
+\contentsline {subparagraph}{Overlay Network}{23}{section*.43}
+\contentsline {subparagraph}{Storage Network}{23}{section*.44}
+\contentsline {subsubsection}{Interfaces de red}{23}{section*.45}
+\contentsline {section}{\numberline {3.7}Configuraci\IeC {\'o}n OSA}{27}{section.3.7}
+\contentsline {subsection}{\numberline {3.7.1}Convenciones}{27}{subsection.3.7.1}
+\contentsline {subsection}{\numberline {3.7.2}Inventario}{27}{subsection.3.7.2}
+\contentsline {subsection}{\numberline {3.7.3}openstack\_user\_config.yml}{27}{subsection.3.7.3}
+\contentsline {chapter}{\numberline {4}Instalaci\IeC {\'o}n}{28}{chapter.4}
+\contentsline {section}{\numberline {4.1}Ambiente de trabajo}{28}{section.4.1}
+\contentsline {subsection}{\numberline {4.1.1}Hardware utilizado}{28}{subsection.4.1.1}
+\contentsline {subsection}{\numberline {4.1.2}Conexi\IeC {\'o}n remota hacia el servidor renata}{28}{subsection.4.1.2}
+\contentsline {subsection}{\numberline {4.1.3}Virtualizaci\IeC {\'o}n con KVM}{29}{subsection.4.1.3}
+\contentsline {subsubsection}{Utilizaci\IeC {\'o}n virt-manager}{29}{section*.52}
+\contentsline {subsection}{\numberline {4.1.4}Especificaciones servidor renata}{36}{subsection.4.1.4}
+\contentsline {subsection}{\numberline {4.1.5}Acceso al exterior desde nodos}{37}{subsection.4.1.5}
+\contentsline {section}{\numberline {4.2}Dise\IeC {\~n}o de arquitectura}{38}{section.4.2}
+\contentsline {section}{\numberline {4.3}Preparaci\IeC {\'o}n de nodos}{38}{section.4.3}
+\contentsline {subsubsection}{Deploy}{38}{section*.70}
+\contentsline {subsubsection}{Infra1}{40}{section*.72}
+\contentsline {subsubsection}{Compute1}{42}{section*.73}
+\contentsline {subsubsection}{Storage1}{42}{section*.74}
+\contentsline {subsubsection}{HAproxy1}{43}{section*.75}
+\contentsline {section}{\numberline {4.4}Configuraci\IeC {\'o}n}{44}{section.4.4}
+\contentsline {subsection}{\numberline {4.4.1}Configuraci\IeC {\'o}n claves SSH}{44}{subsection.4.4.1}
+\contentsline {subsection}{\numberline {4.4.2}Archivos de configuraci\IeC {\'o}n OSA}{44}{subsection.4.4.2}
+\contentsline {subsubsection}{openstack\_user\_config.yml}{44}{section*.76}
+\contentsline {subsubsection}{user\_variables.yml}{47}{section*.77}
+\contentsline {subsubsection}{cinder.yml}{48}{section*.78}
+\contentsline {subsection}{\numberline {4.4.3}Generaci\IeC {\'o}n de claves}{48}{subsection.4.4.3}
+\contentsline {subsection}{\numberline {4.4.4}Correcciones}{48}{subsection.4.4.4}
+\contentsline {subsubsection}{SELinux}{48}{section*.79}
+\contentsline {section}{\numberline {4.5}Ejecuci\IeC {\'o}n de playbooks}{49}{section.4.5}
+\contentsline {subsubsection}{setup-hosts.yml}{49}{section*.80}
+\contentsline {subsubsection}{install-haproxy.yml}{49}{section*.81}
+\contentsline {subsubsection}{setup-infrastructure.yml}{49}{section*.82}
+\contentsline {subsubsection}{setup-openstack.yml}{49}{section*.83}
+\contentsline {section}{\numberline {4.6}Verificaci\IeC {\'o}n}{50}{section.4.6}
diff --git a/docs/latex/resources/acceso-renata.jpg b/docs/latex/resources/acceso-renata.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7cc979dc4275cd0e995e9da03d26a6609a8e6598
Binary files /dev/null and b/docs/latex/resources/acceso-renata.jpg differ
diff --git a/docs/latex/resources/fing.jpg b/docs/latex/resources/fing.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f7609a93570cde9e5a188b48646ec81153949ac7
Binary files /dev/null and b/docs/latex/resources/fing.jpg differ
diff --git a/docs/latex/resources/internet-nodos.png b/docs/latex/resources/internet-nodos.png
new file mode 100644
index 0000000000000000000000000000000000000000..b8a49d59bd053ea62ef8f8227ca207ccbf79b1bb
Binary files /dev/null and b/docs/latex/resources/internet-nodos.png differ
diff --git a/docs/latex/resources/redes-renata.png b/docs/latex/resources/redes-renata.png
new file mode 100644
index 0000000000000000000000000000000000000000..2bb043f94fa93415f4b6cc5276cc043e3e0e1739
Binary files /dev/null and b/docs/latex/resources/redes-renata.png differ
diff --git a/docs/latex/resources/virt-conf-red.png b/docs/latex/resources/virt-conf-red.png
new file mode 100644
index 0000000000000000000000000000000000000000..ce0dde81e06eda5704d9e7abff112be62db1316a
Binary files /dev/null and b/docs/latex/resources/virt-conf-red.png differ
diff --git a/docs/latex/resources/virt-nodo-1.png b/docs/latex/resources/virt-nodo-1.png
new file mode 100644
index 0000000000000000000000000000000000000000..0a8e95009564402c4fd6cf3b3ba2e4e40bec0414
Binary files /dev/null and b/docs/latex/resources/virt-nodo-1.png differ
diff --git a/docs/latex/resources/virt-nodo-2.png b/docs/latex/resources/virt-nodo-2.png
new file mode 100644
index 0000000000000000000000000000000000000000..ef304b002a4bfcc7248266829c41cf2d3c56e019
Binary files /dev/null and b/docs/latex/resources/virt-nodo-2.png differ
diff --git a/docs/latex/resources/virt-nodo-3.png b/docs/latex/resources/virt-nodo-3.png
new file mode 100644
index 0000000000000000000000000000000000000000..c02f5a1a0fb49752de415e071316f0df9affa939
Binary files /dev/null and b/docs/latex/resources/virt-nodo-3.png differ
diff --git a/docs/latex/resources/virt-nodo-4a.png b/docs/latex/resources/virt-nodo-4a.png
new file mode 100644
index 0000000000000000000000000000000000000000..bfeba6d8f9aeb2071664d6f2d54f6d0537c7e724
Binary files /dev/null and b/docs/latex/resources/virt-nodo-4a.png differ
diff --git a/docs/latex/resources/virt-nodo-4b.png b/docs/latex/resources/virt-nodo-4b.png
new file mode 100644
index 0000000000000000000000000000000000000000..f0bffbb5a47801b3577373f123c5ee3b322d9704
Binary files /dev/null and b/docs/latex/resources/virt-nodo-4b.png differ
diff --git a/docs/latex/resources/virt-nodo-4c.png b/docs/latex/resources/virt-nodo-4c.png
new file mode 100644
index 0000000000000000000000000000000000000000..111dd23d7b3bf2d649efa7102ddd632574b8ca70
Binary files /dev/null and b/docs/latex/resources/virt-nodo-4c.png differ
diff --git a/docs/latex/resources/virt-nodo-5.png b/docs/latex/resources/virt-nodo-5.png
new file mode 100644
index 0000000000000000000000000000000000000000..d9feee178b76c615fe0732fcce4e7741bafc8e86
Binary files /dev/null and b/docs/latex/resources/virt-nodo-5.png differ
diff --git a/docs/latex/resources/virt-nodo-6.png b/docs/latex/resources/virt-nodo-6.png
new file mode 100644
index 0000000000000000000000000000000000000000..0270e5f1bb8bcccb436572892a0af0f05bd499e8
Binary files /dev/null and b/docs/latex/resources/virt-nodo-6.png differ
diff --git a/docs/latex/resources/virt-nodo-7.png b/docs/latex/resources/virt-nodo-7.png
new file mode 100644
index 0000000000000000000000000000000000000000..116c878456f69ec912868f45cd36b5ffaac07bd6
Binary files /dev/null and b/docs/latex/resources/virt-nodo-7.png differ
diff --git a/docs/latex/resources/virt-nueva-conexion.png b/docs/latex/resources/virt-nueva-conexion.png
new file mode 100644
index 0000000000000000000000000000000000000000..77f8c62027a0e04a19a1a5c04ac93f6de940f02c
Binary files /dev/null and b/docs/latex/resources/virt-nueva-conexion.png differ
diff --git a/docs/latex/resources/virt-red-1.png b/docs/latex/resources/virt-red-1.png
new file mode 100644
index 0000000000000000000000000000000000000000..3c90fb6b8b898f7659a0213fa1d11f3dc6f16cdb
Binary files /dev/null and b/docs/latex/resources/virt-red-1.png differ
diff --git a/docs/latex/resources/virt-red-2.png b/docs/latex/resources/virt-red-2.png
new file mode 100644
index 0000000000000000000000000000000000000000..17fca2e888482575f60d358e3e8ee6ead4ebab9a
Binary files /dev/null and b/docs/latex/resources/virt-red-2.png differ
diff --git a/docs/latex/resources/virt-red-3.png b/docs/latex/resources/virt-red-3.png
new file mode 100644
index 0000000000000000000000000000000000000000..457e5e92c95a5fa810e7e7d9c277480fc140901b
Binary files /dev/null and b/docs/latex/resources/virt-red-3.png differ
diff --git a/docs/latex/resources/virt-red-4.png b/docs/latex/resources/virt-red-4.png
new file mode 100644
index 0000000000000000000000000000000000000000..5d194602aaf4a62401d27f9d9b90447bb2e5c4f9
Binary files /dev/null and b/docs/latex/resources/virt-red-4.png differ