deployment of datera elastic data fabric with accelerite cloudplatform · 2017-11-25 ·...

DEPLOYMENT OF DATERA ELASTIC DATA FABRIC WITH ACCELERITE CLOUDPLATFORM

Best Practices for Enterprise

Application Deployment

DEPLOYMENT GUIDE

VERSION 1.0

VERSION 2.0

Deployment of Datera Elastic Data Fabric with Accelerite CloudPlatform

© 2017, Datera, Inc.

TABLE OF CONTENTS DATERA OVERVIEW................................................................................................................1

BUSINESS BENEFITS OF THE DATERA PLATFORM ..................................................................................... 1 DATERA ADVANTAGE FOR CLOUDPLATFORM ......................................................................................... 2

CONTRIBUTION TO OPEN SOURCE ..........................................................................................3

DATERA CLOUDPLATFORM DRIVER FOR CLOUDPLATFORM .....................................................4

NETWORK PREPARATION .......................................................................................................5 DATERA ACCESS NETWORK ................................................................................................................. 5

CONFIGURING CLOUDPLATFORM WITH DATERA AS THE PRIMARY STORAGE PROVIDER ..........7 INSTALLING THE DRIVER ..................................................................................................................... 7 CREATING PRIMARY STORAGE ............................................................................................................. 7 USING THE DATERA PRIMARY STORAGE FOR CREATING VMS ................................................................... 8 CREATING A CLOUDPLATFORM COMPUTE OFFERING (ROOT DISK) ............................................................. 8 CREATING CLOUDPLATFORM DISK OFFERING (DATA DISK) ..................................................................... 10 CREATING VM INSTANCE .................................................................................................................. 10 ATTACHING A DATA DISK TO A RUNNING VM ...................................................................................... 11

EXPLORING ADVANCED FEATURES OF THE DATERA CLOUDPLATFORM PLUGIN...................... 12 CREATING ROOT VOLUME SNAPSHOTS ............................................................................................... 12 CREATING TEMPLATES FROM SNAPSHOTS ............................................................................................ 12 CREATING VM INSTANCE FROM TEMPLATE ......................................................................................... 13 CHANGE QOS PARAMETERS USING DISK OFFERING .............................................................................. 13

SETTING UP HYPERVISORS FOR OPTIMAL PERFORMANCE ..................................................... 16 NETWORK CARD IRQ’S BALANCED ACROSS CPU CORES ......................................................................... 16 SET CPUFREQ GOVERNOR TO PERFORMANCE ........................................................................................ 16 BLOCK DEVICES TO THE NOOP SCHEDULER .......................................................................................... 16 MULTIPATH CONFIGURATION ............................................................................................................ 17

CONCLUSION ....................................................................................................................... 18

DEPLOYMENT GUIDE 1


Datera Overview Datera Elastic Data Fabric (EDF) is next-generation elastic block storage deployed on industry-standard x86 servers for enterprise and service provider clouds and shared infrastructures. The Datera EDF takes datacenter automation and efficiency to a whole new level, delivering continuous intelligent infrastructure at transformational speed, agility and economics. Datera EDF provides application-aware, multi-tenant storage that scales near-linearly with performance and capacity with nodes. The system runs on heterogeneous x86 servers (Hybrid Flash Nodes, and All-Flash Nodes) delivering heterogeneous hyper-scale infrastructure that is completely self-aware, self-adaptive, and self-optimizing. The Datera EDF provides a RESTful API that makes the infrastructure programmable and automatable.

Figure 1: Datera Elastic Data Fabric

Business Benefits of the Datera Platform

Given the wide variety of applications hosted in virtual infrastructures, Datera helps match optimize price and performance by truly matching application intent with the right storage. Datera allows for storage to be placed intelligently maintaining the intended service level objectives for any application workload, even in multi-tenant clouds.

Infrastructure consolidation: Supports unified infrastructure for multiple tenants and applications while

guaranteeing customized levels of performance and security

Self-Adaptive: Reduces the need for dedicated storage administrator to manage the cluster and configure and load balance storage

Storage efficiency: With default thin provisioning and zero-overhead on cloning and snapshots, cloud administrators can realize significant effective capacity to used capacity savings

Deployment velocity: Templates empower the developer to rapidly provision applications and can leverage application best practices

Programmability: REST-based API allows for integration with any management or orchestration layer with the multi-tenant roles and privileges and allows customers to integrate with developer tools seamlessly

DEPLOYMENT GUIDE 2


