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
- “Host” machine and “guest” OS
- Type-1 Hypervisor and Type-2 Hypervisor
- 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
- TCP/IP Model or Internet Protocol
- Focus on a single vertical
- Application Layer: SSL
- Network Layer: TCP
- Internet Layer: IPv4/IPv6
- Link Layer: Ethernet
- Packet structure
- Addressing: IP Address and Domain Names
- Firewall, Load Balancer, Router, Adapter
- Virtualized Network
- Higher-order abstractions: Subnets, Zones.
- Hands-on Exercise:
- Get familiar with the ESXi cluster and vSphere client.
- Create or update networks in the ESXi Cluster, deploy guests from VMDK packages, and enable connectivity between guests within 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 quick and affordable way to make products or solutions available globally
- Resource sharing
- Virtualization of virtualized environments
- Key benefits:
- On-demand resource elasticity
- Enables Ideate -> Code -> Deploy without the need for physical infrastructure
- Rapid CI/CD pipelines
- Environment isolation and vertical autonomy
- Security through layering
- Expense optimization
- On-demand resource elasticity
- On-premise Cloud and Cloud Providers
- Cloud as an effective conceptual abstraction for distributed computing
3. Introduction to Cloud Solution Layers:
- IaaS (Infrastructure as a Service)
- AWS, Azure, Google
- Select one provider to proceed. AWS is recommended.
- Introduction to AWS VPC, AWS EC2, etc.
- PaaS (Platform as a Service)
- AWS, Azure, Google, CloudFoundry, Heroku
- Introduction to AWS DynamoDB, AWS Kinesis, etc.
- SaaS (Software as a Service)
- A very brief overview
- Microsoft Office, Confluence, SalesForce, Slack
- SaaS builds on PaaS, which builds on IaaS, which builds on Virtualization
4. IaaS Cloud Hands-on Project
- The project uses AWS as the IaaS Cloud Provider
- Use CentOS/RHEL as the operating system for the rest of the exercise
- Alternatively, Ubuntu is also acceptable, but RHEL/CentOS are preferred
- Obtain individual AWS IAM accounts from your cloud admin
- Each student must complete these steps independently
- The ability to provision your own complete infrastructure on-demand is the best demonstration of the power of cloud computing
- Use AWS Wizards (AWS online consoles) to accomplish these tasks unless otherwise specified
- Create a public VPC in the us-east-1 Region
- Two Subnets (Subnet-1 and Subnet-2) in two different Availability Zones
- See https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenarios.html for reference.
- Create three separate Security Groups
- SG-Internet
- Allows incoming traffic from the Internet on https 443 and http 80
- No other incoming connections allowed
- SG-Service
- Allows incoming traffic only from security group SG-Internet on https 443 and http 80
- Allows ICMP only from SG-Internet
- No other incoming connections allowed
- SG-SSH:
- Allows SSH:22 incoming connection 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
- Two Subnets (Subnet-1 and Subnet-2) in two different Availability Zones
- Deploy an AMI instance for your chosen OS -- preferably the latest RHEL/CentOS versions available in AMIs -- and host it in 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 (such as html pages or 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 the new AMI and host the instance in Subnet-2. Attach the instance to the SG-Service and SG-SSH groups.
- Run the NGINX server and verify 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 from the Application Load Balancer and Network Load Balancer.
- Create a routing rule that forwards all http 80 and https 443 traffic to the instance group containing the two instances created above.
- Using any certificate management tool (such as java keytool), create a key-pair and a 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 explain their variability over time
- 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 the 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
- Migration: From on-premise to public cloud
- Application code migration
- Database migration
- DevOps
- Infrastructure as Code
- AWS CloudFormation Template
- Auto-scaling
- Using AWS CloudWatch metrics to determine health
Requirements
No specific prerequisites are required to join this course.
Target Audience
Software Engineers and Computer Scientists who possess a solid understanding of algorithms and are proficient in at least one programming or scripting language, but have no prior experience with Cloud Computing.
21 Hours
Testimonials (1)
The trainer explains you very well.
