Ucs Director Student Guide.pdf

UCS Director Deployment Student Guide Version 1.1



To install, configure, and manage Cisco UCS Director running on Cisco Unified Computing servers in a virtualized environment



Provisioning of Infrastructure services with Cisco UCS Director.

2

The following prerequisites skills and knowledge are recommended before attending this course: 

Understanding of server system design and architecture



Familiarity with the Unified Computing System (UCS)



Familiarity with Ethernet and TCP/IP



Familiarity with Server Virtualization



Familiarity with Storage Concepts

3

Compute

LAN

Virtual

Storage

Discover

Design

Deploy

Operate

User Groups vDC

Policies Catalogs

Self Service Portal Monitor

Resource Optimization

Management

4

Maintenance

Module 1

Module 2

Module 3

Introduction

UCSD Components

UCSD Deployment

• • • • •

• • •

• • • • •

DataCenter Challenges Cloud Layer Overview UCSD Overview Support Matrix Management Features

UCSD Architecture BMA Architecture Deployment Models

•

UCSD Installation OVF Deployments UCSD Shell Admin UCSD – BMA Configuration Global System Settings o Licensing o Mail Setup o System Parameters o Authentication Preferences o Support Information UCSD Datacenter

•

Lab 1: UCSD and BMA Installation

Module 4

Module 5

Discovery

Design

• • • 

•

Discovery Overview Virtual Infrastructure Discovery Physical Infrastructure Discovery

Lab 2: Discovery •



Lab3: UI Familiarization • • •

Policies o Computing o Network o Storage o Service Delivery User Groups o Group Budget Policy o Resource Limits Users o User Roles o Manage User Profiles Virtual Data Center (vDC) Catalog

•

Lab 4: Services Design

•

Lab 5: Catalog

Module 6

Module 7

Module 8

Deploy

Orchestration

Operate

• •

•

• •

Self Service Provisioning Service Requests

Tasks and Workflows Workflow Templates

Lab 7: Advanced Catalog •

Lab 6: Self Service Portal

• •

Advanced Catalog Workflow Designer

Lab 8: Workflow Design

Chargeback

Module 9 Fenced Containers •

•

Understanding Fenced Containers

Lab 9: Setting up Fenced Containers with a Linux firewall



Discuss DC Trends and Challenges



Describe the Cisco UCSD Solution



Understand the current UCSD Support Matrix



Describe the Management capability of the solution

10



Business Agility



Manual Disconnected Processes



Security and Compliance



Higher TCO and Lower ROI



Resource Visibility – Lifecycle Management , VM Sprawl



Wastage of Resources

11

12

Cloud

Virtualization

Web Client Srv. Mini Comp Mainframe 1960

1970

1980

1990 13

2000

2010

Service Catalog

Orchestration and Management

Infrastructure

VM

CRM

VDI

Cloud Container

Orchestration / Management / Monitoring

Compute

Network

14

Storage

Virtualization



A multi-tenant, multi-hypervisor and multi-cloud (private and public) provisioning and management solution that provides comprehensive virtual infrastructure control, management and monitoring via a single pane of glass



Cisco UCSD delivers unified management for the industry’s leading converged infrastructure solutions, which are based on the Cisco Unified Computing System (UCS) and Nexus platforms.



Cisco UCSD automates the provisioning of resource pools across physical and virtual from a unified centralized management console, reducing time-to-value for both applications and end users.

15

Mobile Devices

End Users

Admins

Self Service Catalog

LDAP, CMDB, Metering DB

Operations

Admin Console

Dashboard

System Integration

UCSD Unified Infrastructure Controller Multi-tenant & integrated cloud platform

UCS Director

Amazon, Rackspace, … Provider API

Public Clouds

Integrated Multi-tenant Cloud Platform

Server Managers UCS

Storage APIs

Network Manager

vCenter

System Center

Nexus

VMware

Infrastructure

HyperV

Cloud Infrastructure 16

UCSD 17

Unified Management of Converged Infrastructures

• NetApp: FlexPod and ExpressPod • VCE: VBlock • EMC: VSPEX

End to End Virtual & Physical Management

• Large breadth and depth of functionality • Multi-platform, multi-vendor

Turnkey Solution

