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
-
Understanding Hypervisors
- The supervisor managing other supervisors
- The 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, and IBM LPAR
-
Network Virtualization
- A brief introduction to the 7-Layer OSI Model
- Focusing on the Network layer
- The TCP/IP Model or Internet Protocol
-
Deep Dive into Specific Layers
- Application Layer: SSL
- Network Layer: TCP
- Internet Layer: IPv4/IPv6
- Link Layer: Ethernet
-
Packet Structure and Components
- Addressing mechanisms: IP Address and Domain Names
- Key components: Firewalls, Load Balancers, Routers, and Adapters
- Virtualized Network concepts
- Higher-order abstractions: Subnets and Zones
-
Hands-on Exercise:
- Familiarize yourself with the ESXi cluster and the vSphere client.
- Create and update networks within the ESXi Cluster, deploy guests from VMDK packages, and enable inter-connectivity between guests in the cluster.
- Modify a running VM instance and capture a snapshot.
- Update firewall rules in ESXi using the vSphere client.
2. Cloud Computing: A Paradigm Shift
- A rapid, cost-effective pathway to bring products or solutions to the global market
-
Resource Sharing
- Virtualization within a virtualized environment
-
Key Benefits:
-
On-demand Resource Elasticity
- 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 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
-
Select one Provider to continue with 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)
- Very brief overview
- Examples: Microsoft Office, Confluence, SalesForce, Slack
- SaaS builds upon PaaS, which builds upon IaaS, which in turn builds upon 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 infrastructure on-demand effectively 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 port 443 and http port 80
- No other incoming connections are allowed
-
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
- No other incoming connections are allowed
-
SG-SSH:
- Allows SSH port 22 incoming connections only from a single IP matching 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 using an AMI related 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 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 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.
-
Create a new "classic" Elastic Load Balancer and attach it to SG-Internet.
- Note the differences between Application Load Balancer and Network Load Balancer.
- 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 a 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
- Overview of AWS CloudWatch metrics
-
Access 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
-
Access 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 -- on-premise and public cloud integration
-
Migration: From on-premise to public cloud
- Application code migration
- Database migration
-
DevOps
- Infrastructure as Code
- AWS CloudFormation Templates
-
Auto-scaling
- Using AWS CloudWatch metrics to determine health
Requirements
There are no specific prerequisites required to attend this course.
21 Hours
Testimonials (1)
The trainer explains you very well.
