fix dead link and change the remote exec example by simpler inline example (#45)

Author: aorcl

README.md

@@ -79,98 +79,8 @@ net start winrm
 ## Configure iSCSI volume attachments
 * For guidance configuring iSCSI on a Windows platform, see [Adding a Block Volume to a Windows Instance](https://docs.cloud.oracle.com/iaas/Content/GSG/Tasks/addingstorageForWindows.htm).
 
-* For guidance configuring iSCSI on a Linux platform, see [iSCSI Commands and Information](https://docs.cloud.oracle.com/iaas/Content/Block/Concepts/iscsiinformation.htm). See also the example file [remote-exec.tf](https://github.com/oracle/terraform-provider-oci/blob/master/docs/examples/compute/instance/remote-exec.tf) for inline commands using `remote_exec_script`.
+* For guidance configuring iSCSI on a Linux platform, see [iSCSI Commands and Information](https://docs.cloud.oracle.com/iaas/Content/Block/Concepts/iscsiinformation.htm). See also this example of inline iSCSI commands execution using `iscsiadm` CLI called from terraform file: [instance.tf](https://github.com/terraform-providers/terraform-provider-oci/blob/master/examples/compute/instance/instance.tf).
 
-Following is the sample inline script that isn't using CHAP authentication:
-
-```hcl
-# Logging for troubleshooting.
-set -x
-sudo -s bash -c "lsscsi -t"
-
-# Command provided in Oracle Cloud Infrastructure console to register ISCSI device.
-sudo -s bash -c "iscsiadm -m node -o new -T ${self.iqn} -p ${self.ipv4}:${self.port}"
-
-# Command provided in Oracle Cloud Infrastructure console for registration to survive reboot.
-sudo -s bash -c "iscsiadm -m node -o update -T ${self.iqn} -n node.startup -v automatic"
-
-# Command provided in Oracle Cloud Infrastructure console to log into iscsi device.
-sudo -s bash -c "iscsiadm -m node -T ${self.iqn} -p ${self.ipv4}:${self.port} -l"
-
-# troubleshooting command.
-sudo -s bash -c "lsscsi -t"
-
-# troubleshooting command.
-lsscsi -t | grep disk | grep ${self.iqn} | awk '{print $1,$2,$3,$4,$5}'
-
-# Find the specific OS level device that is associated with the iscsi volume.
-device=$(lsscsi -t | grep disk | grep ${self.iqn} | awk '{print $4}')
-
-# Create a file system on the device. In this case, we use the ext4 filesystem.
-sudo -s bash -c "mkfs.ext4 -F $device"
-
-# Find the UUID of the iscsi volume.
-uuid=$(sudo blkid | grep $device | awk '{print $2}')
-
-# Create a directory in the OS to mount the new filesystem.
-sudo -s bash -c "mkdir -p ${var.volume_mount_directory}"
-
-# Mount the filesystem so that it is available.
-sudo -s bash -c "mount -t ext4 $uuid ${var.volume_mount_directory}"
-
-# Ensure the filesystem is loaded on a reboot of the instance.
-echo "$uuid ${var.volume_mount_directory} ext4 defaults,noatime,_netdev,nofail    0   2" | sudo tee --append /etc/fstab > /dev/null   
-```
-
-Following is the sample inline script for using CHAP authentication:
-
-```hcl
-# Logging for troubleshooting.
-set -x
-sudo -s bash -c "lsscsi -t"
-
-# Command provided in Oracle Cloud Infrastructure console to register ISCSI device.
-sudo -s bash -c "iscsiadm -m node -o new -T ${self.iqn} -p ${self.ipv4}:${self.port}"
-
-# Command provided in Oracle Cloud Infrastructure console for registration to survive reboot.
-sudo -s bash -c "iscsiadm -m node -o update -T ${self.iqn} -n node.startup -v automatic"
-
-# Authenticate the iSCSI connection by providing the volume's CHAP credentials.
-sudo -s bash -c "iscsiadm -m node -T ${self.iqn} -p ${self.ipv4}:${self.port} -o update -n node.session.auth.authmethod -v CHAP"
-
-# Provide the volume's CHAP user name.
-sudo -s bash -c "iscsiadm -m node -T ${self.iqn} -p ${self.ipv4}:${self.port} -o update -n node.session.auth.username -v ${self.chap_username}"
-
-# Provide the volume's CHAP password.
-sudo -s bash -c "iscsiadm -m node -T ${self.iqn} -p ${self.ipv4}:${self.port} -o update -n node.session.auth.password -v ${self.chap_secret}"
-
-# Command provided in Oracle Cloud Infrastructure console to log into iscsi device.
-sudo -s bash -c "iscsiadm -m node -T ${self.iqn} -p ${self.ipv4}:${self.port} -l"
-
-# troubleshooting command.
-sudo -s bash -c "lsscsi -t"
-
-# troubleshooting command.
-lsscsi -t | grep disk | grep ${self.iqn} | awk '{print $1,$2,$3,$4,$5}'
-
-# Find the specific OS level device that is associated with the iscsi volume.
-device=$(lsscsi -t | grep disk | grep ${self.iqn} | awk '{print $4}')
-
-# Create a file system on the device. In this case, we use the ext4 filesystem.
-sudo -s bash -c "mkfs.ext4 -F $device"
-
-# Find the UUID of the iscsi volume.
-uuid=$(sudo blkid | grep $device | awk '{print $2}')
-
-# Create a directory in the OS to mount the new filesystem.
-sudo -s bash -c "mkdir -p ${var.volume_mount_directory}"
-
-# Mount the filesystem so that it is available.
-sudo -s bash -c "mount -t ext4 $uuid ${var.volume_mount_directory}"
-
-# Ensure the filesystem is loaded on a reboot of the instance.
-echo "$uuid ${var.volume_mount_directory} ext4 defaults,noatime,_netdev,nofail    0   2" | sudo tee --append /etc/fstab > /dev/null   
-```
 
 ## Contributing