intel® cloud builders guide to cloud design and deployment ... › content › dam › www ›...

20
Intel® Cloud Builders Guide to Cloud Design and Deployment on Intel® Platforms Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge Audience and Purpose For enterprise IT professionals looking to move data, applications, or integrated solutions from the data center to the cloud, it is often useful to start with the knowledge and experience gained from previous work. This document addresses Cloud On-Boarding which is one of the key aspects of the VM Interoperability Usage Model as defined by the Open Data Center Alliance. This reference architecture describes cloud on-boarding and why it is important. The paper discusses on-boarding considerations, as well as the key software tools and applications to make the effort successful. Finally, the paper presents an example of on-boarding a complex application in the enterprise data center to an external cloud. This example is shown with detailed descriptions and screen shots. This paper should minimize the learning curve for moving enterprise applications to the cloud and highlight important issues to consider before undertaking cloud on-boarding. Published September 2011 Intel® Cloud Builders Guide Intel® Xeon® Processor-based Servers Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge Intel® Xeon® Processor 5500 Series Intel® Xeon® Processor 5600 Series

Upload: others

Post on 05-Jul-2020

4 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

Intel® Cloud Builders Guide to Cloud Design and Deployment on Intel® PlatformsCloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Audience and PurposeFor enterprise IT professionals looking to move data, applications, or integrated solutions from the data center to the cloud, it is often useful to start with the knowledge and experience gained from previous work. This document addresses Cloud On-Boarding which is one of the key aspects of the VM Interoperability Usage Model as defined by the Open Data Center Alliance. This reference architecture describes cloud on-boarding and why it is important. The paper discusses on-boarding considerations, as well as the key software tools and applications to make the effort successful. Finally, the paper presents an example of on-boarding a complex application in the enterprise data center to an external cloud. This example is shown with detailed descriptions and screen shots. This paper should minimize the learning curve for moving enterprise applications to the cloud and highlight important issues to consider before undertaking cloud on-boarding.

Published September 2011

Intel® Cloud Builders GuideIntel® Xeon® Processor-based ServersCloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Intel® Xeon® Processor 5500 Series

Intel® Xeon® Processor 5600 Series

Page 2: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

Table of Contents

Executive Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

The Need for On-Boarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Typical Use Cases for Cloud On-Boarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Considerations for Cloud On-Boarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Implementation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Use Case Overview and Test Bed Blueprint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Software Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Technical Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Things to Consider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Additional Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Appendix A: NetScaler Cloud Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Appendix B: Software Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Endnotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Page 3: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

Executive SummaryMoving applications to the cloud can be complex, but upfront planning, useful migration tools, and experience can help simplify the process. Many factors must be considered when moving an application to the cloud: application components, network stack, management, security, and orchestration. Cloud on-boarding is the deployment or migration of data, applications, or integrated solutions of compute, storage, and network resources to a public, private, or hybrid cloud. On-boarding addresses business needs, such as a spike in demand, business continuity, and capacity optimization. Enterprises can use on-boarding to address capacity demands without the need to deploy additional infrastructure. Cloud on-boarding should be considered in the design of overarching, enterprise-wide, cloud infrastructure that supports internal, external, and federated clouds. It provides a very compelling usage for enterprises who want to maximize the elastic capabilities of cloud computing.

This paper summarizes a complete example of cloud on-boarding, as it demonstrates on-boarding of a CRM Web application from the data center to a private cloud. The exercise uses Citrix NetScaler Cloud Bridge technology. The CRM Web application is a self- contained application in a single virtual-machine (VM) workload with a Web server that includes a Web portal and a database. During the on-boarding process, the Web application server VM is migrated to the public cloud, and the all of the application components are migrated with the application. During the exercise, the most difficult step was the establishment of full network transparency between the data center and the public cloud. In short, we give system administrators a solution to move applications to the cloud seamlessly with minimum manual effort.

IntroductionCloud on-boarding is the deployment or migration of entire applications, or parts of applications (typically packaged as virtual machines) normally run on internal organizational compute resources, to another internal or external cloud in order to address a spike in demand, for business continuity or to optimize capacity.

Before an application can be successfully on-boarded into a cloud, several things must be taken into account. The application itself likely consists of far more components than will initially appear, and some of these components, especially those like directory services that are shared by other applications, likely cannot be moved to the cloud. Therefore, you must establish secure connectivity between the enterprise and the cloud data center. Additionally, you must ensure that mechanisms for applications running in the cloud can continue to use application components still residing in the enterprise. You must also consider the conversion—be it physical-to-virtual (P2V) or virtual-to-virtual (V2V)—from the way the applications run in the enterprise to how they will run within the cloud. As the application essentially runs across different data centers, you need centralized management mechanisms. The general premise of cloud on-boarding is to allow the cloud to act as an additional resource or extension of the data center for the following reasons:

• For occasions when the data center becomes overloaded by demand spikes

• For cost-effective capacity management and seamless load balancing

• For disaster recovery and failure mitigation

On-boarding provides the opportunity to scale not just based on basic aspects such as load, but on real world metrics such as the quality of experience and

service (QoS). Cloud on-boarding aligns the traditional safe enterprise computing model with cloud computing; it migrates into the cloud when necessary or accesses the cloud when additional compute resources are required.

