<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I intend to continue serving as Swift PTL for the Zed cycle.
<div><br>
</div>
<div>We have seen Swift scale in spectacular ways. Hard drives have grown</div>
<div>from 2-4 terabytes when Swift was started to 10-20T. The idea of a</div>
<div>"large cluster" has gone from dozens of petabytes across hundreds of</div>
<div>nodes to hundreds of petabytes across thousands of nodes.</div>
<div><br>
</div>
<div>We will continue to see (and address) new challenges in scaling Swift.</div>
<div>We anticipate hitting the bounds of our current ring format. We see</div>
<div>operators struggle to balance the prioritization of cluster expansion</div>
<div>and data durability. We see the need to improve sharding, so that</div>
<div>clients are less impacted by what's going on in the backend. All of</div>
<div>these have seen progress in the last cycle, and will continue to be</div>
<div>advanced in the next.</div>
<div><br>
</div>
<div>Just as important as scaling the core storage platform, however, is</div>
<div>building up the ecosystem of ancillary services that users have come</div>
<div>to expect out of their object storage. When a container grows to have</div>
<div>billions of objects, it is impractical to perform thousands of listing</div>
<div>requests to analyze its contents; instead, users expect a periodic</div>
<div>inventory that's easy to pull into their existing data pipelines.</div>
<div>Users should be able to examine their own access logs rather than</div>
<div>needing to involve operators. Users want to manage their data movement</div>
<div>and retention <i>en masse</i> rather than object-by-object.</div>
<div><br>
</div>
<div>I look forward to seeing the balance we strike between enhancing the</div>
<div>core storage platform and building out the data services surrounding</div>
<div>it over the coming years.</div>
<div><br>
</div>
Tim Burke<br>
</div>
</body>
</html>