Cloud computing essentials for managers / software engineers Training Course

Virtualization in Depth

1. Overview of Operating System Concepts: CPU, Memory, Network, and Storage
2. Hypervisors
   1. The Manager of Managers
   2. The “host” system and “guest” operating systems
   3. Type-1 vs. Type-2 hypervisors
   4. Citrix XEN, VMware ESX/ESXi, Microsoft Hyper-V, IBM LPAR
3. Network Virtualization
   1. Brief Introduction to the OSI 7-Layer Model
   2. Emphasis on the Network Layer
   3. The TCP/IP Model, also known as the Internet Protocol
4. Focusing on a Single Vertical Domain
   1. Application Layer: SSL
   2. Network Layer: TCP
   3. Internet Layer: IPv4/IPv6
   4. Link Layer: Ethernet
5. Packet Structure
   1. Addressing: IP Addresses and Domain Names
   2. Firewalls, Load Balancers, Routers, and Adapters
   3. Virtual Networks
   4. Higher-Level Abstractions: Subnets and Zones
6. Hands-On Activity:
   1. Become familiar with ESXi clusters and the vSphere client.
   2. Create and update networks within an ESXi cluster, deploy guests from VMDK packages, and enable connectivity between guests in the cluster.
   3. Modify a running VM instance and capture a snapshot.
   4. Use the vSphere client to update firewall rules on the ESXi host.

2. Cloud Computing: A Paradigm Shift

1. A fast and cost-effective way to make products or solutions available globally
2. Resource Sharing
   1. Virtualizing virtualized environments
3. Key Advantages:
   1. On-demand resource elasticity
      1. Envision, > Code, and > Deploy without needing underlying infrastructure
      2. Swift CI/CD pipelines
   2. Environment isolation and vertical independence
   3. Security achieved through layering
   4. Cost optimization
4. On-premise clouds and cloud service providers
5. Cloud as a powerful conceptual abstraction for distributed computing

3. Introduction to Layers of Cloud Solutions:

1. IaaS (Infrastructure as a Service)
   1. AWS, Azure, and Google Cloud
   2. Select one provider to use for future exercises. AWS is recommended.
      1. Introduction to AWS VPC, AWS EC2, and similar services
2. PaaS (Platform as a Service)
   1. AWS, Azure, Google Cloud, CloudFoundry, and Heroku
   2. Introduction to AWS DynamoDB, AWS Kinesis, and other services
3. SaaS (Software as a Service)
   1. Brief Overview
   2. Microsoft Office, Confluence, Salesforce, and Slack
4. How SaaS sits on top of PaaS, which in turn is built on IaaS, which relies on virtualization

4. IaaS Cloud Hands-On Project

1. This project utilizes AWS as the IaaS cloud provider
2. Use CentOS or RHEL as the operating system for the remainder of the exercise
   1. Ubuntu is also acceptable, though RHEL and CentOS are preferred
3. Obtain individual AWS IAM accounts from your cloud administrator
4. Each learner must complete these steps independently
   1. The ability to build your entire infrastructure on demand is the clearest demonstration of cloud computing’s power
   2. Unless otherwise specified, use AWS wizards—the AWS online consoles—to complete these tasks
5. Create a public VPC in the us-east-1 region
   1. Two subnets (Subnet-1 and Subnet-2) located in two different Availability Zones
      1. Refer to https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenarios.html for guidance.
   2. Create three distinct Security Groups
      1. SG-Internet
         1. Allows incoming HTTPS (443) and HTTP (80) traffic from the internet
         2. No other inbound connections are permitted
      2. SG-Service
         1. Only allows HTTPS (443) and HTTP (80) traffic from the SG-Internet security group
         2. Only allows ICMP from SG-Internet
         3. No other inbound connections are permitted
      3. SG-SSH:
         1. Allows SSH (22) inbound connections only from the single IP address that matches your lab machine’s public IP. If your lab machine is behind a proxy, use the proxy’s public IP.
6. Launch an instance from an AMI for your selected OS—ideally the latest available RHEL or CentOS version—and place the instance in Subnet-1. Attach it to the SG-Service and SG-SSH groups.
7. Connect to the instance using SSH from your lab machine.
8. Install the NGINX server on this instance
9. Place static content of your choice—HTML pages, images—to be served by NGINX (over HTTP on port 80) and define URLs for them.
10. Test the URL from that same machine.
11. Create an AMI image from this running instance.
12. Deploy that new AMI and place the instance in Subnet-2. Attach it to the SG-Service and SG-SSH groups.
13. Start the NGINX server and confirm that the access URL for the static content created in step (i) works.
14. Create a new “classic” Elastic Load Balancer and attach it to SG-Internet.
    1. Note the differences between an Application Load Balancer and a Network Load Balancer.
15. Create a routing rule that forwards all HTTP (80) and HTTPS (443) traffic to the instance group consisting of the two instances created above.
16. Using any certificate management tool—such as Java keytool—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

1. AWS CloudWatch metrics
2. Access the AWS CloudWatch dashboard for your instances
   1. Retrieve the relevant metrics and discuss how they vary over time
      1. 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 how they change over time
   2. https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-cloudwatch-metrics.html

6. Advanced Concepts for Continued Study

1. Hybrid Cloud—combining on-premise and public cloud environments
2. Migration: From on-premise to public cloud
   1. Migrating application code
   2. Migrating databases
3. DevOps
   1. Infrastructure as Code
   2. AWS CloudFormation templates
4. Auto-scaling
   1. Using AWS CloudWatch metrics to assess health