Economics: Tiering allows for cost optimized $/GB, $/IOPS and $/GB/s given that the working set for development and test workloads is a fraction of the complete data set

Grow-as-you go: Supports the grow-as-you-go model for cloud operators, eliminates fork-lift upgrades, and support for multiple generations of hardware and configurations

True multi-tenancy and multi-application support: Supports unified infrastructure for multiple tenants and applications while guaranteeing customized levels of performance and security including noisy-neighbor fencing

Highly available: Ability to upgrade the hardware and software without service disruption or downtime and without the requirement to go to secondary site or backup resources.

Accelerite CloudPlatform Overview

Accelerite CloudPlatform, powered by Apache CloudStack is an application-centric cloud solution designed to deploy

and manage large collection of virtual machines, as a highly available, highly scalable Infrastructure as a Service (IaaS) cloud computing platform. CloudPlatform is a turnkey solution that includes the entire stack of features: compute storage orchestration, Network-as-a-Service, user and account management, a full and open native API, resource accounting, and a first-class User Interface (UI). Users can manage their cloud with an easy to use Web interface, command line tools, and/or a full-featured RESTful API. CloudStack is used by a number of cloud providers to offer public cloud services, and by many companies to provide an on-premises (private) cloud offering, or as part of a hybrid cloud solution.

Datera Advantage for CloudPlatform

Datera Elastic Data Fabric changes the cloud storage playing field and raises the bar far beyond traditional storage solutions capabilities in several areas, including:

1. CloudPlatform Integration: Datera CloudPlatform storage plug-in provides seamless integration with CloudPlatform and a number of advanced functionalities to enable great operator experience.

2. Grow-as-you-go model: Start small, and be able to scale fast. Traditional storage is limited in scale by the proprietary hardware frame size and performance, while Datera delivers heterogeneous COTS scale-out. Software-based system will organically evolve – grow with new hardware, and decommission obsolete old hardware without any disruption. Data gets rebalanced and access optimized for the runtime workloads. No data migration. No forklift upgrades. Ever. CloudPlatform + Datera provides the ability to evolve and change the storage with no service impact.

3. Wide Price/Performance aperture: Given the wide variety of cloud applications, Datera provides the elastic price bands that fit the economic value for particular data. Each volume’s requirements are composable on-demand and that articulates storage placement. Datera system allows for storage to be placed intelligently maintaining the intended services level objectives for any application workload, even in multi-tenant clouds. There is a large difference in the price and performance of the storage choices, CloudPlatform + Datera provides the tools to automatically balance the storage loads based on the application requirements.

4. Workload isolation: With multiple tenants and varying types of applications in the cloud, Datera provides the ability to manage performance at application or volume basis through QoS controls and to address the noisy neighbor problem. The system is deeply multi-tenant aware with resource segmentation and workload isolation natively across the architecture. Cloud environments are multi-tenant. CloudPlatform + Datera provides single tenant performance in a multi-tenant environment.

5. Transparent DevOps to IT Ops transition: Datera allows for application related storage provisioning to be decoupled from the physical infrastructure management. Moreover, customers can seamlessly transition from development to test to IT operations without application configuration changes, but morphing the infrastructure constraints through policy overrides based on application, user or tenant. Traditional

DEPLOYMENT GUIDE 3


environments often times had very different storage for the different stages in the development lifecycle. CloudPlatform + Datera provides a perfect platform to support all stages of development lifecycle.

6. Automated operations model: Datera offloads operations from the on-premises deployments, making the service agile and simple for operators to manage and scale. The Datera system is self-adaptive to application load changes, infrastructure changes, storage additions and hardware failures. Datera provides RESTful API to automate operations, monitoring and failure handling. CloudPlatform + Datera.

Contribution to Open Source CloudStack is open source software designed to deploy and manage large collection of virtual machines, as a highly available, highly scalable Infrastructure as a Service (IaaS) cloud computing platform. CloudStack is a turnkey solution that includes the entire stack of features: compute storage orchestration, Network-as-a-Service, user and account management, a full and open native API, resource accounting, and a first-class User Interface (UI). Users can manage their cloud with an easy to use Web interface, command line tools, and/or a full-featured RESTful API.