• A single integrated, unified platform that installs quickly • 400+ out-of-the-box orchestration tasks • Usable without heavy pro services; fast time to value

Storage Choice

Best Integration with UCS

• Multi-vendor support (NetApp & EMC) • Multi-protocol storage support

• Unmatched breadth and depth of functionality • Tightly integrated; UCSD is part of same BU that makes UCS

Service Catalog

VM

Orchestration and Management

Infrastructure

WorkFlow

VDI

Web Store

Cisco UCS Director Orchestration / Management / Monitoring

Compute

Network

Storage

Virtualization

-

-

-

-

Cisco HP Dell

19

Cisco

NetApp EMC

VMware Hyper-V KVM

Cisco Components UCS Chassis Blade Servers Rack Mounts Fabric Interconnect UCS Manager

Model

Supported Version/ Interfaces

UCS 5100 Series UCS B Series, C Series UCS C200 M2 UCS C210 M2 UCS 6100, 6200 UCSM

1.0, 1.3, 1.4, 2.0, 2.1

HP Type

Model

Supported Version /Interfaces

Blade Servers

C7000

Rack Mounts Servers

GL-380, DL-700 Series

HP-ILO Management

HP-ILO

1.61

Type

Model

Supported Version /Interfaces

Rack Mounts Servers

PowerEdge R200 Poweredge R210x

Dell

20

Cisco Devices Device

Model

Supported Version/ Interfaces

Data Center Switch

Nexus 3K, 5K, 7K series

5.0 or above. 6.2 for 7K 4.2

Nexus 1000v (VXLAN) Data Center Storage Switches

MDS 9000, 9124, 9148 Series Directors and Fabric Switches

Security

PIX ASA 5500 Series (Physical)

8.0 7.0

Model

Supported Version /Interfaces

Brocade 300

v6.3.0a

VDX 6710-54

v2.1.1

VDX 6720-24

v2.1.1

VDX 6730-32

v2.1.1

Brocade Type Fabric OS Switch:

Network OS Switch:

21

NetApp Storage Type

Model

Supported Version /Interfaces

Interfaces

ONCOMMAND

4.0.2

Interfaces

ONTAP

7.3.6, 8.0.1, 8.0.2 (7 mode), 8.2(C Mode)

Storage Controller

FAS 2000, FAS 3000, FAS 6000 Series,

FAS 2240, FAS 3210

Interfaces

ZAPI

1.13 and above

Type

Model

Supported Version /Interfaces

VNX

Block, File, Unified versions of 5100, 5300, 5500, 5700 and 7500

VMAX

Includes 10K, 20K and 40K arrays

EMC

22

VMWare

Type

Model

Version

Management

vCenter

5.1, 5.0, 4.1, 4.0

Hypervisor

ESX/ESXi Versions

5.1, 5.0.0, 4.1.0, 4.0.0, 3.5

Plugin

VSC

2.1

Microsoft Hyper-V Hypervisor

Hyper-V

Microsoft Windows 2008 R2 SP1 ( Hyper-V 2.0 ) Microsoft Windows 2012 ( Hyper-V 3.0 )

Management

System Center Virtual Machine Manager (SCVMM)

System Center Virtual Machine Manager 2008 R2 SP1 (Ver 2.04521.0 SP1)

System Center Virtual Machine Manager 2012 & 2012 SP1 RedHat KVM Hypervisor

RHEVH

5.6 - 9.3el5_6

Management

RHEVM

2.2.4.51796

VDSM

2.2.63.23

Xendesktop Controller

5.5

VDI

Citrix

23

Type

Supported Version /Interfaces

VMWARE

ESXi4.1, ESXi5.0

LINUX

CentOS 5.x/6.x, RHEL5.x

WINDOWS

Windows 2008 R2

24

Category

Description

Cisco branded release

Swift Licensing and Cisco Branding

Licensing

Cisco format documentation (Phase 1)

Bare Metal Server License – CUIC-PHY-SER-BM New Bundles - CUIC-SBUN-OFFERS1 , CUIC-SBUN-OFFERS2 NFR License, Evaluation License (60 Day Trial period from 30 Days) VLA License

Converged Infrastructure

