For optical grid/cloud scenarios, the dimensioning problem comprises not only deciding on the network dimensions (i.e., link bandwidths), but also choosing appropriate locations to install server infrastructure (i.e., data centers), as well as determining the amount of required server resources (for storage and/or processing). Given that users of such grid/cloud systems in general do not care about the exact physical locations of the server resources, a degree of freedom arises in choosing for each of their requests the most appropriate server location. We will exploit this anycast routing principle (i.e., source of traffic is given, but destination can be chosen rather freely) also to provide resilience: traffic may be relocated to alternate destinations in case of network/server failures. In this study, we propose to jointly optimize the link dimensioning and the location of the servers in an optical grid/cloud, where the anycast principle is applied for resiliency against either link or server node failures. While the data center location problem has some resemblance with either the classical p-center or k-means location problems, the anycast principle makes it much more difficult due to the requirement of link disjoint paths for ensuring grid resiliency

Develder, Chris

Jaumard, Brigitte

Shaikh, Ali Shaikh

English

Ghent University Academic Bibliography

Selecting the Best Locations for Data Centers inResilient Optical Grid/Cloud Dimensioning(Invited paper)Brigitte Jaumard*, Ali Shaikh*, Chris Develder†*CSE, Concordia University, Montreal (Qc) H3G 1M8 Canada†Dept. of Information Technology - IBCN, Ghent University – IBBT, Ghent, BelgiumABSTRACTFor optical grid/cloud scenarios, the dimensioning problem comprises not only deciding on the networkdimensions (i.e., link bandwidths), but also choosing appropriate locations to install server infrastructure(i.e., data centers), as well as determining the amount of required server resources (for storage and/orprocessing). Given that users of such grid/cloud systems in general do not care about the exact physicallocations of the server resources, a degree of freedom arises in choosing for each of their requests themost appropriate server location. We will exploit this anycast routing principle (i.e., source of traffic isgiven, but destination can be chosen rather freely) also to provide resilience: traffic may be relocated toalternate destinations in case of network/server failures. In this study, we propose to jointly optimize thelink dimensioning and the location of the servers in an optical grid/cloud, where the anycast principle isapplied for resiliency against either link or server node failures. While the data center location problem hassome resemblance with either the classical p-center or k-means location problems, the anycast principlemakes it much more difficult due to the requirement of link disjoint paths for ensuring grid resiliency.Keywords: Optical Grids, Dimensioning Networks, ILP, Column Generation, Cloud Computing1. INTRODUCTIONA strong motivation for an optical grid/cloud network is to share resources among multiple users dis-tributed geographically but linked by high speed communication links. Optical grid/cloud networksemerge from WDM optical networks and grids/distributed computing. Research communities in differ-ent fields of e-Science are already using optical grid networks. But also more commercially oriented serviceproviders (offering licensing software, storage-systems, e-commerce, and bandwidth-intensive multimediaservices, etc.) can benefit from such distributed computing approaches to attain reliable and cost-effectiveinfrastructure. As such, cloud computing evolved from grid computing, aiming at on-demand provision-ing of resources. A well-known example showcasing the benefits for customers is that of The New YorkTimes using Amazon infrastructure through to process terabytes data in hours [1]. For a comprehensiverecent survey on optical grids and clouds, see, e.g., [2].Below, we address a dimensioning problem, expanded for optical grid/cloud networks: given a set oftraffic requests, determine (i) the link transport capacities, and (ii) the location of server resources.2. RELATED WORKTraffic engineering and the dimensioning of optical networks rely on Routing and Wavelength Assignment(RWA) with the objective of minimizing (min-RWA) the resources or maximizing (max-RWA) the Gradeof Service (GoS). Different RWA approaches have been studied in the literature, and their ILP formulationcomparison is presented in [3] and [4]. For optical grid/cloud environments, where the anycast routingprinciple — jobs can be executed on any designated server, and the location selection is often transparentto the end users — applies, the problem becomes that of anycast RWA (ARWA).Buysse et al. [5] solve the optical grid network dimensioning problem in two steps: (i) first the serverlocation is found, based on node origin of the job request, and its arrival rate; (ii) then the routing andwavelength assignment is optimized for working and backup paths. Other multiple-step approaches havebeen proposed: in [6], first the server locations are chosen, then the amount of computing resources,subsequently the inter-site traffic volumes, and finally the routing and resulting link transport capacities.The optimization of the server location in an optical grid environment has some resemblance withclassical facility location problems, namely the p-median and p-center problems, which have been muchinvestigated in the literature, see, e.g., [7] and [8]. Both problems deal with the location of p facilities.The p-median problem searches the facility locations such that the sum of the shortest demand weighteddistance between “customers” and p “facilities” is minimized. On the other hand, the p-center problemidentifies the facility locations in order to minimize the maximal distance for all demand points. Whilethe optical grid/cloud network dimensioning problem shares some features of the p-median problem, the1former is more complex due to: (i) the distance function (expressed in terms of, e.g., optical hops), and(ii) the additional requirements of backup paths in order to ensure network survivability. These lasttwo features makes the joint optimization of finding server locations and dimensioning both working andbackup paths, much more complex than the facility locations in a p-center or p-median context.We next propose two new decomposition ILP models for the joint optimization of the location of serversand the link dimensioning catering for both primary and backup paths. Some numerical results follow.3. JOINT OPTIMIZATION MODELSThe two proposed ILP models rely on a decomposition (column generation) scheme that extends ourprevious work on link dimensioning in an optical grid network [9]. The decomposition is around so-calledconfigurations which refer to a set of potential primary and backup paths for a given source node. Detailsare given below for each model.The optical network is assumed to be described by a directed graph G = (V,L), where V is the nodeset (n = |V |) and L is the set of (directed) links. Dv is number of job requests originating from sourcenode v ∈ V , ns is the maximum number of server nodes.In both models, binary parameters pw,c` (resp. pb,c` ) equal 1 if link ` is used by the working (resp.backup) path in configuration c, 0 otherwise. Similarly, acv=1 if node v is selected as a server locationeither by the working or the backup path in configuration c, and 0 otherwise. Note that provisioning ofjob requests originating from v is considered only if v is not selected as a server node.3.1. Model IIn Model I, a configuration c is defined for a given source node v ∈ Vd and consists of a pair of workingand backup paths from v to a server node, see Fig. 1(a) for an illustration of two possible configurationsfor source node v1 (the first one has a working path towards v7, and one backup towards v6, the secondone has a working path towards v7 and a backup towards v4 as well as via v4) and one potential onefor source node v2. The subset of configurations associated with source node v is denoted by Cv, andC =⋃v∈Vd Cv. Model I comprises three sets of variables: zc ∈ Z+ is equal to the number of selectedcopies of configuration c, bb` ∈ Z+ is equal to the number of shared backup bandwidth units on link `,and yv ∈ {0, 1} is a decision variable equal to 1 if node v is chosen as a server location, 0 otherwise.The objective function, which aims at minimizing the overall bandwidth requirements is as follows:min∑`∈L(bb` +∑c∈Cpw,c` · zc)(1)subject to: Dv · yv +∑c∈Cvzc ≥ Dv v ∈ Vd (2)∑c∈Cpw,c` · pb,c`′ · zc ≤ bb`′ `, `′ ∈ L : ` 6= `′ (3)∑c∈Cacv · zc ≤M · yv v ∈ V (4)∑v∈Vyv ≤ ns (5)Constraints (2) are the demand constraints. If node v hosts a server, then all the job requests originatingfrom v are readily served by v. Otherwise, we need some configurations associated with v to satisfy thedemand. Constraints (3) are used to compute the bandwidth requirement for a link `′ in a shared backuppath. Indeed, if `′ protects link `, with ` belonging to several working paths (modeled here throughthe various configurations c associated with working paths containing `), we must ensure `′ to have alarge enough transport capacity. Constraints (4) prevents from selecting a configuration in which nodev has been selected as a server location when yv = 0. The maximum number of server locations (ns) iscontrolled in (5).3.2. Model IIIn Model II, a configuration c is defined for a given source node v ∈ Vd and consists of a set of workingpaths and a single backup path from v to a server node, see Fig. 1(b) for an illustration with one potentialconfiguration for node v1 with two working path towards two different servers, v6 and v7, and one backuppath towards v7, and another possible configuration v2 with two working paths towards the same servernode v7 and one backup towards v6. At most one configuration per source node can be selected. Its2!"#!$#!%#!&#!'#!(#!)#(a) Sample configurations for Model I!"#!$#!%#!&#!'#!(#!)#(b) Sample configurations for Model IIFig. 1: In Model I, a configuration comprises a single working and single backup path, where multiplesuch configurations can be used for a single source. In Model II, only a single configuration per sourcenode will be used, but it consists of multiple working paths and a single backup. (Note that plain arrowsrepresent working paths, dashed arrows are backup paths.)mathematical expression can be rather easily deduced from that of Model I, but is not detailed here dueto the lack of space.3.3. Solving Models I and IIBoth Models I and II are solved using the combination of a column generation algorithm with two differentILP heuristic solution schemes. The first one, referred below as the classical one, is very similar to theone in [9], i.e., corresponds to the use of an ILP solver on the constraint matrix associated with theset of generated columns in order to reach the optimal solution of the linear relaxation. The second,referred below as MILP, comprises the following four steps: (i) optimally solve the linear relaxation ofthe model using a column generation (CG) algorithm, (ii) solve the MILP problem obtained with aninteger requirement only for the server variables (yv), (iii) fix the server variables either to 0 or to 1based on the MILP solution, and re-optimize the resulting linear relaxation, again with a CG algorithm,(iv) solve the ILP associated with the columns generated by the linear relaxation of Step iii.4. NUMERICAL RESULTSBoth models were tested on a European network topology (28 nodes and 41 bidirectional links, see e.g.,[9]) with ns = 5 server (cluster) nodes, whose locations had to be optimized. We generated uniformand non-uniform incremental traffic instances from 50 to 500 (discrete) job requests. In the non-uniformtraffic instances, the number of jobs is proportional to the population of the node (city). Models weresolved using the IBM ILOG CPLEX Optimizer software.0500100015002000250050 100 200 300 400 500Number   of  Wavelengths / Hops Number of Job Requests Model-I-Link-Classical Model-I-Link-MILPModel-II-Link-Classical Model-II-Link-MILP(a) Link Protection0500100015002000250050 100 200 300 400 500Number   of  Wavelengths / Hops Number of Job Requests Model-I-Link+Server-Classical Model-I-Link+Server-MILPModel-II-Link+Server-Classical Model-II-Link+Server-MILP(b) Link+Server ProtectionFig. 2: Uniform traffic: Model I vs. Model II and Classical vs. MILP solution approach.Evolution of bandwidth requirements with an increasing number of job requests is illustrated in Fig. 2for uniform traffic. In Fig. 2(a) (resp. Fig. 2(b)), results are provided for protection against single linkfailures (resp. single link or single server node failures). We show the total number of wavelengths summedover all links, where each data point represents an overage over 5 traffic instances, for a given numberof job requests. We observe, as intuitively expected (cf. Model I has more flexibility by possibly using3multiple different backup paths for a given source demand), that Model I requires lower network capacitythan Model II in the MILP approach, under both protection schemes. The MILP approach takes lessbandwidth than the classical, i.e., 12% in Model I and 5% in Model II. Although Model II solutioncomputing times are 66% higher than for Model I, it still offers a reasonable solution time for the off-linealgorithms to be used in planning or advance reservation systems. We note that the MILP approach ismore efficient than the classical one for both models, both in terms of computing times and in terms ofsolution accuracy.Looking at the cost of link+server protection, which also covers failures of a complete server node, we find(as intuitively expected) that this requires more network resources. Yet, the additional network capacityis reasonably limited: the link+server protection scheme requires 10% (resp. 6%) more bandwidth unitsthan only link protection for Model I (resp. Model II).We also assessed how the different models and solution approaches differ for the selection of the locationsof the server nodes. We observed that in more than 98% of the studied cases, the server nodes are selectedamong the same five nodes. In addition, even though Model I allows more than one backup path (ModelII does not), in practice there are very few cases where Model I selects more than one backup path.The same experiments were conducted with the non-uniform traffic instances, and the results are shownin Fig. 3. The qualitative conclusions as drawn from the uniform demands still apply in terms of relativeperformance of the various models (I vs II) and solution approaches (Classical vs MILP).0500100015002000250050 100 200 300 400 500Number   of  Wavelengths / Hops Number of Job Requests Model-I-Link-Classical_W Model-I-Link-MILP_WModel-II-Link-Classical_W Model-II-Link-MILP_W(a) Link Protection0500100015002000250050 100 200 300 400 500Number   of  Wavelengths / Hops Number of Job Requests Model-I-Link+Server-Classical_W Model-I-Link+Server-MILP_WModel-II-Link+Server-Classical_W Model-II-Link+Server-MILP_W(b) Link+Server ProtectionFig. 3: Non-uniform traffic: Model I vs. Model II and Classical vs. MILP solution approach.ACKNOWLEDGMENTB. Jaumard was supported by NSERC (Natural Sciences and Engineering Research Council of Canada) and bya Concordia University Research Chair (Tier I) on the Optimization of Communication Networks. C. Develderwas supported in part as post-doctoral fellow of the Research Foundation – Flanders (FWO–Vl.).REFERENCES[1] D. Gottfrid, “Self-service, prorated supercomputing fun.” http://open.blogs.nytimes.com/2007/11/01/self-service-prorated-super-computing-fun/, 1 Nov. 2007.[2] C. Develder, M. De Leenheer, B. Dhoedt, M. Pickavet, D. Colle, F. De Turck, and P. Demeester, “Opticalnetworks for grid and cloud computing applications,” Proceedings of the IEEE, vol. 100, pp. 1149–1167, May2012.[3] B. Jaumard, C. Meyer, and B. Thiongane, “Comparison of ILP formulations for the RWA problem,” OpticalSwitching and Networking, vol. 4, pp. 157–172, November 2007.[4] B. Jaumard, C. Meyer, and B. Thiongane, “On column generation formulations for the RWA problem,”Discrete Applied Mathematics, vol. 157, pp. 1291–1308, March 2009.[5] J. Buysse, M. De Leenheer, C. Develder, and B. Dhoedt, “Exploiting relocation to reduce network dimensionsof resilient optical grids,” in Proceedings of IEEE/VDE Workshop on Design of Reliable CommunicationNetworks - DRCN, pp. 100–106, October 2009.[6] C. Develder, B. Mukherjee, B. Dhoedt, and P. Demeester, “On dimensioning optical grids and the impact ofscheduling,” Photonic Network Communications, vol. 17, pp. 255–265, June 2009.[7] J. Reese, “Solution methods for the p-median problem: An annotated bibliography,” Networks, vol. 48, no. 3,pp. 125–142, 2006.[8] S. H. Owen and M. S. Daskin, “Strategic facility location: A review,” European Journal of OperationalResearch, vol. 111, no. 3, pp. 423 – 447, 1998.[9] A. Shaikh, J. Buysse, B. Jaumard, and C. Develder, “Anycast routing for survivable optical grids: Scalablesolution methods and the impact of relocation,” Journal of Optical Communications and Networking, vol. 3,pp. 767–779, 2011.4

Selecting the best locations for data centers in resilient optical grid/cloud dimensioning

Brigitte Jaumard

Ali Shaikh

Chris Develder

Crossref

For optical grid/cloud scenarios, the dimensioning problem comprises not only deciding on the network dimensions (i.e., link bandwidths), but also choosing appropriate locations to install server infrastructure (i.e., data centers), as well as determining the amount of required server resources (for storage and/or processing). Given that users of such grid/cloud systems in general do not care about the exact physical locations of the server resources, a degree of freedom arises in choosing for each of their requests the most appropriate server location. We will exploit this anycast routing principle (i.e., source of traffic is given, but destination can be chosen rather freely) also to provide resilience: traffic may be relocated to alternate destinations in case of network/server failures. In this study, we propose to jointly optimize the link dimensioning and the location of the servers in an optical grid/cloud, where the anycast principle is applied for resiliency against either link or server node failures. While the data center location problem has some resemblance with either the classical p-center or k-means location problems, the anycast principle makes it much more difficult due to the requirement of link disjoint paths for ensuring grid resiliency.For optical grid/cloud scenarios, the dimensioning problem comprises not only deciding on the network dimensions (i.e., link bandwidths), but also choosing appropriate locations to install server infrastructure (i.e., data centers), as well as determining the amount of required server resources (for storage and/or processing). Given that users of such grid/cloud systems in general do not care about the exact physical locations of the server resources, a degree of freedom arises in choosing for each of their requests the most appropriate server location. We will exploit this anycast routing principle (i.e., source of traffic is given, but destination can be chosen rather freely) also to provide resilience: traffic may be relocated to alternate destinations in case of network/server failures. In this study, we propose to jointly optimize the link dimensioning and the location of the servers in an optical grid/cloud, where the anycast principle is applied for resiliency against either link or server node failures. While the data center location problem has some resemblance with either the classical p-center or k-means location problems, the anycast principle makes it much more difficult due to the requirement of link disjoint paths for ensuring grid resiliency.P

Develder, ChrisTW058010013958470000-0003-2707-4176F5DC76B8-F0ED-11E1-A9DE-61C894A0A6B4

Archivsystem Ask23

https://biblio.ugent.be/publication/2983352/file/2983353.pdf

Selecting the best locations for data centers in resilient optical grid/cloud dimensioning

Abstract

Similar works

Full text

Available Versions

Ghent University Academic Bibliography

Crossref

Archivsystem Ask23