Datera is committed to the open source community and is a contributor to various initiatives in Linux and CloudStack. In addition, Datera is the primary contributor and maintainer of Linux target mode stack, Linux-IO Target (LIO™)1 and various IO path modules for the Linux kernel. Datera continues to contribute patches and enhancements to the community. These contributions are widely adopted in the industry and are one of the primary drivers for the emergence of the software defined storage market and its use of Linux based storage targets. In addition, the Datera CloudStack and CloudPlatform drivers are open sourced for most of the recent distributions. For access to the CloudPlatform drivers, please go to: https://github.com/Datera/CloudPlatform-driver/ and other open source content, please go to: https://github.com/Datera.

1 www.linux-iscsi.org Linux-IO Target (LIO™) is the standard open-source SCSI target in Linux. It supports all

prevalent storage fabrics, including Fibre Channel, FCoE, IEEE 1394, iSCSI, NVMe-OF, iSER, SRP, USB, vHost, etc.

https://github.com/Datera/cloudstack-driver/

https://github.com/Datera

http://www.linux-iscsi.org/

DEPLOYMENT GUIDE 4


Datera CloudPlatform Driver for CloudPlatform CloudPlatform defines two types of storage: primary and secondary. Primary storage can be accessed by either iSCSI or NFS. Root volumes are created automatically when a virtual machine is created. Root volumes are deleted when the VM is destroyed. Data volumes can be created and dynamically attached to VMs. Data volumes are not deleted when VMs are destroyed. Administrators add primary storage to the system by creating a CloudStack storage pool. Each storage pool is associated with a cluster or a zone. Datera provides primary storage easily configurable through the Datera CloudPlatform Driver. In addition, Datera can also server as secondary storage with a vNFS server on the CloudPlatform system. Datera as primary storage can be used to create Root Disks, and Data Disks to existing instances or to new instances. The Datera driver and CloudPlatform version compatibility information is located on GitHub. Datera CloudPlatform driver page at https://github.com/Datera/cloudstack-driver/ Datera CloudPlatform driver supports the following features:

1. Configuring Datera as primary storage, either to a cluster and/or zone with QoS parameters, login credentials

2. Volume provisioning and management including create, delete, list, resize, attach and detach 3. Performing offloaded snapshots from volumes (snapshot operation is completely performed by Datera EDF,

rather than CloudPlatform) 4. Creating volumes from snapshots 5. Creating templates from snapshots 6. Creating VM instances from templates 7. Attaching and detaching volumes to VMs in different clusters 8. Support Storage XenMotion (Live volume migration in XenServer) from one XenServer cluster to another

Operating Systems Supported:

1. XenServer 6.2, 6.5 2. CentOS 7


DEPLOYMENT GUIDE 5


Network Preparation

iSCSI uses the same network stack for storage as does the compute layer. Care should be taken to setup the networking in accordance with CloudPlatform best practices for iSCSI. Datera network topology typically looks like the following schematic:

Figure 2. Datera Logical Network Topology

Multiple private networks help with Datera inter-node communications and management. The Access network is the storage network that the client nodes (CloudPlatform Hypervisor hosts) use to communicate with the storage. This access network is usually dedicated for storage; public access networks are segregated into other VLANs. In planning for Datera networking all these different network segments should be architected and deployed in their own VLANs for optimal storage performance.

Datera Access Network The CloudPlatform Hypervisors access the Datera storage through the Access Network iSCSI ports. Each Datera node connects to the Access Network through one or two 10 Gigabit Ethernet (GbE) interfaces. The Access Network must be a traditional IP-based network. The target IP addresses float during node failure, and target port rebalancing activities that occur as part of the load redistribution activities. The Access Network uses floating IP addresses to present iSCSI LUNs to hosts. The IP address range you provide must at least be equal to the number of nodes in the Datera storage system. However, the more IP addresses available the better the load distribution for the system. Datera recommends at least 32 addresses for small systems

DEPLOYMENT GUIDE 6


with up to 10 nodes, 64 addresses for medium systems up to 20 nodes, and 128-250 addresses for large systems greater than 20 nodes. For more details on the latest recommendations, please refer to the Datera Quick Start Guide and Datera EDF User’s Guide. The target IP addresses presented by the target iSCSI ports are drawn from the Access Network IP pools. The IP address in the pools are defined by the Access Network IP blocks. You must create at least one IP pool and at least one block of IP addresses to be assigned to Storage Instances. In the user interfaces, the Access Network ports are identified as Access VIP 1 and Access VIP 2.

DEPLOYMENT GUIDE 7


Configuring CloudPlatform with Datera as the Primary Storage Provider The client nodes are expected to access the Datera EDF through the iSCSI block protocol. All client nodes accessing the Datera EDF must have iSCSI initiator and associated tools.