VBlock (200,300 – VNX), VBlock (700, 720 - VMAX), VSPEX 125,250 (VNX), FlexPOD N7K/Clustered Data ONTap ,

Compute

UCSM 2.1 (Del Mar) new features, C-Series standalone (Double peak ) enhancements

Storage

VNX File,Block, Unified versions 5100,5300,5500,7500 Series , VMAX 10K,20K,40K, NetApp OnTap 8.2 Compatibility

Network

Nexus 1000v (VXLAN), Nexus 7K, MDS 9000 Series Director & Fabric Switches, ASA 55xx Series

Hypervisors Platform Multi Vendor

Microsoft Hyper-V (2012) updates , VMWare ESXi updates LDAP enhancements, Orchestrator task library, Views, Reporting, 64 bit UCS Director VM, Bug Fixes HP – iLO3/4

Ecosystem

Northbound REST Based API (JSON, XML) and Open Automation SDK available as EFT

Localization

Japanese, Spanish



Out of the box, Cisco UCSD has support for Physical and Virtual component management o Physical Components

• Server Management • Storage Management •

Network Management

o Virtual Component

• Computing Management • Storage Management •

Network Management

26



Discover and collect configurations and changes



Monitor and manage physical servers



Perform policy-based server provisioning



Manage blade power



Manage the server lifecycle



Perform server use trending and capacity analysis



Perform bare-metal provisioning using pre-boot execution environment (PXE) boot management

27

UCS Director is not a replacement for UCSM



Configuration / Administration

Monitoring / Reporting

•

Fabric interconnects, including ports

•

Power consumption

•

Chassis, blade servers, and rack-mount servers, including auto-discovery

•

Temperature

•

Server availability

•

Service profile association

•

Network Connections

•

Storage connections

•

Pools

•

Policies

•

Service profiles

28



Discover, collect, and monitor storage filers



Perform policy-based provisioning of vFilers



Provision and map volumes



Create and map LUN and iGroup instances



Perform SAN zone management



Monitor and manage network-attached storage (NAS) and SAN based storage



Implement storage best practices and recommendations

29



Discover, collect, and monitor physical network elements



Provision VLANs across multiple switches



Configure ACLs on network devices



Configure the storage network



Implement dynamic network topologies

30



Discover, collect, and monitor virtual computing environment



Perform policy-based provisioning and dynamic resource allocation



Manage the host server load and power



Manage the virtual machine lifecycle and snapshots



Perform analytics to assess virtual machine capacity and sprawl and host utilization

31



Discover, collect, and monitor storage vFilers and storage pools



Perform policy-based storage provisioning for thick and thin clients



Create new data stores and map them to virtual device contexts



Add and resize disks to virtual machines



Monitor and manage organizational storage use



Perform virtual storage trend and capacity analysis

32



Add networks to virtual machines



Perform policy-based network provisioning with IP and DHCP allocation



Configure and connect vNICs to VLANs and private VLANs



Create port groups and port profiles for virtual machines



Monitor organization use of virtual networks

33

UCSD – Components

  

Describe the components of the UCSD Solution Understand the deployment options Understand UCSD-BMA connectivity options

35

• UCS Director

UCSD

• UCSD is the key component which has pre-

integrated capabilities to build a cloud. Modules within UCSD can be deployed on a single VM or multiple VMs • UCSD Bare metal Agent

BMA

BMA

• BMA provides PXE boot capabilities for bare

metal provisioning. • BMA acts as a PXE image repository. • Act as DHCP and TFTP server

36



CentOS Virtual Appliance – 32 bit or 64 bit o VMware o Hyper-V



Multi-Cloud, Multi Hypervisor Management



Discovery



Automation



Monitoring

37

Dynamic UI

Dynamic UI

Mobile APPs

UCSD Flex UI Framework

UCSD AJAX UI Framework

UCSD Mobile Framework

UCSD SDK

Admin shell

REST APIs

Console Client Web Apps

Infra Manager

JMS

Apache Tomcat 6.x

SSH

Feature Modules

Orchestrator & Scheduler

UCSD Cloud Framework Event Manager Identity & Access Manager Secure Domain Controller CentOS 5.4

38

MySQL 5.x



