Opensource for Cloud Deployments – Risk – Reward – Reality John Gormally Enterprise Relationship Manager Citrix Networking and Cloud Team

OpenStack – An Open Way to Build Cloud http://www.openstack.org/ Open source cloud infrastructure platform Massively scalable elastic architecture Designed for both public and private clouds Open API enables interoperability Technology agnostic and broad multi-vendor support Open source Apache 2 license. Designed to be very large scale. Open source and open API makes it possible to interoperate between private, public and hybrid clouds. Technology agnostic: hypervisor, authentication, networking, storage all pluggable. A large ecosystem and no vendor lock in.

OpenStack Projects OpenStack Compute OpenStack Object Storage Swift Original Compute code from NASA, and Object Storage code from Rackspace. Blue colors are code names for the project. Compute enables you to build EC2 like cloud. Object storage enables you to build S3 like service. Image service provides image registry and delivery service. When you try to implement a compute service, you will be using both OpenStack compute and image service, and the backend for storing actual machine images can be Object Storage or file systems. Object Storage can be deployed on its own. OpenStack Compute Nova OpenStack Object Storage Swift OpenStack Image Service Glance

RISK

OpenStack Design Philosophy Horizontally scalable Technology agnostic Standard and extensible API Open source option with commercial alternatives Standard hardware Future Proof Flexible Cost Effective OpenStack is designed from scratch to scale horizontally. It is the same architecture that powers Rackspace and Amazon like clouds. This makes it suitable for very large deployments, because it can tolerate individual node failures, and it is possible to add capacity quickly. There is always a standard set of APIs that is relatively stable from version to version, and there is always an open source implementation. In addition, vendors can build API extensions and plug in alternative implementations. As a service provider, you have lots of flexibility to switch in and out modules as you need. It runs on commodity hardware. It does not require expensive SAN.

Risk – Factors Building and Supporting Legal challenges Intellectual Property Costs for long term Support and maintenance

OpenStack Community 70+ companies, 100s of developers A large ecosystem Citrix is a founding member of the community. We have been involved from day one.

Reward

OpenStack Compute RESTful API Asynchronous eventually consistent communication: RabbitMQ message queue  Uses commodity server and local storage to run virtual machines. Images are fetched into the local storage using Image Service. OpenStack supports 8 hypervisor options in its third release (Cactus). Project Olympus will support major commercial hypervisors only. Horizontally and massively scalable: Use local storage to run VM Hypervisor agnostic: support for XenServer, KVM, ESX, Hyper-V, etc. Hardware agnostic: commodity hardware

OpenStack Object Storage RESTful API Data distributed evenly throughout system Scalable to multiple petabytes, billions of objects For building Amazon S3 like storage. Designed to run on commodity hardware (e.g. server with SATA drives attached) Object Storage is not built for SAN as the backend. Built-in replication (default is 3 copies) and failover Support large object size (up to 5G natively, >5G supported with segmentation) Data stored as-is (no compression or encryption) CDN: content delivery network Account/Container/Object structure: ideal for virtual disk images, static data, CDN, not a file system, no nesting Replication: N copies of accounts, containers, objects  No central database Hardware agnostic: commodity hardware, RAID not required

OpenStack Image Service Image registry and delivery service RESTful API Store virtual disk images in various backend storage systems OpenStack Object Storage, Amazon S3, file system, read-only HTTP store Store image metadata in a registry

OpenStack Networking Native Flat and VLAN based network isolation (DHCP) VLAN Network Connectivity as a Service Network Container Service IPAM Service Native Flat and VLAN based network isolation Network Connectivity as a Service to provide more flexibility API for Layer 2 operation Multiple vendor plugins Dotted lines are still under development, and are not yet official OpenStack projects. VLAN: instances are configured on a private network on a per-customer VLAN. FlatDHCP: Public IP addresses are shared from a pool of IP addresses. Instance IP addresses are controlled via a DHCP server running on the host. Flat: Public IP addresses are assigned from a pool of IP addresses. IP addresses can be “injected” into the client machine, or can be DHCP managed by an external DHCP infrastructure. Network Connectivity as a Service is developed to provide more flexibility. For example, a very large cloud will exhaust the VLAN # space or can span multiple L2 broadcast domains. This will require a different method for network isolation (e.g. QinQ, network abstraction with GRE tunnel). Some vendors like Cisco and Nicira provide advanced network management functionalities. This project will provide an API for the service at L2 and vendors can build their plugins for their network management products. IPAM stands for IP address management. It provides IP address management capabilities across services include compute, load balancer and firewall, etc. Container service is a general method of defining containers of network, compute and storage resources. It is a logic group of resources that can be created and managed as one unit. The initial focus is on network containers. Logos represent a list of core companies involved in defining Network Connectivity as a Service, IPAM and Network Container Service.

Other OpenStack Initiatives Dashboard Volume as a service Load balancing as a service Database as a service … These are not yet part of the official OpenStack projects. The Dashboard is originally from NASA. It is an open source sample GUI for user self-service. OpenStack Compute already has built in support for a variety of block storage options as a supplementary (non-boot) volume: ATA over Ethernet and iSCSI. Volume as a service is a separate service with its own API that OpenStack Compute can leverage. It makes the OpenStack Compute deployment more modular and flexible.

Build IaaS Compute Service with OpenStack Load Balancer Load Balancer Compute API Compute API Compute API Distributed Message Queue Database RabbitMQ RabbitMQ RabbitMQ RabbitMQ RabbitMQ MySQL MySQL MySQL Schedular Network Volume There are many components involved for building an IaaS clouds. It might seem complicated to configure each node and make them talk to each other. Compute Node Compute Node Compute Node Compute Node Image Service Image Service Object Storage Object Storage Object Storage

