<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:small">Yannis,<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Feb 3, 2019 at 9:39 PM Yannis Milios <<a href="mailto:yannis.milios@gmail.com">yannis.milios@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div dir="auto">Are you saying this needs to be done for every single resource potentially hundreds of vm's with multiple disks attached? This sounds like a huge pita.<br></div></div></blockquote><div><br></div><div>Yes. However, I did a test. I temporarily reduced redundancy level in /etc/pve/storage.cfg and the created a new VM in PVE.</div><div>Then I added the resource to the additional node by using 'linstor resource create' command. Finally I checked the properties of the resource and I noticed that the two important keys, 'PeerSlots' and 'StorPoolName' were automatically added to the newly added resource, so I would assume that this is not an issue anymore...</div><div><br></div><div>Yannis</div></div></div>
</blockquote></div><div style="font-size:small" class="gmail_default"></div><div style="font-size:small" class="gmail_default">Thanks for your input on this, very useful info!</div><br></div>