North Bound API Rest Based (JSON,XML data format) – This API exposes functions like orchestration, database etc. Provides the ability to write own portal using this API's, integrate other orchestrators, Change Management etc.



Open Automation Framework which provides the ability to write adapters to integrate storage, other hypervisors, or call out external systems like Service Now, Remedy, allows you to build task library.

39



CentOS Virtual Appliance o VMware o Hyper-V



Needed for Bare Metal PXE Boot



Provides DHCP (optional) and TFTP services

40

Root shell

DHCPd

SSH

Network Services Agent

JMS

PXE Manager MySQL 5.x TFTPd

HTTPd

Secure Domain Controller

CentOS 5.4

41

Shared DB with UCSD

IT Operations

End users

Deployment Type: • Proof of Concept or Demo • Small Production Deployments (with Remote DB Backups)

UCSD Deployed as Virtual Appliance on vCenter - 2 vCPUs (with 2GHz Reserved) - 3 GB RAM (with 2GB reserved) - 40 GB+ Storage - 1 vNIC (static IP)

Use Cases: • Public Cloud Mgmt • Private Cloud (Virtual Infrastructure Only)

UCSD

Scalability: • Under 2000 VMs • Under 100 users

HA • Through VMware HA

vCenter 42

End users

IT Admins

IT Operations

Deployment Type: • Proof of Concept or Demo • Small Production Deployments (with Remote DB Backups)

UCSD Deployed as Virtual Appliance on vCenter - 2 vCPUs (with 3GHz Reserved) - 4 GB RAM (with 3GB reserved) - 40 GB+ Storage - 1 vNIC (static IP)

Use Cases: • Public Cloud Mgmt • FlexPOD - Private Cloud (With Bare Metal Provisioning)

BMA Deployed as Virtual Appliance on vCenter - 2 vCPUs (with 2 GHz Reserved) - 3 GB RAM (with 1GB reserved) - 40 GB+ Storage - 2 vNIC (static IP)

UCSD

Scalability: • Under 2000 VMs • Under 100 users BMA

HA • Through VMware HA vCenter On Command (or ONTAP)

UCS Manager 43

Default VLAN (for PXE Boot)

Nexus Switches (5k/1k)

End users

IT Admins

IT Operations UCSDs Deployed as Virtual Appliance on vCenter - 2 vCPUs (with 3 GHz Reserved) - 4 GB RAM (with 3 GB reserved) - 40 GB Storage - 1 vNIC (static IP)

Deployment Type: • Production

Use Cases: • Public Cloud Mgmt • Private Cloud (Virtual Infrastructure Only)

Scalability: • Under 2000 VMs • Under 1000 users

Load Balancer UCSD-1 (Active)

UCSD-2 (Standby)

My SQL 5.x (External DB)

HA • Active-Standby

44 vCenter

MySQL Deployed as Virtual Appliance on vCenter - 2 vCPUs (with 3 GHz Reserved) - 4 GB RAM (with 3 GB reserved) - 40 GB+ Storage - 1 vNIC (static IP) - Periodic VM level snapshots OR storage level snapshots

End users

IT Operations

IT Admins

UCSDs Deployed as Virtual Appliance on vCenter - 2 vCPUs (with 3 GHz Reserved) - 4 GB RAM (with 3 GB reserved) - 40 GB Storage - 1 vNIC (static IP)

Deployment Type: • Production

Use Cases: • Public Cloud Mgmt • FlexPOD - Private Cloud (With Bare Metal Provisioning)

Load Balancer

UCSD (Active)

Scalability:

UCSD (Standby)

BMA Deployed as Virtual Appliance on vCenter - 2 vCPUs (with 2 GHz Reserved) - 3 GB RAM (with 1GB reserved) - 40 GB+ Storage - 2 vNIC (static IP)

• Under 2000 VMs • Under 1000 users My SQL 5.x (External DB)

HA • Active-Standby

BMA

Default VLAN (for PXE Boot)

vCenter On Command (or ONTAP)

UCS Manager 45

Nexus Switches (5k/1k)

UCSD

BMA

Management and PXE Install Network

UCSD

BMA

Management Network

PXE Install Network

UCSD

Management Network

BMA

L3 Routing

PXE Install Network

UCSD Deployment

   

 

