Table of Contents - OpenStack on VMware Infrastructure In this step, we will review the VMware...
Embed Size (px)
Transcript of Table of Contents - OpenStack on VMware Infrastructure In this step, we will review the VMware...
Table of Contents Lab Overview - HOL-SDC-1320 ......................................................................................... 2
HOL-1320 OpenStack with vSphere + NSX ............................................................. 3 Module 1 - OpenStack Compute & Storage....................................................................... 4
OpenStack Compute and Storage with vSphere ..................................................... 5 Module 2 - OpenStack Network Management with VMware NSX ....................................62
OpenStack Network Management with VMware NSX ............................................63
Lab Overview - HOL- SDC-1320
HOL-1320 OpenStack with vSphere + NSX Please continue to the lab overview.
This hands on lab consists of one module:
• Module #1: Basic overview of OpenStack + vSphere integration, using the vCenter Web Client and the Openstack Horizon Dashboard (60 minutes)
There is a file copy-paste.txt on your windows desktop that includes any strings you need to enter. This can be useful if you are using an international keyboard and the lab requires you to enter text that you cannot easily type.
• Module #2: Basic overview of OpenStack + VMware NSX integration, using the OpenStack Horizon Dashboard (60 minutes)
• Gary Kotton • Sabari Murugesan • Dan Wendlandt • Arvind Soni
Module 1 - OpenStack Compute & Storage
OpenStack Compute and Storage with vSphere In the next step, we will begin with an overview of OpenStack.
What is OpenStack?
OpenStack is open source software enabling the creation of clouds on top of a diverse set of hardware and software infrastructure technologies.
Cloud API Layer in a Cloud Technology Stack
A typical cloud technology stack consists of following major components
1. Hardware Infrastructure 2. Software Infrastructure (or virtualization layer) 3. Cloud API layer that enables consumption and orchestration of underlying cloud
infrastructure 4. Cloud Management Layer that provides governance, monitoring, provisioning,
budgeting etc and potentially manages multiple underlying cloud fabrics 5. Applications running on top of cloud infrastructure
In a non-cloud datacenter model, an application owner would contact one or more datacenter administrators, who would then deploy the application on the application owner's behalf using software infrastructure tools (e.g., VMware vSphere) to deploy the application workloads on top of physical compute, network, and storage hardware.
OpenStack is a software layer that sits on top of the software infrastructure and enables an API based consumption of infrastructure. OpenStack enables "self-service" model in which application owners can directly request and provision the compute, network, and storage resources needed to deploy their application.
The primary benefits of self-service are increased agility from applications owners getting "on demand" access to the resources they need and reduced operating expenses by eliminated manual + repetitive deployment tasks.
Anatomy of a Cloud Technology Stack
OpenStack Cloud API Layer adds following services in the cloud technology stack.
• An API layer presents abstracted compute/network/storage resources, completely decoupled from any datacenter hardware, for user by self-service tools.
• Enables self-service to compute/network/storage resources, there is a Web GUI, CLI tools, and programmatic SDK
• Provides an identity service that provides authentication and basic control over resource consumption by managing quotas on infrastructure resources.
• The core logic of OpenStack takes requests from the API layer, determines if the request is permitted, and routes the request to the proper portion of the software infrastructure.
• Based on the type of software infrastructure in use, OpenStack uses a "driver" layer to translate abstract resource requests into a call to a particular underlying technology (e.g., create a VM on VMware vSphere).
Anatomy of OpenStack
OpenStack matches this same architecture, but splits functions into several different services. Each of these services is known by its project code name:
• Keystone: Identity service.
• Horizon: Web GUI. • Nova: Compute service. • Glance: Image service. • Neutron: Network services (formerly called "Quantum"). • Cinder: Block Storage service.
OpenStack services orchestrate and manage the underlying infrastructure and expose APIs for end users to consume the resources. OpenStack's strength is that it is a highly customizable framework, allowing those deploying it to choose from a number of different technology components, and even customize the code themselves.
OpenStack on VMware Infrastructure
In this step, we will review the VMware vSphere infrastructure for the lab and how OpenStack has been deployed within this infrastructure.
This lab focuses on how the compute, image, and storage portions of OpenStack interact with VMware vSphere. You will provision virtual servers and virtual disk volumes via OpenStack and learn how these capabilities are implemented on the back-end by using vCenter APIs.
You will also get an overview of managing virtual networks by leveraging VMware NSX plugin for Neutron. For detailed information on VMware NSX for multi-hypervisor environments, see HOL-SDC-1319. Also, note that OpenStack's object storage (Swift) is not covered in this lab.
Understanding Administrators vs. Users
In the course of the lab, you will switch between behavior as the "Cloud Administrator" who is operating the cloud infrastructure, and a "Cloud User" who is consuming the cloud infrastructure in a self-service fashion in order to deploy application workloads.
In OpenStack, a Cloud Administrator is able to access the software + hardware infrastructure layer directly (e.g., for setup or troubleshooting), while a Cloud User is limited to only interacting with the API/GUi or CLI tools, since OpenStack abstracts and limits their access to hardware resources.
For example, in this Lab, as a Cloud Administrator you will be able to access vCenter via the vSphere web client as well as perform some actions via the OpenStack Admin tab, but all actions that emulate a Cloud User are performed via the OpenStack Horizon GUI, CLI, or via SDKs.
As you perform steps in the lab, we will indicate whether you are performing the step as a Cloud Administrator or as a Cloud User.
Overview of the lab environment
This lab environment has the following main components.
• vCenter Server with single datacenter and single cluster. The cluster has 2 ESXi hosts.
• VOVA which runs all OpenStack compute, storage and network services in a single Ubuntu appliance
• VMware NSX appliance which is used by OpenStack Neutron to provide network virtualization services
• NFS based datastore that is shared across both the ESX hosts.
Lets review these components in more detail.
Access vCenter via the Web Client
Launch the Firefox web browser and select the 'vSphere Web Client" tab. This will bring up the login screen for vSphere Web Client.
You can either select the "Use Windows session authentication" and press login.
Or manually enter the following credentials:
User name: root
Then click "Login".
View vCenter Hosts and Clusters
Click on Home tab, then 'Hosts and Clusters" icon.
View vCenter Inventory
Navigate the Inventory, expanding the vCenter vc-1-01a, datacenter “Datacenter Site A”, and cluster “Cluster Site A” elements until you see the two ESX hosts.
vSphere compute capacity can be exposed to OpenStack on a per-vSphere Cluster basis, as OpenStack models the entire cluster as a single pool of capacity. In this lab, we will expose Cluster 'Cluster Site A' to OpenStack for self-service consumption by Cloud Users.
View Cluster Properties
Click on 'Cluster Site A' in the Inventory, and then click on the 'Summary' tab of the Cluster. This is the cluster we will expose as OpenStack capacity.
This is a small cluster, with 7.99 GHZ of CPU and 8 GBs of RAM. But OpenStack can handle any cluster size up to vSphere limits and can provision workloads to multiple clusters for larger deployments.
Notice that as the Cloud Administrator, you can still take advantage of key vSphere features like DRS and HA by enabling them on a cluster added to OpenStack.
Currently, DRS with auto-placement must be enabled for any cluster used by OpenStack, as OpenStack relies on DRS to spread VMs across all cap