Installing the Driver Datera CloudPlatform driver is available https://github.com/Datera/cloudstack-driver/. Be sure to pick the driver that matched the Accelerite CloudPlatform release.

To install the driver:

1. Download the associated jar file located at https://github.com/Datera/cloudstack-driver/blob/master that matches the CloudPlatform/CloudStack release

2. Copy the jar file to the CS management server at the following location: /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/

3. Restart the CloudStack service: systemctl restart cloudstack-management.service

4. Make sure that the CloudStack service has restarted: systemctl status cloudstack-management.service

Creating Primary Storage To add Datera as a dynamic primary storage backend for CloudPlatform:

1. Select Infrastructure > Primary Storage > Add Primary Storage. 2. Select the scope as Zone-Wide

3. Select Hypervisor as Any 4. Select the respective Zone 5. Provide the <Name> for this Primary Storage. This name is used in the Datera EDF system in order to

create the app instance. 6. Select the protocol as Custom. If any other protocol is selected, the mandatory fields of those protocols

aren’t used by CloudPlatform. 7. Check Managed 8. Provide the desired Capacity Bytes value. This can be a really large number such as 4398046511104

(4TB) 9. Provide the Capacity IOPS needed from the Datera cluster. This value gets updated as QoS

Performance of Max Total IOPS in Datera. 10. URL – Specific Datera plugin

MVIP=172.19.2.214;SVIP=172.28.214.9;clusterAdminUsername=admin;clusterAdminPass

word=password;ClusterDefaultMinIops=5000;ClusterDefaultMaxIops=15000;numReplica

s=2

a. The above example includes a key value pair where key and value are separated by = and different

keys are separated by ;

b. MVIP – Management IP of the Datera system for REST communication c. SVIP – Datera Access (iSCSI) Network Virtual IP d. clusterAdminUsername – Datera REST API username e. clusterAdminPassword – Datera REST API password f. clusterDefaultMinIops – Has no effect on Datera volumes in dynamic primary storage g. ClusterDefaultMaxIops - Has no effect on Datera volumes in dynamic primary storage h. numReplicas - Number of replicas for Datera Volumes

11. Storage Tags – User defined tag used by CloudPlatform in order to select a particular primary storage. Any number of tags can be created or used from existing ones. During the selection of primary storage all tags are used to identify a particular primary storage.


https://github.com/Datera/cloudstack-driver/blob/master

DEPLOYMENT GUIDE 8


Figure 3: CloudPlatform Primary Storage Configuration

Note: For every primary storage creation a Datera AppInstance is created in the Datera storage system. For each AppInstance one storage instance named storage-1 and for the storage instance one volume named volume-1 is created. The storage instance contains initiator group with same name as Primary storage. The initiator group contains the entire host IQNs of the cluster. Once the hosts in the cluster gets connected with the Datera storage instance, all hosts IQNs are gets listed as Active initiators.

Using the Datera Primary Storage for Creating VMs In order to create a VM that uses the Datera Primary Storage for its root and data disk, you must:

1. Create a CloudPlatform compute offering (root disk) 2. Create a CloudPlatform disk offering 3. Create VM Instance 4. Attach Data disk to a Running VM

Creating a CloudPlatform Compute Offering (root disk) The compute offering is used to specify the virtual machine root disk. To create a compute offering:

DEPLOYMENT GUIDE 9


1. Select Service Offerings > Add Compute Offering 2. When filling the compute offering form, use the following guidelines:

a. Storage Tag field must match the storage tag from the Datera Primary Storage b. Hypervisor Snapshot Reserve should be more than 100, for CloudStack 4.7 and 4.8. This is

required otherwise snapshot creation will fail with insufficient capacity. c. Use QOS Type: storage if you would like to make use of Datera QoS features d. Min IOPS is required for CloudStack/CloudPlatform but is not applicable to the Datera

CloudPlatform Driver (Datera EDF 2.x release doesn’t support Provisioned IOPS) e. Select Storage Type: Shared

Figure 4: CloudPlatform Compute Offering Configuration

DEPLOYMENT GUIDE 10


Creating CloudPlatform Disk Offering (Data disk) A disk offering is used to specify the virtual machine data disk. To create a disk offering:

1. Select Service Offerings. 2. Select Disk Offering dropdown from Select Offering menu. 3. Select Add Disk Offering 4. When filling the Add disk offering form, use the following guidelines:

a. Storage Tag field must match the storage tag from the Datera Primary Storage b. Use QOS Type: storage if you would like to make use of Datera QoS features c. Use Write-cache Type: No disk cache d. Storage Type: Shared

