---

govuk_safe_to_reboot::can_reboot: 'careful'
govuk_safe_to_reboot::reason: 'Reboot a single node at time and check that the cluster goes green between reboots'

govuk_elasticsearch::version: '2.4.6'

lv:
  data:
    pv: '/dev/xvdf'
    vg: 'elasticsearch'

mount:
  /mnt/elasticsearch:
    disk: '/dev/mapper/elasticsearch-data'
    govuk_lvm: 'data'
    mountoptions: 'defaults'
    percent_threshold_warning: 16
    percent_threshold_critical: 11

---

govuk_safe_to_reboot::can_reboot: 'careful'
govuk_safe_to_reboot::reason: 'Reboot a single node at time and check that the cluster goes green between reboots'

govuk_elasticsearch::version: '2.4.6'

lv:
  data:
    pv: '/dev/nvme1n1'
    vg: 'elasticsearch'

mount:
  /mnt/elasticsearch:
    disk: '/dev/mapper/elasticsearch-data'
    govuk_lvm: 'data'
    mountoptions: 'defaults'
    percent_threshold_warning: 16
    percent_threshold_critical: 11

Update device for elasticsearch VG to work with m5 instances.
Update device for elasticsearch VG to work with m5 instances.

When we run these VMs as m5 types, the device name will change and Puppet needs to know what the new device will be. This doesn't seem to be resolvable with disk labels.
