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 Details
- Overview of Operating System Concepts: CPU, Memory, Network, Storage
- Hypervisor
- Supervisor of Supervisors
- Concept of the "Host" machine and "guest" operating systems
- Distinction between Type-1 and Type-2 Hypervisors
- Examples including Citrix XEN, VMware ESX/ESXi, MS Hyper-V, and IBM LPAR.
- Network Virtualization
- Brief introduction to the 7-Layer OSI Model
- Emphasis on the Network layer
- The TCP/IP Model or Internet Protocol
- Deep Dive into a Single Vertical
- Application Layer: SSL
- Network Layer: TCP
- Internet Layer: IPv4/IPv6
- Link Layer: Ethernet
- Packet Structure
- Addressing mechanisms: IP Address and Domain Names
- Components such as Firewall, Load Balancer, Router, and Adapter
- Virtualized Network environments
- Higher-order abstractions including Subnets and Zones.
- Practical Exercise:
- Become familiar with an ESXi cluster and the vSphere client.
- Configure networks within an ESXi Cluster, deploy guest instances from VMDK packages, and establish connectivity between guests.
- 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 and cost-effective method to deploy products or solutions globally
- Resource Sharing
- Virtualization within a virtualized environment
- Primary Advantages:
- On-demand resource elasticity
- Ability to Ideate, Code, and Deploy without dedicated infrastructure
- Rapid CI/CD pipelines
- Environment isolation and vertical autonomy
- Security achieved through layering
- Cost optimization strategies
- On-demand resource elasticity
- On-premise Cloud infrastructure and Cloud Service Providers
- Cloud as a conceptual abstraction for distributed computing
3. Introduction to Cloud Solution Layers:
- IaaS (Infrastructure as a Service)
- Providers including AWS, Azure, and Google
- Select one provider for subsequent exercises; AWS is recommended.
- Introduction to AWS VPC, AWS EC2, and related services.
- PaaS (Platform as a Service)
- Providers such as AWS, Azure, Google, CloudFoundry, and Heroku
- Introduction to services like AWS DynamoDB and AWS Kinesis.
- SaaS (Software as a Service)
- Concise overview of the category
- Examples include Microsoft Office, Confluence, SalesForce, and Slack
- The hierarchical relationship where SaaS builds on PaaS, which builds on IaaS, which in turn 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 this exercise
- Alternatively, Ubuntu is acceptable, but RHEL/CentOS are preferred
- Obtain individual AWS IAM accounts from your cloud administrator
- Each participant must complete these steps independently
- Provisioning an entire infrastructure on-demand is the clearest demonstration of cloud computing power
- Use AWS Wizards and online consoles to complete these tasks unless otherwise specified
- Create a public VPC in the us-east-1 Region
- Establish 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 distinct Security Groups
- SG-Internet
- Permits incoming traffic from the Internet on https (443) and http (80)
- Blocks all other incoming connections
- SG-Service
- Permits incoming traffic only from security group SG-Internet on https (443) and http (80)
- Allows ICMP only from SG-Internet
- Blocks all other incoming connections
- SG-SSH:
- Allows SSH:22 incoming connections only from a single IP matching the public IP of the participant's lab machine, or the proxy public IP if applicable.
- SG-Internet
- Establish two Subnets (Subnet-1 and Subnet-2) across two different Availability Zones
- Deploy an instance from an AMI for the selected OS—preferably the latest RHEL/CentOS versions available—and host it on Subnet-1. Attach the instance to the SG-Service and SG-SSH groups.
- Access the instance via SSH from the lab machine.
- Install the NGINX server on this instance
- Place static content, 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 an AMI image from this running instance.
- Deploy this new AMI and host the instance on Subnet-2. Attach the instance to the SG-Service and SG-SSH groups.
- Start the NGINX server and verify that the access URL for the static content created in the previous step functions correctly.
- Create a new "classic" Elastic Load Balancer and attach it to SG-Internet.
- Understand the differences between the Application Load Balancer and Network Load Balancer.
- Configure routing rules to forward all http 80 and https 443 traffic to an instance group containing the two instances created above.
- Use a certificate management tool, such as Java keytool, to create a key-pair and self-signed certificate, then import the certificate into AWS Certificate Manager (ACM)
5. Cloud Monitoring: Introduction and Hands-on Project
- Understanding AWS CloudWatch metrics
- Navigate to the AWS CloudWatch dashboard for the instances
- Retrieve relevant metrics and analyze their variability over time
- https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/viewing_metrics_with_cloudwatch.html
- Retrieve relevant metrics and analyze their variability over time
- Navigate to the AWS CloudWatch dashboard for the ELB
- Examine the ELB metrics and interpret their fluctuations over time
- https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-cloudwatch-metrics.html
6. Advanced Concepts for Further Learning
- Hybrid Cloud architectures combining on-premise and public cloud resources
- Migration strategies from on-premise to public cloud
- Migrating application code
- Migrating databases
- DevOps practices
- Infrastructure as code
- AWS CloudFormation Templates
- Auto-scaling mechanisms
- Utilizing AWS CloudWatch metrics to assess health
Requirements
No specific prerequisites are required to participate in this course.
Audience
This course is designed for Software Engineers and Computer Scientists who possess a solid grasp of algorithms and familiarity with at least one programming or scripting language, but who have not yet worked with Cloud Computing technologies.
21 Hours
Testimonials (1)
The trainer explains you very well.
