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
Virtualization Fundamentals
- Overview of Operating System Concepts: CPU, Memory, Network, and Storage
-
Hypervisors
- The role of the hypervisor as a supervisor of resources
- Distinction between the "Host" machine and the "Guest" OS
- Differences between 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
- Focus on the Network layer
- Understanding the TCP/IP Model and Internet Protocol
-
Detailed Look at Protocol Layers
- Application Layer: SSL
- Transport Layer: TCP
- Internet Layer: IPv4/IPv6
- Link Layer: Ethernet
-
Packet Structure and Networking Components
- Addressing mechanisms: IP Address and Domain Names
- Key components: Firewalls, Load Balancers, Routers, and Adapters
- Virtualized Network environments
- Higher-order abstractions: Subnets and Zones
-
Hands-on Exercise:
- Familiarization with ESXi clusters and the vSphere client.
- Creating and updating networks within an ESXi cluster, deploying guests from VMDK packages, and enabling inter-connectivity between guest VMs.
- Modifying a running VM instance and capturing snapshots.
- Updating firewall rules in ESXi using the vSphere client.
2. Cloud Computing: A Paradigm Shift
- A fast, cost-effective pathway to make products and solutions globally available.
-
Resource Sharing
- Virtualization of virtualized environments
-
Key Benefits:
-
On-demand Resource Elasticity
- Streamlined process: Ideate -> Code -> Deploy without needing dedicated infrastructure
- Rapid CI/CD pipelines
- Environment isolation and vertical autonomy
- Enhanced security through layering
- Cost optimization
-
On-demand Resource Elasticity
- On-premise Cloud solutions and Public Cloud Providers
- Understanding Cloud as an effective conceptual abstraction for distributed computing
3. Introduction to Cloud Solution Layers:
-
IaaS (Infrastructure as a Service)
- Major Providers: AWS, Azure, Google
-
Select one provider to focus on later. AWS is recommended.
- Introduction to AWS VPC, AWS EC2, etc.
-
PaaS (Platform as a Service)
- Major Providers: AWS, Azure, Google, CloudFoundry, Heroku
- Introduction to AWS DynamoDB, AWS Kinesis, etc.
-
SaaS (Software as a Service)
- Brief overview
- Examples: Microsoft Office, Confluence, SalesForce, Slack
- The dependency chain: 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 or 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 provision your own entire infrastructure on-demand best demonstrates the power of cloud computing.
- Use AWS Wizards and the 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) 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 security group SG-Internet on https (443) and http (80).
- Allows ICMP traffic only from SG-Internet.
- No other incoming connections are allowed.
-
SG-SSH:
- Allows SSH (22) incoming connections only from a single IP that matches the public IP of the student’s lab machine. If the lab machine is behind a proxy, use the public IP of the proxy.
-
SG-Internet
-
Create two Subnets (Subnet-1 and Subnet-2) in two different Availability Zones.
- Deploy an instance of an AMI matching 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 groups.
- Access the instance via SSH from your lab machine.
- Install the NGINX server on this instance.
- Place 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 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 the SG-Service and SG-SSH groups.
- Run the NGINX server and validate that the access URL for the static content created in the previous step 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 that forwards 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 overview.
-
Go to the AWS CloudWatch dashboard for the instances.
-
Retrieve the relevant metrics and explain their variability over time.
- Reference: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/viewing_metrics_with_cloudwatch.html
-
Retrieve the relevant metrics and explain their variability over time.
-
Go to the AWS CloudWatch dashboard for the ELB.
- Observe the 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 environments.
-
Migration: From On-premise to Public Cloud
- Application code migration
- Database migration
-
DevOps
- Infrastructure as Code (IaC)
- AWS CloudFormation Templates
-
Auto-scaling
- Using AWS CloudWatch metrics to determine system health
Requirements
There are no specific prerequisites for attending this course.
21 Hours
Testimonials (1)
The trainer explains you very well.