The beginning of this paper presents the way cloud on-boarding can address specific needs. It then describes typical use cases for cloud on-boarding and general items to consider before on-boarding applications. Later the paper explains an on-boarding architecture, and how to implement on-boarding. A complete use case example of cloud on-boarding, including details of the setup and installation, follows, and the paper concludes with additional items to consider.

The Need for On-BoardingCloud on-boarding addresses three basic needs for an enterprise virtual data center.

First, companies rarely need additional capacity to handle demand spikes (which typically manifest as overload); investing internally to handle peak loads means investment in mostly unused capacity.

Second, companies are hesitant to move all infrastructures to a cloud-computing provider due to security and stability concerns. Cloud bursting, or the extension of the data center on demand based on policy that monitors load, QoS, and so on, alleviates some of the reluctance to shift to a cloud because it provides a hybrid model for enterprises. Cloud on-boarding is a pre-requisite for cloud bursting.

Third, companies occasionally have a need to migrate an executing workload from one cloud to another based on usage of resources and performance (network bandwidth, storage, management, security, and so on), in which case on-boarding is not triggered by load overflow;

3

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Page 4: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

instead there is a need for live migration to optimize the resource utilization.

Not all demand spikes on the enterprise virtual data center infrastructure are the same, and there are different characteristics that determine the spikes.

Periodic peaks. These occur multiple times during certain times of the year, for example, quarter finance close, and have two to four times the amount of loads. Peak-to-average ratio of load is three to four, and cloud bursting could be a good option.

Random peaks. These are hard to plan for, especially if the usage is long downloads like software bits, catalogs, pricing sheets, etc. Enterprises typically smooth these spikes out to enhance utilization and to reduce infrastructure costs. Migration to a cloud service provider helps to smooth the spike, and also potentially reduces costs.

One-time, unforeseeable events. These have unpredictable timing and amplitude. Launch of new products, special announcements, natural disasters, scandals, etc. can increase demand on enterprise Web sites and potentially create a “request surge” at the origin site. Similarly, time-sensitive events drive demand and produce load peaks, and the overflow capacity of the cloud can help.

Today, enterprises handle these by over provisioning the infrastructure. Enterprises can take advantage of on-boarding to the overflow capacity in the cloud, and avoid deployment of enterprise infrastructure for this aggregate demand.

Typical Use Cases for Cloud On-BoardingLet’s explore three typical use case scenarios for cloud on-boarding.

Use Case 1: On-boarding simple, self-contained applications or VMs: The migration and instantiation of a single,

integrated, virtualized application such as a static Web application, and simple, self-contained applications, into an external or public cloud.

Use Case 2: On-boarding multiple-VM workloads with storage and services residing in the enterprise: The instantiation of a multi-VM workload with interconnections to storage and other enterprise applications. One or more VMs of the workload are migrated to the cloud, but storage and other services (infrastructure, database, and so on) still reside in the enterprise. Network transparency between the two clouds enables seamless execution.

Use Case 3: On-boarding multiple-VM workloads with storage: The migration and instantiation of an integrated number of applications and a virtualized workload that interconnect with storage also located in the cloud. This involves the migration of both application workloads and storage to the cloud.

The emphasis of this paper is on the first two use cases and these will be explained in the following sections.

Considerations for Cloud On-BoardingCloud on-boarding can be complicated; it can require the redesign or re-architecture of application components, network stack, management, security, or orchestration, all dependent upon the application and infrastructure intricacies and complexities.

Before an application can be successfully on-boarded to the cloud, here are some key considerations:

• The application will likely consist of more components and infrastructure dependencies than will initially appear in the cloud environment. Some of these components, like directory services, domain name system (DNS), or dynamic

host configuration protocol (DHCP), that are shared by other applications simply cannot be moved to the cloud, and cloud applications that require them must integrate back into the enterprise implementation.

• Enterprises want to run applications across multiple cloud service providers in an integrated, secure manner with an integrated management solution. Enterprises must also consider the way the applications run in the enterprise vs. how they will run within the cloud. Cloud on-boarding may involve a conversion from P2V or V2V environments.

4

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Page 5: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

Table 1: Steps for On-Boarding Applications

Prepare Identify VMs and application files in the private cloud, and prepare them for migration to the public cloud. Verify that workloads are ready for export. Convert VMs and workloads to the target cloud image format, if needed.

Provision cloud resources Establish relationships with cloud service provider. Determine the best offering, and establish contracts, including agreements, costs, and SLAs. Provision the cloud resources (storage, network, servers, user-accounts).

Secure connectivity and bridging between enterprise and external cloud

Create bi-directional network connectivity between the data centers and clouds. Enable IPSec and VPN connections, and configure L2 bridge for network transparency.

Application migration Migrate the VMs from the enterprise to the cloud. Verify that all files transferred, and that network, storage, and compute configurations remain intact.

End-to-end validation Validate seamless network connectivity to services on either side of bridge for all relevant services to ensure successful execution of the on-boarded services.

Stop service in enterprise and instantiate and monitor in cloud

Stop services in the enterprise and instantiate them in the cloud. Provide uninterrupted service to users’ client access.

Table 1 shows the logical steps needed to successfully on-board applications, and still maintain the security, transparency, and availability requirements, including seamless network access to IT services from the cloud.

Architecture for Cloud On-boarding

Architecture supporting the use cases described above requires some basic elements including a virtualized data center, one or more remote clouds, some means of connectivity, and devices used to access applications. See Figure 1.

Figure 1: Cloud On-boarding Reference Architecture

5

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Page 6: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

