Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Heat template for monitoring network

I have launched an instance (bootable from volume) using Heat template. The VM and the volumes reside in separate nodes. Consequently, the instance becomes read-only from time to time (don't know why). I suspect that there occurs a disconnectivity of the network between the corresponding compute and cinder nodes of the instance.

What I plan to do is this : 1. Get the Compute node IP/hostname of the instance 2. Get the Cinder node IP/hostname of the instance 3. Set an alarm which triggers when the network gets disconnected between the compute and the cinder nodes. 4. Wait till the network reconnects 5. On reconnecting, check if the instance OS has become read-only. 6. If yes, reboot the instance to fix the read-only issue

What should be the heat template achieving the above objectives?

Heat template for monitoring network

I have launched an instance (bootable from volume) using Heat template. The VM and the volumes volume reside in separate nodes. Consequently, the The instance becomes read-only from time to time (don't know why). why) and becomes all right after reboot. I suspect that there occurs a temporary disconnectivity of the network between the corresponding compute and cinder nodes of the instance.

What I plan to do is this :

1.
  • Get the Compute node IP/hostname of the instance 2. instance
  • Get the Cinder node IP/hostname of the instance 3. instance
  • Set an alarm which triggers when the network gets disconnected between the compute and the cinder nodes. 4. nodes.
  • Wait till the network reconnects 5. reconnects
  • On reconnecting, check if the instance OS has become read-only. 6. read-only.
  • If yes, reboot the instance to fix the read-only issue

What should be the heat template achieving the above objectives? objectives?