Architecture Design Guide

Total Page:16

File Type:pdf, Size:1020Kb

Architecture Design Guide Architecture Design Guide Release Version: 15.0.0 OpenStack contributors Jun 18, 2017 CONTENTS Abstract 2 Contents 3 Conventions ............................................. 3 Architecture requirements ...................................... 3 Design ................................................ 16 Use cases ............................................... 55 Appendix ............................................... 68 Index 106 i Architecture Design Guide (Release Version: 15.0.0) Note: This guide is a work in progress. Contributions are welcome. CONTENTS 1 ABSTRACT The Architecture Design Guide provides information on planning and designing an OpenStack cloud. It explains core concepts, cloud architecture design requirements, and the design criteria of key components and services in an OpenStack cloud. The guide also describes five common cloud use cases. Before reading this book, we recommend: • Prior knowledge of cloud architecture and principles. • Linux and virtualization experience. • A basic understanding of networking principles and protocols. For information about deploying and operating OpenStack, see the Installation Tutorials and Guides, Deploy- ment Guides, and the OpenStack Operations Guide. 2 CONTENTS Conventions The OpenStack documentation uses several typesetting conventions. Notices Notices take these forms: Note: A comment with additional information that explains a part of the text. Important: Something you must be aware of before proceeding. Tip: An extra but helpful piece of practical advice. Caution: Helpful information that prevents the user from making mistakes. Warning: Critical information about the risk of data loss or security issues. Command prompts $ command Any user, including the root user, can run commands that are prefixed with the $ prompt. # command The root user must run commands that are prefixed with the # prompt. You can also prefix these commands with the sudo command, if available, to run them. Architecture requirements This chapter describes the enterprise and operational factors that impacts the design of an OpenStack cloud. 3 Architecture Design Guide (Release Version: 15.0.0) Enterprise requirements The following sections describe business, usage, and performance considerations for customers which will impact cloud architecture design. Cost Financial factors are a primary concern for any organization. Cost considerations may influence the type of cloud that you build. For example, a general purpose cloud is unlikely to be the most cost-effective environment for specialized applications. Unless business needs dictate that cost is a critical factor, cost should not be the sole consideration when choosing or designing a cloud. As a general guideline, increasing the complexity of a cloud architecture increases the cost of building and maintaining it. For example, a hybrid or multi-site cloud architecture involving multiple vendors and technical architectures may require higher setup and operational costs because of the need for more sophisticated orches- tration and brokerage tools than in other architectures. However, overall operational costs might be lower by virtue of using a cloud brokerage tool to deploy the workloads to the most cost effective platform. Consider the following costs categories when designing a cloud: • Compute resources • Networking resources • Replication • Storage • Management • Operational costs It is also important to consider how costs will increase as your cloud scales. Choices that have a negligible impact in small systems may considerably increase costs in large systems. In these cases, it is important to min- imize capital expenditure (CapEx) at all layers of the stack. Operators of massively scalable OpenStack clouds require the use of dependable commodity hardware and freely available open source software components to reduce deployment costs and operational expenses. Initiatives like Open Compute (more information available in the Open Compute Project) provide additional information. Time-to-market The ability to deliver services or products within a flexible time frame is a common business factor when building a cloud. Allowing users to self-provision and gain access to compute, network, and storage resources on-demand may decrease time-to-market for new products and applications. You must balance the time required to build a new cloud platform against the time saved by migrating users away from legacy platforms. In some cases, existing infrastructure may influence your architecture choices. For example, using multiple cloud platforms may be a good option when there is an existing investment in several applications, as it could be faster to tie the investments together rather than migrating the components and refactoring them to a single platform. 4 Architecture requirements Architecture Design Guide (Release Version: 15.0.0) Revenue opportunity Revenue opportunities vary based on the intent and use case of the cloud. The requirements of a commer- cial, customer-facing product are often very different from an internal, private cloud. You must consider what features make your design most attractive to your users. Capacity planning and scalability Capacity and the placement of workloads are key design considerations for clouds. A long-term capacity plan for these designs must incorporate growth over time to prevent permanent consumption of more expensive external clouds. To avoid this scenario, account for future applications’ capacity requirements and plan growth appropriately. It is difficult to predict the amount of load a particular application might incur if the number of users fluctuates, or the application experiences an unexpected increase in use. It is possible to define application requirements in terms of vCPU, RAM, bandwidth, or other resources and plan appropriately. However, other clouds might not use the same meter or even the same oversubscription rates. Oversubscription is a method to emulate more capacity than may physically be present. For example, a physical hypervisor node with 32 GB RAM may host 24 instances, each provisioned with 2 GB RAM. As long as all 24 instances do not concurrently use 2 full gigabytes, this arrangement works well. However, some hosts take oversubscription to extremes and, as a result, performance can be inconsistent. If at all possible, determine what the oversubscription rates of each host are and plan capacity accordingly. Performance Performance is a critical consideration when designing any cloud, and becomes increasingly important as size and complexity grow. While single-site, private clouds can be closely controlled, multi-site and hybrid deploy- ments require more careful planning to reduce problems such as network latency between sites. For example, you should consider the time required to run a workload in different clouds and methods for reducing this time. This may require moving data closer to applications or applications closer to the data they process, and grouping functionality so that connections that require low latency take place over a single cloud rather than spanning clouds. This may also require a CMP that can determine which cloud can most efficiently run which types of workloads. Using native OpenStack tools can help improve performance. For example, you can use Telemetry to measure performance and the Orchestration service (heat) to react to changes in demand. Note: Orchestration requires special client configurations to integrate with Amazon Web Services. For other types of clouds, use CMP features. Cloud resource deployment The cloud user expects repeatable, dependable, and deterministic processes for launching and deploying cloud resources. You could deliver this through a web-based interface or pub- licly available API endpoints. All appropriate options for requesting cloud resources must be available through some type of user interface, a command-line interface (CLI), or API endpoints. Consumption model Cloud users expect a fully self-service and on-demand consumption model. When an OpenStack cloud reaches the massively scalable size, expect consumption as a service in each and every way. Architecture requirements 5 Architecture Design Guide (Release Version: 15.0.0) • Everything must be capable of automation. For example, everything from compute hardware, storage hardware, networking hardware, to the installation and configuration of the supporting software. Manual processes are impractical in a massively scalable OpenStack design architecture. • Massively scalable OpenStack clouds require extensive metering and monitoring functionality to maximize the operational efficiency by keeping the operator informed about the status and state of the infrastructure. This includes full scale metering of the hardware and software status. A corresponding framework of logging and alerting is also required to store and enable operations to act on the meters provided by the metering and monitoring solutions. The cloud operator also needs a solution that uses the data provided by the metering and monitoring solution to provide capacity planning and capacity trending analysis. Location For many use cases the proximity of the user to their workloads has a direct influence on the per- formance of the application and therefore should be taken into consideration in the design. Certain ap- plications require zero to minimal latency that can only be achieved by deploying the cloud in multiple locations. These locations could be in different data centers, cities, countries or geographical
Recommended publications
  • Poweredge M1000e Blade Chassis
    PowerEdge M1000e Blade Chassis The Dell PowerEdge M1000e Modular Blade Enclosure is the rock-solid foundation for Dell’s blade server architecture, providing an extremely reliable, flexible and efficient platform for building any IT infrastructure. The Dell PowerEdge M1000e Modular Blade Enclosure M1000e blade slot instead of directly to the blade. By is built from the ground up to combat data center removing the network and storage identity from the sprawl and IT complexity, delivering one of the most server hardware, customers are now able to upgrade and energy efficient, flexible, and manageable blade server replace components or the entire blade server without implementations on the market. being forced to change the identity on the network or rezoning switches. Unlike other solutions, which often Leading energy efficiency require separate management interfaces and proprietary The M1000e enclosure takes advantage of its world- hardware, FlexAddress will work with any network and is class design by coupling ultra-efficient power supplies implemented directly from the integrated CMC by simply with large variable-speed fans and optimized airflow to selecting the chassis slots and fabrics that you want effectively cool the entire chassis while using less power. to enable. FlexAddress delivers persistent network and Effortless scalability storage identities, equipping your data center to handle predictable or even unplanned changes — add, upgrade, Only Dell provides complete, scale-on-demand switch or remove servers without affecting your networks. designs. With additional I/O slots and switch options, you have the flexibility you need to meet ever-increasing Global services and support demands for I/O consumption.
    [Show full text]
  • Dell Networking MXL Blade Switch for Dell M1000e Blade Enclosures Expand the Value of Your Blade Investment
    Dell Networking MXL blade switch For Dell M1000e blade enclosures Expand the value of your blade investment. The Dell Networking MXL blade switch delivers performance and scalability in a flexible package to meet the shifting demands of your business and data center as it transitions to 1/10/40GbE. The Dell Networking MXL blade switch provides 1/10GbE High-performing architecture and connectivity on server-facing ports for up to 32 M-Series Ethernet stacking blade servers equipped with the latest KR-based 10GbE network daughter or mezzanine cards. The MXL switch The MXL switch is an industry-first, 40GbE-capable, offers 1/10/40GbE connectivity on the uplinks to interface modular and stackable blade switch for the M1000e chassis. with a top of rack switch, directly to the core, or directly to Ethernet stacking using two 40GbE ports enables scalable an Ethernet-based SAN. The MXL switch also has enhanced network switch growth for up to six interconnected blade bandwidth, performance and flexibility to satisfy the switches that are managed as one logical device. Both changing demands of data centers embracing virtualization, stacking across chassis and local switching of traffic within network convergence and other I/O-intensive applications the chassis offer high performance, efficiency and lower or workloads. TCO. Flexibility and pay as you grow Powerful and robust OS The Dell Networking MXL blade switch provides rich Dell Networking Operating System 9 (OS9) is a robust and functionality using 1/10/40GbE, addressing the diverse scalable operating system comprised of feature-rich Layer 2 needs of environments ranging from data centers, large and Layer 3 switching and routing functionality using industry enterprises, government networks, education/research and standard command line interface.
    [Show full text]
  • Dell Force10 MXL 10/40Gbe Switch
    Dell Force10 MXL 10/40GbE Switch For Dell M1000e Blade Enclosures Expand the value of your blade investment with Dell Force10 MXL 10/40GbE switch, delivering performance and scalability in a flexible package that are designed to meet the shifting demands of your business and data center as it transitions from 1GbE to 1/10/40GbE. The MXL switch provides 1/10GbE connectivity on server facing ports for up to 32 M-Series blade servers equipped with the latest KR-based 10GbE network daughter cards (NDCs) or mezzanine cards. The switch offers 1/10/40GbE connectivity on the uplinks to interface with a top of rack switch, directly to the core, or directly to an Ethernet based SAN. The Force10 MXL switch has enhanced bandwidth, performance, and flexibility to satisfy the changing demands of data centers embracing virtualization, network convergence, and other I/O-intensive applications/workloads. Flexibility and Pay As You Grow With Powerful and Robust OS FlexIO Modules Dell Force10 Operating System (FTOS) is a robust and scalable The Dell Force10 MXL switch provides rich functionality operating system that comprises of feature rich Layer 2 and using 1/10/40GbE addressing the diverse needs of Layer 3 switching and routing functionality using industry environments ranging from data centers, large enterprises, standard CLI. The MXL switch brings this high performing and government networks, education/research, and high resilient FTOS deployed by some of today’s most demanding performance computing. The MXL switch supports 32 internal DC customers to the M1000e chassis. 1/10GbE ports, as well as two fixed 40GbE QSFP+ ports and offers two bays for optional FlexIO modules.
    [Show full text]
  • Dell Networking MXL and M IOA FC-Flexio Direct Connect Storage Deployment Guide
    Dell Networking MXL and M IOA FC-FlexIO Direct Connect Storage Deployment Guide FC FlexIO Fabric Services Update - Providing F-port Connectivity to Storage Dell Networking Solutions Engineering February 2015 A Dell EMC Deployment Guide Revisions Date Description Authors February 2015 Initial Release Jim Slaughter, Kevin Locklear, Curtis Bunch Copyright © 2015-2016 Dell Inc. or its subsidiaries. All Rights Reserved. Except as stated below, no part of this document may be reproduced, distributed or transmitted in any form or by any means, without express permission of Dell. You may distribute this document within your company or organization only, without alteration of its contents. THIS DOCUMENT IS PROVIDED “AS-IS”, AND WITHOUT ANY WARRANTY, EXPRESS OR IMPLIED. IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE SPECIFICALLY DISCLAIMED. PRODUCT WARRANTIES APPLICABLE TO THE DELL PRODUCTS DESCRIBED IN THIS DOCUMENT MAY BE FOUND AT: http://www.dell.com/learn/us/en/vn/terms-of-sale-commercial-and-public-sector-warranties Performance of network reference architectures discussed in this document may vary with differing deployment conditions, network loads, and the like. Third party products may be included in reference architectures for the convenience of the reader. Inclusion of such third party products does not necessarily constitute Dell’s recommendation of those products. Please consult your Dell representative for additional information. Trademarks used in this text: Dell™, the Dell logo, Dell Boomi™, PowerEdge™, PowerVault™, PowerConnect™, OpenManage™, EqualLogic™, Compellent™, KACE™, FlexAddress™, Force10™ and Vostro™ are trademarks of Dell Inc. Other Dell trademarks may be used in this document. EMC VNX®, and EMC Unisphere® are registered trademarks of Dell.
    [Show full text]
  • Cisco Catalyst Blade Switch 3032 for Dell M1000e
    Data Sheet Cisco Catalyst Blade Switch 3032 for Dell M1000e Product Overview The Cisco Catalyst ® Blade Switch 3032 for Dell M1000e (Figure 1) is an integrated switch for Dell M1000e customers that extends resilient and secure Cisco ® infrastructure services to the server edge and uses existing network investment to help reduce operating expenses. Figure 1. Cisco Catalyst Blade Switch 3032 for Dell M1000e The Cisco Catalyst Blade Switch 3032 for Dell M1000e provides Dell M1000e customers with an integrated switching solution that dramatically reduces cable complexity. This solution offers consistent network services such as high availability, quality of service (QoS), and security. It uses the comprehensive Cisco management framework to simplify ongoing operations. Cisco advanced network services in combination with simplified management help reduce total cost of ownership (TCO). Configuration The Cisco Catalyst Blade Switch 3032 for Dell M1000e provides the following hardware configuration: ● 16 internal 1000BASE ports connected to servers through the Dell M1000e backplane ● Up to 8 Gigabit Ethernet uplink ports: 4 10/100/1000BASE-T ports and 4 Small Form-Factor Pluggable (SFP) Gigabit Ethernet ports (using Cisco TwinGig Converter Modules in the X2 slots) ● One external console port Available with Cisco IOS ® Software, with the IP Base image, the Cisco Catalyst Blade Switch 3032 offers a complete set of intelligent services to deliver security, QoS, basic IP routing, and high availability in the server farm access environment. Features and Benefits Intelligence in the Server Access Network As companies increasingly rely on the network as the strategic business infrastructure, and with servers having Gigabit Ethernet capabilities, it is more important than ever to consistently try to All contents are Copyright © 1992–2008 Cisco Systems, Inc.
    [Show full text]
  • Dell Equallogic PS-M4110 Blade Array Technical Article
    Dell EqualLogic Technical Article Dell EqualLogic PS-M4110 Blade Array Technical Article THIS WHITE PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPHICAL ERRORS AND TECHNICAL INACCURACIES. THE CONTENT IS PROVIDED AS IS, WITHOUT EXPRESS OR IMPLIED WARRANTIES OF ANY KIND. © 2012 Dell Inc. All rights reserved. Reproduction of this material in any manner whatsoever without the express written permission of Dell Inc. is strictly forbidden. For more information, contact Dell. Dell, the DELL logo, and the DELL badge, PowerConnect™, EqualLogic™, Force10™, PowerEdge™ and PowerVault™ are trademarks of Dell Inc. Broadcom® is a registered trademark of Broadcom Corporation. Brocade is a registered trademark and VCS is a trademark of Brocade Communications Systems, Inc., in the United States and/or in other countries. Intel® is a registered trademark of Intel Corporation in the U.S. and other countries. Microsoft®, Windows®, Windows Server®, and Active Directory® are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Qlogic is a registered trademark of QLogic Corporation. Table of contents 1 Executive summary ......................................................................................................................... 5 2 Audience ......................................................................................................................................... 5 3 Introduction ...................................................................................................................................
    [Show full text]
  • 2016-2019 District Technology Plan
    WALL TOWNSHIP PUBLIC SCHOOLS DISTRICT TECHNOLOGY PLAN 2016 – 2019 Developed by the Wall Township Public Schools Technology Committee Spring/Summer 2016 WALL TOWNSHIP PUBLIC SCHOOLS 2016-2019 TECHNOLOGY PLAN TABLE OF CONTENTS Technology Committee ................................................................................ 5 Introduction ................................................................................................... 6 Executive Summary ...................................................................................... 7 Planning Process .......................................................................................... 8 2016 – 2019 Technology Goals and Objectives ……………………….. .... 9 Technology Inventory ................................................................................... 11 Equipment and Facilities Planning ............................................................. 12 Implementation Strategies ............................................................................ 18 Staff Development ........................................................................................ 26 Funding Plan ............................................................................................... 27 Evaluation Plan ............................................................................................ 32 Appendix A - Board of Education Approval .............................................. 33 Appendix B - Board Policies on Technology and Internet Use ................... 35 Appendix C - Technology
    [Show full text]
  • Comparing Dell Compellent Network-Attached Storage to an Industry- a Principled Technologies Test Report 2 Leading NAS Solution
    COMPARING DELL EQUALLOGIC DELL COMPELLENT PS6110XS ENTERPRISE NETWORK -VDIATTACHED STORAGE TO ANPERFORMANCE INDUSTRY-LEADING AND POWE NAS SOLUTIONR USAGE Traditionally, it has taken various types of storage platforms to meet an organization’s needs. Now, with network-attached storage (NAS) solutions, companies can address diverse storage requirements with a single solution. NAS solutions can do work as varied as hosting virtual machines and production databases, storing and sharing files, and even work as backup solutions. NAS solutions are not just flexible; they are highly scalable as well and can grow as business does. With NAS, administrators can add controllers and disks or even new types of disks as workloads increase. However, not all NAS solutions deliver the same performance. In the Principled Technologies labs, we tested the performance of two NAS solutions, the Intel Xeon processor-based Dell Compellent FS8600 and an industry- leading NAS solution, by backing up large volumes of data. We found the Dell Compellent FS8600 was up to 17.1 percent faster than a similarly configured, industry- leading NAS solution when backing up server files. This means that selecting the Dell Compellent FS8600 could deliver superior performance however you choose to use it. NOVEMBERAUGUST 20122013 A PRINCIPLEDA PRINCIPLED TECHNOLOGIES TECHNOLOGIES TEST REPORTREPORT CommissionedCommissioned by by Dell, Dell Inc.Inc. Dell Compellent FS8600 NAS delivered superior backup performance We compared the performance of an industry-leading NAS solution and a Dell Compellent FS8600 NAS solution using a Dell M1000e chassis and 20 Dell PowerEdge M420 server blades. We created two file corpuses: 1) a set of 12.2 million unique smaller files, each sized between 10 and 200 KB, and 2) a set of 12 thousand unique larger files, each sized between 10 and 200 MB.
    [Show full text]
  • Innovating Private Clouds for Optimal Service Delivery
    Convergence to cloud Innovating private clouds for optimal service delivery By Shelley Palmer, Wendy Williams, Paul Koteras and Art Fewell After priming data centers with virtualized IT resources, many government agencies are ready to progress toward a converged infrastructure that leverages private clouds to meet rigorous service delivery demands quickly, securely and cost-effectively. overnment organizations are resources. For example, cloud-based functions seeking ways to effectively that facilitate automatic orchestration of transition IT infrastructure and approval requests with associated governance Gservices to a cloud-based model tasks and self-service deployment of desktop for many reasons, including key directives applications are highly desirable for many such as the 25-Point Implementation Plan agencies. In addition, organizations are looking to Reform Federal IT Management and to deploy consolidated community clouds the Federal IT Shared Services Strategy — that support both local and geographically commonly referred to as Shared First. The dispersed locations, even if a shared cloud federal chief information officer (CIO) has strategy involves working through interagency established these mandates along with the differences in IT process design. Because Federal Data Center Consolidation Initiative the same cloud model does not fit every (FDCCI) to heighten efficiency in financial, deployment scenario, careful infrastructure technical, environmental and workforce design that is tailored to meet specific areas. By adopting
    [Show full text]
  • Poweredge M Series Blades
    M-Series I/O Guide I/O Connectivity Options for M1000e and M-Series Blades January 2013 PowerEdge M1000e Redundant I/O Modules View Fabric A1 Fabric A2 Reserved for Reserved for 1/10GbE LOMs or 1/10GbE LOMs or Select Network Select Network Adapters Adapters Fabric Fabric B1 B2 1/10GbE, 1/10GbE, 4/8/16Gb FC, 4/8/16Gb FC, 20/40/56Gb IB 20/40/56Gb IB Fabric Fabric C1 C2 1/10GbE, 1/10GbE, 4/8/16Gb FC, 4/8/16Gb FC, 20/40/56Gb IB 20/40/56Gb IB A total of 6 I/O bays per M1000e blade enclosure Redundant I/O modules provide high-availability 2 Dell Inc. M-Series Blade I/O Fabrics Quarter Height Blades C1 C2 One dual port LOM • IOM with 32 internal ports (M6348 or Quarter Height OR Dell Force10 MXL) is needed to connect all LOM ports on all blades 1 2 B B • 2 x 32 port IOMs needed to connect the 2 LOM ports on each blade One fabric B OR fabric C mezzanine card C1 C2 Half Height Blades One Select Network Adapter or LOM Half Height B1 B2 One fabric B mezzanine card One fabric C mezzanine card C1 C2 Full Height Blades B1 B2 Two Select Network Adapters or LOMs Two fabric B mezzanine cards Full Height Two fabric C mezzanine cards C1 C2 B1 B2 3 Dell Inc. I/O Fabric Architecture for Half-Height Blades Fabric A: • Dedicated to LOMs (2 ports/blade) or Select Network Adapters (2-4 ports/blade) • Each port links to separate I/O modules for redundancy • Reserved for 1/10Gb Ethernet (including iSCSI &/or FCoE) Fabrics B and C: • Customizable for Ethernet (including iSCSI &/or FCoE), Fibre Channel, &/or InfiniBand • Two I/O Mezzanine cards per half height blade • 2 or 4 ports per I/O mezzanine card • Each card has ports links to separate I/O modules for redundancy 4 Dell Inc.
    [Show full text]
  • Simplifying Virtual Desktop Deployments with Equallogic PS-M4110 Blade Storage Arrays
    Solution Brief Simplifying virtual desktop deployments with EqualLogic PS-M4110 blade storage arrays A typical virtual desktop infrastructure (VDI) integrates many components; Dell EqualLogic PS-M4110 blade servers to host the desktop virtual machines (VMs), connection broker and management software, storage for virtual desktop data, and network switching storage arrays help optimize interconnectivity. Pilot projects start off small, but scaling the infrastructure VMware VDI deployments can introduce deployment complexity and project risk. These risks need to be carefully mitigated in order to ensure smooth and timely implementation Simplify deployment: Blade-based without cost overruns. architecture unifies storage, compute Proper storage selection and sizing plays a key role in ensuring successful and switching infrastructure, for a virtual desktop deployments. Storage needs to mitigate performance complete VDI solution in a modular issues associated with storage I/O storms, for example, when many users and compact enclosure. concurrently boot up, log-in or log-out. It is also critical to carefully manage Achieve optimal virtual desktop storage footprint, due to the requirement for higher cost enterprise-class performance: EqualLogic multi- storage, which can have a significant impact on the total cost of the VDI tiered hybrid arrays effectively project. In addition, it is critical to simplify virtual desktop provisioning and mitigate storage I/O bottlenecks. infrastructure management to achieve greater efficiencies and manageability. VAAI integration improves performance and scalability Modular, high-density blade architecture for simple by offloading storage tasks to deployment EqualLogic arrays. Dell PowerEdge Blade Server solutions, based on the Dell m1000e blade Realize transformative cost savings: enclosure, seamlessly integrate best-of-breed blade-based components into Thin clones lower storage footprint a converged infrastructure.
    [Show full text]
  • 2011: How Does Dell Steward Corporate Responsibility and Report on Our Progress? Table of Contents
    2011: How does Dell steward Corporate Responsibility and Report on our progress? Table of contents 01 Letter from Michael Dell 02 Our heritage and business 03 Progress 05 By the numbers 09 Goals 10 Environment 24 Human rights and social responsibility 32 Workplace and team members 40 Giving and communities 48 Corporate accountability and governance 56 Join the conversation Michael Dell is pictured with Fatima at Boys and Girls Club of Austin Letter from Michael Dell Enabling human potential — that’s the ultimate benefit of technology and the driving Enablingforce behind human everything potential we— that’s do at the Dell. ultimate We are benefit listening of totechnology and partnering and the with driving our force behindcustomers everything every daywe doto atdeliver Dell. technologyWe are listening solutions to and that partnering drive efficiencies, with our customers increase every dayproductivity to deliver technologyand enable humansolutions connections that help them at lightning operate, speedincrease and productivity on the go. andWe callenable it humanthe power connections to do more. at lightning speed and on the go. We call it the power to do more. ThisThis core core philosophy philosophy of of advancing advancing human human potential potential is is not not limited limited to to our Dell solutions solutions and and productproduct creation. creation. We’re We are also also applying applying it to it tohow how we we invest invest in andin and innovate innovate on on behalf behalf of ofour planetour planet and our and people. our people. It is ingrained It is ingrained in our in sustainability our sustainability and giving and giving practices practices as well as aswell in ouras inrelationships our relationships with our with global our globalteam.
    [Show full text]