Here is how the diverse elements in Figure 1 relate to each other:

• The left side of the figure is the representation of the enterprise virtual data center which is assumed to be a virtualized data center. The right is a representation of a remote cloud—either a different data center in the enterprise, or multi-tenant cloud resources at a cloud service provider (public cloud). The two data centers are connected through a WAN, with an external Internet connection. For secure access, VPN connection is enabled between the endpoints with an Internet protocol security (IPSec) tunnel.

• The service provider provides “isolated” but not “dedicated” resources for the enterprise tenant. This means that the enterprise/tenant’s VMs and workloads could coexist with other tenant VMs/workloads on the same physical resources. The isolation is typically network isolation to ensure that the tenant’s network traffic flows are secure and isolated from each other. Physical isolation is enabled by the hypervisor through the VM sandbox. Storage is partitioned to support multitenancy. The network isolation model is not consistent across cloud service providers. Providers like Savvis, OpsCloud, and AT&T provide VLANs for each enterprise tenant (four to five VLANs per enterprise). However, providers like Amazon provide “proprietary” Layer 2 isolation. The enterprise policy for network isolation thus has a bearing on the service provider selected.

• Typically, the external cloud resources are considered as a logical extension to the “enterprise” resources, and thus adhere to the management, security, and trust models and policies of the enterprise. There would not be “external/public” access to the VMs/

workloads in the “overflow” capacity, and public access is through the existing enterprise firewall. This way, the enterprise security, firewall, IDS/IPS controls, and monitoring can be enforced on the overflow capacity traffic as well. In this model, the cloud is used as a “back office extension.”

• All traffic on the WAN/Internet with VPN is encrypted for security. The latency of the WAN/Internet and the additional latency due to the encryption/decryption may not be acceptable to certain workloads.

The following sections describe the various solution stack components that have been used in the reference architecture.

Implementation OverviewCloud computing transforms the economics and the nature of IT, changing it from a cost of doing business into an on-demand service that can be used according to the needs of the business. To achieve the highest level of success and savings with IT-as-a-service, businesses must maximize the cloud and their investments in existing technologies, as well as unify on-premise and off-premise resources into a cloud-extended data center.

Citrix Cloud Solutions

Citrix Cloud Solutions help businesses accelerate the move to the cloud, including on-boarding, disaster recovery, compliance, application development, and test, desktop, and application virtualization. Cloud providers can help their customers move key workloads to the cloud or extend them there for increased availability and flexibility by combining Citrix Cloud Stack with their own expertise and best practices.

Implementation Requirements

Citrix Cloud Solutions offer an open,

pragmatic approach to cloud computing. Seven turnkey solutions, focused on practical cloud use cases and delivered by proven cloud providers, let enterprises immediately take advantage of cloud economics to address pressing business and IT needs. Citrix Cloud Solutions let enterprises use existing investments, including third-party virtualization technologies and tools, to migrate application workloads to the cloud without having to overhaul existing applications or their underlying infrastructure.

Citrix Cloud Infrastructure and Networking is powered by an open and extensible suite of technologies. These technologies enable a range of solutions, from on-boarding application workloads to the cloud, to optimizing application performance, to effectively managing enterprise SLAs—all while delivering on the promise of cloud economics, elasticity, and scale. Extensibility and on-demand customization are built into the design of each Citrix cloud technology component to address the unique needs of every enterprise. A high degree of interoperability among Citrix cloud technology components and third-party cloud technologies ensures that there is no lock-in when customers adopt a Citrix solution. Customer choice is a fundamental goal of the underlying technology powering the Citrix Cloud Platform.

Citrix Cloud On-Boarding Solution Requirements

The Citrix Cloud On-Boarding Solution enables seamless on-boarding of applications and workloads to the cloud. It uses a robust virtual platform, VM migration, open virtualization format (OVF), and key cloud technologies to simplify on-boarding applications to the cloud.

6

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Page 7: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

Requirement Citrix Cloud Solution: On-boarding

Policy-driven control of orchestration, management, and security for compute, network, and storage resources.

Citrix Cloud Stack

Enable the on-boarding of any application workload format to the cloud. Currently supported formats to cloud: .xva, .vmdk, .vhd, and .ovf.

Heterogeneous Formats

Automate the on-boarding of production application workloads to the cloud, so these application workloads can be used to create templates for future provisioning, or to instantiate and run the application workloads in the cloud.

Citrix Cloud Migration Services

Ability to use identity management infrastructure within the enterprise with the application workloads deployed in the cloud.

Citrix NetScaler Cloud Gateway

Seamlessly connect the enterprise data center and the cloud data center with full security, performance, and network transparency.

Citrix NetScaler Cloud Bridge

Enable enterprise SLA support through high availability, global access, optimization, load balancing, and secure remote connectivity.

Edge Networking Services

Easily allocate pooled network, CPU, and memory capacity to bring up server, application, and network appliance instances on demand.

Platform Virtualization

Table 2: Citrix Cloud On-Boarding Solution

Citrix Cloud Stack

CloudStack provides a feature rich out-of-the-box user interface implemented on top of the CloudStack API to manage the cloud infrastructure. It is a fully AJAX-based solution compatible with most of the latest internet browsers and can also be easily integrated with your existing portal.

Citrix Cloud Migration Services and Heterogeneous Formats