Figure 5: CloudPlatform Disk Offering Configuration

Creating VM Instance Once a compute offering and disk offering have been created, you can use them to create a VM Instance. To create a VM instance:

1. Select Instances

DEPLOYMENT GUIDE 11


2. Select Add Instance 3. In the Compute Offering step, select the compute offering created above. This will use Datera storage for

the VM root disk 4. Optionally, in the Disk Offering step, select the disk offering created above if you wish to attach a data

disk to the VM at VM creation time. Note: In CloudStack 4.7 and CloudStack 4.8, one AppInstance will be created and VM template blocks will be copied from secondary storage (NFS to XenServer then iSCSI to Datera). In CloudStack 4.9+, VM template will be created as Datera Cloudstack-TEMPLATE-<UUID> AppInstance with matching UUID, and the VM root disk will be cloned from the template AppInstance with ACL. The cloned AppInstance will be of the form Cloudstack-VOLUME-<UUID>. The subsequent VMs using the same VM template will be cloned directly from the cached AppInstance in Datera EDF system.

Attaching a Data Disk to a Running VM To attach a data disk to a running VM Instance:

1. Select Storage > Volumes. 2. Click Add to add a new volumes of a given disk offering type 3. Select the corresponding Disk Offering for the volume 4. Once the volume is created, click the ‘+’ button next to the new volume, followed by Attach Disk 5. Select the Instance to attach the data disk to

Figure 6: Configuring Data Volume to VM

DEPLOYMENT GUIDE 12


Exploring Advanced Features of the Datera CloudPlatform Plugin This section will explore some of the advanced features of the Datera CloudPlatform plugin including:

Creating Root Disk Snapshots Creating Templates from Snapshots Creating VM Instances from Templates Changing QoS Parameters using Disk Offering

Creating Root Volume Snapshots Depending on the specific CloudStack version that CloudPlatform is running, root volume snapshots can be created either at the hypervisor-level or at the storage-level. For CloudStack 4.7 and 4.8 do not have APIs to support storage-level root volume snapshots. Hence, only VM snapshots are supported which are performed at the hypervisor-layer on Secondary storage. For CloudStack v4.9 and later, the Datera CloudPlatform plugin makes use of the resignature supplement pack installed on XenServer, to create native storage-level root volume snapshots. This optimizes and speeds up the snapshot workflow significantly. To create root disk snapshots:

1. Select Instance > {VM} > View Volumes. 2. Find the row with type ROOT 3. Click Take Snapshot

Figure 7: CloudPlatform Snapshot configuration

Creating Templates from Snapshots

DEPLOYMENT GUIDE 13


When a template is created from a snapshot, the Datera CloudPlatform plugin applies the initiating hypervisor’s ACL to the snapshot application instance. It then mounts the snapshot as a volume on the hypervisor and copies the volume data into the secondary storage to create a VM template. To create a template from a snapshot:

1. Select Storage > Select view: Snapshots 2. Select Create Template 3. To verify template creation, navigate to Home -> Template -> {Name} -> Zones

Figure 8: CloudPlatform Templates configuration

4. Find the row with type ROOT 5. Click ‘+’ 6. Click Take Snapshot

Creating VM Instance from Template The process to create a VM Instances from a template is the same as the process to create a VM instance described in “Creating VM Instance” section above. In the Select a template step, use the newly created template to deploy the VM

Change QoS Parameters Using Disk Offering The Datera CloudPlatform plugin is able to make full use of Datera QoS capabilities, by providing the ability to modify QoS parameters of a data volume on the fly. This is done by utilizing 2 disk offerings as illustrated in the example below:

1. Create two disk offerings, one with a Max IOPs 3000 and one with a Max IOPs of 5000

DEPLOYMENT GUIDE 14


Figure 9: CloudPlatform Disk Offering View

2. Attach a data disk using the Max IOPs 3000 disk offering to a VM 3. Drive some IO to the data disk and note that the max IOPs is capped to 3000 IOPs in the Datera UI

Figure 10: Datera AppInstance View

4. While IO is running, navigate to Home -> Storage -> Volumes -> {Data disk} 5. Select Resize Volume 6. Select the disk offering with the higher Max IOPs (5000), and click Save

DEPLOYMENT GUIDE 15


Figure 11: Configuring CloudPlatform Disk

7. Note the Datera UI to confirm that the max IOPs are now reshaped to 5000 from 3000 IOPs

Figure 12: Datera Application Instance View

