Hi,
see my actual approach bellow (with null resource and triggers). Anybody using smarter procedure ?
resource "baremetal_core_volume" "demo" {
count = "${var.count}"
availability_domain = "${lookup(data.baremetal_identity_availability_domains.ADs.availability_domains[var.locked],"name")}"
compartment_id = "${var.compartment_ocid}"
size_in_mbs = "${var.volume_size_in_mbs}"
}
resource "baremetal_core_volume_backup" "demo" {
count = "${var.count}"
volume_id = "${baremetal_core_volume.demo.id}"
display_name = "demo-backup"
}
resource "baremetal_core_volume_attachment" "attach-demo" {
count = "${var.count}"
attachment_type = "iscsi"
compartment_id = "${var.compartment_ocid}"
instance_id = "${baremetal_core_instance.demo.id}"
volume_id = "${baremetal_core_volume.demo.id}"
}
resource "null_resource" "volume-mount" {
count = "${var.count}"
triggers {
cluster_instance_ids = "${join(",", baremetal_core_instance.demo.*.id)}"
}
connection {
type = "ssh"
user = "${var.system_user}"
host = "${baremetal_core_instance.demo.private_ip}"
private_key = "${file("mykey.pem")}"
}
provisioner "remote-exec" {
inline = [
"sudo iscsiadm -m node -o new -T ${baremetal_core_volume_attachment.attach-demo.iqn} -p ${baremetal_core_volume_attachment.attach-demo.ipv4}:${baremetal_core_volume_attachment.attach-demo.port}",
"sudo iscsiadm -m node -o update -T ${baremetal_core_volume_attachment.attach-demo.iqn} -n node.startup -v automatic",
"sudo iscsiadm -m node -T ${baremetal_core_volume_attachment.attach-demo.iqn} -p ${baremetal_core_volume_attachment.attach-demo.ipv4}:${baremetal_core_volume_attachment.attach-demo.port} -l",
"sudo mkfs.xfs -f /dev/sdb",
"sudo mkdir -p /data",
"sudo sh -c 'echo \"/dev/sdb /data xfs defaults,noatime,_netdev,nofail 0 2\" >> /etc/fstab'",
"sudo mount -al",
]
}
}