<div><div dir="auto">For the time being drbd is using tcp 2020 during the build process, but that may change in the future. This is just in case you want to open only this specific port and not everything.</div></div><div dir="auto"><br></div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 19 Dec 2019 at 15:14, Denis <<a href="mailto:drbdsys@made.net">drbdsys@made.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div>Thank you for your reply Gianni and all
for reading.<br>
</div>
<div><br>
</div>
<div>I realized that internet on my nodes
was limited only to standard ports out, then drbd-dkms failed.</div>
<div>I solved my problem opening all ports
out.</div>
<div><br>
</div>
<div>Sorry for wasting your time, next time
I can read better even if I am not a developer ;-)</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Il 19/12/19 13:32, Gianni Milo ha
scritto:<br>
</div></div><div>
<blockquote type="cite">
<div dir="ltr">
<div>Hello,</div>
<div><br>
</div>
<div>In general, there's no need to be a developer (I'm not) to
setup DRBD9/LINSTOR on PVE. </div>
<div>LINBIT have made things easy enough, for the average
sysadmin to get your cluster up and running without any
special knowledge (apart from the obvious Linux sysadmin
skills that one must have of course to maintain such setup).</div>
<div><br>
</div>
<div>The issues I had building drbd9 were due to the fact that
my pve cluster nodes, do not have direct access to the
internet. That is required for building recent drbd9 kernel
module versions on pve, due to some changes in its code base.
So, as soon as your pve nodes can access http/https traffic on
the internet, then you should be fine.</div>
<div>Even when your pve cluster nodes do not have internet
access, it's still possible to build drbd9 kernel modules on a
different machine (which has internet access) and then
manually move them to the production server, as
mentioned previously in this post. What I usually do to
further control drbd/pve stability is to prevent automatic
kernel upgrades, which can sometimes lead to a broken system.</div>
<div><br>
</div>
<div>You can follow the steps described in the blog post below
and the Linstor documentation, for more details in setting up
your cluster:</div>
<div><a href="https://www.linbit.com/en/linstor-setup-proxmox-ve-volumes/" target="_blank">https://www.linbit.com/en/linstor-setup-proxmox-ve-volumes/</a> <br>
</div>
<div><a href="https://docs.linbit.com/docs/linstor-guide/#ch-proxmox-linstor" target="_blank">https://docs.linbit.com/docs/linstor-guide/#ch-proxmox-linstor</a> </div>
<div><br>
</div>
<div>Last but not least, both pve and linbit offer paid support
plans. </div>
<div><br>
</div>
<div>Hope this helps ...</div>
<div><br>
</div>
<div>Regards,</div>
<div>G. <br>
</div>
<div><br>
</div>
<div><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, 19 Dec 2019 at
10:07, Den <<a href="mailto:drbdsys@made.net" target="_blank">drbdsys@made.net</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">Hello,<br>
<br>
I have to go live with a PVE 6.1 cluster and drbd9.<br>
<br>
I'm not a developer so I'm asking for the cleanest way to
work now and <br>
avoid update problems in the future.<br>
<br>
If someone can write me a step-by-step tutorial I will thank
him :-)<br>
<br>
<br>
Il 10/12/19 09:22, Roland Kammerer ha scritto:<br>
> On Mon, Dec 09, 2019 at 06:55:08PM +0000, Gianni Milo
wrote:<br>
>> Thanks Roland for your suggestions, they were very
helpful.<br>
>><br>
>> Just a side note, tested your docker image from
dockerhub<br>
>> (linbit/coccinelle), but it appears to be slightly
outdated (it's on 1.0.7).<br>
> Yeah, it was good enough (1.0.7 + patches) at the time.
Now we have a<br>
> stricter check and the script magic thinks it is too
old. All of that<br>
> was before I wrote SPAAS and before there was a recent
enough version of<br>
> spatch available (pretty long upstream release cycles).<br>
><br>
>> To be honest, the tarball method works fine for me,<br>
> nice.<br>
><br>
>> but having also the docker image up to date would
be helpful.<br>
> Christoph, either we maintain it or we remove it. I'm
for removing.<br>
><br>
> Best, rck<br>
> _______________________________________________<br>
> Star us on GITHUB: <a href="https://github.com/LINBIT" rel="noreferrer" target="_blank">https://github.com/LINBIT</a><br>
> drbd-user mailing list<br>
> <a href="mailto:drbd-user@lists.linbit.com" target="_blank">drbd-user@lists.linbit.com</a><br>
> <a href="https://lists.linbit.com/mailman/listinfo/drbd-user" rel="noreferrer" target="_blank">https://lists.linbit.com/mailman/listinfo/drbd-user</a><br>
<br>
<br>
_______________________________________________<br>
Star us on GITHUB: <a href="https://github.com/LINBIT" rel="noreferrer" target="_blank">https://github.com/LINBIT</a><br>
drbd-user mailing list<br>
<a href="mailto:drbd-user@lists.linbit.com" target="_blank">drbd-user@lists.linbit.com</a><br>
<a href="https://lists.linbit.com/mailman/listinfo/drbd-user" rel="noreferrer" target="_blank">https://lists.linbit.com/mailman/listinfo/drbd-user</a><br>
</blockquote>
</div>
</div>
</blockquote>
<p><br>
</p>
</div>
_______________________________________________<br>
Star us on GITHUB: <a href="https://github.com/LINBIT" rel="noreferrer" target="_blank">https://github.com/LINBIT</a><br>
drbd-user mailing list<br>
<a href="mailto:drbd-user@lists.linbit.com" target="_blank">drbd-user@lists.linbit.com</a><br>
<a href="https://lists.linbit.com/mailman/listinfo/drbd-user" rel="noreferrer" target="_blank">https://lists.linbit.com/mailman/listinfo/drbd-user</a><br>
</blockquote></div></div>