Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
EMC Syncplicity EMC Atmos Syncplicity Deployment Guide VERSION: 7.0 UPDATED: AUGUST 2016 EMC Syncplicity Copyright Notices Copyright © 2002-2016 KEMP Technologies, Inc.. All rights reserved.. KEMP Technologies and the KEMP Technologies logo are registered trademarks of KEMP Technologies, Inc.. KEMP Technologies, Inc. reserves all ownership rights for the LoadMaster product line including software and documentation. The use of the LoadMaster Exchange appliance is subject to the license agreement. Information in this guide may be modified at any time without prior notice. Microsoft Windows is a registered trademarks of Microsoft Corporation in the United States and other countries. All other trademarks and service marks are the property of their respective owners. Limitations: This document and all of its contents are provided as-is. KEMP Technologies has made efforts to ensure that the information presented herein are correct, but makes no warranty, express or implied, about the accuracy of this information. If any material errors or inaccuracies should occur in this document, KEMP Technologies will, if feasible, furnish appropriate correctional notices which Users will accept as the sole and exclusive remedy at law or in equity. Users of the information in this document acknowledge that KEMP Technologies cannot be held liable for any loss, injury or damage of any kind, present or prospective, including without limitation any direct, special, incidental or consequential damages (including without limitation lost profits and loss of damage to goodwill) whether suffered by recipient or third party or from any action or inaction whether or not negligent, in the compiling or in delivering or communicating or publishing this document. Any Internet Protocol (IP) addresses, phone numbers or other data that may resemble actual contact information used in this document are not intended to be actual addresses, phone numbers or contact information. Any examples, command display output, network topology diagrams, and other figures included in this document are shown for illustrative purposes only. Any use of actual addressing or contact information in illustrative content is unintentional and coincidental. Portions of this software are; copyright (c) 2004-2006 Frank Denis. All rights reserved; copyright (c) 2002 Michael Shalayeff. All rights reserved; copyright (c) 2003 Ryan McBride. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE ABOVE COPYRIGHT HOLDERS ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or implied, of the above copyright holders.. Portions of the LoadMaster software are copyright (C) 1989, 1991 Free Software Foundation, Inc. -51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA- and KEMP Technologies Inc. is in full compliance of the GNU license requirements, Version 2, June 1991. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Copyright © 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved. 2 EMC Syncplicity Portions of this software are Copyright (C) 1988, Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Portions of this software are Copyright (C) 1998, Massachusetts Institute of Technology Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Portions of this software are Copyright (C) 1995-2004, Jean-loup Gailly and Mark Adler This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. Portions of this software are Copyright (C) 2003, Internet Systems Consortium Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies. THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Used, under license, U.S. Patent Nos. 6,473,802, 6,374,300, 8,392,563, 8,103,770, 7,831,712, 7,606,912, 7,346,695, 7,287,084 and 6,970,933 Copyright © 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved. 3 EMC Syncplicity Table of Contents 1 Introduction .................................................................................................................................... 5 1.1 Document Purpose ................................................................................................................. 5 1.2 Intended Audience .................................................................................................................. 5 1.3 Prerequisites ........................................................................................................................... 5 2 EMC Atmos Syncplicity Template ................................................................................................... 6 3 Solution Overview ........................................................................................................................... 7 4 3.1 Topology.................................................................................................................................. 7 3.2 LoadMaster Functionality Applied .......................................................................................... 7 Deployment Example ...................................................................................................................... 9 4.1 5 Network Environment............................................................................................................. 9 LoadMaster Configuration ............................................................................................................ 11 5.1 Enable Subnet Originating Requests Globally....................................................................... 11 5.2 Virtual Service for Syncplicity Cloud to Storage Connectors ................................................ 12 5.2.1 6 Virtual Service Settings ................................................................................................. 12 5.3 Content Rules ........................................................................................................................ 13 5.4 Virtual Service for Storage Connector to Atmos ................................................................... 14 Configuration: Summary ............................................................................................................... 15 References ............................................................................................................................................ 16 Document History ................................................................................................................................. 17 Copyright © 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved. 4 EMC Syncplicity Introduction 1 Introduction Syncplicity is an enterprise sync and share solution from EMC which enables corporate users to collaborate from anywhere while providing corporate IT with the security and control required to comply with best practice and policy. In addition to being a service hosted by EMC, Syncplicity can be deployed as an on-premise solution integrated with storage architectures such as EMC Atmos. The KEMP LoadMaster not only addresses the load balancing requirements defined by EMC, it can add significant value in multi-tenant environments such as service providers and enterprise deployments. 1.1 Document Purpose This document outlines how a KEMP LoadMaster can be deployed together with EMC Syncplicity. It also provides guidelines for the configuration of LoadMaster services. 1.2 Intended Audience This document is intended to be used by anyone deploying a LoadMaster in conjunction with on premise Syncplicity and by service providers deploying a multi-tenant Syncplicity service. 1.3 Prerequisites The reader should have sufficient knowledge of networking, the LoadMaster and Syncplicity products to implement the solution outlined. Copyright © 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved. 5 EMC Syncplicity EMC Atmos Syncplicity Template 2 EMC Atmos Syncplicity Template KEMP has developed a template containing our recommended settings for EMC Atmos Syncplicity. This template can be installed on the LoadMaster and used when creating Virtual Services. Using a template automatically populates the settings in the Virtual Services. This is quicker and easier than manually configuring each Virtual Service. If needed, changes can be made to any of the Virtual Service settings after using the template. Download released templates from the Templates section on the KEMP documentation page: http://kemptechnologies.com/documentation/. For more information and steps on how to import and use templates, refer to the Virtual Services and Templates, Feature Description For steps on how to manually add and configure each of the Virtual Services, refer to the LoadMaster Configuration section of this document. Copyright © 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved. 6 EMC Syncplicity Solution Overview 3 Solution Overview 3.1 Topology Syncplicity consists of a cloud-based orchestration layer connecting authenticated and authorized clients with their storage via a customer-specific URL. Figure 3-1: Topology Based on the URL content, the LoadMaster infrastructure forwards the customer request to the customer-specific Storage Connector. The Storage Connector services the customer request by communicating with the EMC Atmos service via the LoadMaster. While the Cloud Orchestrator is designed to deal with a single IP address (Storage Connector), the LoadMaster enables a multi-tenant environment by selecting the client’s Storage Connector based on the client-specific URL. 3.2 LoadMaster Functionality Applied The LoadMaster environment enhances the Syncplicity environment in the following ways: It load balances Storage Connector hosts It load balances traffic on the Atmos storage cluster It simplifies scaling of Storage Connectors It performs Network Address Translation (NAT) of internal addresses Acts as a single point for managing and controlling digital certificates Copyright © 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved. 7 EMC Syncplicity Solution Overview Enables multi-tenancy on a single IP address by mapping the request URL to subscriberspecific Storage Connectors Copyright © 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved. 8 EMC Syncplicity Deployment Example 4 Deployment Example To highlight the LoadMaster capabilities, the example below assumes the following: 4.1 On-Premise, Multi-Tenant service on the domain example.com Services are provided to Customer A, Customer B and Customer C Each customer has a pair of Storage Connectors deployed A single certificate is used to secure communication with all customers An EMC Atmos cluster provides a multi-tenant storage platform For simplicity, a single LoadMaster is deployed, although in a real situation a pair of LoadMasters would be used for resilience Network Environment Figure 4-1: Network Environment The LoadMaster sits behind a NAT firewall on subnet 192.168.83.0/24. A virtual IP of 192.168.83.200 is created to service requests from the Cloud Orchestrator The Storage Connector VMs are on subnet 172.16.10.0/24 Customer A connects via https://customera.example.com and has Storage Connector hosts at 172.16.10.1 and 172.16.10.2 Customer B connects via https://customerb.example.com and has Storage Connector hosts at 172.16.10.3 and 172.16.10.4 Customer C connects via https://customerc.example.com and has Storage Connector hosts at 172.16.105 and 172.16.10.6 Copyright © 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved. 9 EMC Syncplicity Deployment Example The EMC Atmos cluster is on subnet 10.1.1.0/24 with IP addresses of 10.1.1.101, 10.1.1.102, 10.1.103, 10.1.1.104, 10.1.1.105, and 10.1.1.106 The LoadMaster is configured with addresses of 10.1.1.200 and 172.16.10.200 to provide connectivity to the Storage Connector and the EMC Atmos storage platform Copyright © 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved. 10 EMC Syncplicity LoadMaster Configuration 5 LoadMaster Configuration 5.1 Enable Subnet Originating Requests Globally It is best practice to enable the Subnet Originating Requests option globally. In a one-armed setup (where the Virtual Service and Real Servers are on the same network/subnet) Subnet Originating Requests is usually not needed. However, enabling Subnet Originating Requests should not affect the routing in a one-armed setup. In a two-armed setup where the Virtual Service is on network/subnet A, for example, and the Real Servers are on network B - Subnet Originating Requests should be enabled on LoadMasters with firmware version 7.1-16 and above. When Subnet Originating Requests is enabled, the LoadMaster will route traffic so that the Real Server will see traffic arriving from the LoadMaster interface that is in that network/subnet. When Subnet Originating Requests is enabled globally, it is automatically enabled on all Virtual Services. If the Subnet Originating Requests option is disabled globally, you can choose whether or not to enable Subnet Originating Requests on a per-Virtual Service basis. To enable Subnet Originating Requests globally, follow the steps below: 1. In the main menu of the LoadMaster WUI, go to System Configuration > Miscellaneous Options > Network Options. Figure 5-1: Subnet Originating Requests 2. Tick the Subnet Originating Requests check box. Copyright © 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved. 11 EMC Syncplicity LoadMaster Configuration 5.2 Virtual Service for Syncplicity Cloud to Storage Connectors For our example, a Virtual Service needs to be created on 192.168.83.200 which redirects requests to the customer-specific Sub-Virtual Service (SubVS) based on the requestor URL. To do this, follow the steps below in the LoadMaster Web User Interface (WUI): 1. Create a Virtual Service on the LoadMaster which responds to requests on port 443 coming from the Syncplicity Cloud. Figure 3: Virtual Service parameters 2. Configure the Virtual Service using the recommended settings as listed in Section 5.2.1. 3. For each customer, create a SubVS and add Real Servers for their Storage Connector servers. Figure 4: SubVS - Basic Properties The Storage Connection host is on port 9000. 4. Add any Real Servers, as needed. 5.2.1 Virtual Service Settings The following, are KEMP recommended settings for a Syncplicity Virtual Service. All other options remain as per the default configuration. However, changes can be made to any settings, as needed based on your environment. Section Option Value Standard Options Transparency Persistence Method Scheduling Method Enabled None round robin Copyright © 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved. Comment 12 EMC Syncplicity LoadMaster Configuration Section Option Value Comment SSL Properties SSL Acceleration Enabled Cipher Set Best Practices A wildcard certificate allows secure connections to be established with a request URL in the format of *.example.com. With this approach, a single certificate secures traffic for all clients in a multi-tenant environment. For further information on cipher sets, please refer to the SSL Accelerated Services, Feature Description. Real Server Check Parameters HTTP Method HTTP Protocol Real Servers HEAD These settings are used to define the URL to use for checking the availability of a Real Server. Figure 5-2: Virtual Service Settings 5.3 Content Rules Content rules allow traffic be redirected based on criteria, including the URL requested by the client. Figure 7: Content Matching Rules In our example, the LoadMaster is configured with a content rule for each customer so requests to the customer-specific URL are redirected to the customer-specific Storage Controller pair. Figure 5-3: SubVSs - Adding Appropriate Rules In the SubVS section of the Virtual Service properties page, add the appropriate content matching rule for each customer. For more information on content rules in general, please refer to the Content Rules, Feature Description. Copyright © 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved. 13 EMC Syncplicity LoadMaster Configuration 5.4 Virtual Service for Storage Connector to Atmos The Storage Connector nodes communicate with the Atmos storage backend via port 80. The Atmos storage environment consists of multiple nodes and any of which are capable of servicing requests from Storage Connectors. EMC suggests using a round robin algorithm on a load balancer. This results in even distribution of service requests across the Atmos nodes. The health of the Atmos environment can be tested using PING or by requesting the /rest page from the Atmos node. Figure 5-4: Virtual Service A Virtual Service should be created on the LoadMaster interface which is connected to the particular Storage Connector subnet. This Virtual Service should accept HTTP requests on port 80 and balance them, using round robin, to the Atmos nodes (the six IP addresses on 10.1.1.0/24 in this example). Figure 5-5: Real Servers Section Atmos nodes are added as Real Servers with the server check set to ICMP Ping or HTTP Protocol. Using HTTP as the check protocol gives a view of the Atmos REST service status while PING only checks the host network status. Figure 5-6: Real Servers Copyright © 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved. 14 EMC Syncplicity Configuration: Summary 6 Configuration: Summary Figure 11: Virtual Services Syncplicity clients connect via the Syncplicity orchestration cloud to the Virtual IP [1] on the LoadMaster which is listening on port 443. Based on the request URL, the connection [2] is forwarded to the customer’s Connection Server pair on port 9000 [3]. The Connection Server makes a REST request on port 80 to the Atmos Virtual IP [4] which balances the request to one of the available Atmos nodes [5]. Copyright © 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved. 15 EMC Syncplicity References References Unless otherwise specified, the following documents can be found at http://kemptechnologies.com/documentation. Content Rules, Feature Description Virtual Services and Templates, Feature Description SSL Accelerated Services, Feature Description Copyright © 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved. 16 EMC Syncplicity Document History Document History Date Change Reason for Change Version Resp. May 2015 Initial draft First draft of document 1.0 KG Oct 2015 Release updates Updates for 7.1-30 release 3.0 LB Dec 2015 Release updates Updates for 7.1-32 release 4.0 LB Jan 2016 Minor changes Updated Copyright Notices 5.0 LB May 2016 Release updates Updated for 7.1-34 release 6.0 LB Aug 2016 Minor changes Enhancements made 7.0 LB Copyright © 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved. 17