[DMANET] CfP: Workshop on Distributed Cloud Computing

FIRST CALL FOR PAPERS

Workshop on
Distributed Cloud Computing (DCC)

https://sites.google.com/site/dcc2013workshop/

held in Dresden, Germany
December 9-12

co-located with 6th IEEE/ACM International Conference on Utility and Cloud
Computing (UCC)


DATES

Abstracts due: 14 July 2013

Submissions due: 21 July 2013

Notification of acceptance: 10 September 2013

Camera-ready papers due: 27 September 2013

WORKSHOP GOAL

The workshop is interdisciplinary and touches both distributed systems as
well as networking and cloud computing. It is intended as a forum where
people with different backgrounds can learn from their respective field and
expertise. We want to attract both industry relevant papers as well as
papers from academic researchers working on the foundations of the
distributed cloud.

DCC 2013 accepts high-quality papers related to the distributed cloud which
fall into at least one of the following categories:

- Novel ideas on how to design and operate/manage the distributed cloud

- Principles and foundations of distributed cloud computing; algorithmic
solutions (resource management, scheduling, embedding, elasticity,
brokering)

- Architectural models, prototype implementations and applications (content
distribution, games, social networks, scientific computing, business)

- Virtualization technology and enablers (network virtualization,
software-defined networking)

- Experience with existing deployments and measurements (private, public,
hybrid, federated, aggregated clouds)

- Service and resource specification, languages, and formal verification

- Economic, robustness, and energy aspects of the distributed cloud (e.g.,
pricing and service models)


SYNOPSIS

Most of the focus in public cloud computing technology over the last 10
years has been on deploying massive, centralized data centers with thousands
or hundreds of thousands of servers. The data centers are typically
replicated with a few instances on a continent wide scale in semi-autonomous
zones. This model has proven quite successful in economically scaling cloud
service, but it has some drawbacks. Failure of a zone can lead to service
dropout for tenants if the tenants do not replicate their services across
zones. Some applications may need finer grained control over network latency
than is provided by a connection to a large centralized data center, or may
benefit from being able to specify location as a parameter in their
deployment.
Nontechnical issues, such as the availability of real estate, power, and
bandwidth for a large mega data center, also enter into consideration.

Another model that may be useful in many cases is to have many micro or even
nano data centers, interconnected by medium to high bandwidth links, and the
ability to manage these data centers and interconnecting links as if they
were one larger data center. This distributed cloud model is perhaps a
better match for private enterprise clouds, which tend to be smaller than
the large, public mega data centers, and it also has attractions for public
clouds run by telcom carriers which have facilities in geographically
diverse locations, with power, cooling, and bandwidth already available. It
is attractive for mobile operators as well, since it provides a platform on
which applications can be deployed and easily managed that could benefit
from a tighter coupling to the wireless access network. The two models are
not mutually exclusive:
for instance a public cloud operator with many large data centers
distributed internationally could manage its network of data centers like a
distributed cloud. The distinguishing characteristic from federated clouds
is that the component data centers are more integrated, especially with
respect to authentication and authorization, so that the computation,
storage, and networking resources are as tightly managed as if they were in
a single large data center.

SUBMISSION AND PUBLICATION

Submissions are single-blind and should not exceed 6 pages in length (in
IEEE format). For an accepted paper, at least one author must attend the
workshop (all participants must pay the UCC 2013 workshop and conference
fee).

Submissions will be handled by EasyChair.

The DCC 2013 workshop proceedings will be published as part of the UCC 2013
proceedings volume.


CHAIRS

James Kempf, Ericsson Research, San Francisco, USA

Stefan Schmid, Telekom Innovation Laboratories (T-Labs) & TU Berlin, Germany


TPC:

Chen Avin, Ben Gurion Uni, Israel

Raouf Boutaba, Uni Waterloo, Canada

David Breitgand, IBM Research Haifa, Israel

Marco Canini, T-Labs & TU Berlin, Germany

Yvonne Coady, Uni Victoria, Canada

Paolo Costa, Microsoft Research Cambridge & Imperial College, United Kingdom

György Dán, KTH, Sweden

Xiaoming Fu, Uni Goettingen, Germany

Pan Hui, HKUST, Hong Kong

Holger Karl, Uni Paderborn, Germany

Wolfgang Kellerer, TU Munich, Germany

Hermann de Meer, Uni Passau, Germany

Ruben S. Montero, Universidad Complutense de Madrid, Spain

Djamel F. H. Sadok, UFPE, Brazil

Arunabha Sen, Arizona State University, USA

Srini Seetharaman, T-Labs Silicon Valley, USA

Azimeh Sefidcon, Ericsson Research, Sweden

Puneet Sharma, HP Labs Palo Alto, USA

Upendra Sharma, IBM T. J. Watson Research Center, USA

Soren Telfer, AT&T Palo Alto, USA

Benoit Tremblay, Ericsson Research, Canada

Christian Tschudin, Uni Basel, Switzerland

VENUE:

DCC 2013 will take place in the Dorint Hotel Dresden, in the center of the
lively capital of Saxony. Dresden offers much more than the historic center
with its opera house, the 'Semperoper', and the 'Frauenkirche' church.
Dotted along the approximately 30 km long stretch of the Elbe River which
runs through the city, you will find many treasures: castles, villas,
vineyards, historic funiculars, and steamboats that are up to 130 years old.
During the conference week, the 579th annual Striezelmarkt will welcome all
conference participants for a unique artisanal and culinary experience.



**********************************************************
*
* Contributions to be spread via DMANET are submitted to
*
* DMANET@zpr.uni-koeln.de
*
* Replies to a message carried on DMANET should NOT be
* addressed to DMANET but to the original sender. The
* original sender, however, is invited to prepare an
* update of the replies received and to communicate it
* via DMANET.
*
* DISCRETE MATHEMATICS AND ALGORITHMS NETWORK (DMANET)
* http://www.zaik.uni-koeln.de/AFS/publications/dmanet/
*
**********************************************************