Citrix Cloud Migration Services will use Citrix XenConvert* to seamlessly on-board application workloads to the cloud. The support of the Open Virtual Machine Format (OVF) will allow VMs to be packaged into applications workloads. Citrix XenConvert will on-board application workloads from an enterprise data center that may be running on a different virtualization platform than the key Citrix cloud partners. Examples include virtual-to-virtual application workload migration conversions from .xva, .vmdk, .vhd, and .ovf to a private or public cloud.

Citrix NetScaler Cloud Gateway

Cloud Gateway provides automated user management for cloud and software-as-a-service (SaaS) applications so that organizations can granularly control authorization and access for any service. It also provides missing utilization and expense information to the business group for better resource planning and cost reduction efforts. With Cloud Gateway, lines of business (LoB) can quickly gain insight into how each SaaS and cloud-delivered service is directly benefiting the business—seeing who is using any particular application, how often, and whether the company's license agreement is "right-sized" with actual requirements.

Citrix NetScaler Cloud Bridge

NetScaler Cloud Bridge connects enterprise datacenters to external clouds and hosting environments, making the cloud a secure extension of the enterprise network. NetScaler Cloud Bridge is a complete network solution—available as a standalone physical or virtual

appliance or integrated into NetScaler Platinum—that sits at the "back door" of the enterprise datacenter, where it enables enterprises to transparently shift web and app servers to the cloud while keeping sensitive data assets (including databases and corporate directories) safely on-premise. With NetScaler Cloud Bridge, enterprises can augment their datacenters with the infinite capacity and elastic efficiency provided by cloud providers. Citrix NetScaler Cloud Bridge utilizes key capabilities within Citrix NetScaler*, Citrix Branch Repeater*, Citrix XenServer*.

The Citrix NetScaler Cloud Bridge solution uses Layer 2 bridging and IPSec VPN functionality to create a seamless network bridge between the enterprise data center and the cloud to ensure secure network transparency.

Edge Networking Services

Edge networking services utilize Citrix NetScaler and Citrix Branch Repeater. Citrix NetScaler is an integrated

7

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Page 8: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

web application delivery controller that functions as an application accelerator through caching and HTTP compression and provides advanced traffic management through Layer 4-7 load balancing and content switching functions. Citrix NetScaler also includes application security through a web application firewall, including PCI-DSS security mandate protection, and secure sockets layer (SSL) VPN. Citrix NetScaler further offloads applications and web servers to ensure application availability, increased security through SSL, and server consolidation. Citrix NetScaler takes the Layer 4-7 load balancer capabilities and applies them worldwide across geographically distributed server farms. Global server load balancing can be shifted from the data center to the cloud, which provides critical business continuity and disaster recovery support in case of site-level disruptions and outages.

Citrix Branch Repeater, available as a physical or virtual appliance, is a WAN optimization solution that provides a high-definition desktop and application experience to branch and mobile users while it dramatically reduces WAN bandwidth costs and simplifies branch infrastructure. Citrix Branch Repeater accelerates desktop and application delivery, decreases WAN bandwidth consumption, and enables server consolidation.

Platform Virtualization Services

Citrix XenServer is the only enterprise-class, cloud-proven server virtualization platform that delivers the critical features of live migration and centralized multiple-server management at no cost. Citrix XenServer is an open and powerful server virtualization solution that radically reduces cloud computing costs as it transforms static and complex cloud environments into more dynamic, easy to manage IT service delivery

centers. Citrix XenServer, created by the inventors of Citrix Xen*, is powered by the industry-standard Xen hypervisor. Citrix XenServer’s heterogeneous format support, the capability to import various VM formats, enables seamless migration strategies to the cloud.

Citrix NetScaler VPX* provides the complete Citrix NetScaler web application load balancing, acceleration, security, and offload features set in a simple, easy to install, virtual appliance. IT organizations of any size can deploy Citrix NetScaler VPX on industry-standard servers—on-demand—anywhere in the data center and cloud.

The following sections describe a working use case of on-boarding using Citrix NetScaler Cloud Bridge technology.

Use Case Overview and Test Bed BlueprintTo fully implement a working use case, we demonstrate the on-boarding of a multipart CRM Web application installation from the data center to a private cloud using Citrix NetScaler Cloud Bridge technology. SugarCRM is a Web-based customer relationship management solution for small and medium sized businesses. The Web-based CRM application is a single-VM workload which includes an application server, a Web server, and a database backend.

For the purposes of this paper, the enterprise data center was built out using the VMware vSphere* stack and the private cloud data center was built out using Citrix XenServer. Because large complex applications are not easily moved to the cloud, Use Case 2 was applied, in which one of the VMs was migrated to the cloud and other storage and services remained in the data center. This reflects how many applications will be on-boarded to the cloud. SugarCRM web application running in the enterprise, was on-boarded

to the private cloud, with no impact to the users.

We used the following steps for the use case scenario that we explored for this paper:

1. Deploy an installation of Microsoft Windows* Server 2008 into a virtual machine.

2. Deploy Apache2, PHP 5.0 and MySQL into the Microsoft Windows Server 2008 virtual machine.

3. Deploy SugarCRM Customer Relationship Management Web application in the enterprise data center on a VMware vCloud* implementation following the guidelines recommended by SugarCRM. The guidelines help ensure a successful deployment of SugarCRM.

4. Create a seamless network bridge (L2 Bridge)—using NetScaler Cloud Bridge—between the enterprise data center and the public cloud to ensure network transparency. This allows the public cloud to become an extension of the data center capacity. Enterprise security, trust, and compliance can be enforced on the public cloud capacity also.

