<div dir="ltr"><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Satellite and Controller are quite obvious, Combined is a node that runs<br>
a Satellite and may sometimes run a Controller, Auxiliary is a node that<br>
runs neither but is registered for other reasons, this is mostly<br>
reserved for future features.<br></blockquote><div><br></div><div>Can these 'roles' be modified afterwards once set? or they are static, i.e do we have to remove node and re-add it with another role specification.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">There is a NodeLost API and a corresponding command for it. </blockquote><div><br></div><div>Is there a way for an admin to access API and run this command or it's for dev only use?</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">it is expected that a system<br>
administrator will clean up a resource manually if automatic cleanup<br>
does not work, </blockquote><div><br></div><div>I presume here you mean cleaning up resource LVs,ZVOLs etc. Sure, this is true as long as the node is accessible.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">...and as soon as LINSTOR detects that the resource has been<br>
cleaned up properly, it will disappear from LINSTOR's database if the<br>
resource was marked for deletion.<br></blockquote><div><br></div><div>Nice.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">There are however no plans to add any force flags like in drbdmanage to<br>
resource management (or similar) commands, because that frequently<br>
caused massive desyncs of drbdmanage's state and the real state of<br>
backend storage resource, as it was frequently misused by<br>
administrators, who also often expected the various "force" options to<br>
do something completely different than they actually did.<br></blockquote><div><br></div><div>True ...</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Deleting the database will cause LINSTOR to initialize a new database.<br>
The database could be anywhere depending on how LINSTOR was installed,<br>
where it currently is can be found out by looking at the connection-url<br>
setting in controller's database.cfg file.<br></blockquote><div><br></div><div>In my case it's in /opt/linstor-server/database.cfg and the entry is..</div><div><div><entry key="connection-url">jdbc:h2:/opt/linstor-server/linstordb</entry></div></div><div><br></div><div>Are you saying that deleting <span style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">/opt/linstor-server/linstordb will reset all settings and cause LINSTOR to create a new database file?</span></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
This is supposed to be managed by a cluster resource manager like pacemaker.<br>
Obviously, in a multi-controller HA environment, the controller database<br>
must be available on all nodes, and there are various possibilities to<br>
ensure it is<br></blockquote><div><br></div><div>Thanks, I think it has already been mentioned that for Proxmox, this will be in the form of a HA VM appliance, which will be provided by LINBIT.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
I'll leave answering the package-related questions to our packaging experts.<br></blockquote><div><br></div><div>Thanks again..<br></div><div><br></div><div>BR </div><div>Yannis</div></div></div>