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 In-Depth
- Overview of Operating System Concepts: CPU, Memory, Network, and Storage
- Hypervisors
- The concept of a Supervisor of Supervisors
- Distinguishing between "Host" machines and "Guest" operating systems
- Understanding Type-1 and Type-2 Hypervisors
- Examining platforms such as Citrix XEN, VMware ESX/ESXi, MS Hyper-V, and IBM LPAR.
- Network Virtualization
- A brief introduction to the 7-Layer OSI Model
- Emphasis on the Network Layer
- Exploring the TCP/IP Model and Internet Protocol
- Focusing on Specific Layers
- Application Layer: SSL
- Network Layer: TCP
- Internet Layer: IPv4/IPv6
- Link Layer: Ethernet
- Packet Structure
- Addressing mechanisms: IP Addresses and Domain Names
- Components: Firewalls, Load Balancers, Routers, and Adapters
- Concepts in Virtualized Networks
- Higher-level abstractions: Subnets and Zones.
- Practical Exercise:
- Get familiar with the ESXi cluster and the vSphere client.
- Create or update networks within an ESXi Cluster, deploy guest instances from VMDK packages, and establish connectivity between guests in the cluster.
- Make changes to a running VM instance and take a snapshot.
- Modify firewall rules in ESXi via the vSphere client.
2. Cloud Computing: A Paradigm Shift
- A rapid and cost-effective way to make products or solutions globally accessible
- Resource Sharing
- Virtualization within virtualized environments
- Primary Advantages:
- On-demand Resource Elasticity
- From idea to code to deployment without the need for dedicated infrastructure
- Accelerated CI/CD pipelines
- Environment isolation and vertical autonomy
- Enhanced security through layering
- Optimization of expenses
- On-demand Resource Elasticity
- On-premise Clouds versus Public Cloud Providers
- Cloud as a conceptual abstraction for distributed computing
3. Introduction to Cloud Service Layers:
- IaaS (Infrastructure as a Service)
- Providers including AWS, Azure, and Google
- Select a single provider to continue with; AWS is recommended.
- Introduction to AWS VPC, AWS EC2, and related services.
- PaaS (Platform as a Service)
- Platforms such as AWS, Azure, Google, CloudFoundry, and Heroku
- Overview of services like AWS DynamoDB and AWS Kinesis.
- SaaS (Software as a Service)
- A brief overview
- Examples include Microsoft Office, Confluence, SalesForce, and Slack
- Understanding the hierarchy: SaaS builds on PaaS, which builds on IaaS, which is built on Virtualization
4. IaaS Cloud Hands-On Project
- This project utilizes AWS as the IaaS Cloud Provider
- CentOS/RHEL will be used as the operating system for the exercise
- Ubuntu is also acceptable, though RHEL/CentOS are preferred
- Obtain individual AWS IAM accounts from your cloud administrator
- Each student must complete these steps independently
- The ability to provision entire infrastructure on-demand best demonstrates the power of cloud computing
- Utilize AWS Wizards and online consoles to complete tasks unless stated otherwise
- Create a public VPC in the us-east-1 Region
- Set up two Subnets (Subnet-1 and Subnet-2) in different Availability Zones
- Refer to https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenarios.html for guidance.
- Create three distinct Security Groups
- SG-Internet
- Permit inbound traffic from the Internet on HTTPS (443) and HTTP (80)
- Block all other inbound connections
- SG-Service
- Allow inbound traffic only from the SG-Internet security group on HTTPS (443) and HTTP (80)
- Allow ICMP traffic only from SG-Internet
- Block all other inbound connections
- SG-SSH:
- Allow SSH (port 22) inbound connections only from the specific public IP address of the student’s lab machine, or the proxy’s public IP if behind a proxy.
- SG-Internet
- Set up two Subnets (Subnet-1 and Subnet-2) in different Availability Zones
- Deploy an AMI instance using the selected OS (preferably the latest RHEL/CentOS version available) and place it in Subnet-1. Attach it to the SG-Service and SG-SSH groups.
- Connect to the instance via SSH from your lab machine.
- Install the NGINX server on this instance
- Place static content of your choice (such as HTML pages or images) to be served by NGINX on port 80 over HTTP, and define the corresponding URLs.
- Test the URL from the local machine.
- Create a new AMI image from this running instance.
- Deploy the new AMI and place the instance in Subnet-2. Attach it to the SG-Service and SG-SSH groups.
- Start the NGINX server and verify that the static content URLs created in the previous step are accessible.
- Create a new “classic” Elastic Load Balancer and attach it to the SG-Internet security group.
- Understand the differences between Application Load Balancers and Network Load Balancers.
- Establish a routing rule to forward all HTTP (80) and HTTPS (443) traffic to the instance group containing the two instances created above.
- Use a certificate management tool (such as Java keytool) to generate a key pair and self-signed certificate, then import the certificate into 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 analyze how they vary over time
- https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/viewing_metrics_with_cloudwatch.html
- Retrieve relevant metrics and analyze how they vary over time
- Access the AWS CloudWatch dashboard for the ELB
- Observe ELB metrics and explain their variability over time
- 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: Moving from on-premise to public cloud
- Migrating application code
- Migrating databases
- DevOps
- Infrastructure as Code
- AWS CloudFormation Templates
- Auto-scaling
- Using AWS CloudWatch metrics to determine system health
Requirements
This course has no specific prerequisites for attendance.
Intended Audience
Software engineers or computer scientists who possess a solid understanding of algorithms and experience with at least one programming or scripting language, but have no prior background in cloud computing.
21 Hours
Testimonials (1)
The trainer explains you very well.
