1 files changed, 74 insertions, 1 deletions
diff --git a/unit4/unit4.typ b/unit4/unit4.typ
index 77a1331..113849b 100644
--- a/unit4/unit4.typ
+++ b/unit4/unit4.typ
@@ -204,4 +204,77 @@ _When a VM is created, it is presented with virtual hardware components that app
   [ Log File ], [ Keeps log of the VM's activity and is used for troubleshooting. ]
 )
 == File system to manage VM Files
-// Start with slide 25
+#figure(image("./assets/vmfs.png"))
+- File system is configured on storage to manage VM files.
+- Capacity of the file system can be dynamically changed without disrupting the VM.
+- Hypervisors support two file systems, hypervisor native and shared file system.
+=== Hypervisor Native File System
+- Usually a clustered file system and optimized for storing VM files.
+- Can be deployed on storage provisioned from local storage or external storage.
+- Allows multiple hypervisors running on different compute systems, to read and write to same shared storage concurrently.
+- This enables high availability capabilities, like migration of VMs between hypervisors in the event of failure.
+- Locking mechanism ensures that a VM is not powered on by multiple hypervisors at the same time.
+- When hypervisor fails, locking mechanism for each VM on the physical compute is released.
+- VMs can them be restarted from other hypervisors.
+=== Shared File System
+- Allows for VMs to be stored on remote servers or NAS.
+- Accessed using file sharing protocols, like NFS and CIFS.
+- Hypervisors have builtin NFS/CIFS clients.
+== VM Console
+_VM Console is an interface used to view and manage the VMs on a compute system or cluster._\
+- VM console can be:
+  - Installed locally on compute system.
+  - Web-based
+  - Accessed over a remote desktop connection.
+- Can be used to perform
+  - Installing a guest OS and accessing VM BIOS
+  - Powering a VM on or off
+  - Configuring virtual hardware and troubleshooting.
+== VM Template
+_A VM Template is a master copy of a virtual machine with a standardized virtual hardware and softeare configuration that can be used to create and provision new VMs._\
+- Typically includes:
+  - Guest OS
+  - Set of applications
+  - hardware and software configurations to deploy a VM
+- Can be created in two ways, converting a VM to a template or cloning a VM to a template.
+  1. Converting a VM to a template\
+    Original VM replaced by the template
+  2. Cloning a VM to a template\
+    Original VM is retained
+- Provides preinstalled and preconfigured software.
+- It is faster as it eliminates installation, configuration, and maintenance overheads.
+- Ensures consistency and standardization across VMs, making troubleshooting easier.
+- Can be updated with new software, OS updates, and software patches.
+- After update is complete, VM is converted back into a template.
+== Virtual Appliance
+_A virtual appliance is a preconfigured virtual machine preinstalled with a guest OS and application dedicated to a specific function. In a cloud environment they are used to provide different functions, such as provide SaaS, run cloud management software, route packets, and provide security._\
+- Simplifies the delivery and operation of applications.
+- Faster as VM is preconfigured and has preinstalled software.
+- Simplifies installation and eliminates configuration issues.
+- Application runs in isolation, so is protected against crashes and other applications.
+- Created using Open Virtualization Format, a open, hypervisor-independent packaging and distribution format.
+== VM Network
+#figure(image("./assets/vmnet.png"))
+_A VM network is a logical network that provides Ethernet connectivity and enables communication between VMs running on a hypervisor within a compute system._\
+- Contains logical switches called virtual switches.
+- Virtual switches function similarly to physical Ethernet switches but may not have full functionality.
+- VM traffic travels over both VM network and physical networks.
+== VM Network Components
+#table(
+  columns: (auto, auto),
+  table.header([ Component ], [ Description ]),
+  [ Virtual Switch ], [
+    - Logical OSI Layer 2 Ethernet switch created in a compute system.
+    - Connects VMs locally can also directs VM traffic to a physical network.
+    - Forwards frames to a virtual switch port based on destination address.
+    - A distributed virtual switch can function across multiple physical compute systems.
+  ], [ Virtual NIC ], [
+    - Connects a VM to a virtual switch and functions like a physical NIC.
+    - Has unique MAC and IP addresses.
+    - Forwards the VM's network I/O in the form of Ethernet frames to a virtual switch.
+  ], [ Uplink NIC ], [
+    - A physical NIC connected to the uplink port of a virtual switch.
+    - Functions as an ISL between virtual and physical Ethernet switches.
+    - Not addressable from the network.
+  ]
+)