Looking Closer at an IaaS Cloud Citrix Confidential - Do Not Distribute

Think: Server Virtualization ++ Think: Amazon Web Services Private Clouds Public Clouds Built for traditional enterprise apps & client-server compute Scale-up (pool-based) Enterprise hardware components IT Mgmt-centric [1:100’s] Proprietary vendor stack Designed around big data, new workloads & next-gen apps Scale-out (horizontal resourcing) Commodity hardware components Autonomic [1:1,000’s] Open, value-added stack The world will have two kinds of clouds…. Most of the public clouds that serve this rapidly growing market look nothing like traditional enterprise datacenters. They run on radically different platforms purpose built for cloud computing – platforms designed from the ground up to deliver multi-tier, multi-tenant services in the simplest, most cost-effective way possible. They are designed for “scale-out” (infinite ability to add more low-cost components as needed) rather than “scale-up” (central virtualization resources pools, large expensive hardware with layers of management stacked on top, etc.). Public clouds are designed around automation and orchestration… they assume one operator will handle 1,000s of servers. Rather than build huge, industrial strength systems designed for “failover”, public clouds are designed with “fail-and-eliminate” in mind… if something goes wrong, it’s just thrown away and a new resource is added automatically. Public clouds are generally designed as open systems with a value-added stack, while enterprise datacenters are traditionally designed as somewhat closed stacks based on the virtualization platform of a single vendor. The world will have lots of both kinds… Citrix CloudStack is focused on the right side of this diagram. We are the platform for public cloud providers (and SP-minded enterprises who want to stand up private clouds designed like the Amazons of the world). Think: Server Virtualization ++ Think: Amazon Web Services

Reality

The Cloud Pioneers All Use Next Generation Architectures Worlds largest public cloud environment Delivering video on demand via the cloud Uses the cloud to sell more pigs Transformed their hosting business with the cloud All of the world’s most successful cloud providers, no matter what their business model or who they serve, are built with this modern architecture. They don’t use big enterprise-like server virtualization management stacks… they don’t use enterprise SAN storage… Uses the cloud to disrupt the way we communicate Built one of the fastest growing and most innovative companies on the planet on the cloud

Secure, multi-tenant platform Designed to build and orchestrate clouds Hypervisor agnostic Massively scalable and efficient Self service portal Open source, open standards Deploys in public or private cloud environments Deliver cloud services 50 times faster at 1/5th the cost Committed to OpenStack support The Cloud.com flagship product is called CloudStack. It is not a traditional enterprise server virtualization platform with cloud management layered on top. It’s a powerful, lightweight, hypervisor-agnostic solution designed from the ground up to help customers build clouds the way the world’s largest and most successful public clouds are built – simple, automated, elastic, scalable and massively efficient. This proven approach has helped Cloud.com customers roll out new cloud services up to 50 times faster, at one fifth the cost of alternative solutions.

Cloud.com powers the world’s most innovative clouds 60+ Large Scale Clouds In Deployment CloudStack is the most widely deployed platform in the public cloud today, powering more than 60 of the world’s most innovative cloud brands (including some really big names you would recognize, but we can’t put on the slide because they are highly protective of their cloud architectures)… many of these clouds scale to 1000s of servers.

Strong Commitment to OpenStack Prevents Lock-In Citrix and Cloud.com are both founding members of OpenStack open source project OpenStack has 1,000+ cloud developers and more than 80 supporting vendors This will accelerate our OpenStack work We will be added broad OpenStack support to the Cloud.com product line Citrix and Cloud.com share a strong commitment to openness as a key foundational principle of cloud computing. A key part of this commitment to openness is a full embrace of open source. In addition to providing leadership in communities like Xen.org at the virtualization layer, Citrix will accelerate its support of OpenStack, the popular open source cloud infrastructure movement that now includes over 1,100 cloud developers, and more than 80 member companies. As a founding member of Openstack.org, Citrix is the second largest contributor to the project and has membership on the OpenStack policy board.

CloudStack Architecture User Interface Developer API Administrator End User Console Amazon Open Stack Custom Availability and Security Image Libraries Backup LB HA Monitoring Application Catalog Integration API Dynamic Workload Management Custom Templates (OSS/BSS, Monitoring, Identity Management , Etc) Operational Integration Resource Management Operating System ISOs Servers Storage Network Service Management (Billing, Metering, Accounts, etc.) Virtualization Layer Servers Network Storage Citrix Confidential - Do Not Distribute

Cloud Scalability is Critical Availability Zone VMOps Pod VMOps Pod VMOps Pod CloudStack Pod CloudStack Pod CloudStack Pod CloudStack Pod Citrix Confidential - Do Not Distribute

Cloud Scalability Must Span Datacenters CloudStack Management Cluster San Jose Frankfurt Austin Acme Dehli Tokyo Acme Rio Citrix Confidential - Do Not Distribute

Citrix Confidential - Do Not Distribute Conclusion Risk – Reward – Reality Opensource is a enabler to successful early stages of both private and public clouds Having open API’s and continued development with only continue expand cloud functionality and deployment abilities of cloud services for years to come. Citrix Confidential - Do Not Distribute

Citrix Confidential - Do Not Distribute Contact Information: John Gormally – ERM – Citrix – Networking and Cloud Team John.gormally@citrix.com 760 613 3391 – Cell Phone Thank you! Citrix Confidential - Do Not Distribute