anchor.diff:  packages.
   The Agent uses these instructions to install and configure MySQL on the VM.
   
  -## <a id="blobstore"></a>Blobstore ##
  +### <a id="blobstore"></a>Blobstore ###
   The BOSH Blobstore stores the source forms of releases and packages and the
   compiled images of BOSH packages.
   An operator uploads a release using the BOSH CLI, and the Director inserts the
  
positive.code: 1. The Director uses the CPI to tell the IaaS to launch a VM.
  1. The IaaS provides the Director with information (IP addresses and IDs) the
  Agent on the VM needs to configure the VM.
  1. The Director updates the BOSH Registry with the configuration information for 
  the VM.
  1. The Agent running on the VM requests the configuration information for the VM
  from the BOSH Registry.
  
negative.code: Once created, the Director adds these tasks to the Task Queue.
  BOSH Worker processes take tasks from the Task Queue and act on them.
  
  ### <a id="health-monitor"></a>Health Monitor ###
  The Health Monitor uses status and lifecycle events received from BOSH Agents to
  monitor the health of VMs.
  If the Health Monitor detects a problem with a VM, it can send an alert through
  a notification plugin, or trigger the BOSH Resurrector.
  
  ### <a id="nats"></a>Message Bus (NATS) ###
  The Director and the Agents communicate through a lightweight publish-subscribe
  and distributed queueing messaging system called NATS.
  These messages have two purposes: to confirm the health of the Agent, and to
  inform the Director about changes in the health of monitored processes.
  
  ### <a id="registry"></a>Registry ###
  When BOSH creates or updates a VM, BOSH stores the following VM configuration
  information in the registry:
  
  * IP addresses for the network interface, gateway, and netmask
  * IDs for the volume reserved for the VM, for the VM itself, and for disks and other devices
  
  ### <a id="resurrector"></a>Resurrector ###
  If enabled, the BOSH Resurrector plugin automatically recreates VMs identified
  by the Health Monitor as stopped or unresponsive.
  
  ### <a id="queue"></a>Task Queue ###
  An asynchronous queue used by the BOSH Director and Workers to manage tasks.
  The Task Queue resides in a Redis key-value store.
  
  ### <a id="workers"></a>Workers ###
  BOSH Workers take tasks from the Task Queue and act on them.
  
  ## <a id="example"></a>Example Component Interaction ##
  This example shows how BOSH components interact when creating a new VM.
  
  ### <a id="create-vm"></a>Creating a New VM ###
  <%= image_tag("/images/deploy-sequence.png") %><br />
  
  1. Through the BOSH CLI, the operator takes an action (e.g. deploy for the first
  