Comment 1 for bug 1642166

We should probably store this data in a separate table and query all the rows that apply to a particular server from the DB when we need it, rather than combine them all into a single blob that then causes contention issues. (This might also solve various issues we have had with updating metadata while a resource is locked.)

In the short term though, Jan came up with this workaround which was fairly effective in spreading out the thundering herd:

  delete_delay_time:
    type: OS::Heat::RandomString
    properties:
      character_classes:
        - min: 2
          class: digits
      length: 2
  delete_delay:
    type: OS::Heat::TestResource
    properties:
      action_wait_secs:
         delete: {get_attr: [delete_delay_time, value]}
    depends_on: deployment_bastion_node_cleanup