Get in Touch

Course Outline

1. Virtualization Fundamentals

  1. Overview of Operating System Concepts: CPU, Memory, Network, and Storage
  2. Hypervisors
    1. The supervisor of virtual environments
    2. Understanding "Host" machines and "guest" operating systems
    3. Distinguishing between Type-1 and Type-2 Hypervisors
    4. Key platforms: Citrix XEN, VMware ESX/ESXi, Microsoft Hyper-V, and IBM LPAR
  3. Network Virtualization
    1. Brief introduction to the 7-Layer OSI Model
    2. Focusing on the Network Layer
    3. Understanding the TCP/IP Model or Internet Protocol
  4. Detailed Focus on Protocol Layers
    1. Application Layer: SSL
    2. Transport Layer: TCP
    3. Internet Layer: IPv4/IPv6
    4. Link Layer: Ethernet
  5. Packet Structure and Networking Components
    1. Addressing: IP Addresses and Domain Names
    2. Key Network Devices: Firewalls, Load Balancers, Routers, and Adapters
    3. Virtualized Networks
    4. Higher-Level Abstractions: Subnets and Availability Zones
  6. Practical Exercise:
    1. Familiarize yourself with the ESXi cluster and the vSphere client.
    2. Create and update networks within the ESXi Cluster, deploy guest VMs from VMDK packages, and enable inter-VM connectivity within the cluster.
    3. Modify a running VM instance and capture a snapshot.
    4. Update firewall rules in ESXi using the vSphere client.

2. Cloud Computing: A Paradigm Shift

  1. A rapid and cost-effective pathway to bring products and solutions to the global market.
  2. Resource Sharing
    1. Virtualization of already virtualized environments
  3. Key Benefits:
    1. On-Demand Resource Elasticity
      1. Facilitates ideation, coding, and deployment without heavy infrastructure commitments
      2. Enables rapid CI/CD pipelines
    2. Environment isolation and vertical autonomy
    3. Enhanced security through layered architecture
    4. Cost optimization
  4. On-premise Cloud solutions versus Public Cloud Providers
  5. Cloud computing as an effective conceptual abstraction for distributed computing

3. Introduction to Cloud Solution Layers:

  1. IaaS (Infrastructure as a Service)
    1. Major providers: AWS, Azure, Google Cloud
    2. Select one provider for continued study. AWS is recommended.
      1. Introduction to AWS VPC, AWS EC2, etc.
  2. PaaS (Platform as a Service)
    1. Platforms include: AWS, Azure, Google Cloud, CloudFoundry, Heroku
    2. Introduction to AWS DynamoDB, AWS Kinesis, etc.
  3. SaaS (Software as a Service)
    1. Brief overview
    2. Examples: Microsoft Office, Confluence, Salesforce, Slack
  4. SaaS builds upon PaaS, which in turn builds upon IaaS, all of which rely on Virtualization.

4. IaaS Cloud Hands-on Project

  1. This project utilizes AWS as the IaaS Cloud Provider.
  2. Use CentOS/RHEL as the operating system for the remainder of the exercise.
    1. Ubuntu is also acceptable, but RHEL/CentOS are preferred.
  3. Obtain individual AWS IAM accounts from your cloud administrator.
  4. Each participant must complete these steps independently.
    1. The ability to carve out your own entire infrastructure on-demand best demonstrates the power of cloud computing.
    2. Use AWS Wizards and the AWS online consoles to accomplish these tasks unless otherwise specified.
  5. Create a public VPC in the us-east-1 Region.
    1. Configure two Subnets (Subnet-1 and Subnet-2) across two different Availability Zones.
      1. Refer to https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenarios.html for guidance.
    2. Create three separate Security Groups.
      1. SG-Internet
        1. Allows incoming traffic from the Internet on ports https 443 and http 80
        2. Blocks all other incoming connections
      2. SG-Service
        1. Allows incoming traffic only from security group SG-Internet on ports https 443 and http 80
        2. Allows ICMP traffic only from SG-Internet
        3. Blocks all other incoming connections
      3. SG-SSH:
        1. Allows SSH:22 incoming connections only from a single IP address 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.
  6. Deploy an instance of an AMI corresponding 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.
  7. Access the instance using SSH from your lab machine.
  8. Install the NGINX server on this instance.
  9. Upload static content of your choice (HTML pages, images) to be served by NGINX (on port 80 over HTTP) and define URLs for them.
  10. Test the URL from within the instance itself.
  11. Create an AMI image from this running instance.
  12. Deploy a new instance using that AMI and host it on Subnet-2. Attach the instance to SG-Service and SG-SSH groups.
  13. Run the NGINX server on the new instance and validate that the access URL for the static content (as created in step (i)) works correctly.
  14. Create a new “classic” Elastic Load Balancer (ELB) and attach it to SG-Internet.
    1. Note the differences between Classic, Application, and Network Load Balancers.
  15. Create a routing rule to forward all http 80 and https 443 traffic to an instance group comprising the two instances created above.
  16. 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

  1. AWS CloudWatch metrics
  2. Access the AWS CloudWatch dashboard for the EC2 instances.
    1. Retrieve the relevant metrics and explain their variability over time.
      1. Reference: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/viewing_metrics_with_cloudwatch.html
  3. Access the AWS CloudWatch dashboard for the ELB.
    1. Observe the ELB metrics and explain their variability over time.
    2. Reference: https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-cloudwatch-metrics.html

6. Advanced Concepts for Further Learning

  1. Hybrid Cloud -- combining on-premise and public cloud resources.
  2. Migration Strategies: Moving from On-premise to Public Cloud
    1. Application code migration
    2. Database migration
  3. DevOps Practices
    1. Infrastructure as Code (IaC)
    2. AWS CloudFormation Templates
  4. Auto-scaling
    1. Using AWS CloudWatch metrics to determine system health

Requirements

There are no specific prerequisites required to enroll in this course.

 21 Hours

Testimonials (1)

Upcoming Courses

Related Categories