Describe the UCSD / BMA deployment procedure Understand the configuration steps for UCSD BMA Connectivity Describe the methods for accessing UCSD and BMA Understand the DHCP server configuration Describe the Global System Settings like Licensing, Mail Setup in UCSD Understand the UCSD Datacenter Construct

50

Installation

UCSD / BMA

LAN

Compute

Virtual

Storage

Discover

Design

Deploy

Operate

User Groups vDC

Policies Catalogs

Self Service Portal Monitor Management

Resource Optimization Maintenance



Provided as an appliance for VMware Environment



Download UCSD Appliance zip file(s)



Import UCSD Virtual Appliance (OVF) file into ESXi/ESX host via

vCenter/vSphere client into your environment for simple deployment 

Resource Allocation for the UCSD VM

53



vCenter (4.0 / 4.1 / 5.0 / 5.1)



vSphere Client



Downloaded UCSD (OVF) Appliance



System Requirements: VMware : ESX 4.x or ESXi 4.x/5.x vCPU :2, Memory : 3 GB Hard Disk : 40 GB

54



vCenter (4.0 / 4.1 / 5.0 / 5.1)



vSphere Client



Downloaded UCSD (OVF) Appliance



System Requirements: VMware : ESX 4.x or ESXi 4.x/5.x vCPU :2, Memory : 2 GB Hard Disk : 30 GB

55



Login to vCenter



Select File | Deploy OVF Template



Select Downloaded OVF File



Deploy

57

58



Access to appliance console with vCenter / vSphere Client



Power on VM



Setup Network Configuration



UCSD Access is via Web or CLI o Web Access – admin / admin o Shell Access – shelladmin / changeme

59

60

61

Supported Browser Versions 

Internet Explorer 8 or higher



Google Chrome 4.1 or

higher 

Firefox 3.5 or higher



Safari 4.0 or higher (for

Mac/Windows) *Note: Requires Adobe Flash Player 11 plug-in

62



Manage UCSD Services



Manage UCSD Database



Database Backup/Recovery



Configure Network



BMA Connectivity options



Apply Patch



Time Sync with NTP

63

Main services should be up and running 64



BMA is required for bare metal provisioning



Provided as an appliance for VMware Environment



Download BMA Appliance zip file(s)



Import BMA Virtual Appliance (OVF) file into ESXi / ESX host via vCenter/vSphere client into your environment just as UCSD OVF deployment



BMA is used as DHCP server and TFTP server

65

66



Configure BMA - UCSD Connectivity o Configure BMA o Configure UCSD



DHCP Configuration o DHCP Server setup



TFTP Server o Enabled by default

67

Initially, ‘BMA’ must be configured with IP address of ‘UCSD’ 

Log into BMA using SSH o cd /opt/infra

o ./stopInfraAll.sh o ./configure.sh o ./startInfraAll.sh



Verify network connectivity between BMA and UCSD using the ping command

68



Edit ‘DHCP’ configuration file & make relevant DHCP server settings



Restart DHCP service

