Your SlideShare is downloading. ×
  • Like
  • Save
C3 Citrix Cloud Center
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

C3 Citrix Cloud Center

  • 1,291 views
Published

Citrix Cloud Center demo for CloudViews 2009 @ IPP.

Citrix Cloud Center demo for CloudViews 2009 @ IPP.

Published in Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,291
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Presentation Title Goes Here Insert Version Number Here © 2007 Citrix Systems, Inc.—All rights reserved.
  • Presentation Title Goes Here Insert Version Number Here © 2007 Citrix Systems, Inc.—All rights reserved.
  • Plase 1: Many issues. Commoditized hardware and one app per server model has created a monster. Average utilization of servers ~ 15% ( Source: Gartner) Space, power, cooling challenges abound. Nearly 80% of IT costs spent just to keep the lights on…let alone innovate. Etc… Phase 2: Virtualization begins to take root in test/dev. Benefits of consolidation starting to be seen for some production apps (“Craplications”) This is goodness. Phase 3: Virtualization beginning to be seen for more than just consolidation. Moving to more business and mission critical apps. HA and recovery (DR) become focus areas. Virtualization seen as a way to eliminate planned downtime. Again, more goodness… Phase 4: Goes beyond “Agility” to policy based computing and new ways (paradigms) to deliver apps. Applications may become largely streamed and diskless. More “Utility-like” Virtualization is a key enabler and begins to become pervasively adopted. BUT… reality is that very few severs (even today) are virtualized. We’re still a long way off from seeing pervasive adoption of virtualization. Still in the low teens. (see next slide…) 79% of IT budget to keep the business running Source: Gartner Server sprawl, electricity, floor space Managing too many physical servers
  • We must first start with the underpinnings of XenServer and that’s the Xen hypervisor. Leverages Open Source standard Lean with < 50K lines of code Work closely with OS vendors and advisory board: Citrix, IBM, Intel, HP, Novell, Red Hat and Sun Microsystems Community patches, updates and enhancements Security CIA and NSA actively contribute to Xen XS Differentiation from Xen Open Source Management console; XenMotion; Templates; Optimization
  • XenMotion. Check. Got it.
  • XenServer supports several features to guarantee service uptime in the event of infrastructure failure. Firstly, resource pools can be configured for automated high-availability. This deals with individual host failures by restarting VMs that were running on that host onto the next available machine in the resource pool. Notable features include: Peer-to-peer "self-healing" architecture ensures there is no single point of management failure. Set VM restart priorities individually, to control the order in which services are restarted in the event of host failure. Dynamic failure planning algorithms allow administrators to see how many hosts failures can be tolerated without compromising services. Presentation Title Goes Here Insert Version Number Here © 2007 Citrix Systems, Inc.—All rights reserved.
  • VM’s on failed physical servers can automatically be restarted on other servers in the pool
  • From an architectural point of view, a XenServer virtual machine (VM) consists of two components: metadata describing the virtual machine environment, and the virtual disk image (VDI) which is being used by the virtual machine. The VM metadata is stored in a small database on the XenServer hosts, and the virtual disk images are stored on the configured Storage Repository, which in multiple host deployments will be a NAS or SAN device. The metadata for a VM contains information about the VM (e.g. name, description, uuid), VM configuration (e.g. amount of virtual memory, number of virtual CPU’s) and information about the use of resources on the host or Resource Pool (e.g. Virtual Networks, Storage Repository, ISO Library).
  • To provide effective Disaster Recovery (DR), we need to replicate both the metadata and the virtual disk images from our production environment to our DR environment. This is easily accomplished by exporting the metadata from the production environment, and importing this data into the DR environment. The replication of the virtual disk image is best handled by the storage vendor, as they will vary from device to device, but any real-time or scheduled replication system will suffice. Later on during this presentation we will hear a little bit more about which solutions NetApp can offer.
  • Even if you are not using remote storage you can backup VMs and move them around using our import/export functionality. Again since the VMs are isolated from any hardware differences between the underlying servers you remove all of the driver headache found when moving a physical OS instance around to different boxes.
  • Presentation Title Goes Here Insert Version Number Here © 2007 Citrix Systems, Inc.—All rights reserved.
  • With virtual desktop delivery we can provide desktops as a service to the users.
  • How XD works is essentially quite similar to how end users connect to XenApp. The end user will get to the landing page shown earlier and enter their credentials at which point, the request for the desktop are sent to the delivery controller. The delivery controller then works out which desktop is appropriate for the end user. It establishes that from the data store. What it does then is to set up the environment for the end user to connect to. If it’s a provisioned desktop (the way that we’ve recommended that you implement the product) and the environment is not already spun up, it will initiate a boot of the virtual machine and the operating system will be delivered from Provisioning Server. In the setup for XD, you have an alternative option to eliminate the startup delay for the end user. You can do this by configuring that for particular desktop groups, you want to specify an idle pool. From marketing perspective, this will be known as an ‘instant on’ capability. What that really means is that on the backend, we can have the virtual machines pre-launched such that when the user connects, they get an instant on experience. The way that this is configured on the desktop delivery controller is for each group, you specify the range of time you want a specific number of idle machines available. For example you can say that from 9am to 5pm you want 15 machines spun up and ready for use, where as outside of working hours, you bring it down to 2 or 3. Then the Desktop delivery controller will manage your infrastructure accordingly so that the user gets an instant on experience. That integration is only available for virtual machines at launch, but an SDK will be coming later on for customers to modify that for support with blades. We’re going to introduce blade support as we move forward in upcoming releases. Once the VM has been started, we send a preparation for connection to the VDA (the thing that delivers the ICA experience from the virtual desktop). The VDA resides on the virtual desktop. Its not always waiting for a connection. From a security perspective, we wanted to be able to control when you’d be able to connect to those virtual machines. Not until an end user authenticates and the desktop delivery controller sends a preparation message to the VDA that you can connect to a virtual machine using ICA. This is a nice security feature that we’ve implemented to control who can access the virtual desktop and when. What happens then is that the Desktop Receiver connects to the VDA. What's important about this is that clearly unlike the first release of DS v1, this is a direct ICA connection to whatever the virtual desktop is running on, virtual machine or the blade. This is a direct ICA experience just like customers are used to with XenApp. What we do then is that we validate through examining a ticket that was previously created, whether that is the right user that is supposed to be connecting to the virtual machine and if that is not correct, we drop the connection. We consume a license (XenDesktop will be licensed on a CCU basis, just like XenApp). Then we implement policies for the way that that ICA connection is delivered. This is the point at which we would in XenApp say which apps are available. In XenDesktop this is the point at which we control policies like the ‘end user is able to map drives from the local machine’. We have full support for the policies that customers are familiar with in XenApp as well as the SmartAccess capabilities of the AG product line. That is when those policies would be implemented. That is essentially how XD works.
  • Just like we described in the whiteboard discussion, the traditional way of doing it is to load everything onto individual desktops or laptops – all the client software of client/server applications, the desktop applications, the web clients, etc. This is costly to manage and support in this distributed fashion – never mind trying to secure it on the endpoints, lock down devices, ensure client-side compatibility, etc. So, rather than “deploy” applications, “deliver” them using Presentation Server and its application virtualization and application streaming features.
  • With application virtualization, those applications are centralized – the application is no longer installed on the endpoint, instead it is installed on servers in the data center, where you can monitor, control, update and secure them. The client device doesn’t actually need to process the application at all – freeing the application from client-side dependencies altogether. This is why we call this virtualization.
  • Presentation Title Goes Here Insert Version Number Here © 2007 Citrix Systems, Inc.—All rights reserved.
  • The power of OS Streaming technology is more evident the wider it gets deployed. Simplifies intractable problems. Now, rather than having dedicated back up sites, multiple sites can back up to the same datacenter. This creates big savings.
  • Presentation Title Goes Here Insert Version Number Here © 2007 Citrix Systems, Inc.—All rights reserved.
  • The purpose of today’s HOT session is to update the environment for a fictitious company named SNR, inc. This slide represents the current environment. Remote employees have access to the internal network through an IPSec VPN. This works but there is no way to enforce conditional access. Everyone that logs in through the IPSec VPN receives the same level of access.
  • SmartAccess is not a feature but rather a concept. SmartAccess incorporates the following: Who is connecting? Access Gateway uses EPA scans to determine various characteristics about a client device. What is the result of the connection? Once users are authenticated, will they receive a full VPN connection, clientless access, Web Interface/Published Applications, etc? What resources can be accessed? Will users receive full access to internal network resources or only a subset of resources? How will users be able to access these resources (published apps only, FTA, etc.)?
  • Here is an example of providing different levels of access, based on the results of client security scans. Here, if the user doesn’t have Windows XP they are denied. Full access is given to PC’s with Prism, Symantec, a particluar registry key, and are running XP. Access is reduced as the users have fewer of these components.
  • In most environments the communication between the AGEE and the backend servers would be as follows: Communication to the DNS and Authentication Server will occur in most topologies using the Netscaler IP. In this example, we are using LDAP or LDAPS which means we need 389 and 636 open from the DMZ to the private network. Communication to the Web Interface and XenApp Servers will occur using the Mapped or Subnet IPs. Typical ports required at the firewall for allowed access will be 80, 443, 1494, and 2598. Last, management traffic generally comes from an internal device to the NSIP. Initially users will connect over 80 or 443 to the NSIP, but once the java administration applet has luanched connections will occur over 3010 for unsecure and 3008 for secured. Depending on whether you connected to HTTP or HTTPS initially will determine if the actual management connection is secured or not.
  • Presentation Title Goes Here Insert Version Number Here © 2003 Citrix Systems, Inc.—All rights reserved. Important points to remember: WI can point to any vpn vserver, not necessarily the one where users connect. WI must be able to resolve the FQDN of the virtual server WI must be able to route to the virtual server IP of HTTPS WI must trust the SSL certificate from a machine level.
  • The Access Gateway Wizard can be used to create/edit virtual servers, bind certificates, configure DNS/WINS settings, configure authentication settings, specify default authorization settings and access scenarios.
  • Presentation Title Goes Here Insert Version Number Here © 2007 Citrix Systems, Inc.—All rights reserved.
  • Availability The Workflow Studio platform is available as a feature of the Citrix Delivery Center. All customers of XenApp, XenDesktop, XenServer, and NetScaler current on SA for all editions except the Express Editions will be able to download from MyCitrix.
  • Workflow Studio builds on the capabilities of Workflow Foundation and PowerShell. Workflow Foundation provides the Visual Designer, the base activity library functionality, and runtime services. Workflow Studio extends each of these to target an IT Professional. Workflow Studio also melds Workflow Foundation with PowerShell, providing native support for PowerShell activities (not available yet in Workflow Foundation.) Starting at the bottom: Automation is desired for a product or a group of products (both Citrix and 3 rd party) Products expose functionality through an API Activity Libraries expose this functionality to a workflow developer Workflows can be created that solve business problems Activity libraries can be implemented as a raw translation of the product API, but this is not the most usable method. Some thought needs to be put into what we expect customers to do with a workflow. We have built support for Snippets into the core product to help facilitate this process, but these activity libraries still need to be ‘designed’.
  • Let’s review the list of activity libraries that are available today for Workflow Studio. Many Windows systems are supported today: Active Directory and Group Policy libraries provide the building blocks necessary for user provisioning and rights management The Networking library provides the ability to do remote shutdown of your Windows servers and desktops as well as supporting WakeOnLAN for power on technology The Windows and WMI libraries offers a broad range of activities for typical Windows OS management. Reading from the Windows Registry, querying performance counters, manipulating files, and accessing any data exposed via WMI The PowerShell library exposes the functionality of PowerShell, and in particular allows you to import and export CSV files Initial Citrix libraries are available for XenApp, XenServer, and NetScaler today with XenDesktop support and deeper integration with product sub-features (like Provisioning Server and StorageLink) coming soon. An SDK is also available if you want to build your own libraries to integrate with other products.
  • Presentation Title Goes Here Insert Version Number Here © 2007 Citrix Systems, Inc.—All rights reserved.