DEPLOYMENT GUIDE 16


Setting up Hypervisors for Optimal Performance As with all parameters, the impact of any tunable parameter may or may not impact performance. It is best to tune these parameters in a controlled environment and see how they impact the specific application use-case. Datera recommends changing the following areas to ensure best performance:

Network card IRQ’s balanced across CPU cores Set CPU governor to performance Block devices to the NOOP scheduler

Multipath configuration

Network card IRQ’s balanced across CPU cores We recommend to configure the affinity of interrupts of the Intel 10gbE iSCSI NIC to all cores. To balance the IRQs across all cores:

1. Disable irqbalance on the system

# service irqbalance stop

Stopping irqbalance: [ OK ]

2. Next perform the re-balancing and consult the vendor documentation for the network HBA.

Set cpufreq governor to performance To keep the CPU from going into lower pstates, explicitly set the cpufreq governor to 'performance'. The procedure depends on which kernel version of Linux and which distribution. Consult the OS vendor documentation for the exact steps.

Block devices to the NOOP scheduler 2 The Linux kernel offers several block device schedulers to handle the myriad of devices that Linux could support. For high performance block devices like Datera the recommendation is to use the “NOOP” scheduler. This ensures the hypervisor does not process or alter the characteristics of the guest IO. The Datera EDF will optimize the IO on the back end beyond what is possible for the elevator algorithm.

Edit /etc/default/grub,such as gksudo gedit /etc/default/grub, here you need to add elevator=noop:

Change:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

To:

2 http://askubuntu.com/questions/78682/how-do-i-change-to-the-noop-scheduler

DEPLOYMENT GUIDE 17


GRUB_CMDLINE_LINUX_DEFAULT="quiet splash elevator=noop"

Then run:

sudo update-grub2 and restart.

To Verify:

for i in /sys/block/sd*; do echo $i; cat $i/queue/scheduler; done

Multipath configuration Multipath allows you to configure multiple I/O paths between server nodes and storage arrays into a single device. Multi-pathing aggregates the I/O paths, creating a new device that consists of the aggregated paths.

defaults {}

devices {

device {

vendor "DATERA"

product "IBLOCK”

path_grouping_policy group_by_prio

path_checker tur

prio alua

path_selector "queue-length 0”

hardware_handler "1 alua"

failback 5

no_path_retry 24

}

}

blacklist {

device {

vendor ".*"

product ".*"

}

}

blacklist_exceptions {

device {

vendor "DATERA.*"

DEPLOYMENT GUIDE 18


Conclusion

Datera is a highly scalable platform for CloudPlatform environments allowing for horizontal scale in capacity and performance as you go. The seamless integration of Datera CloudPlatform driver for Accelerite CloudPlatform makes it very simple to provision and manage the Datera system. Datera helps makes CloudPlatform clouds successful with a wide price/performance band for a wide range of applications, non-disruptive software and hardware upgrades, grow-as-you-go and simplified operations.

DEPLOYMENT GUIDE 19


Copyright Copyright© 2017 Datera, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written consent of Datera, Inc., 1050 Enterprise Way, Suite 230, Sunnyvale, CA 94089. Trademarks Datera®, LIO™ and the Datera logo are trademarks of Datera, Inc., which are registered in some jurisdictions. Microsoft and Windows are trademarks of Microsoft Corp. in the US and other countries, used under license. vSphere is a trademark of VMware Inc. in the US and other countries, used under license. Linux is a registered trademark of Linus Torvalds. CloudStack is a registered trademark of the Apache Foundation. CloudPlatform is a registered trademark of Accelerite. All other trademarks are the property of their respective owners. Changes

The material in this document is for information only and is subject to change without notice. While reasonable efforts have been made in the preparation of this document to assure its accuracy, Datera, Inc. assumes no liability resulting from errors or omissions in this document, or from the use of the information contained herein. Datera, Inc. reserves the right to make changes in the product design without reservation and without notification to its users. Disclaimer If this product directs you to copy materials, you must have permissions from the copyright owner of the materials to avoid violating the law, which could result in serious damages and/or remedies. Customer Support

Visit our website at www.datera.io

Email: [email protected]

U.S. Toll Free: +1-844-432-8372

International +1-408-404-8736

Datera, Inc. 1050 Enterprise Way Suite 230 Sunnyvale, CA 94089

http://www.datera.io/

mailto:[email protected]

deployment of datera elastic data fabric with accelerite cloudplatform · 2017-11-25 ·...

Documents