anchor.diff:  
   <li>Mediates all communication between the Cell and the BBS</li>
   
  -<li>Maintains a presence record for the Cell in BBS and Locket</li>
  +<li>Maintains a presence record for the Cell in Locket</li>
   
   </ul></td>
   	</tr>
  
positive.code: 	<tr>
  		<td><strong>Job:</strong><br> bbs<br>
  		<strong>VM:<br></strong> <% if vars.product_name == "CF" %> diego-api <% else %> <%= vars.diego_vm_2 %> <% end %></td>
  		<td><ul><li>Maintains a real-time representation of the state of the Diego cluster, including desired LRPs, running LRPs, and in-flight Tasks.</li><li>Provides an RPC-style API over HTTP to Diego Core components and external clients, including the SSH Proxy and Route Emitter.</li><li>Ensures consistency and fault tolerance for Tasks and LRPs by comparing desired state with actual state.</li>
  		<li>Keeps <code>DesiredLRP</code> and <code>ActualLRP</code> counts synchronized. If the <code>DesiredLRP</code> count exceeds the <code>ActualLRP</code> count, requests a start auction from the Auctioneer. If the <code>ActualLRP</code> count exceeds the <code>DesiredLRP</code> count, sends a stop message to the Rep on the Cell hosting an instance</li>
  		<li>Monitors for potentially missed messages, resending them if necessary</li></td>
  	</tr>
  	<tr>
  		<td><strong>Job:</strong><br> file_server<br>
  		<strong>VM:</strong><br> <% if vars.product_name == "CF" %> api <% else %> <%= vars.diego_vm_1 %> <% end %></td>
  		<td><ul><li>Serves static assets that can include general-purpose App Lifecycle binaries and app-specific droplets and build artifacts</li></ul></td>
  	</tr>
  	<tr>
  		<td><strong>Job:</strong><br> locket<br>
  
negative.code: 
  ##<a id='overview'></a> Overview 
  
  Cloud Foundry uses the Diego system to manage app containers. Diego components assume app scheduling and management responsibility from the Cloud Controller. 
  
  
  Diego is a self-healing container management system that attempts to keep the correct number of instances running in Diego cells to avoid network failures and crashes. Diego schedules and runs Tasks and Long-Running Processes (LRP). For more about Tasks and LRPs, see [How the Diego Auction Allocates Jobs](diego-auction.html).
  