5. Convert SugarCRM web application VM from VMware to Citrix XenServer (V2V conversion) using Citrix XenConvert and migrate to the cloud on the L2 Bridge. The conversion retains the original network stack and configuration.

6. Shutdown the SugarCRM VM in the enterprise data center.

7. Start the SugarCRM VM in the cloud. Ensure that SugarCRM web application communicates with the windows client’s remaining in the data center (web portal).

8

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Page 9: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

8. Users accessing the SugarCRM web portal delivered from the SugarCRM server will experience no differences whether SugarCRM is located in the data center or in the cloud.

Figure 2 is an overview of this cloud on-boarding use case.

Solution Stack for On-Boarding Reference Implementation

Here is a summary of the key solution stack components for the test bed, as illustrated in Figure 3.

• VMware vSphere: Hypervisor containing the virtualized compute infrastructure in the enterprise

• VMware vCenter*: Virtualization management tool for the enterprise

• Microsoft Windows Server 2008*: Operating system for enterprise and cloud VMs

• Citrix NetScaler Cloud Bridge: Secure network tunnel between enterprise and cloud

• Citrix XenServer: Hypervisor containing the virtualized compute infrastructure in the cloud

• Citrix XenCenter*: XenServer management tool for the cloud

• Citrix XenConvert: Citrix Xen VM conversion and migration utility

Figure 2: Cloud On-boarding Reference Architecture

Figure 3: On-boarding Test Bed

9

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Page 10: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

Software DescriptionThe data center was configured using a VMware vSphere (ESXi 4.1) hypervisor3 and the Microsoft Windows Server 2008 operating system.4

In the data center, a typical SugarCRM workload installation was created. In this installation a single VMincluded:

• SugarCRM Web application services

• SugarCRM data store (with MySQL)

• SugarCRM Web portal (with Apache and PHP)

In addition to the VM, three more VMs were used for network and VM management, domain services, and to simulate user access to portals:

Virtual Machine Purpose

SugarCRM SurgarCRM Web Application

Domain controller Active Directory, DNS, DHCP

Virtual clients Simulate client users

Table 3: Virtual Machine Configuration for Data Center

• VMware vCenter (VM management)5

• Domain controller (Active Directory*, DNS, DHCP)

• Virtual clients (Simulate user access to SugarCRM Web portal)

Table 3 shows all of the VMs used as the starting point for the use case.

System Design

To simplify and ease the application migration to the cloud, we preserved the application environment as much as possible and promoted network transparency. We used the same subnet in both data center and cloud (192.168.10.0/24). After the migration, the portion of the application residing

Server/Node Physical Hostname Data Center Network Cloud Network

ESX 4.1i Host Fmsesxpubcld01 192.168.10.31 -

VMware vCenter vCenter-srv1 192.168.10.30 -

Domain controller Fmsesxpubcld01 192.168.10.2 -

SugarCRM Application VM Fmsesxpubcld01 192.168.10.6 -

Citrix NetScaler Cloud Bridge NS-Private NetScaler IP: 192.168.10.101

SNIP: 75.147.238.115

SNIP: 192.168.10.11

-

Citrix XenServer Xenserver1 - 192.168.10.33

Citrix XenCenter Xencenter1 - 192.168.10.32

SugarCRM Application VM Xenserver1 - 192.168.10.6

Citrix NetScaler Cloud Bridge NS-Public - NetScaler IP: 192.168.10.100

SNIP: 198.175.112.246

SNIP: 192.168.10.10

Table 4: Network IP Configuration Before and After On-boarding

in the cloud will require little or no reconfiguration. During the on-boarding process, the SugarCRM VM was converted from a VMware vSphere VM to a Citrix Xen VM using Citrix XenConvert. Then it was on-boarded from the data center to the cloud.

We used VMware vSwitch* to assign a static IP address to each VM. Table 4 shows the network IP configuration before and after the on-boarding exercise.6

10

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Page 11: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

Hardware Description

The hardware configuration consisted of two servers in the data center and two servers in the cloud. The exercise was completed with one server in the data center and one in the cloud. The remaining servers were designated as backups.

Table 5 presents the hardware configuration and details.

Table 5: Hardware Setup

System Location Other Info

Fmsesxpubcld01 Data center System: Intel Server

Processor: Two Intel Xeon Westmere processors X5680, 3.33 GHz,

Memory: 24 GB RAM

Storage: Local, 4x146 GB SATA HDD (Raid)

Network: Two GB Ethernet NICs

vCenter-srv1 Data center System: Intel Server

Processor: Two Intel Xeon Westmere processors X5670, 2.93 GHz,

Memory: 24 GB RAM

Storage: Local, 4x146 GB SATA HDD (Raid)

Network: Two GB Ethernet NICs

Xenserver1 Cloud System: Intel Server

Processor: Two Intel Xeon Westmere processors X5680, 3.33 GHz,

Memory: 24 GB RAM

Storage: Local, 4x146 GB SATA HDD (Raid)

Network: Two GB Ethernet NICs

Xencenter1 Cloud System: Intel Server

Processor: Two Intel Xeon Westmere processors X5670, 2.93 GHz,

Memory: 24 GB RAM

Storage: Local, 4x146 GB SATA HDD (Raid)

Network: Two GB Ethernet NICs

Network WAN Two Citrix NetScaler MPX 9500’s – NetScaler Cloud Bridge