Transcript

  • 1. Citrix Cloud CenterRui Miguel LopesSystem Engineer – Albora Soluciones
  • 2. Agenda  Conceitos e Componentes do C3  Xenserver – Virtualização de Servidores  Virtualização e Provisão de Desktops  Virtualização de Aplicacões  Acesso Remoto e gestao de tráfego  Automação do datacenter  Resposta em cenários de contingência © 2008 Citrix Systems, Inc. — All rights reserved 2
  • 3. C3 - Citrix Cloud Center
  • 4. Service delivery infrastructure for hosting, managing and delivering cloud-based services © 2008 Citrix Systems, Inc. — All rights reserved 4
  • 5. Laboratorio IPP : my.cloudcenter.demo ZONA “PUBLICA” REDE DATACENTER 172.17.41.0 /24 10.20.0.0 /16 Xen50-alb03 Xen50-alb02 10.20.30.253 10.20.30.252 PvS DC 10.20.40.150 10.20.30.100IP WAN Xendesktop vDesktops 10.20.40.140 10.20.40.[1...50] Xenapp50 10.20.40.160 workflow web1porto 10.20.40.170 10.20.50.1 web2porto 10.20.50.2 AGEE-Porto Vip: 172.17.41.5 AGEE-Lisboa Vip: 172.17.41.5 © 2008 Citrix Systems, Inc. — All rights reserved 5
  • 6. Saber mais : Citrix C3 Lab online• Citrix Developer Network • Comunidade de desenvolvimento para soluções Citrix • Aplicação de diferentes tecnologias numa prespectiva de cloud computing http://community.citrix.com/• Citrix C3 Lab @ Amazon • Recurso recentemente publicado • Cenário de laboratório e investigação • Provisão de serviços na nuvem http://community.citrix.com/pages/viewpage.action?spaceKey=cdn&title=Citrix+C3+ © 2008 Citrix Systems, Inc. — All rights reserved 6
  • 7. Citrix XenServer(Hipervisor e consola de administração)
  • 8. D a ta c e nte r E v o lu t io n P ha s e 1 – P has e 4 – P has e 2 – P has e 3 – R e c o g n iz e D y n a m ic C o n s o lid a t e A g ilit y D a ta c e nte rUnder utilized Test/Dev Some tier 1 Dynamic Workloadhardware applications Delivery EncapsulationIncreasing costs of High Availability Automation / Policyownership Consolidation Disaster Recovery Chargeback / UtilityDifficult management “Craplications” Mobility PervasiveBarriers to expansion Virtualization © 2008 Citrix Systems, Inc. — All rights reserved 8
  • 9. W h a t is X e n ?• Native 64-bit hypervisor• Runs on bare metal• Widely-deployed at tens of thousands ofsites• Optimized for hardware-assisted & S un C it r ixparavirtualization HP C it r ix• Highly secure Xen open securityframework In t e l IB M• Small exposure footprint• Lightweight and efficient © 2008 Citrix Systems, Inc. — All rights reserved 9
  • 10. XenMotion enables zero downtimeDevice Drivers Device Drivers Device DriversXenTool Stack XenTool Stack XenTool Stack Xen Hypervisor Xen Hypervisor Xen Hypervisor Bare Metal Hardware Bare Metal Hardware Bare Metal Hardware Remote VM guest storage © 2008 Citrix Systems, Inc. — All rights reserved 10
  • 11. High Availability• Automatically restart VMs upon host server failure• Easily administered within XenCenter• Reports failover capacity © 2008 Citrix Systems, Inc. — All rights reserved 11
  • 12. High Availability Shared StorageVIDEO © 2008 Citrix Systems, Inc. — All rights reserved 12
  • 13. Disaster Recovery – Virtual Machine • From an architectural point of view a VM exists of: • Metadata and Virtual Machine • Virtual Disk Image(s) XenServer Host • Metadata is stored in a database Metadata on the hosts: • VM Name, Description, uuid • Virtual Memory, vCPUs • Virtual Networks, SR, etc. VDI1 VDI2 Storage Repository • VDIs are stored on storage array © 2008 Citrix Systems, Inc. — All rights reserved 13
  • 14. Disaster Recovery • Storage Replication is out-of-band • Use vendor specific instructions for Storage Replication • Metadata export and import done from CLI /script Production Environment Disaster Recovery Environment XenServer Host XenServer Host Export/Import Metadata Metadata VDI1 VDI2 VDI1 VDI2 Storage Replication Storage Repository Storage Repository © 2008 Citrix Systems, Inc. — All rights reserved 14
  • 15. Simplifying Disaster Recovery1 Automated backup of VM metadata to SR 42 Replication of SR includes Virtual Disks and VM metadata 1 33 Attach replicated SR4 Restore of VM metadata 2 Shared Storage Shared Storage will recreate VMsVIDEO: 7:30 Production Site DR Site © 2008 Citrix Systems, Inc. — All rights reserved 15
  • 16. XenDesktop & XenApp(Desktops & WinApps as a Service)
  • 17. Desktop as a Service© 2008 Citrix Systems, Inc. — All rights reserved 17
  • 18. How Do XenApp and XenDesktop Complement Each Other? XenApp for Virtual Desktops Virtual Desktop Apps virtual delivery User protocol Settings Use O Data rs S Center On-demand AssemblyDelivered Dynamically Single master with best assembled at image of each user runtime componentexperience © 2008 Citrix Systems, Inc. — All rights reserved 18
  • 19. How XenDesktop Works Desktop Delivery Controller request license A D Login Page Licensing Data DomainO U Store Controller ch policies find desktop un la validate & gn si ICA prepare resume ProfilesDesktop Receiver Xen, Hyper-V, VM Apps Golden Image: •PV Tools •Virtual Desktop Agent •ICA & Streaming Client OS VDisk © 2008 Citrix Systems, Inc. — All rights reserved 19
  • 20. Protocolo ICA• Largura de banda optimizada : 5-10 Kbps. (kilobits por segundo)• Normalmente estabelece-se uma média de 20 Kbps por utilizador © 2008 Citrix Systems, Inc. — All rights reserved 20
  • 21. Implementação Windows Tradicional 16-bit/32-bitClient components Server component Web apps Desktop apps Custom apps Web Browser Data Center Desktop Gestão e suporte dispendioso. Pouco Seguro Limitado na acessibilidade © 2008 Citrix Systems, Inc. — All rights reserved 21
  • 22. XenApp - Virtualização de Applicações Server component Client component Web apps Web browser Custom apps Desktop apps Data Center Application Servers Presentation Server environment Desktop Centralização do host no data center Fácil de instalar, gerir e suportar Apps e dados protegidos © 2008 Citrix Systems, Inc. — All rights reserved 22
  • 23. Why Separate Apps?Integrated App Delivery – Streamed Applications Application Profile Streamed Application XenApp for Virtual Desktops Isolation Environ ment  Centralized application management XenDesktop  Apps streamed to the Applications are leverage CPU/RAM of virtual desktop desktop Applications execute locally in  Best for common productivity apps with isolation moderate CPU/RAM requirements Applications can be used offline © 2008 Citrix Systems, Inc. — All rights reserved 23
  • 24. Independent Validation by Tolly Group & EntisysSeparating Apps and Desktops SAP running on SAP hosted virtual desktop on XenApp Server Dual quad core, Dual quad core, 32GB RAM 32GB RAM RAM required per 1GB 512MB desktop CPU utilization 85% 85% © 2008 Citrix Systems, Inc. — All rights reserved 24
  • 25. Saber Mais: Virtualização de Aplicações• Download XenApp 5.0 (versão trial – 30 dias) http://www.citrix.com/English/ps2/products/subfeature.asp?contentID=1680656• Demos Online http://citrix.com/English/ps2/products/demo.asp?contentid=186• Documentação XenApp 5.0 Win2003: http://support.citrix.com/product/xa/v5.0_2003/ Win2008: http://support.citrix.com/product/xa/v5.0_2008/• Forums de suporte (XenApp 5.0) http://forums.citrix.com/category.jspa?categoryID=151 © 2008 Citrix Systems, Inc. — All rights reserved 25
  • 26. Provisioning Server(provisão e gestão de workloads - OS)
  • 27. Delivering Native and VirtualizedWorkloadsSilo One A Citrix Provisioning Server BSilo Two CSilo Three Image repository holds Virtual Hard Disks Servers are configured for network boot. No local storage required © 2008 Citrix Systems, Inc. — All rights reserved 27
  • 28. “Any Workload, Any Server, Any Time”Silo One XenServer / Hyper-V A Citrix Provisioning Server BSilo Two CSilo Three Virtual Hard Disks are streamed from image repository Boot hundreds of VMs/servers from © 2008 Citrix Systems, Inc. — All rights reserved 1 image 28
  • 29. Managing Disaster Recovery Primary Data Center Backup Data Center XenServer / Hyper-V XenServer / Hyper-V XenServer / Hyper-V Backup 2 3 1 Site host Server servers Failure Failure real workloads Storage ReplicationProvisioning Server Network Provisioning Server Network Storage StorageVIDEO © 2008 Citrix Systems, Inc. — All rights reserved 29
  • 30. Access Gateway Entreprise(Segurança no acesso a recursos)
  • 31. Existing Remote Access Scenario Remote DSL/Cable Firewall Datacenter Employees Connection IPSec VPN Madison, s WI Citrix XenApp Web Interface © 2008 Citrix Systems, Inc. — All rights reserved 31
  • 32. What is Citrix SmartAccess™? Who is connecting? What is the result What resources of the connection? can be accessed? Which User What Device VPN Access Clientless Web and FileNetwork Level Access Server Access Access What What Web Interface XenDesktop Outlook Web XenApp Authentication Location XenApp Access XenDesktop Resources Endpoint Analysis Session Policy Session and Authentication Policy Authorization Policy © 2008 Citrix Systems, Inc. — All rights reserved 32
  • 33. All Applications Reduced Applications Denied Access & Virtual Channels & Virtual Channels Full Network Access Restricted network Access+ + + Full Access + + Reduced Access + Restricted Access Clientless Portal and SnR Security + Email Access Remediation Web Site Global Access © 2008 Citrix Systems, Inc. — All rights reserved 33
  • 34. XenApp Integration External DMZ Internal DNS 53 (UDP) LDAP/ IP 443,80* (HTTP/ NS LDAPS TCP) P NSI 389/636 Web Interface (TCP) VIP SNIP or MIP Remote End User 80, 8080, 443 (HTTP/TCP) 1494, 2598 (TCP) XenApp NS* Port 80 used for https IPredirect 443,80 (TCP/HTTP) 3010, 3008 ,22 (TCP) © 2008 Citrix Systems, Inc. — All rights reserved 34
  • 35. Accessing XenApp with Access Gateway 1. User accesses https://agee.corp.ctx Web 2. Access Gateway authenticates the 4) HTTPS 3) HTTP(S) Interface user and validates the end-point 1) SSL 3. Access Gateway communicates the 8) SSL 9) X 6) XML user credentials and policy conditions Access 10) ML to Web Interface Gateway ICAClient 4. Web Interface displays the user’s set XenApp of applications. Farm 5. User clicks an application icon 6. Web Interface requests a ticket from the Secure Ticket Authority 7. Web Interface sends a ticket to the user in a ICA ® file 8. The ICA client launches and sends secure ICA traffic to Access Gateway 9. Access Gateway validates the ticket against the STA 10. The ICA session is established © 2008 Citrix Systems, Inc. — All rights reserved 35
  • 36. © 2008 Citrix Systems, Inc. — All rights reserved 36
  • 37. Automação do Datacenter(Automação do datacenter)
  • 38. Workflow Studio Workflow Studio SSL 001000111010101 SSL 001000111010101 SSL 001000111010101 SSL 0011010101 SSL 001000111010101 Receiver Branch Access Repeater Gateway • Graphically compose workflows without scriptingUsers • Automate IT processes across technology components • Dynamically orchestrate systems to deliver on- demand © 2008 Citrix Systems, Inc. — All rights reserved 38
  • 39. Availability Available to All Customers of All Products in Citrix Delivery Center • XenApp • XenDesktop • XenServer • NetScaler © 2008 Citrix Systems, Inc. — All rights reserved 39
  • 40. Technology WorkflowStack Activity Libraries Product APIs Web PowerS VBScr W Service hell ipt MI s Citrix Products 3rd Party Products XenApp XenDesktop XenServer NetScaler © 2008 Citrix Systems, Inc. — All rights reserved 40
  • 41. Available Activity Libraries • XenApp • Active • XenServer Directory • NetScaler • Group Policy • Networking • Windows / WMI • PowerShell © 2008 Citrix Systems, Inc. — All rights reserved 41
  • 42. The Citrix Delivery Center in Action Citrix Workflow Studio Citrix XenServer Pool A Unpowered, bare Metal servers Citrix NetScaler Pool B Monitor Decide Act © 2008 Citrix Systems, Inc. — All rights reserved 42
  • 43. Global Site load balancing(Gestão de tráfego e alta disponibilidade comNetscaler)
  • 44. What Is GSLB?• DNS-based technology that uses an authoritative DNS service to direct users to an appropriate instance of an application using its Fully Qualified Domain Name (FQDN)• Distributes network traffic and server load across multiple sites based upon service availability © 2008 Citrix Systems, Inc. — All rights reserved 44
  • 45. NetScaler GSLB• NetScaler Monitors• Server Response, Service Availability, Service Response: • NetScaler Verifies applications are responding correctly at each site• Eligibility of Site for GSLB distribution: • NetScaler excludes site from distribution if application is not completely available © 2008 Citrix Systems, Inc. — All rights reserved 45
  • 46. How NetScaler GSLB Works1. Client makes a DNS Request for the GSLB domain What site should I go to?2. NetScaler GSLB ADNS returns the IP address of the mostsuitable site Go to site number 3.3. Client makes network connection to the ADNS specified IPaddress Site 1 Site 2 Site 3 © 2008 Citrix Systems, Inc. — All rights reserved 46
  • 47. GSLB Distribution Methods• Basic • Round Robin • Weighted Round Robin• Geographic Proximity • IP - Location• Network Proximity • Least Return Trip Time• Disaster Recovery • Passive © 2008 Citrix Systems, Inc. — All rights reserved 47
  • 48. Distribution: Round Robin Datacenter 1 Datacenter 1 Site Up: Active Site Up: ActiveRound Robin 33% 50%• Requests are distributed evenly across all sites in round-robin fashion Datacenter 2 Datacenter 2 Site Site Down Up: Active 33% 0%• If site goes down, the other sites automatically receive the remaining traffic Datacenter 3 Site Up: Active 50% 33% © 2008 Citrix Systems, Inc. — All rights reserved 48
  • 49. Distribution: Weighted Round Robin Datacenter 1 Site Up: ActiveWeighted Round Robin 50% Weight: 5• Site traffic distributed based on administrator configured weights Datacenter 2 Site Up: Active• Site capacities or cost of operations dictate distribution models 20% Weight: 2 Datacenter 3 Site Up: Active 30% Weight: 3 © 2008 Citrix Systems, Inc. — All rights reserved 49
  • 50. Distribution: Disaster Recovery Datacenter 1 Datacenter 2• Sites set up in Site Up: Passive active/passive mode Site Up: Active• All traffic routed to active site until it becomes unavailable• Passive site assumes active role when Datacenter 2 Datacenter 1 primary site is unavailable Site Down Site Up: Active © 2008 Citrix Systems, Inc. — All rights reserved 50
  • 51. OBRIGADO! Rui Miguel Lopes rlopes@ingrammicro.pt +351 91 414 3083 mai2009© 2008 Citrix Systems, Inc. — All rights reserved 51