UNIMI: Provisioning Services Stream Process Architecture

Slides:



Advertisements
Similar presentations
Storage Design for Agile VDI Alex Danilychev, PhD.
Advertisements

Confidential a complete data protection solution.
Desktop U-M September 28, 2011 Ryan Henyard ITS – Desktop Infrastructure.
Implementing vSphere David J Young. Implementing vSphere Agenda Virtualization vSphere ESXi vSphere Client vCenter Storage Implementation Benefits Lessons.
Business Solutions Network Storage Solutions Cc c Network Size Small MediumLarge SAN NAS DNS Bay Enclosure USB port for direct- to-PC connection.
Planning and Implementation of a Provisioning High Availability (HA) Solution Keith T McLaughlin Escalation Engineer.
NAS vs. SAN 10/2010 Palestinian Land Authority IT Department By Nahreen Ameen 1.
What’s New: Windows Server 2012 R2 Tim Vander Kooi Systems Architect
Wyse.com 2010 Cameron Smith Sales Engineer for IN, KS, and MO Desktop Virtualization.
Planning Server Deployments
1 CSC 486/586 Network Storage. 2 Objectives Familiarization with network data storage technologies Understanding of RAID concepts and RAID levels Discuss.
Linux Clustering A way to supercomputing. What is Cluster? A group of individual computers bundled together using hardware and software in order to make.
Vorlesung Speichernetzwerke Teil 2 Dipl. – Ing. (BA) Ingo Fuchs 2003.
Moving to a Virtual World Don Mendonsa Lawrence Livermore National Laboratory This work performed under the auspices of the U.S. Department of Energy by.
SQL Server, Storage And You Part 2: SAN, NAS and IP Storage.
VMware Infrastructure Alex Dementsov Tao Yang Clarkson University Feb 28, 2007.
IBM® Spectrum Storage Virtualize™ V V7000 Unified in a nutshell
DSN-6000 series Introduction. ShareCenter Pulse DNS-320 SMB/ Entry SME SOHO/ Consume r SOHO DNS-315 Capacity and Performance D-Link Storage Categories.
CCAT Troubleshooting Training – Provisioning Services April 2012 Citrix Consulting Architecture Team.
Virtualization 101.
Virtual Network Servers. What is a Server? 1. A software application that provides a specific one or more services to other computers  Example: Apache.
ProjectWise Virtualization Kevin Boland. What is Virtualization? Virtualization is a technique for deploying technologies. Virtualization creates a level.
Greg Porter, MCITP: EA, Cal Poly October 17, 2010.
Virtualization 101.
Virtual Desktop Infrastructure Solution Stack Cam Merrett – Demonstrator User device Connection Bandwidth Virtualisation Hardware Centralised desktops.
Using Virtualization in the Classroom. Using Virtualization in the Classroom Session Objectives Define virtualization Compare major virtualization programs.
GDC Workshop Session 1 - Storage 2003/11. Agenda NAS Quick installation (15 min) Major functions demo (30 min) System recovery (10 min) Disassembly (20.
XD 5.6 Overview. XenDesktop 5.6 Main Focus = Integration of personal vDisk Features Support for Microsoft SCVMM 2012 and SCCM 2012 Updated Citrix License.
Yury Kissin Infrastructure Consultant Storage improvements Dynamic Memory Hyper-V Replica VM Mobility New and Improved Networking Capabilities.
Virtual Desktops and Flex CSU-Pueblo Joseph Campbell.
Stuart Cunningham - Computer Platforms COMPUTER PLATFORMS Network Operating Systems Week 9.
About the Presentations The presentations cover the objectives found in the opening of each chapter. All chapter objectives are listed in the beginning.
Configuration of Linux Terminal Server Group: LNS10A6 Thebe Laxmi, Sharma Prabhakar, Patrick Appiah.
Introducing Snap Server™ 700i Series. 2 Introducing the Snap Server 700i series Hardware −iSCSI storage appliances with mid-market features −1U 19” rack-mount.
Workstation Virtualization Nicholas A. Hay Technology Coordinator Jefferson Schools
DIY: Your First VMware Server. Introduction to ESXi, VMWare's free virtualization Operating System.
XenDesktop Built on FlexPod Flexible IT Infrastructure for Desktop Virtualization.
Sydney Region IT School Support Term Smaller Servers available on Contract.
Gordon Mangione VP, Emerging Virtualization Products Citrix Systems, Inc. Gordon Mangione VP, Emerging Virtualization Products Citrix Systems, Inc.
Using Virtualization in the Classroom. Using Virtualization in the Classroom Session Objectives Define virtualization Compare major virtualization programs.
Redefining the Desktop Stu Baker AUL for Library Technology
Objective  CEO of a small company  Create a small office network  $10,000 and $20,000 Budget  Three servers (workstations)  Firewall device  Switch.
608D CloudStack 3.0 Omer Palo Readiness Specialist, WW Tech Support Readiness May 8, 2012.
Sandor Acs 05/07/
Microsoft Virtual Academy Module 8 Managing the Infrastructure with VMM.
IST Storage & Backup Group 2011 Jack Shnell Supervisor Joe Silva Senior Storage Administrator Dennis Leong.
Using NAS as a Gateway to SAN Dave Rosenberg Hewlett-Packard Company th Street SW Loveland, CO 80537
ITGS Networks. ITGS Networks and components –Server computers normally have a higher specification than regular desktop computers because they must deal.
70-412: Configuring Advanced Windows Server 2012 services
ClinicalSoftwareSolutions Patient focused.Business minded. Slide 1 Opus Server Architecture Fritz Feltner Sept 7, 2007 Director, IT and Systems Integration.
Hands-On Virtual Computing
The 2001 Tier-1 prototype for LHCb-Italy Vincenzo Vagnoni Genève, November 2000.
Planning Server Deployments Chapter 1. Server Deployment When planning a server deployment for a large enterprise network, the operating system edition.
PHD Virtual Technologies “Reader’s Choice” Preferred product.
Citrix Academic Network
BY: SALMAN 1.
Using Virtualization in the Classroom
Video Security Design Workshop:
Bentley Systems, Incorporated
BY: SALMAN.
1Y0-301 Deploying Citrix XenDesktop 7.6 Solutions
Virtualization OVERVIEW
Desktop Virtualization
2016 Citrix presentation.
HP HPE0-J74 - Foundations of HPE Storage Solutions exam Braindumps
Introduction to Networks
,Dell PowerEdge 13 gen servers rental.
Zero Clients and Virtual Desktops in Academic Environments
Virtualization 101.
Presentation transcript:

UNIMI: Provisioning Services Stream Process Architecture

Server and Desktop Provisioning Create a virtual image of a server’s or Desktop’s workload: OS, applications and configuration Virtualize Store the virtual workload image on a network storage device Store Stream the workload image on-demand to virtual and bare-metal servers/Endpoints Stream Stream A Virtualize Store …and Provisioning Server does just that. It changes the game for IT. It does this by streaming workloads on-demand rather than pushing full images onto each target system. There’s a lot of really cool and complex technology under the hood that I could spend an entire day talking about but really the model is quite simple, it’s virtualize, store, and stream. You virtualize a system image by capturing it from a reference system. That image is stored somewhere on the network And then Provisioning Server streams it to any number of target devices. We’re going to walk through a number of use cases, but in all of them, the model stays the same: Virtualize, store, and stream.

Provisioning Server For Desktops Using Citrix Provisioning Server for Desktops OS-streaming functionality, two Virtual Disks are created – one configured with the Windows XP operating system and software and one with Windows Vista and software. The vDisks are stored as files on the network.

Provisioning Server For Desktops LAN-connected “diskless” workstation. No software pre-loaded and the system is configured to boot from the network.

Provisioning Server For Desktops The XP operating system and software vDisk is streamed to the desktop using Citrix Provisioning Server for Desktops OS-streaming functionality. Workstation is powered on.

Provisioning Server For Desktops Workstation image delivery and management are centralised; data security is assured because there is no persistent storage at the desktop. PC processing power is harnessed for an uncompromised user experience.

Provisioning Server For Desktops Workstation image delivery and management are centralised; data security is assured because there is no persistent storage at the desktop. Provisioning the workstation with the Vista vDisk is quickly accomplished by rebooting.

PXE Booting a Provisioning Services Target DHCP Server IP Info IP Info IP Info Target Device 1 Provisioning Services Workloads DHCP Discover BOOT A Target Device 2 TFTP PXE Network Storage B Provisioning Services allows multiple end points, be it Virtual machines, or physical to boot off of a single image using the PXE Protocol. When a PXE Enabled Target boots it will send out a DHCP Discover packet, [CLICK] Both the DHCP AND Citrix PXE Service will respond with offers, DHCP will send the IP information and the PXE Service will reply with the hostname/IP of the TFTP server and the bootstrap file name. [CLICK] The target will then download the Bootstrap file from the TFTP Server [CLICK] and begin streaming the image. The bootstrap can also be loaded by booting to a ISO file via the BootDevice manager. Bootstrap Bootstrap Bootstrap PXE Info PXE Info PXE Info Target Device 3

Failover & Login Process 1.1.1.1 StreamServer 1.1.1.3:vDisk3 PVS Target Device Login Process 1.1.1.2 Streaming from 1.1.1.4 Request for vDisk3 This slide is going to show exactly what happens when a target device fails over. The Target is up and streaming from 1.1.1.4. [CLICK] 1.1.1.4 becomes unresponsive. Target refers to the bootstrap for other options. The Target will try to contact the first server in the bootstrap. In this case 1.1.1.2 Target will go through the login process, authenticating with the MAC address and requesting vDisk assignment exactly as it would if it was booting for the first time. In this example the Target is assigned vDisk3 streaming from Server 1.1.1.3. The Target connects to 1.1.1.3 and requests vDisk3. Failover is accomplished. Bootstrap 1.1.1.2 1.1.1.1 1.1.1.3 X 1.1.1.4

Load balancing with High Availability (cont) PVS2 PVS1 X If a PVS Server goes down [CLICK] all the targets connected to that server will failover. Once the down PVS Server comes back up however, those targets will not automatically rebalance. They will stay connected to the server they are on until a rebalance command is sent. All newly booted Targets will stream to PVS1.

Where to store the cache file in a HA environment Cache on local RAM Cache on Server Disk Cache on Local Disk Another factor to consider when designing a High Availability solution is where to store the cache files. There are three options to storing cache: Cache on Local Ram, Cache on Server, Disk, Cache on local Disk. We will discuss the pros and cons of each of them in regard to High Availability. The main thing to keep in mind when choosing the cache location is that the cache needs to be available to both servers so in the event of a failover the Target Device can still access it’s cache file.

X Cache on Local RAM Shared Storage PVS1 PVS2 Cache vDisks If caching on local RAM the amount of RAM allotted needs to be large enough to support the target device between reboots. If it is not it the Target Device will run out of cache space and eventually bluescreen. In this slide the two Targets to the left are booted to PVS1 the two on the right are booted to PVS2 [CLICK] If PVS1 experiences an outage the two targets on the left will failover to PVS2 and still have access to their cached information. Pros: Ram cache has very quick read/write times Cons: Ram is expensive and in some environments it is impractical to load the extra memory into the end point devices. Cache vDisks SQL database

X Cache on Local Disk Shared Storage PVS1 PVS2 Cache vDisks In this slide the two Targets to the left are booted to PVS1 the two on the right are booted to PVS2 [CLICK] If PVS1 experiences an outage the two targets on the left will failover to PVS2 and still have access to their cached information Hard Drive needs to be formatted with at least 1GB of free space. PVS will use the first Hard Drive that matches these requirements. If multiple local hard drives are installed there is no way to configure PVS to cache on a certain drive. Pros: Most end point devices already have a local hard drive which would make local hard drive caching cost effective. No extra shared storage space is needed for the cache file. Less traffic on the network. Less strain on the Provisioning Servers Cons: Some thin clients do not have local hard drives. Cache vDisks SQL database

X Cache on Server Disk Shared Storage PVS1 PVS2 Cache vDisks In this slide the two Targets to the left are booted to PVS1 the two on the right are booted to PVS2 [CLICK] If PVS1 experiences an outage the two targets on the left will failover to PVS2 and still have access to their cached information Pros: Cache in one centralized location Cons: All reads and writes are sent through the provisioning server reducing performance. Large Shared storage solution is required. Larger strain on network since all of the cache reads and writes are going over the network. Cache vDisks SQL database

Cache on Server Disk (incorrect configuration) Shared Storage PVS1 PVS2 X In this slide the two Targets to the left are booted to PVS1 the two on the right are booted to PVS2 [CLICK] If PVS1 experiences an outage the two targets on the left will failover to PVS2 but do not have access to the write cache. Eventually the Target Device will attempt to access critical information written to the cache file and will bluescreen. Cache vDisks SQL database

Possible single point of failure Shared Storage PVS1 PVS2 DHCP PXE TFTP High Available provides failover for the Streaming Service only. Single points of failure could still exist that will effect the employment. Previously slides showed a high level very simple view of a provisioning server deployment, focusing on the target devices, Provisioning Servers and shared storage. Provisioning Server solution relies on other components as well. High Availability only provides failover for the streaming service. All other components need to be setup with failover separately. In this section we are going to talk about these components and the options. [CLICK] These componets are DHCP PXE Server TFTP And the Network. Switch Cache vDisks SQL database

Possible single points of failure TFTP Network Storage Bootstrap Delivery TFTP, Network, Storage and bootstrap delivery could be single points of failure if not configured properly.

TFTP Redundancy DHCP Option 66 only allows for one TFTP server to be entered. Using TFTP Clustered Servers or PXE Service instead of DHCP options will solve this issue. This slide is going to talk about possible ways of setting up redundant TFTP. If using DHCP and want fully available TFTP a load balancer such as (netscaler glsb) must be used to make the TFTP highly available. This is not needed if instead of using DHCP, PXE is used since multiple PXE Services can run on the same network.

Network Redundancy Target Device PVS Server Target Device PVS Server Switch PVS Server Target Device This slide is going to talk about possible ways of setting up redundant networks: PVS is only as redundant as the network it is running on. NIC Teaming Load Balancing Switches and routers with failover Dual connections to backend storage with multiple paths.

Storage Redundancy Type of Storage Pros Cons CIFS on Windows Server Easy to setup Free with OS Hard drives are cheap Performance due to SMB traffic Lack of scalability HA requires two plus servers CIFS on NAS Device Device typically less expensive than SAN device Built in redundancy for disks (depends on vendor/model) Various vendors/models Less expensive solutions equal single point of failure Scalability can be an issue depending on vendor/model purchased This slide is going to talk about possible ways of setting up redundant storage: Clustered File Systems

Storage Redundancy (continued) iSCSI to NAS Device Moderate to setup Device typically less expensive than SAN device Built in redundancy for disks (depends on vendor/model) Various vendors/models offer resiliency benefits Less expensive solutions equal single point of failure Scalability can be an issue depending on vendor/model purchased Requires cluster file system when sharing LUN across multiple servers iSCSI to SAN Device Highly scalable Built in resiliency Build in features like storage replication and high performance disk arrays Moderate to complex to setup Typically more expensive than NAS devices This slide is going to talk about bootstrap Delivery redundancy. DHCP Clustering Multiple PXE Servers

Storage Redundancy (continued) Fiber to SAN Device Highly scalable Built in resiliency Build in features like storage replication and high performance disk arrays Complex to setup Typically more expensive than NAS devices Requires cluster file system when sharing LUN across multiple servers This slide is going to talk about possible ways of setting up redundant storage: Clustered File Systems

Bootstrap Delivery Redundancy Solution Pros Cons DHCP Clustering Less traffic on the network Moderate to setup Multiple servers needed More expensive Multiple PXE Servers Easy to setup Less hardware needed. More broadcast traffic on the network This slide is going to talk about bootstrap Delivery redundancy. DHCP Clustering Multiple PXE Servers

Soluzione per UNIMI - Centralized HA per LAB Target Devices Provisioning Servers Centralized HA stores the vDisks on shared storage: Easier to manage, all vDisks are in one location only requiring one vDisk to be updated to make a change. Requires shared storage. More network traffic then distributed. Target Devices vDisks Shared Storage

Soluzione per UNIMI completa LAB 2 2 provisioning servers & 50 Target Devices LAB 1 – 50 Target Devices Target Device 1 LAB 3 – 2 provisioning servers & 10 Target Devices + 10 Remote Desktop Linux Provisioning Services Workloads A Target Device 2 Network Storage B Provisioning Services allows multiple target devices physical and virtual, to boot off of one streamed image saving greatly on management and storage costs. Pxe Options can also be used. ................................. HA Target Device 50

Proposta commerciale: LICENSING - Lab1: 50 licenze XenDesktop Platinum per user - Lab2: 40 licenze XenDesktop Platinum per user - Lab3: 10 licenze XenDesktop Platinum per user

Proposta commerciale: PROVISIONING SERVERS (1) Lab1: 50 users (licenze citrix + 1y di sw assurance) 8.750,00 € (subscription ~ 60$ x lic) 2 Server reali con XenSever in HA 6.600,00 € 2 Server virtuali con Provisioning Sever 5.6SP1 - Lab2: 40 users (licenze citrix + 1y di sw assurance) 7.000,00 € (subscription ~ 60$ x lic) - Lab3: 10 users (licenze citrix + 1y di sw assurance) 1.750,00 € (subscription ~ 60$ x lic) 2 Server virtuali con XenDesktop 5

Proposta commerciale: PROVISIONING SERVERS (2) 6 x Server Reali: DELL Server rack 1U PowerEdge R410   Processore: Processori 2x Intel Xeon E5506 Memoria: 24GB DDR3 1333MHz Sistemi operativi - Opzioni di virtualizzazione: Citrix®  XenServer®  HDD: 2x 146GB, SAS 3Gbps 15kRPM (hot plug) Controller RAID: PERC H200A Controller di rete: 6x Broadcom NetXtreme II 1GbE Alimentazione: Ridondante 500 W

Proposta commerciale: NETWORK STORAGE NetApp FAS2040-R5 24 x 450 GB (15K) 8 (4+4) porte 1 Gb 4 (2+2) porte 8 Gb Base Sw inclusi Licenza CIFS-NFS Garanzia 5y NBD 50.000,00€

Base pack comprende un set di funzionalità quali (Incluso) : Snapshot™, FlexVol®, Thin Provisioning, RAID-DP®, FilerView®, FlexShare® , iSCSI, FCP, SyncMirror NearStore®, Deduplication, System Manager, Operations Manager, HTTP, host utilities