Refer to Figure 2 to relate the conceptual design of the VMs and network with the hardware implementation.

11

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Page 12: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

Technical ReviewThis section provides a detailed overview of the actions performed to implement cloud on-boarding. Many of the steps and commands are unique to this particular design, but they should provide enough detail to understand what was done and also to help on-boarding other applications.

For the details about application installation and setup, please see the respective product documentation. Be sure to check product release notes, service bulletins, and knowledge base articles.

Installation Overview

This section discusses the installation process for software prior to testing. The following setup steps assume you have an understanding of how to install and configure Microsoft Windows Server 2008, VMware vSphere, VMware vCenter server and client, Citrix XenServer,7 and Citrix XenCenter.8

Data Center Installation

1. Install VMware vSphere 4.1 hypervisor on data center system Fmsesxpubcld01.

2. Using VMware vSphere, create the following VM for the SugarCRM installation:

a. Windows Server 2008 (for SugarCRM Web Application)

i. Host name: SugarCRM

ii. Apply static IP address

iii. Install Apache

iv. Install PHP

v. Install MySQL

vi. Install SugarCRM

b. Windows Server 2008 (for domain controller—Active Directory, DNS, DHCP)

i. Install Active Directory Domain Services in accordance with your domain preferences

• Ensure that the domain administrator can add users to the domain through VPN connections

ii. Enable and install DNS role

• Configure Forward Lookup zones

• Configure Reverse Lookup zones

• Ensure that nslookup resolves in both domains

iii. Enable and install DHCP role

c. Windows 7 Enterprise Client

3. Install Windows Server 2008 R2 on data center system vCenter-srv1.

a. Host name: vCenter-srv1

b. Install VMware vCenter.

4. Place all VMs into the domain.

Cloud Installation

Install Citrix XenServer hypervisor on Xenserver-cob1 server. This will be the cloud destination for the migrated VM.

Install Citrix XenCenter application on Xencenter1 server. This will be used to manage the XenServer VM’s.

Use Case Overview

The data center and cloud test bed were initialized as described above. During the SugarCRM application on-boarding exercise, the following use cases were executed:

1. Set up and prepare the data center

2. User requests data from the SugarCRM in the data center

3. Establish secure connectivity between data center and cloud

Execution and Results

All the steps that are described above were successfully executed. Documentation of the use cases, including screen shots, is shown in the following sections.

Set Up and Prepare the Data Center

1. Verify that all data center VMs are created and initialized.

a. Domain controller (Active Directory, DNS, DHCP)

b. SugarCRM Application

c. Virtual client (Windows 7)

2. All VMs should be able to “ping” all other VMs in the data center.

3. SugarCRM is now installed in the data center and ready for users to access the Web portal.

4. Migrate application from data center to cloud

5. Instantiate application in cloud

6. User requests data from the SugarCRM in the in cloud

12

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Page 13: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

User Requests Data from the SugarCRM Web Portal in Data Center

