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
1. Virtualization Fundamentals
- Overview of Operating System Concepts: CPU, Memory, Network, and Storage
-
Hypervisors
- The "Supervisor of Supervisors"
- Understanding the "Host" machine and the "guest" OS
- Distinguishing between Type-1 and Type-2 Hypervisors
- Key platforms: Citrix XEN, VMware ESX/ESXi, Microsoft Hyper-V, and IBM LPAR
-
Network Virtualization
- Brief introduction to the 7-Layer OSI Model
- Focus on the Network Layer
- The TCP/IP Model or Internet Protocol
-
Deep Dive into Key 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
- Essential components: Firewall, Load Balancer, Router, and Network Adapter
- Concepts of Virtualized Networks
- Higher-order abstractions: Subnets and Availability Zones
-
Hands-on Exercise:
- Familiarization with the ESXi cluster and the vSphere client.
- Creating and updating networks within an ESXi Cluster, deploying guests from VMDK packages, and enabling inter-connectivity between guests in the ESXi cluster.
- Modifying a running VM instance and capturing snapshots.
- Updating firewall rules in ESXi using the vSphere client.
2. Cloud Computing: A Paradigm Shift
- A rapid and cost-effective pathway to make products or solutions available globally.
-
Resource Sharing
- Virtualization of already virtualized environments
-
Key Benefits:
-
On-demand resource elasticity
- Seamlessly move from Ideation to Code to Deployment without managing infrastructure
- Rapid CI/CD pipelines
- Environment isolation and vertical autonomy
- Enhanced security through layered architecture
- Expense optimization
-
On-demand resource elasticity
- On-premise Cloud solutions versus Cloud Providers
- Cloud computing as an effective conceptual abstraction for distributed computing
3. Introduction to Cloud Solution Layers
-
IaaS (Infrastructure as a Service)
- Major providers: AWS, Azure, Google Cloud
-
Selection of one Provider for continued study. AWS is recommended.
- Introduction to AWS VPC, AWS EC2, etc.
-
PaaS (Platform as a Service)
- Providers: AWS, Azure, Google, CloudFoundry, Heroku
- Introduction to AWS DynamoDB, AWS Kinesis, etc.
-
SaaS (Software as a Service)
- Very brief overview
- Examples: Microsoft Office, Confluence, Salesforce, Slack
- The dependency chain: SaaS builds on PaaS, which builds on IaaS, which ultimately 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.
- While Ubuntu is acceptable, 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 demonstrates the true power of cloud computing.
- Utilize AWS Wizards and the AWS online consoles to accomplish these tasks unless specified otherwise.
-
Create a public VPC in the us-east-1 Region.
-
Set up two Subnets (Subnet-1 and Subnet-2) in 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 (443) and HTTP (80).
- No other incoming connections are allowed.
-
SG-Service
- Allows incoming traffic only from the SG-Internet security group on HTTPS (443) and HTTP (80).
- Allows ICMP traffic only from SG-Internet.
- No other incoming connections are allowed.
-
SG-SSH:
- Allows SSH port 22 incoming connections only from the 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
-
Set up two Subnets (Subnet-1 and Subnet-2) in two different Availability Zones.
- Deploy an instance of an AMI corresponding to your chosen OS (preferably the latest RHEL/CentOS versions available in AMIs) and host the instance on Subnet-1. Attach the instance to the SG-Service and SG-SSH security groups.
- Access the instance using SSH from your lab machine.
- Install the NGINX server on this instance.
- Upload static content of your choice (HTML pages, images) to be served by NGINX on port 80 over HTTP, and define URLs for them.
- Test the URL directly from that machine.
- Create an AMI image from this running instance.
- Deploy the new AMI and host the instance on Subnet-2. Attach the instance to the SG-Service and SG-SSH security 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 Load Balancer, Application Load Balancer, and Network Load Balancer.
- Create a routing rule to forward all HTTP (80) and HTTPS (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 a self-signed certificate, then import the certificate to AWS Certificate Manager (ACM).
5. Cloud Monitoring: Introduction and Hands-on Project
- AWS CloudWatch metrics.
-
Navigate to the AWS CloudWatch dashboard for the instances.
-
Retrieve relevant metrics and explain their variability over time.
- Reference: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/viewing_metrics_with_cloudwatch.html
-
Retrieve relevant metrics and explain their variability over time.
-
Navigate to the AWS CloudWatch dashboard for the ELB.
- Observe ELB metrics and explain their variability over time.
- Reference: https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-cloudwatch-metrics.html
6. Advanced Concepts for Further Learning
- Hybrid Cloud -- combining on-premise and public cloud.
-
Migration: From on-premise to public cloud.
- Application code migration.
- Database migration.
-
DevOps.
- Infrastructure as Code.
- AWS CloudFormation Templates.
-
Auto-scaling.
- Utilizing 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.
