DOCSLIB.ORG

Data Center Interconnection Service +

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Data Center Interconnection Service + DATA CENTER INTERCONNECTION SERVICES + Part I: Rates and Charges. Part II: Service Description and Requirements. Part III: Terms and Conditions. Part IV: Service Level Agreement. Part V: Definitions. Part I: Rates and Charges. 1. Details. Customer agrees to pay the monthly recurring charges (“MRC”) and non-recurring charges (“NRC”) for Data Center Interconnection Services as specified in the applicable Service Order. Part II: Service Description and Requirements. 1. Data Center Interconnection Services. Data Center Interconnection Services provides Customer with network connectivity within a Facility operated by Verizon. To use Data Center Interconnection Services, Customer must also contract separately with Verizon for Colocation Services. 2. Carrier Neutrality and Alternate Carriers. Customer may arrange on its own (via separate contract) to bring in additional non-Verizon circuits from a third-party subject to the following conditions: 2.1 The alternate carrier must have an approved existing presence inside the Facility, and Customer must purchase a Verizon provided interconnection (cross connect) to the alternate carrier’s existing presence in Faculty. 2.2 Verizon does not take responsibility for alternate carrier circuits, nor does Verizon make any promises or warranties whatsoever regarding their performance. 2.3 Verizon does not monitor or maintain alternate carrier capacity in the Facility. If Customer is utilizing an alternate carrier in a Verizon data center and such alternate carrier infrastructure requires augmentation, Customer acknowledges that the alternate carrier is responsible for notifying Verizon a minimum of one- hundred and twenty (120) Business Days prior to the desired augment availability. 2.4 Customer may not directly interconnect with any third parties without prior written consent of Verizon. Verizon reserves the right to require that any permitted interconnection with a third party be set forth in separate contract. 2.5 Specific to Signature Data Centers (Including Data Centers on the Alternate Carrier Data Center Exception List). All Signature Data Centers are carrier neutral. 2.6 Specific to Sterling, Advanced and Standard Data Centers (as set forth on the Alternate Carrier Data Center Exception List): 2.6.1 Customer must purchase at least an equal amount of Data Center colocation -related connectivity from Verizon. For example, if Customer wishes to bring in a T-3 circuit from another provider, it must purchase a T-3 or greater circuit from Verizon. Should Verizon determine Customer is purchasing more bandwidth from the alternate carrier, Customer will promptly purchase additional bandwidth from Verizon. Except as set forth herein, Verizon’s Data Centers are not carrier- neutral facilities. Verizon allows alternate carrier access to its Data Center Colocation customers for redundancy purposes only. 2.7 Customer will not be allowed to purchase alternate carrier access if such access requires the alternate carrier to pull fiber to Customer’s cabinet directly. 2.8 Alternate Carrier Data Center Exception List. location CodeSite Site Classification InternetPublic (Yes/No) Exchange Point Services Available (Yes/No) Carrier Neutral (Yes/No) Number of Carriers Sterling Ashburn IAD1 Yes No NO 2 Series Sterling Atlanta ATL1 Yes No No 2 Series DATA CENTER NETWORKING AND CONNECTIVITY + Sterling Carteret EWR1 Yes No NO 2 Series Sterling Doral (Miami) MIA2 Yes No NO 2 Series Sterling Houston IAH1 Yes No NO 2 Series Irving Sterling DFW1 Yes No NO 2 (Dallas) Series Sterling Norcross ATL2 Yes No No 2 Series Sterling Piscataway EWR2 Yes No NO 3 Series Richardson Sterling DFW3 Yes No NO 2 (Dallas) Series San Jose Sterling SJC1 Yes No NO 2 (Fortune) Series Torrance Sterling LAX1 Yes No NO 2 (Los Angeles) Series Sterling Toronto YYZ1 Yes No NO 4 Series Sterling Vancouver YVR1 Yes No NO 4 Series Westmont Sterling ORD1 Yes No NO 2 (Chicago) Series 3. Inter-Connect Cables. Inter-Connects are required for any connection outside of the Customer’s environment. Inter-Connect cables connect Customer’s Colocation Equipment with telecommunications services via a circuit from the patch panel inside the Data Center to the Customer’s cabinet inside the Data Center. The patch panel is the demarcation point (“d-marc”) where Verizon or a third-party carrier terminates its circuit. Various types of Inter-connect cables may be provisioned through Verizon. All Inter-connections relevant to interconnecting the Customer Colocation Equipment with telecommunications services shall be established through Verizon’s common Inter-connect panel in each Facility. Interconnect signal and power cabling between Verizon and Customer will be as designated by Verizon. 4. Customer Communication. Except as provided herein, Verizon will communicate with Customer and all of Verizon’s Other Customers and Verizon’s Other Customers will communicate with Customer and each other, primarily via email. Customer must ensure that all contact information it provided to Verizon in the IRR remains correct and current. 5. Peering. If Customer chooses Exchange Point Services or peering and such services are available at the data center where Customer has Equipment Space, the following shall apply: 5.1 By choosing Exchange Point Services, Customer is requesting the right to establish a Connection. The peering agreements that Customer and any of Verizon’s Other Customers may establish between and among each other are binding on Customer and Verizon’s Other Customers. Verizon will not be party to Customer’s peering agreements with Verizon’s Other Customers and those agreements will not be binding on Verizon. 5.2 Customer must provide Verizon an email address to which Verizon’s Other Customers may send requests for peering. If any of Verizon’s Other Customers, or a potential new Verizon Other Customer, sends Customer a peering request to the email address that the Verizon Other Customer provides for that purpose, Customer must respond to that peering request within five (5) working days. 5.3 Customer may only connect equipment that Customer owns and operates to Verizon’s peering LAN. Customer may not connect equipment to Verizon’s peering LAN on behalf of third parties. 5.4 Customer must only use IP addresses on the interface(s) of Customer’s router(s) connected to Verizon’s peering LAN which Verizon allocates to Customer. 5.5 Customer may only present a single MAC address to any of Verizon’s individual ports that is allocated to Customer. 5.6 Customer must register in advance all routes to be announced through a peering in the ARIN, RIPE or equivalent routing registry. 5.7 Customer must have its own Autonomous System (“AS”) number and must register the routing policy for AS in the ARIN, RIPE or equivalent routing registry. 2014 Verizon. All Rights Reserved. Page 2 of 6 Verizon CONFIDENTIAL DATA CENTER NETWORKING AND CONNECTIVITY + 5.8 Peering between Customers' routers across the Verizon Peering Fabric will be via BGP-4. 5.9 Customer shall not generate unnecessary route flap or advertise unnecessarily specific routes in peering sessions with Verizon’s Other Customers across the Verizon Peering Fabric. 5.10 Customer may not advertise routes with a next-hop other than that of Customer’s own routers without Verizon’s prior written permission or that of the advertised party. 5.11 Customer may not forward traffic across the Verizon Peering Fabric unless either the traffic follows a route advertised in a peering session at the Verizon Peering Fabric or where Customer has received prior written permission to do so from the Customer to whom the traffic is forwarded. 5.12 On all interfaces connected to us, Customer must disable: • Proxy ARP, ICMP redirects, CDP, IRDP, Directed broadcasts, IEEE802 Spanning Tree, Interior routing protocol broadcasts, and all other MAC layer broadcasts except ARP; and • Any duplex, speed, or other link parameter auto-sensing. 5.13 Customer shall not announce ("leak") prefixes including some or all of Verizon’s peering LAN to other networks without Verizon’s explicit written permission. 5.14 Customer must set net masks on all interfaces connected to Verizon to include Verizon’s entire peering LAN. Customer will not touch equipment and/or cabling owned by Verizon or Verizon’s Other Customers and installed at the Facility, or in the room containing Verizon’s peering equipment, without both the explicit written permission of both Verizon and Verizon’s Other Customer who owns the equipment. 5.15 Customer will not install 'sniffers' to monitor traffic passing through the Verizon Peering Fabric, except through Customer’s own ports. 5.16 Customer shall not routinely use the Verizon Peering Fabric for carrying traffic between Customer’s own routers. 5.17 Customer’s use of the Verizon Peering Fabric must at all times conform to the relevant standards as laid out in STD0001 (RFC2600) www.ietf.org/rfc/rfc2600.txt and associated Internet STD documents. 5.18 Customer will not circulate correspondence on confidential Verizon mailing lists to non-Customers. Part III: Terms and Conditions. 1. Termination of Service Order. If Customer terminates Data Center Interconnection Services without Cause (as defined in the Agreement), or if Verizon terminates Data Center Interconnection Services due to Customer’s default before the end of the Commitment Period, Customer agrees to pay Verizon a termination liability charge equal to the monthly fees due for the terminated Data Center Interconnection Services multiplied by the number of months left before the end of the Commitment Period for such Data Center Interconnection Services (“Termination Fee”), plus a pro rata portion of any and all credits received by Customer, in addition to all amounts owed for Data Center Interconnection Services already received. The parties acknowledge that this Termination Fee is an estimate of the actual damage that Verizon will suffer and is not a penalty. 2. Prohibited Uses. Customer shall not create or set up a meet-me-point or peering exchange or engage in or provide any services either directly or indirectly related thereto which may compete with similar services provided by Verizon via Verizon’s Peering Fabric or physical or optical interconnect platforms.
Load more