1. Verify that the user is able to access and login into the SugarCRM Web portal. At a client, open Internet browser and navigate to SugarCRM Web portal (http://SugarCRM/sugarcrm/index.php).

2. The user is presented with the Welcome page and an opportunity to log on as a user.

Figure 4: SugarCRM Welcome Page

13

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Page 14: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

3. Log on to SugarCRM

a. Username; admin

b. Password: P@ssw0rd

Figure 5: SugarCRM User account data

User “admin” can now see his or her customer relationship management data.

14

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Page 15: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

Establish Secure Connectivity between Data Center and Cloud

1. Setup the NetScaler Cloud Bridge MPX appliance in data center.7

2. Using the NetScaler Cloud Bridge GUI or command line Configure the bridge as an internet gateway for data center. In this example, the command line was used:

a. Enable Cloud Bridge

b. Enable L2 Mode

c. Configure IPs

d. Configure GRE Tunnel

e. Configure Bridge

f. Configure and Bind Bridge to VLAN (optional)

g. Configure Route (if needed)

Enable Cloud Bridge Feature:

#enable ns feature CloudBridge

Enable L2 Mode: #en ns mode l2

Configure IPs: #add ns ip <ip> <subnet> -type SNIP (public facing or NATed IP) #add ns ip <ip> <subnet> -type SNIP (private network)

Tunnel Command: #add ipTunnel tun1 <remoteIP> 255.255.255.255 <localIP> -protocol GRE –secure NO

Create a netbridge #add netbridge <tunnalID#> #bind netbridge <bridgeID#> -tunnel <tunnalID#>

Bind VLANs (optional) #add vlan <ID#> #bind vlan <ID#> -ifnum <NIC ID> #bind netbridge <tunnalID#> -vlan <ID#>

Create route: #add route 0.0.0.0 0.0.0.0 <gateway>

NOTE: If your NSIP (first IP you set) is private you will #have to have a route

that points to your external gateway.

3. Setup/Import the NetScaler Cloud Bridge MPX appliance in the target cloud.7

4. Using the NetScaler Cloud Bridge GUI or command line Configure the bridge as an internet gateway for data center. In this example, the command line was used:

a. Enable Cloud Bridge

b. Enable L2 Mode

c. Configure IPs

d. Configure GRE Tunnel

e. Configure Bridge

f. Configure and Bind Bridge to VLAN (optional)

g. Configure Route (if needed)

Enable Cloud Bridge Feature: #enable ns feature CloudBridge

Enable L2 Mode: #en ns mode l2

Configure IPs: #add ns ip <ip> <subnet> -type SNIP (public facing or NATed IP) #add ns ip <ip> <subnet> -type SNIP (private network)

Tunnel Command: #add ipTunnel tun1 <remoteIP> 255.255.255.255 <localIP> -protocol GRE –secure NO

Create a netbridge #add netbridge <tunnalID#> #bind netbridge <bridgeID#> -tunnel <tunnalID#>

Bind VLANs (optional) #add vlan <ID#> #bind vlan <ID#> -ifnum <NIC ID> #bind netbridge <tunnalID#> -vlan <ID#>

Create route: #add route 0.0.0.0 0.0.0.0 <gateway>

NOTE: If your NSIP (first IP you set) is private you will #have to have a route that points to your external gateway

Migrate Application from Data Center to Cloud

1. Install Citrix XenConvert in the SugarCRM VM. Citrix XenConvert will convert a VMware vSphere VM to a Xen VM.8

2. Run Citrix XenConvert. Convert Citrix XenApp Core from a VMware vSphere VM to a Xen VM to prepare its movement from the data center to the cloud (VMDK to XenServer Conversion).

a. Set the source to drive C.

b. Set the destination as XenServer1 in the cloud.

c. The conversion process may take several hours to complete, depending on the size of the VM, the network performance, other factors.

15

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Page 16: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

Figure 6: Conversion of the SugarCRM VM using Citrix XenConvert

Instantiate Application in Cloud

1. Power down the original SugarCRM Application VM in the data center using VMware vCenter.

2. From Citrix XenCenter in the cloud, start the SugarCRM Application VM. The VM should be able to startup and connect to the Domain Controller in the data center.

User Accesses SugarCRM in Cloud

1. At this point, when a user requests the SugarCRM web portal, it is delivered from the cloud and not from the data center. At the same earlier client, open an Internet browser and navigate to the SurgarCRM web

portal (http://sugarcrm/sugarcrm/index.php).

2. The user is presented with the Welcome page and an opportunity to log on as a user.

3. Log on as “admin” and P@ssw0rd.

4. This time, the web portal will be delivered from the SugarCRM server in the cloud rather than from the data center.

Things to ConsiderThe following discussion highlights issues and concerns for cloud on-boarding.

Cloud Provisioning

Consider the time, effort, and resources

needed to provision the cloud before on-boarding. Consider how existing SLAs, user accounts, and billing will be impacted. Identify and provision the resources and services needed, including the servers, network infrastructure, and storage. Establish or update existing SLAs, contracts, and costs. Consider how user and identity management will work across the data center and the cloud.

Scalability and Performance

Moving applications to the cloud may impact application performance and scalability. As the application may now be divided between the data center and the cloud, communication between VMs

16

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Page 17: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

could be impacted by network speed and throughput, especially the performance of the WAN. Application latency can also be impacted. The application may have access to fewer resources or more resources, so application performance may be expected to improve or degrade.

Applications may have different load balancing concerns after on-boarding. Network traffic flows may be quite different after on-boarding applications.

Downtime Impact

On-boarding an application may impact application availability. Consider the time to migrate applications, including any VM conversion time and VM transfer time over the network. Consider the number and size of the VMs to convert. You may need time to validate and test the application once it has been migrated to the cloud.

Application State

Consider the state of the application, including any data stores, before you attempt cloud on-boarding. You may need to shut down some applications in an orderly fashion before you migrate the application or portions of the application.

Network Transparency

The network architecture can impact on-boarding efforts. In most cases, we want to minimize the disruption and reconfiguration of software after on-boarding.

Proper installation of DNS and Active Directory is mandatory when you set up the enterprise. Advanced knowledge of DNS forward and reverse looking zone configuration is a must as applications typically require both to function properly. A user with domain privileges is a requirement for user and group creation. Consider how DNS, DHCP, LDAP, and so on will operate across both the data center and the cloud.

Think about bundling together applications or groups of applications into simpler units before on-boarding. This may ease application migration to the cloud.

Security Considerations

Firewall and virus protection software may cause issues after the migration of applications to the cloud. Firewall software may limit access to needed network ports. Either disable firewalls or create rules to allow network access. Application firewalls and security settings may need to be reconfigured. Enterprise virus protection may limit network packet flow.

Management

Application management procedures and tools may be impacted by on-boarding. Application monitoring and management tools need to be aware of application migrations. Key features such as a management portal for provisioning, billing and metering information, monitoring capabilities, and basic lifecycle management will allow for tight integration of the data center and the cloud.

Additional InfoIntel® Cloud Builders Program: www.intel.com/cloudbuilders

Citrix Solution Brief: “Citrix Cloud Solution for On-boarding”: www.citrix.com/site/resources/dynamic/salesdocs/Citrix_Cloud_Solution_Onboarding.pdf

NetScaler Cloud Bridge: http://www.citrix.com/English/ps2/products/product.asp?contentID=2311976

NetScaler Cloud Bridge Whitepaper: http://www.citrix.com/cloud-bridge/whitepapers/intro_to_cb

Citrix Cloud Solutions: www.citrix.com/cloud/overview

Citrix Cloud Infrastructure: http://www.citrix.com/English/ps2/products/product.asp?contentID=2304709&ntref=prod_top

Intel® Xeon® processors: www.intel.com/xeon

GlossaryDHCP: Dynamic Host Configuration Protocol is an auto-configuration protocol used on IP networks.

DNS: Domain Name System is a distributed hierarchical naming system for computers, services, or resources connected to the Internet or a private network.

GRE: Generic Routing Encapsulation is a tunneling protocol which can encapsulate a wide variety of network layer protocol packet types inside IP tunnels.

IP: Internet Protocol

IPSec: Internet Protocol Security is a protocol suite for securing IP communications by authenticating and encrypting each packet of a session.

L2 Bridge: An L2 Bridge is a network bridge operating at Layer 2, which is the Data Link or MAC Layer.

LDAP: Lightweight Directory Access Protocol is an application protocol for querying and modifying data of directory services for IP networks.

QoS: Quality of Service is the ability to provide different priority to different applications, users, or data flows, or to guarantee a certain level of performance.

SP: Service Provider is a business or entity that provides services to other entities.

SSL: Secure Sockets Layer is a cryptographic protocol that provides security for network communications.

VLAN: A Virtual LAN is a group of hosts that communicate as if they were connected to the same broadcast domain, regardless of their physical location.

17

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Page 18: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

VM: Virtual Machine is a software implementation of a computer that executes programs like a physical machine.

VPN: A Virtual Private Network is a network that encapsulates data transfers between two or more network devices not on the same private network so as to keep data private from other devices on one or more intervening local or wide area networks.

WAN: A Wide Area Network is a computer network that covers a broad area, typically crossing metropolitan, regional, or national boundaries.

Appendix A: NetScaler Cloud BridgeNetScaler Cloud Bridge satisfies the enterprise’s need to combine datacenter security with cloud elasticity and economics by making cloud-hosted applications appear as though they are running on one contiguous enterprise network. With Cloud Bridge in place,

administrators, users, tools and the application itself believe that the application resides on the enterprise network.

To address the issues discussed earlier, NetScaler Cloud Bridge provides transparent network and user connectivity between the enterprise datacenter and the cloud-based datacenter:

• Seamless Network: L2 network bridging makes the cloud network a natural extension of the enterprise’s L2 network, making it easy to shift resources to the cloud w/out having to re-architect the application.

• Secured Tunnel: IPSec security ensures that data remains secure as it traverses the network links between the enterprise and the cloud.

• Optimized Access: TCP optimizations, compression, and data de-duplication minimize WAN-caused performance

Table B.1: Software Application Versions

Application Version

Citrix XenServer 5.6 FP1

Citrix XenConvert 2.1

NetScaler Cloud Bridge 9.3

Microsoft SQL Server 2008 2008 R2

Microsoft Internet Information Services (IIS) 7.5

VMware vSphere Hypervisor (ESXi) 4.1.0, 260247

degradation between enterprise datacenters and the cloud.

• User Transparency: Global server load balancing gives end-users get a single, consistent path to their applications regardless of which enterprise or cloud datacenter happens to be hosting the application at any given time.

Appendix B: Software VersionsTable B.1 shows the versions of the software applications that were used in the on-boarding example.

18

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Page 19: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

Endnotes1. Product Support for VMware vSphere, http://www.vmware.com/go/vsphere-help

2. Microsoft TechNet “Windows Server 2008 and Windows Server 2008 R2,” http://technet.microsoft.com/en-us/library/dd349801(WS.10).aspx

3. VMware vCenter Server, http://www.vmware.com/products/vcenter-server/support.html

4. VMware Virtual Networking Concepts, http://www.vmware.com/files/pdf/virtual_networking_concepts.pdf

5. Citrix XenServer 5.6, http://support.citrix.com/product/xens/v5.6/

6. Citrix XenCenter Knowledge Center, http://support.citrix.com/product/xens/v5.0/topic/xencenter/

7. NetScaler Documentation: http://support.citrix.com/product/nsad/v9.3/#tab-doc

8. VMware Knowledge Base Article “Configuring promiscuous mode on a virtual switch or portgroup,” http://kb.vmware.com/kb/1004099

19

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge

Page 20: Intel® Cloud Builders Guide to Cloud Design and Deployment ... › content › dam › www › public › us › en › ... · network stack, management, security, or orchestration,

Disclaimers∆ Intel processor numbers are not a measure of performance. Processor numbers differentiate features within each processor family, not across different processor families. See www.intel.com/

products/processor_number for details.INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROP-

ERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL’S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. UNLESS OTHERWISE AGREED IN WRITING BY INTEL, THE INTEL PRODUCTS ARE NOT DESIGNED NOR INTENDED FOR ANY APPLICATION IN WHICH THE FAILURE OF THE INTEL PRODUCT COULD CREATE A SITUATION WHERE PERSONAL INJURY OR DEATH MAY OCCUR.

Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked “reserved” or “undefined.” Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The infor-mation here is subject to change without notice. Do not finalize a design with this information.

The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized er-rata are available on request. Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order. Copies of documents which

have an order number and are referenced in this document, or other Intel literature, may be obtained by calling 1-800-548-4725, or by visiting Intel’s Web site at www.intel.com.Copyright © 2011 Intel Corporation. All rights reserved. Intel, the Intel logo, Xeon, Xeon inside, and Intel Intelligent Power Node Manager are trademarks of IntelCorporation in the U.S. and other countries. *Other names and brands may be claimed as the property of others.

Intel® Cloud Builders Guide: Cloud Interoperability with Citrix NetScaler MPX and Cloud Bridge