<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi there,<br><br>Something I find missing in OpenNebula is a "sync state" functionality.<br>OpenNebula could monitor hosts and update the relationships between instances and hosts dynamically.<br>So, for example, when a host fails we could manually fix the problem by "virsh create" the deployments on a new server, and OpenNebula would pick the new host for the instances.<br>Currently, the machines stay as "UNKNOWN".<br><br>Also related is the potential danger "UNKNOWN" states present when the system datastore runs on shared storage.<br>So, on my last example:<br>- I would start the instances on a new host. <br>- Users on Sunstone would still see the machines as "UNKNOWN" and can restart the machines<br>- Both instances would start writing on the same file, leading to corruption<br><br>To prevent that OpenNebula ccan/should make use of sanlock. OpenNebula would be required to act as the lock manager.<br>By syncing state we could limit conflicts, and by using sanlock we could make it fail proof.<br><br>Regards,<br>Ricardo<br> </div></body>
</html>