( #service dhcpd restart )

69



SSH/console to UCSD



Run option 10 with BMA Hostname/IP



Run option 16 ‘Enable Database for BMA’



Run option 17 ‘Add BMA Hostname/IP’

70



Licensing



Mail Setup



System Parameters



LDAP Integration & Preference



Support Information

72



Base Model o Update Cloud features



A La Carte Model o Update additional servers and network devices



POD Model o Add POD like FlexPod, ExpressPod,VSPEX

73

Administration  System Administration  License Keys  Update License 74



All Outgoing emails from UCSD will require an Outgoing SMTP server



Alerts, Approval & Provisioning status are sent via email

Administration  System Administration  Mail Setup 75

(Optional) System parameters to specify:  

Currency Retention period for events, deleted VMs, metering data and trend data

Administration  System 76 Administration  System Parameters



By default, Local Authentication is used



Change Authentication Preference as per requirement

Administration  Users and 77 Group  Authentication Preferences





Basic System Information (UCSD version, System clock etc.) Services Logs o Service Status

logs (Tomcat, Infra Manager, etc.) 

Debug Logging

Administration  System Administration  Support Information  System Information 78 and Logs Link Page



Customers are increasingly deploying compute, network, storage, and virtualization as a single, converged system



A Datacenter is a logical structure in UCSD where resources are

placed 

The following types of Datacenter can be defined in UCSD o FlexPod o VBlock o VSPEX o ExpressPod Small o ExpressPod Medium o Generic

80



Logical structure where resources are placed



Resources include o Virtual o Compute o Network o Storage

Converged  + Add

81

Discovery

   

Describe the Protocols used for Discovery by UCSD Understand the Discovery process Understand the Management capabilities of UCSD Gain familiarity with the UCSD UI

84

Compute

LAN

Virtual

Storage

Discover

Design

Deploy

Operate

User Groups vDC

Policies Catalogs

Self Service Portal Monitor

Resource Optimization

Management

85

Maintenance

 

Virtual and Physical Infrastructure is discovered by UCSD using various protocols / API’s and placed in a Datacenter container The Infrastructure can be o Virtual

• VMware vCenter • Hyper-V o Physical

• Compute • Network • Storage 

Credentials and reachability information required for discovery

86

Resource

Protocol Used

VMware

vCenter API

Hyper-V SCVMM

Powershell Agent

Compute

UCSM XML-API

Network

Command line over SSH / Telnet

Netapp

Native ONTAP API / OnCommand API

EMC

Native Unisphere API

87



Cloud refers to a Virtual Infrastructure – a single VMware vCenter for example • • •

• • • •

AWS-EC2 VMware RackSpace-Cloud Tier3-Cloud Hyper-V RedHat KVM XenDesktop

Administration  88 Virtual Accounts  + Add



Each Cloud requires a unique name in UCSD



VMware Datacenter allow discovering, monitoring and managing only the specified datacenter's resources



Physical Datacenter is the Converged Infrastructure Datacenter the resource is to be placed in

89



Hyper-V discovery requires a PowerShell agent



The PowerShell agent is provided by Cisco



Physical Datacenter is the Converged Infrastructure Datacenter the resource is to be placed in

90

91



The following type of compute resources can be discovered o Cisco UCSM o Cisco Standalone

Racks o HP iLO o Generic IPMI complaint servers

Administration 92Physical Accounts  + Add



Physical Datacenter is the Converged Infrastructure Datacenter the resource is to be placed in



The following type of storage resources can be discovered o Netapp ONTAP o Netapp OnCommand o EMC VNX o EMC VMAX Solutions

Enabler

Administration 93Physical Accounts  + Add









Interfaces with Solutions Enabler Uses Symmetrix Command Line Interface (SYMCLI) Provides a host with comprehensive command set for managing Symmetrix Storage Invoked from the host OS command line

94

 Detailed Configuration Information  Status  On-line Configuration Changes

 Performance  Control



Physical Datacenter is the Converged Infrastructure Datacenter the resource is to be placed in



The following type of network devices can be discovered o Cisco Nexus o Cisco IOS o Cisco ASA o Force 10 o Brocade Fabric OS o Brocade Network OS

Administration  Physical Accounts  Managed Network Elements  + Add Network 95 Elements

96

97

98

99

100

101

102

Design

   

 

Describe the various Policies for VM provisioning Understand UCSD User Groups Understand Users and Roles Describe the Virtual Data Center (vDC) construct Understand Catalogs Understand how to create a Standard Catalog

106

Compute

LAN

Virtual

Storage

Discover

Design

Deploy

Operate

User Groups vDC

Policies Catalogs

Self Service Portal Monitor

Resource Optimization

Management

107

Maintenance



A policy is a group of rules which determines where and how a new VM will be provisioned within the infrastructure based on the availability of system resources.



The UCSD needs four policies to be setup in order to provision VMs. The policies are for o Computing o Storage o Network

o System

108

Computing Policy defines Computing resources/conditions 

Host Node /Cluster Scope (Include, Exclude)



Resource Pool



ESX Type (ESX, ESXi or Any)



Minimum conditions (if any)



Deployment Options (Modify vCPU, etc.)



Resizing Options



Deploy to Folder

109

Policies  Computing 110 VMware Computing Policy  + Add



Network Policy defines network resources/conditions



Which Cloud a provisioned VM(s) should go



Minimum network requirements to be met (if any)



Network Port group Name/Type (Distributed or Normal)



DHCP/Static IP configuration while provisioning new VM(s)



Option for multiple vNICs for VMs.

111

Policies  Network 112 VMware Network Policy  + Add

Storage Policy defines storage resources/conditions 

Data stores scope (All, Include, Exclude)



Storage Options (Local, SAN, NFS)



Minimum conditions on storage (if any)



Deployment Options (Override template, Thin provisioning)



Allow Resizing of Disk



Allow Datastore selection

113

Policies  Storage 114 VMware Storage Policy  + Add

System Policy defines service delivery information like : 

VM Name Template



Host Name Template



DNS Details



Time zone



VM Image Type (Linux or Windows, if Windows license details etc.)

115

Policies  Service Delivery 116 VMware System Policy  + Add

Policies  Service Delivery 117 VMware System Policy  + Add



Users and User groups are required for organizations to model their organization structure and roles in cloud environments.



UCSD Self-service portal requires that at least one User Group (or

Customer Organization) be setup. 

Users are created within a User Group.



UCSD supports multiple roles with varying Access Control/Privileges

for users which belong to a User Group.

118

Administration  Users and 119 Groups  User Groups  +Add

Administration  Users 120 and Groups  Budget Policy

Administration  Users and 121 Groups  Edit Resource Limits

Organization  Summary  Select a group  Click on Resource Limits 122

Administration  Users and Group Login Users  +Add

UCSD Roles/Access Control:

• • • • • • • • • • •

Service End-User Group Admin System Admin IS Admin Computing Admin Storage Admin Network Admin Operator All Policy Admin Billing Admin MSP Admin

Administration  System124 administration  User Permissions

Administration  System Administration  Menu Settings

Administration  Users and Group Manage Profiles  +



A Virtual Data Center is a logical construct that combines o Infrastructure o Virtual resources o Policies to manage specific group requirements o Business Operational Processes o Cost Model o Enable/Disable Storage Efficiency o End User Self Service Option



A User Group can have and manage multiple vDC ‘s



A VM provisioned using a Service Request can be associated with a vDC 127

Policies  Virtual Data Centers  + Add



A catalog is a logical construct that presents a single “Menu Item” to the Self Service user.



A Catalog combines o User Group o Image o Application Category, Application Type, OS Type, etc. o Additional options such as Credentials, Guest customization etc.



Standard o VM self-provisioning based

on standard Pre-built Images 

Advanced o Complex workflows as a

single interface 

Service Container o Fenced Container



VDI o Virtual Desktop

130



Standard Catalog uses predefined image templates for VM provisioning



Creating a Standard Catalog requires specifying the User Groups it is published for.



Cloud Name and the Image Template reference the virtual resource



Post provisioned workflows can be specified

Deploy

 

Understand the Self Service Portal Understand Service Requests

135

Compute

LAN

Virtual

Storage

Discover

Design

Deploy

Operate

User Groups vDC

Policies Catalogs

Self Service Portal Monitor

Resource Optimization

Management

136

Maintenance



Self-service portal provides service catalog, self-service provisioning, self-service dashboard and management to create, deploy and reconfigure servers and applications in minutes

Key Benefits • • • • •

Rapid provisioning Define & publish infrastructure offerings via self-service catalog Reduced operational costs Improve productivity & customer satisfaction Reduced administration burden

137

Services as defined by IT admin

141

142

143

144

Resource limits checked if Budget Watch is enabled for the group

145

Identification of Resources based on Policies, Current Capacity and Performance requirements.

146

Organization  Service Request  Select Service Request  View Details

Orchestration

   

Understand Tasks and Workflows Describe Workflow Use Cases Describe Workflow Creation and Execution Understand the Workflow UI Designer

150



Tasks o A task is a specific action or operation. UCSD has numerous pre-

defined tasks for Compute, Storage and Network in both Virtual and Physical Infrastructures. Individual tasks are grouped together in a sequence to create a workflow. Tasks can have inputs and outputs. 

Workflow o A workflow typically consists of a sequence of connected tasks. A task

has a specific functionality representing a specific action or operation. A workflow determines the order in which the tasks are executed. Also the output of the previous tasks can be used as input to the subsequent tasks.

151

Create VLANs

Update Trunks

Create Network Policies

Create UCS Service Profiles

Configure SAN Zoning

Service Profile Creation

Bare metal Provisioning (ESX 5.1)

Configure Servers

Create Storage Resources (LUNs & Volumes)

Create VLAN

Add VLAN to Service Profile

Create IP space

Create vFilers

Add vFilers to Group

Map NetApp LUN

Create Storage Policy

UCS Blade Power On

Register Host Node

Send Complete Notifications

152

154



Infrastructure Management o Bare Metal OS Provisioning o Storage, Network, Compute Provisioning



DR Automation o Server Backup Workflow o Launching VM at DR site



Workload Automation o Scaling up and down based on demand o VM Consolidation to minimize power load

155



Workflows templates provide a “portable” blue-print of a service which can be imported/exported to/from a system.



Workflow Designer allows one to create a workflow and export it as a workflow template.



By default, certain workflow templates come pre-populated. For example, Deploy ESXi Host



Workflows can be instantiated via templates which is when specific details on resources (Physical and Virtual) for a given environment need to be provided.

156

Workflow

Import or Use existing Workflow

Design Workflow using UI Designer

Create Workflow from Workflow Template

157

158

159



Advanced Catalog references a Workflow in the Workflow library



Creating an Advanced Catalog requires specifying the User Groups it to published for.



Bare Metal Provisioning for example will be a type of Advanced Catalog.

163

164

168

169

170

171

172

Operate

 

Understand Chargeback in UCSD Understand the reporting and trending capability in UCSD

175

Compute

LAN

Virtual

Storage

Discover

Design

Deploy

Operate

User Groups vDC

Policies Catalogs

Self Service Portal Monitor

Resource Optimization

Management

176

Maintenance



Provides visibility into the cost of the Virtual Infrastructure



Supports fixed overhead costs and variable resource costs



Allows Cost Models to be assigned to departments / organizations



Exportable (PDF, XLS, CSV) data for enterprise integration

177



Standard Cost Model o Defining of costs in a linear model o Costs defined at unit level and chargeback is based on how many units

provisioned for a particular VM 

Advanced (Package Based) Cost Model o Suitable for non-linear models o Cost defined in the form of package – CPU-Memory together for

example

178



Provide name, description, and Type as Standard



Charge frequency – hourly / monthly / yearly



One time / Setup cost, Active / Inactive VM



Provide Compute, Network and Storage Unit Cost

Policies  Service Delivery  Cost Model  +

179



UCSD supports defining CPU and Memory Packages. Storage Tier has to be specified for Storage Cost



Script for this model is provided separately.



Format C – M:X o C is the number of CPU cores o M is the memory in GB o X is the combined monthly cost of C

and M

A package with entry : “2-4:200” implies, CPU cores = 2, Memory = 4 GB and cost of this package is $200 per month. 

Policies  Service Delivery  Cost Model  +

180

181

Organization  Chargeback

182

Organization  Virtual Resources  ‘Select Group’  VMs 183

Virtual  Computing  ‘Select Cloud’  Top 5 Reports 184

Virtual  Computing  ‘Select Cloud’  More Reports 185

Virtual  Computing  ‘Select Cloud’  More Reports 186

Virtual  Computing  ‘Select Cloud’  More Reports  Instant Report 187

Virtual  Computing  ‘Select Cloud’  More Reports 188

Virtual  Storage  DataStore Capacity Report 190

Virtual  Storage  More Reports

191

Physical  Compute  ‘Select UCS Account’ 192  More Reports

Fenced Containers



A Fenced Container is a collection of VM’s with an internal private network based on rules set by the administrator



The internal VM’s are guarded by a gateway



The gateway can be a (firewall) VM or the Cisco ASA (physical appliance)



UCSD deploys and configures the VMs / firewall and network as part of instantiation

194

Web Tier

External Network

Apache

App Tier Fencing Gateway (Firewall)

JBoss Database Tier

MySQL

195



Tiered Applications Gateway Policy o Gateway Type – VM or ASA o Details of the Gateway – Cloud / Image



Tiered Applications Container Template o Network and Firewall Rules o Deployment Policies for VMs o Self Service Options o Gateway Policy

196

197

198

199

200

201

202

203

204

205

206