Thank you for sending your enquiry! One of our team members will contact you shortly.
Thank you for sending your booking! One of our team members will contact you shortly.
Course Outline
Understanding Virtualization
- Operating System Fundamentals: Overview of CPU, Memory, Network, and Storage components
-
The Hypervisor
- The 'Supervisor of Supervisors'
- Distinction between the 'Host' machine and the 'Guest' OS
- Type-1 and Type-2 Hypervisors
- Examples: Citrix XEN, VMware ESX/ESXi, MS Hyper-V, IBM LPAR
-
Network Virtualization
- Brief introduction to the 7-Layer OSI Model
- Deep dive into the Network layer
- TCP/IP Model and Internet Protocol fundamentals
-
Focusing on Specific Layers
- Application Layer: SSL
- Transport Layer: TCP
- Internet Layer: IPv4/IPv6
- Link Layer: Ethernet
-
Packet Structure and Networking Components
- Addressing mechanisms: IP Addresses and Domain Names
- Key devices: Firewall, Load Balancer, Router, Network Adapter
- Concept of Virtualized Networks
- Higher-order abstractions: Subnets and Availability Zones
-
Hands-on Exercise:
- Familiarization with ESXi clusters and the vSphere client interface.
- Creating and updating networks within an ESXi cluster, deploying guests from VMDK packages, and enabling inter-connectivity between guests.
- Modifying running VM instances and capturing snapshots.
- Updating firewall rules within ESXi using the vSphere client.
2. Cloud Computing: A Paradigm Shift
- Enabling fast, cost-effective deployment of products and solutions to the global market
-
Resource Sharing
- Virtualization within virtualized environments
-
Key Benefits:
-
On-demand Resource Elasticity
- Ideate - Code - Deploy without the need for physical infrastructure
- Implementation of Rapid CI/CD Pipelines
- Environment Isolation and Vertical Autonomy
- Enhanced Security through Layering
- Expense Optimization
-
On-demand Resource Elasticity
- On-premise Cloud Solutions vs. Public Cloud Providers
- Viewing Cloud Computing as an Effective Abstraction for Distributed Computing
3. Introduction to Cloud Solution Layers:
-
IaaS (Infrastructure as a Service)
- Major Providers: AWS, Azure, Google Cloud
-
Selecting a Provider for Continued Learning (AWS is recommended)
- Introduction to AWS VPC, AWS EC2, etc.
-
PaaS (Platform as a Service)
- Major Providers: AWS, Azure, Google Cloud, CloudFoundry, Heroku
- Introduction to AWS DynamoDB, AWS Kinesis, etc.
-
SaaS (Software as a Service)
- Brief Overview
- Examples: Microsoft Office, Confluence, SalesForce, Slack
- The Stack: SaaS builds on PaaS, which builds on IaaS, which builds on Virtualization
4. IaaS Cloud Hands-on Project
- This project utilizes AWS as the IaaS Cloud Provider
-
Use CentOS/RHEL as the operating system for the remainder of the exercise
- Ubuntu is also acceptable, but RHEL/CentOS are preferred
- Obtain individual AWS IAM accounts from your cloud administrator
-
Each student must complete these steps independently
- The ability to carve out your own entire infrastructure on-demand best demonstrates the power of cloud computing
- Use AWS Wizards -- AWS online consoles -- to accomplish these tasks unless otherwise specified
-
Create a public VPC in the us-east-1 Region
-
Create two Subnets (Subnet-1 and Subnet-2) across two different Availability Zones
- Refer to https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenarios.html for guidance.
-
Create three separate Security Groups
-
SG-Internet
- Allows incoming traffic from the Internet on https (port 443) and http (port 80)
- Blocks all other incoming connections
-
SG-Service
- Allows incoming traffic only from security group SG-Internet on https (port 443) and http (port 80)
- Allows ICMP traffic only from SG-Internet
- Blocks all other incoming connections
-
SG-SSH:
- Allows SSH (port 22) incoming connections only from a single IP address matching the public IP of the student’s lab machine (or the public IP of the proxy if the lab machine is behind one).
-
SG-Internet
-
Create two Subnets (Subnet-1 and Subnet-2) across two different Availability Zones
- Deploy an instance of an AMI pertaining to your chosen OS (preferably the latest RHEL/CentOS versions available in AMIs) and host the instance on Subnet-1. Attach the instance to SG-Service and SG-SSH groups.
- Access the instance using SSH from your lab machine.
- Install the NGINX server on this instance.
- Place static contents of your choice (e.g., HTML pages, images) to be served by NGINX (on port 80 via HTTP) and define URLs for them.
- Test the URL from that machine itself.
- Create an AMI image from this running instance.
- Deploy that new AMI and host the instance on Subnet-2. Attach the instance to SG-Service and SG-SSH groups.
- Run the NGINX server and validate that the access URL for the static content created in step (i) works correctly.
-
Create a new 'classic' Elastic Load Balancer and attach it to SG-Internet.
- Note the differences between Classic, Application, and Network Load Balancers.
- Create a routing rule forwarding all http (port 80) and https (port 443) traffic to an instance group comprising the two instances created above.
- Using any certificate management tool (e.g., java keytool), create a key-pair and self-signed certificate, then import the certificate to AWS Certificate Manager (ACM).
5. Cloud Monitoring: Introduction and Hands-on Project
- Understanding AWS CloudWatch metrics
-
Navigating the AWS CloudWatch dashboard for the instances
-
Retrieve relevant metrics and explain their variability over time
- Refer to https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/viewing_metrics_with_cloudwatch.html
-
Retrieve relevant metrics and explain their variability over time
-
Navigating the AWS CloudWatch dashboard for the ELB
- Observe the ELB metrics and explain their variability over time
- Refer to https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-cloudwatch-metrics.html
6. Advanced Concepts for Further Learning
- Hybrid Cloud architectures (on-premise and public cloud)
-
Migration Strategies: On-premise to Public Cloud
- Application code migration
- Database migration
-
DevOps Practices
- Infrastructure as Code (IaC)
- AWS CloudFormation Templates
-
Auto-scaling
- Using AWS CloudWatch metrics to determine system health
Requirements
There are no specific prerequisites required to enroll in this course.
21 Hours
Testimonials (1)
The trainer explains you very well.