Recommended publications
  • Data Centers and Cloud Computing Data Centers
    Data Centers and Cloud Computing Data Centers • Large server and storage farms – 1000s of servers • Intro. to Data centers – Many TBs or PBs of data • Virtualization Basics • Used by – Enterprises for server applications – Internet companies • Intro. to Cloud Computing • Some of the biggest DCs are owned by Google, Facebook, etc • Used for – Data processing – Web sites – Business apps Computer Science Lecture 22, page 2 Computer Science Lecture 22, page 3 Inside a Data Center MGHPCC Data Center • Giant warehouse filled with: • Racks of servers • Storage arrays • Cooling infrastructure • Power converters • Backup generators • Data center in Holyoke Computer Science Lecture 22, page 4 Computer Science Lecture 22, page 5 Modular Data Center Virtualization • ...or use shipping containers • Each container filled with thousands of servers • Can easily add new containers • Virtualization: extend or replace an existing interface to – “Plug and play” mimic the behavior of another system. – Just add electricity – Introduced in 1970s: run legacy software on newer mainframe hardware • Allows data center to be easily • Handle platform diversity by running apps in VMs expanded – Portability and flexibility • Pre-assembled, cheaper Computer Science Lecture 22, page 6 Computer Science Lecture 22, page 7 Types of Interfaces Types of OS-level Virtualization • Different types of interfaces – Assembly instructions – System calls • Type 1: hypervisor runs on “bare metal” – APIs • Type 2: hypervisor runs on a host OS • Depending on what is replaced /mimiced,
    [Show full text]
  • Deploy, Operate, and Evolve Your Data Center: HP Datacenter Care
    Brochure Deploy, operate, and evolve your data center HP Datacenter Care The data center is evolving—shouldn’t Improve agility, scalability—react at the your support keep pace? speed of business Historically, business-critical IT has been delivered on dedicated, HP Datacenter Care service is designed to support this homogenous, and proprietary infrastructures. In this siloed results-oriented approach by providing an environment-wide IT model, performance, uptime, and security outweighed support solution tailored to your needs. HP Datacenter Care considerations of speed, agility, and cost. Now, however, the trends is a flexible, comprehensive, relationship-based approach to of mobility, big data, and cloud computing are fundamentally personalized support and management of heterogeneous data changing how you deliver information, and how technology is centers. Datacenter Care is a structured framework of repeatable, implemented, moving closer to unconstrained access to IT. tested, and globally available services “building blocks.” You have an account support manager (ASM) who knows your business and your IT is delivered as services anywhere, across hybrid deployments of IT environment, and who can help you select the services you need private, managed, and public cloud, as well as traditional IT. It’s what from an extensive portfolio of support and consulting services. The HP is developing as the Converged Cloud, and it can finally allow ASM leverages our experience in supporting complex environments, enterprises to achieve business agility, with choice and improved global support partnerships, and technical expertise. ROI. Today, HP is a leader in the industry for support services, for customers worldwide who need to keep their systems running, So you get exactly the services you need—when and where you reduce costs, and avoid issues.
    [Show full text]
  • The Cloud-Enabled Data Center
    A Revolutionary Technology Extending the Ultra-Broad Functionality of Ethernet White Paper May 2013 The Cloud-Enabled Data Center The Cloud-Enabled Data Center Introduction A growing number of organizations are adopting some form of cloud computing to meet the challenges of rapidly deploying their IT services and addressing their dynamic workload environments while maximizing their IT return on investments (ROIs). Cloud computing gives users the ability to access the IT resources faster than traditional and virtual servers. It also provides improved manageability and requires less maintenance. By deploying technology as a service, your users access only the resources they need for a specific task, which prevents you from incurring costs for computing resources not in use. In addition, developing a cloud-enabled data center can improve operational efficiencies while reducing operational expenses by 50%. Panduit, the leader in Unified Physical Infrastructure offerings, and IBM, a pioneer in delivering cloud computing solutions to clients, have joined forces to deliver optimized, custom and preconfigured solutions for the cloud- enabled data center. This white paper describes how network, storage, compute and operations are important factors to consider when deploying private and public cloud computing in the data center. Specifically, it examines integrated stack/pre- configured and custom cloud deployments. It also explains the importance of the physical infrastructure as the foundation in successful cloud deployment and maintenance. Finally, it showcases how IBM’s depth of experience in delivering systems and software for cloud solutions when combined with Panduit’s physical infrastructure expertise, provides a tremendous impact on room-level data center environmental and new-age topology.
    [Show full text]
  • Comparison of Availability Between Local and Cloud Storage Leviathan Security Group
    Comparison of Availability Between Local and Cloud Storage Leviathan Security Group limitless innovation. no compromise. Introduction The U.S. National Institute for Standards and Technology denes cloud computing as having ve essential characteristics: on-demand self- service for provisioning, network access, the use of virtual machines to provide servers, rapid elastic provisioning and release of servers, and metering capability on the service provided.1 This paper seeks to answer whether, from the perspective of availability of data, especially in the face of natural or manmade threats to data and access, cloud computing is able to provide a greater benet than local data storage. For the purposes of this discussion, local data storage will include arrangements where data is kept on business premises or in a nearby datacenter, such as a colocation facility or other rigidly-provisioned resource. We will rst examine the signicant dierentiator that cloud computing provides in this space, and then examine dierent scales of threats to availability to see whether local data storage or cloud data storage fares better against known historical threats. 2 The Cloud Dierentiator: Geographic Redundancy At its heart, cloud computing and cloud storage are exactly the same as computing and storage provided through a datacenter or SOHO server; the cloud is made of computers. The dierence between cloud- based storage and local storage is that using cloud-based storage allows replication between separate geographic regions. Indeed, the key feature of
    [Show full text]
  • Ovirt Storage Overview
    Ovirt Storage Overview Jun 8 th, 2012 Barak Azulay Storage overview – oVirt workshop 2011 1 Agenda ● Defining the problem ● Roadmap ● Storage Domain ● How to contribute ● Storage Pool ● Q&A ● Example ● Domain Classes ● Domain Types ● File Domains ● Block Domains ● SPM ● Thin Provisioning Storage overview – oVirt workshop 2011 2 Defining the problem ● The requirements ● Manage tens of thousands of virtual disk images ● Each image potentially accessible from hundreds (thousands?) of nodes ● Support both file based storage as well as raw block devices ● The assumptions ● Exclusive access when used ● Big (X GBs) ● Centralized manager (can be HA in and by itself) Storage overview – oVirt workshop 2011 3 Defining the problem - guidelines ● High level, image centered API ● Cluster safe ● High performance (not in data path) ● Highly available ● no single point of failure ● Continues working in the absence of the manager ● Backing storage agnostic Storage overview – oVirt workshop 2011 4 Storage Domain ● A standalone storage entity ● Stores the images and associated metadata (but not VMs) Only true persistent storage for VDSM Domain Storage overview – oVirt workshop 2011 5 Domain Classes ● Data ● Master ● ISO (NFS only) ● Backup (NFS only) ● Domain classes are planned for deprecation Storage overview – oVirt workshop 2011 6 Domain Types ● File Domains (NFS, local dir) ● Use file system features for segmentation ● Block Domains (iSCSI, FCP, FCoE, SAS, ...) ● Use LVM for segmentation ● Very specialized use of LVM Storage overview – oVirt workshop
    [Show full text]
  • The Cloud V. Data Center Decision
    SPECIAL REPORT The cloud v. data center decision COPYRIGHT ©2017 CBS INTERACTIVE INC. ALL RIGHTS RESERVED. THE CLOUD V. DATA CENTER DECISION TABLE OF CONTENTS 03 Cloud v. data center: Key trends for IT decision-makers 11 Infographic: Cloud use is growing, but the data center isn’t dead yet 12 Understanding the pros and cons of five cloud types 16 Five major pitfalls to avoid in a cloud migration 19 Multi-cloud is a messy reality, but there’s hope 23 Six reasons why companies hang on to their data centers 27 Has IT’s default setting switched from data center to cloud? 30 How hybrid cloud is strengthening Fitness First 2 COPYRIGHT ©2017 CBS INTERACTIVE INC. ALL RIGHTS RESERVED. THE CLOUD V. DATA CENTER DECISION CLOUD V. DATA CENTER: KEY TRENDS FOR IT DECISION-MAKERS BY CHARLES MCLELLAN Cloud-based compute, networking and storage infrastructure, and cloud-native applications, are now firmly on the radar of IT managers—be they in startups, small businesses or large enterprises. So much so that, whereas a few years ago the question facing CIOs was “Which workloads should I move to the cloud?”, it’s now becoming “Which, if any, workloads should I keep on-premises?”. While most organisations will probably end up pursuing a hybrid cloud strategy, it’s worth examining this turnaround, and the reasons behind it. The general background, as ZDNet has explored in recent special features, is the competitive pressure for organisations to undergo a digital transformation based on cloud-native applications and methods such as DevOps, in pursuit of improved IT and organisational performance.
    [Show full text]
  • Amazon Web Services (AWS) Is Committed
    The Cloud Amazon Web Services (AWS) is committed to running our business in the most environmentally friendly way possible and achieving 100% renewable energy usage for our global infrastructure. AMAZON SUSTAINABILITY ENVIRONMENT 44 Learn how AWS is working to achieve Amazon’s goal of 100% renewable energy. JAN 2016 JAN Amazon launches Wind Farm JUL 2015 AWS announces Fowler Ridge, marking the first that it has contract- of our four announced renew- APR 2015 Amazon announces joining ed with Iberdrola able energy projects to move the American Council on Renewables, LLC into full operation. Renewable Energy (ACORE) to construct and op- and will participate in erate Amazon Wind JUN 2016 AWS and Dominion the U.S. Partnership for Farm U.S. East. Virginia Power join forces Renewable Energy Finance on a landmark renewable (U.S. PREF) to increase our energy delivery deal. work with state and federal NOV 2015 NOV With this, Dominion Vir- policymakers and other AWS announces that it ginia Power will manage stakeholders to enable more has contracted with EDP and integrate the energy renewable energy opportu- Renewables to construct produced from various nities for cloud providers. and operate Amazon Wind Amazon wind and solar OCT 2016 Farm U.S. Central. Amazon Solar Farm U.S. farm projects onto the East is now in production grid that serves AWS in Accomack County, data centers. Virginia. 2014SEP 2015 2015 2016 Amazon joins The Buyers’ Princi- NOV 2016 NOV ples to collaborate with more than AWS announces five new solar farms across the Common- NOV 2014 NOV AWS shares 40 other companies on making wealth of Virginia.
    [Show full text]
  • All About Cloud
    Everything as a service HP’s point of view on cloud computing and cloud services Rebecca Lawson April 2010 1 Everything as a Service A world of information, opportunities and experiences—from computing power to business processes to personal interactions, are delivered wherever, however and whenever you need it. 2 It’s All About the Service Service providers Service consumers Field engineer Business Finance services executive Campaign director Application Sales person services Logistics manager Data Call center services representative App developer Infrastructure QA engineer services Service manager 3 Driving Outcomes That Matter Technology- Business enabled Business Outcomes Strategy services Improve value Become more agile Enable innovation 4 Source and Govern Services That Result in Outcomes That Matter Cloud service IT organization Outcomes that providers Strategic service broker matter Hosted/managed Accelerate growth service providers Services Service Services Lower costs Network service sourced portfolio delivered providers Mitigate risk Internal service providers 5 Perspective on the IT Service Supply Chain Cloud service provider IT organization Global-class Service portfolio software Business users Massive scale-out infrastructure S S S S S Business S outcome Enterprise-class Hosted, managed, software outsourced service provider S Dedicated / shared Enterprise-class infrastructure software Dedicated / shared infrastructure 6 The Real Question: Which Services, From Which Source? Corporate website service Sales forecasting service E-mail service Linux Dev lab service Supply Chain service 7 Cloud Services Deliver New Kinds of Value Service providers Service consumers Cloud services are highly scalable and elastic technology-enabled services, delivered and consumed over the internet through an as-needed, pay-per-use business model.
    [Show full text]
  • Pi DATACENTERS
    Case Study Data Center Modernization Pi DATACENTERS As an enterprise-class cloud service provider, Pi DATACENTERS wanted to offer its clients a transparent, cost-effective and technically superior experience. By selecting SUSE® OpenStack Cloud, the company gained a cost-effective and open solution, backed by enterprise support from SUSE. With its “@PiCloud™” platform powered by SUSE OpenStack Cloud in place, Pi DATACENTERS provides robust, yet optimized, IaaS, PaaS, DRaaS and a host of other cloud-enabled services, allowing its enterprise customers to concentrate on their businesses, not IT. Mr. Sunder Muthevi Overview Challenge Founded in 2014, Pi DATACENTERS is an As a new business entering the enterprise- enterprise-class cloud service provider, class cloud service provider sector, Pi based out of Amaravati, the capital of the DATACENTERS wanted to provide clients newly reorganized state of Andhra Pra- with a completely different experience desh, India. As a state-of-the-art, green- from existing operators. Many competing field data center, the company offers a full public clouds lacked a data center in India, spectrum of solutions across Infrastructure and could therefore not provide transpar- Pi DATACENTERS at a Glance as a Service (IaaS), Platform as a Service ency about where data was physically Pi DATACENTERS is an enterprise-class cloud (PaaS), and Disaster Recovery as a Service located. Pi DATACENTERS knew that it service provider with clients in the government, (DRaaS), along with a host of other cloud- could provide a more personalized, local, retail and IT sectors amongst others. enabled services riding on its “@PiCloud™” and economical service, but needed to platform.
    [Show full text]
  • F5 Application Delivery Services in the Google Cloud
    OVERVIEW F5 APPLICATION DELIVERY SERVICES IN THE GOOGLE CLOUD Public cloud vendors offer enterprises increased scalability and flexibility, along with a reduction in infrastructure and operational costs. As a result, 89 percent of companies are housing part of their application portfolio in the public cloud.1 Whether located in the public cloud, private cloud, or an on-premises data center, applications require specific services to ensure their security, availability, and performance. F5® BIG-IP® virtual editions (VEs) provide all of these benefits. Now fully integrated into the Google Cloud Engine, BIG-IP VEs extend F5’s application delivery capabilities beyond that of the traditional data center perimeter. KEY BENEFITS CHALLENGE • Cut costs by scaling in the cloud, Infinite scalability, unmatched flexibility, and reduced overheads make computing in the public cloud not on premises seem like the perfect IT solution. However, many enterprises making the shift to the cloud do so • Protect customer data anywhere amidst concerns that their applications’ security and performance may be diminished, or that they’ll within a hybrid cloud architecture fall victim to vendor lock-in and incur large re-architecting costs. This is a common fear, with a recent • Easily move workloads between study finding that 78 percent of IT decision makers worry about the portability of their workloads in Google Cloud and data centers the cloud.2 Increased network segregation and inconsistent application services across hybrid cloud • Maintain high availability of web architectures are also placing additional strain on IT departments while generating new security applications vulnerabilities for attackers to take advantage of. But it doesn’t need to be this way.
    [Show full text]
  • Multi-Site Openstack Deployment Options & Challenges for Telcos
    MULTI-SITE OPENSTACK DEPLOYMENT OPTIONS & CHALLENGES FOR TELCOS Azhar Sayeed Chief Architect [email protected] DISCLAIMER Important Informaon The informaon described in this slide set does not provide any commitments to roadmaps or availability of products or features. Its inten+on is purely to provide clarity in describing the problem and drive a discussion that can then be used to drive open source communi+es Red Hat Product Management owns the roadmap and supportability conversaon for any Red Hat product 2 AGENDA • Background: OpenStack Architecture • Telco Deployment Use case • Distributed deployment – requirements • Multi-Site Architecture • Challenges • Solution and Further Study • Conclusions 3 OPENSTACK ARCHITECTURE WHY MULTI-SITE FOR TELCO? • Compute requirements – Not just at Data Center • Mul+ple Data Centers • Managed Service Offering • Managed Branch Office • Thick vCPE • Mobile Edge Compute • vRAN – vBBU locaons • Virtualized Central Offices • Hundreds to thousands of locaons • Primary and Backup Data Center – Disaster recovery • IoT Gateways – Fog compung 6 Centrally managed Compute closer to the user Multiple DC or Central Offices Independent OpenStack Deployments Remote Sites E2E Orchestrator • Hierarchical Connec+vity model of CO • Remote sites with compute Security & Firewall requirements Quality of Service (QoS) • Extend OpenStack to these sites Traffic Shaping Overlay Device Management Tunnel over Internet Main Data Center Backup Data Center A typical service almost always spans across mulple DCs Remote Data 7 Centers
    [Show full text]
  • Emerging Indonesian Data Center Market and Energy Efficiency Opportunities
    THE EMERGING INDONESIAN DATA CENTER MARKET AND ENERGY EFFICIENCY OPPORTUNITIES ASIAN DEVELOPMENT BANK THE EMERGING INDONESIAN DATA CENTER MARKET AND ENERGY EFFICIENCY OPPORTUNITIES April 2017 ASIAN DEVELOPMENT BANK Creative Commons Attribution 3.0 IGO license (CC BY 3.0 IGO) © 2017 Asian Development Bank 6 ADB Avenue, Mandaluyong City, 1550 Metro Manila, Philippines Tel +63 2 632 4444; Fax +63 2 636 2444 www.adb.org Some rights reserved. Published in 2017. ISBN 978-92-9257-799-5 (Print), 978-92-9257-800-8 (e-ISBN) Publication Stock No. TCS178743 DOI: http://dx.doi.org/10.22617/TCS178743 The views expressed in this publication are those of the authors and do not necessarily reflect the views and policies of the Asian Development Bank (ADB) or its Board of Governors or the governments they represent. ADB does not guarantee the accuracy of the data included in this publication and accepts no responsibility for any consequence of their use. The mention of specific companies or products of manufacturers does not imply that they are endorsed or recommended by ADB in preference to others of a similar nature that are not mentioned. By making any designation of or reference to a particular territory or geographic area, or by using the term “country” in this document, ADB does not intend to make any judgments as to the legal or other status of any territory or area. This work is available under the Creative Commons Attribution 3.0 IGO license (CC BY 3.0 IGO) https://creativecommons.org/licenses/by/3.0/igo/. By using the content of this publication, you agree to be bound by the terms of this license.
    [Show full text]