co-located with ACM PODC 2016
25 July, 2016
Chicago, Illinois, USA
Important Dates
Abstract Submission: 5 May 2016 (extended!)
Submission: 12 May 2016 (extended!)
Notification: 1 June 2016
Camera-ready: 20 June 2016
Workshop: 25 July 2016
Keynote Speaker
Larry Peterson, Princeton, USA
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 telco 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 locality and a tighter coupling to the
access network. Applications with latency constraints or with too much data
to backhaul to a large mega data center can benefit from distributed
processing. 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.
Goals
The International Workshop on Distributed Cloud Computing (DCC) 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 fields 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.
In particular, this year's edition of DCC will feature an applied session
in the afternoon, chaired by Rick McGeer.
Scope
DCC 2016 accepts high-quality papers related to the distributed cloud which
fall into at least one of the following categories:
- Foundations and principles of distributed cloud computing
- Optimization and algorithms
- Economics and pricing
- Experience with and performance evaluation of existing deployments and
measurements (public, private, hybrid, federated environments)
- Architectural models, prototype implementations and applications
- Virtualization technology and enablers (network virtualization,
software-defined networking)
- Service and resource specification, languages, and formal verification
Submission and Publication
Submissions are single-blind and should not exceed 6 pages in length (in
ACM format:http://www.sigmetrics.org/sig-alternate-per.cls).
Accepted papers will appear on ACM Digital Library. However, authors may
voluntarily also opt out from an official publication, and simply present
their work at the workshop.
For an accepted paper, at least one author must attend the workshop.
Workshop History
DCC 2013 was co-located with IEEE/ACM UCC 2013, DCC 2014 was co-located
with ACM SIGCOMM 2014, and DCC 2015 was co-located with ACM SIGMETRICS.
TPC Chairs
Patrick Eugster, TU Darmstadt, Germany and Purdue, USA
James Kempf, Ericsson Research, Silicon Valley, USA
Rick McGeer, US Ignite, USA
Stefan Schmid, Aalborg University, Denmark
TPC
• Ali Al-Shabibi, Open Networking Laboratory (ONLab), USA
• Hadi Bannazadeh, University of Toronto, Canada
• Andy Bavier, Princeton University, USA
• Pramod Bhatotia, TU Dresden, Germany
• Annette Bieniusa, TU Kaiserslautern, Germany
• Ivona Brandic, Vienna University of Technology, Austria
• Justin Cappos, New York University, USA
• Gregory Chockler, Royal Holloway, University of London (RHUL), UK
• Lars Eggert, NetApp, Germany
• Serge Fidida, Université Pierre et Marie Curie (UPMC), Sorbonne
University, France
• Anshul Gandhi, Stony Brook University, USA
• Erwan Le Merrer, Technicolor, France
• Hanoch Levy, Tel Aviv University, Israel
• Tamás Lukovszki, Eötvös Loránd University, Hungary
• Joe Mambretti, Northwestern University, USA
• Catalin Meirosu, Ericsson Research, Sweden
• Hausi Müller, University of Victoria, Canada
• Akihiro Nakao, University of Tokyo, Japan
• Marina Papatriantafilou, Chalmers University of Technology, Sweden
• Fernando Pedone, University of Lugano (USI), Switzerland
• Glenn Ricart, US Ignite and U. Utah, USA
• Robert Ricci, University of Utah, USA
• Niky Riga, BBN Technologies, USA
• Rodrigo Miragaia Rodrigues, Instituto Superior Tecnico (University of
Lisbon) and INESC-ID, Portugal
• Elad Michael Schiller, Chalmers University of Technology, Sweden
• James P.G. Sterbenz, University of Kansas, USA
• François Taïani, Université de Rennes 1, France
• Vicraj Thomas, BBN Technologies, USA
• Kurt Tutschku, BTH, Sweden
• Maarten van Steen, University of Twente, the Netherlands
• Brecht Vermeulen, iMinds and Ghent University, Belgium
• Marko Vukolić, IBM Research Zurich, Switzerland
• John Wroclawski, University of Southern California, USA
**********************************************************
*
* 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/
*
**********************************************************
Posts
