anchor.diff:  --------------------------------------------------
   // TESTRESPONSE[skip:no way to know if we will get this response immediately]
   
  -<1> The policy used to manage the index 
  +<1> The policy used to manage the index
   <2> The age of the index
   <3> The step {ilm-init} is performing on the index
   <4> The definition of the current phase (the `hot` phase)
  
positive.code: 
  To automate rollover and management of time-series indices with {ilm-init}, you:
  
  . <<ilm-gs-create-policy, Create a lifecycle policy>> with the {ilm-init} put policy API.  
  . <<ilm-gs-apply-policy, Create an index template>> to apply the policy to each new index.
  . <<ilm-gs-bootstrap, Bootstrap an index>> as the initial write index.
  . <<ilm-gs-check-progress, Verify indices are moving through the lifecycle phases>> 
  as expected with the {ilm-init} explain API. 
  
  [float]
  [[ilm-gs-create-policy]]
  
negative.code: [[ilm-gs-bootstrap]]
  === Bootstrap the initial time-series index
  
  To get things started, you need to bootstrap an initial index and
  designate it as the write index for the rollover alias specified in your index template.
  The name of this index must match the template's index pattern and end with a number.
  On rollover, this value is incremented to generate a name for the new index.
  
  For example, the following request creates an index called `timeseries-000001`
  and makes it the write index for the `timeseries` alias.
  
  [source,console]
  -----------------------
  PUT timeseries-000001
  {
    "aliases": {
      "timeseries": {
        "is_write_index": true
      }
    }
  