summaryrefslogtreecommitdiff
path: root/unit4/unit4.typ
diff options
context:
space:
mode:
Diffstat (limited to 'unit4/unit4.typ')
-rw-r--r--unit4/unit4.typ44
1 files changed, 43 insertions, 1 deletions
diff --git a/unit4/unit4.typ b/unit4/unit4.typ
index 7072193..77a1331 100644
--- a/unit4/unit4.typ
+++ b/unit4/unit4.typ
@@ -42,7 +42,7 @@ This layer also specifies the entities that operate in this layer:
2. Resource Pools
3. Virtual resources
= Process and Operations
-The key steps involved in making resources available to comsumers are:
+The key steps involved in making resources available to consumers are:
1. Deploying virtualization software.
- Compute systems.
- Network devices.
@@ -163,3 +163,45 @@ _An identity pool, unlike a resource pool, specifies a range of network identifi
- If it runs out of IDs, then administrators may create an additional pool or add more identities to the existing pool.
- 1-to-1 mapping between identity pool and service simplifies the tracking and use of IDs by a particular service.
- Increases management complexity as multiple identity pools must be created and managed.
+= Virtual Resources
+== Virtual Machine
+_A logical compute system that, like a physical compute system, runs an OS and applications._\
+- Created by hosted or bare-metal hypervisor installed on physical compute.
+- Has self-contained OS, applications, virtual hardware.
+- 'Guest' OS is installed on a VM the same way it is installed on physical compute.
+- From 'guest' perspective, VM appears to be a physical compute.
+- Virtual Machine Monitor (VMM) is responsible for execution of VM.
+- Each VM has dedicated VMM and configuration for hardware, software, network, etc.
+- Does not have direct access to host OS or hardware.
+- Hypervisor translates virtual VM requests and maps virtual hardware to physical hardware.
+- Compute virtualization software enables creating and managing several VMs on a physical compute or compute cluster.
+- Providers provision VMs to consumers to deploy applications.
+- VM hardware and software are configured to meet requirements.
+- Consumer VMs are isolated from each other so there is no interference.
+- Isolation also provides fault tolerance.
+== VM Hardware
+_When a VM is created, it is presented with virtual hardware components that appear as physical hardware components to the guest OS._\
+- Within vendor's environment, each VM has standardized hardware components, so they are portable.
+- Based on requirements, virtual components can be added or removed.
+- However some components are part of the virtual motherboard and cannot be removed.
+- Can be configured with one more virtual processors. This number can later be changed.
+- When a VM starts, it's virtual processors are scheduled by the hypervisor kernal to run on physical processors.
+- Each VM is assigned a virtual motherboard with standardized devices necessary for compute to function.
+ 1. *Virtual RAM* is the amount of physical memory allocated to the VM.
+ 2. *Virtual Disk* is a large physical file, or a set of files.
+ 3. *Virtual Network Adapter* provides connectivity to VMs running on same or different compute or VM and compute.
+ 4. *Virtual optical or floppy drives* can be configured to connect to physical drives or to image files.
+ 5. *SCSI/IDE virtual controllers* provide a way for VMs to connect to storage devices.
+ 6. *Virtual USB controller* is used to connect to a physical USB controller to access storage and devices.
+== VM Files
+#table(
+ columns: (auto, auto),
+ table.header([ File ], [ Description ]),
+ [ Configuration File ], [ Stores information such as VM name, BIOS information, guest OS type, memory size. ],
+ [ Virtual Disk File ], [ Stores contents of VM's disk drive. ],
+ [ Memory State File ], [ Stores the memory contents of a VM in a suspended state. ],
+ [ Snapshot File ], [ Stores the VM settings and virtual disk of a VM. ],
+ [ Log File ], [ Keeps log of the VM's activity and is used for troubleshooting. ]
+)
+== File system to manage VM Files
+// Start with slide 25