WWW/Internet - Portal do Software Público Brasileiro

More documents

Recommendations

Info

IADIS International Conference WWW/Internet 2010 algorithmic solutions, oriented to the efficient extraction of server status information from manyservers.In our experience, scalability at the network traffic level is not an issue comparable to the aforementionedproblems. In order to keep the control enforcement process scalable, each management task must orchestratethe control using the least amount of resources available. This implies the monitoring and control of only alimited subset of the entire system (this holds particularly true for short-time tasks). We decide not topermanently store each raw performance measure obtained from the subset, since this would be unfeasible,given the literally hundreds of time series that would need to be monitored. Instead, we treat each monitor asa stream of data which is filtered in a basic fashion and made directly available to the orchestrator. Thisoperation is straightforward, since low-level system monitors such vmstat and sar can be easily instrumentedto pipe their output to different processes. For some proprietary systems, it is possible to exploit the SNMPquerying capabilities offered by more sophisticated tools such as Cacti, Nagios, Zenoss, to extract the sameinformation from several system components.Since longer tasks tend often to use the results of shorter tasks, we instrument the orchestrator to extractproper subsets of the filtered data (typically, the last n performance measures coming from the mostimportant monitor probes) and to store them in a lightweight database. In this way, we reduce considerablythe set of monitored data available to the mid-term and long-term tasks, and we provide a persistent datastorage which is necessary to hold data spanning in longer ranges. A RAM database such as Firebird wouldfit perfectly, since it provides excellent performance over a moderately high volume of stored data. Ourexperience shows that this approach allows to monitor tens of hardware and software resources per node, in asubsystem consisting of a few hundreds nodes.The mid-term management tasks take the filtered data, aggregate it, detect (and possibly correct)anomalies, and produce a meaningful representation of a subsystem's internal state, which is used to enforcecontrol decisions aimed at improving the performance and optimizing the present behavior relevantsubsystems. These operations can be implemented through any standard math environment (Matlab, ROctave) or through mathematical libraries available for the most popular general purpose languages (Scipy,Numpy in Python). With respect to the whole set of time series available from the monitors, therepresentations produced by mid-term management tasks are much more compact in terms of size and arecomputed less often; thus, they can be stored into a DBMS, such as MySQL, PostgreSQL, Oracle.Finally, the long-term management tasks also perform more sophisticated tasks oriented improve theperformance and optimize the behavior of the whole system in the future. To this purpose, they retrieve thestate representations computed by the mid-term management tasks and perform sophisticated computationsinvolving long-term predictions, what-if analysis, capacity planning. The resulting models drive the decisionsof the orchestration modules.Our architecture is designed in such a way that the control actions can be implemented through off-theshelfhardware and software components. For example, request dispatching and load balancing can beoperated through standard setups based on Apache2 (through the mod_rewrite and mod_proxy modules),Tomcat (through AJP connectors in a clustered setup) and, more recently, on nginx. There are several viablealternatives for the virtualization of services; the most popular are Xen (version 3.0 and above) and KVM(the hypervisor officially adopted by the Linux community). All these solutions support (live) migrations,dynamic resource re-allocation, ballooning, paravirtualized device drivers for close-to-native performance.Another alternative is the use of resource containers (OpenVZ), which provide native performance at theexpense of executing a shared operating system kernel for all running services.205
ISBN: 978-972-8939-25-0 © 2010 IADISFigure 2. A hierarchical architecture for on-line management of cloud-based systems206
Page 2:
IADIS INTERNATIONAL CONFERENCEWWW/I
Page 5 and 6:
Copyright 2010IADIS PressAll rights
Page 7 and 8:
HOTLINK VISUALIZER: ADDING HOTLINKS
Page 9 and 10:
THE ROLE OF WEB-BASED COLLABORATIVE
Page 11 and 12:
DOCTORAL CONSORTIUMTOWARDS A DOMAIN
Page 13 and 14:
‣ Services, Architectures and Web
Page 15 and 16:
xiv
Page 17 and 18:
Ciprian Dobre, University Politehni
Page 19 and 20:
Runa Jesmin, University Of London,
Page 22:
Full Papers
Page 25 and 26:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 27 and 28:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 29 and 30:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 31 and 32:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 33 and 34:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 35 and 36:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 37 and 38:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 39:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 42 and 43:
IADIS International Conference WWW/
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140:
Page 143 and 144:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 145 and 146:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 147 and 148:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 149 and 150:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 151 and 152:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 153 and 154:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 155 and 156:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 157 and 158:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 159 and 160:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 161 and 162:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 163 and 164:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 165 and 166:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 167 and 168:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 169 and 170:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 171 and 172:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 173 and 174:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 175 and 176: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 177 and 178: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 179 and 180: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 181 and 182: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 183 and 184: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 185 and 186: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 187 and 188: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 189 and 190: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 191 and 192: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 193 and 194: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 195 and 196: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 197 and 198: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 199 and 200: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 201 and 202: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 203 and 204: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 205 and 206: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 207 and 208: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 209 and 210: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 211 and 212: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 213 and 214: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 215 and 216: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 217 and 218: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 219 and 220: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 221 and 222: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 223 and 224: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 225: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 229 and 230: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 231 and 232: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 233 and 234: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 235 and 236: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 237 and 238: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 239 and 240: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 241 and 242: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 243 and 244: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 245 and 246: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 247 and 248: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 249 and 250: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 251 and 252: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 253 and 254: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 255 and 256: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 257 and 258: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 259 and 260: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 261 and 262: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 263 and 264: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 265 and 266: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 267 and 268: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 269 and 270: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 271 and 272: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 273 and 274: ISBN: 978-972-8939-25-0 © 2010 IAD
Page 276:
Short Papers
Page 279 and 280:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 281 and 282:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 283 and 284:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 285 and 286:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 287 and 288:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 289 and 290:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 291 and 292:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 293 and 294:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 295 and 296:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 297 and 298:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 299 and 300:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 301 and 302:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 303 and 304:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 305 and 306:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 307 and 308:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 309 and 310:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 311 and 312:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 313 and 314:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 315 and 316:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 317 and 318:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 319 and 320:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 321 and 322:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 323 and 324:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 325 and 326:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 327 and 328:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 329 and 330:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 331 and 332:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 333 and 334:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 335 and 336:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 337 and 338:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 339 and 340:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 341 and 342:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 343 and 344:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 345 and 346:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 347 and 348:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 349 and 350:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 351 and 352:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 353 and 354:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 355 and 356:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 357 and 358:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 359 and 360:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 361 and 362:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 363 and 364:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 365 and 366:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 367 and 368:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 369 and 370:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 371 and 372:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 373 and 374:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 375 and 376:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 377 and 378:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 379 and 380:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 381 and 382:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 383 and 384:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 385 and 386:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 387 and 388:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 390 and 391:
Page 392 and 393:
Page 394 and 395:
Page 396 and 397:
Page 398 and 399:
Page 400 and 401:
Page 402 and 403:
Page 404 and 405:
Page 406 and 407:
Page 408 and 409:
Page 410 and 411:
Page 412:
Posters
Page 415 and 416:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 417 and 418:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 419 and 420:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 421 and 422:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 423 and 424:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 425 and 426:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 427 and 428:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 429 and 430:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 431 and 432:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 433 and 434:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 435 and 436:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 437 and 438:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 439 and 440:
ISBN: 978-972-8939-25-0 © 2010 IAD
Page 442 and 443:
Page 444 and 445:
Page 446 and 447:
Page 448 and 449:
Page 450 and 451:
Page 452:
Page 455 and 456:
Jang, C. ..........................
show all

WWW/Internet - Portal do Software Público Brasileiro

Create successful ePaper yourself

Delete template?

Save as template?