Mailing List Archive

I second this. A resource definition or resource rename functionality would
be useful. This should be fairly easy to accomplish in Linstor given that
drbd .res files (without Linstor layer) can be easily renamed?

On Thu, 20 May 2021 at 13:22, Dr. Volker Jaenisch <volker.jaenisch@inqbus.de>
wrote:

> Dear Drbd-Users!
>
> I have to move a linstore resource from one VM say vm-120-disk-2 from vm-120
> to another VM say vm-116.
>
> Utilizing proxmox this can be simply and successfully be done be editing
> the vm-definitions.
>
> I come up with a vm-116 which has now two HDD resources:
>
> vm-116-disk-1
>
> vm-120-disk-2
>
> Works like a charm.
>
> But I do not like the asymmetry in the device names. Is there a way to
> rename the linstore resource ?
> vm-120-disk-2 -> vm-116-disk-2
>
> I have dug into linstore but found no command for renaming a resource.
>
> Can somebody point me in the right direction, please.
>
> Any help appreciated
>
> Volker
>
> --
> =========================================================
> inqbus Scientific Computing Dr. Volker Jaenisch
> Hungerbichlweg 3 +49 (8860) 9222 7 92
> 86977 Burggen https://inqbus.de
> =========================================================
>
> _______________________________________________
> Star us on GITHUB: https://github.com/LINBIT
> drbd-user mailing list
> drbd-user@lists.linbit.com
> https://lists.linbit.com/mailman/listinfo/drbd-user
>

On Thu, May 20, 2021 at 01:54:13PM +0100, Yanni M. wrote:
> I second this. A resource definition or resource rename functionality would
> be useful. This should be fairly easy to accomplish in Linstor given that
> drbd .res files (without Linstor layer) can be easily renamed?

https://github.com/LINBIT/linstor-server/issues/44#issuecomment-618923893

Regards, rck
_______________________________________________
Star us on GITHUB: https://github.com/LINBIT
drbd-user mailing list
drbd-user@lists.linbit.com
https://lists.linbit.com/mailman/listinfo/drbd-user

Sorry Ronald,

On 20.05.21 15:09, Roland Kammerer wrote:
> On Thu, May 20, 2021 at 01:54:13PM +0100, Yanni M. wrote:
>> I second this. A resource definition or resource rename functionality would
>> be useful. This should be fairly easy to accomplish in Linstor given that
>> drbd .res files (without Linstor layer) can be easily renamed?
> https://github.com/LINBIT/linstor-server/issues/44#issuecomment-618923893

but this is a really lame excuse. I have developed software since 40
years. At least in the last 30 years no real developer mixes primary
keys with names of resources any more.

And if he did, and be told about it, he would notice that this was a
severe error and be glad to fix it.

All that I and some others here like to have is the possibility to
change the "label" of a resource. No more, no less. We do not like to
change any data on disk, nor UIDs of partitions or the such.

That the current information "vm-X-disk-Y" on what VM as which disk the
resource acts is not needed for linstore/drbd internally to work
correctly is shown in my example. I can add
"vm-X-disk-Y" to a VM Q as Disc R and it would run flawlessly. Only that
the label then does not match the logical "context" any more.

What linbit lacks is simply the abstraction and distinction of "display
label" and "internal unique identifier".

Cheers,

Volker


--

=========================================================
inqbus Scientific Computing Dr. Volker Jaenisch
Hungerbichlweg 3 +49 (8860) 9222 7 92
86977 Burggen https://inqbus.de
=========================================================

@Volker the community will be very happy if you provide a consistent and
reliable patch.

Regards,
Andreas

Am 20.05.21 um 15:46 schrieb Dr. Volker Jaenisch:
> Sorry Ronald,
>
> On 20.05.21 15:09, Roland Kammerer wrote:
>> On Thu, May 20, 2021 at 01:54:13PM +0100, Yanni M. wrote:
>>> I second this. A resource definition or resource rename functionality would
>>> be useful. This should be fairly easy to accomplish in Linstor given that
>>> drbd .res files (without Linstor layer) can be easily renamed?
>> https://github.com/LINBIT/linstor-server/issues/44#issuecomment-618923893
>
> but this is a really lame excuse. I have developed software since 40
> years. At least in the last 30 years no real developer mixes primary
> keys with names of resources any more.
>
> And if he did, and be told about it, he would notice that this was a
> severe error and be glad to fix it.
>
> All that I and some others here like to have is the possibility to
> change the "label" of a resource. No more, no less. We do not like to
> change any data on disk, nor UIDs of partitions or the such.
>
> That the current information "vm-X-disk-Y" on what VM as which disk the
> resource acts is not needed for linstore/drbd internally to work
> correctly is shown in my example. I can add
> "vm-X-disk-Y" to a VM Q as Disc R and it would run flawlessly. Only that
> the label then does not match the logical "context" any more.
>
> What linbit lacks is simply the abstraction and distinction of "display
> label" and "internal unique identifier".
>
> Cheers,
>
> Volker
>
>
> --
>
> =========================================================
> inqbus Scientific Computing Dr. Volker Jaenisch
> Hungerbichlweg 3 +49 (8860) 9222 7 92
> 86977 Burggen https://inqbus.de
> =========================================================
>
>
> _______________________________________________
> Star us on GITHUB: https://github.com/LINBIT
> drbd-user mailing list
> drbd-user@lists.linbit.com
> https://lists.linbit.com/mailman/listinfo/drbd-user
>

_______________________________________________
Star us on GITHUB: https://github.com/LINBIT
drbd-user mailing list
drbd-user@lists.linbit.com
https://lists.linbit.com/mailman/listinfo/drbd-user

Dear Andreas!

> @Volker the community will be very happy if you provide a consistent and
> reliable patch.
>
Thank you for your confidence in me.

But, sorry, I program in Python, Cython and VUE.JS, and not in Java. I
fixed some things in drbdmanage (which was the Python predecessor of
linstor) and the proxmox interface for our internal purpose but Java is
definitively not my domain.

On the other hand according to their GH post the problem is not the code
only, but the DB structure and the overall design. Such things cannot be
fixed by a simple patch from a user. Such bad weeds hat to be rooted
out, deeply.

I have never said that it will be easy to fix, I just stated, that it
seems to be a mess if it is not easy to fix. I still cannot even grasp
the reality that vm-X-disk-Y is in any way the primary identifier in
linstor. I still hope that the GH statement was incorrect or misleading.

Before any patch could be thought of the linstor developers should give
the users at least a workaround how to fix this by hand. In the 10 year
doing clusters with DRBD it is the first time that I have the need to
rename a resource. It is truly a corner case but an IMHO important one.
The positive resonance here shows that I am not the only one with this
particular problem.

Proxmox for instance also states that (swapping VM devices) this is a
corner case, and that they do not have a Button for it. But in the same
instant they point to a documented workaround where the problem can be
solved by editing some config files. This is IMHO really enough to deal
with a corner case.

Even If I had to shut down my VM to fix the resource name it would be a
doable workaround. If you take into account the time to do the
alternative which is copying a terabyte of email storage from one
resource to an other simply because you cannot change the resource name,
even shutting down a VM to rename a resource by hand gets some appeal.


I am quite disappointed by linbit in the last years. DRBD was and still
is a top notch performance, a really good and reliable product, which I
would miss tremendously if it would vanish. But after the dumping of

drbdmanage, the DRBD-Proxmox struggle and the introduction of linstore,
working with DRBD9 has become a real pain.

I never thought I would, but I think I will have my eyes open in the
future to look for alternatives.


Cheers,

Volker

--
=========================================================
inqbus Scientific Computing Dr. Volker Jaenisch
Hungerbichlweg 3 +49 (8860) 9222 7 92
86977 Burggen https://inqbus.de
=========================================================

I'm not a developer, so I cannot comment on how difficult it is to
acomplish this. I'm sure that there must be good reasons behind it, so I
leave that to the experts. ????

What I would personally would like to have is an option to "rename" or
"update" a resource while _not_ "InUse" (i.e while the resource is down
cluster wide). This "should" impose less risk in my opinion, as there may
be less chances for something to go terribly wrong.
As the OP already mentioned, I would like to avoid having to clone the
resource for something as simple (in my eyes) as renaming vm-101-disk-1 to
vm-101-disk-2 while preserving the original resource data/metadata.





On Thu, 20 May 2021 at 16:39, Dr. Volker Jaenisch <volker.jaenisch@inqbus.de>
wrote:

> Dear Andreas!
>
> @Volker the community will be very happy if you provide a consistent and
> reliable patch.
>
> Thank you for your confidence in me.
>
> But, sorry, I program in Python, Cython and VUE.JS, and not in Java. I
> fixed some things in drbdmanage (which was the Python predecessor of
> linstor) and the proxmox interface for our internal purpose but Java is
> definitively not my domain.
>
> On the other hand according to their GH post the problem is not the code
> only, but the DB structure and the overall design. Such things cannot be
> fixed by a simple patch from a user. Such bad weeds hat to be rooted out,
> deeply.
>
> I have never said that it will be easy to fix, I just stated, that it
> seems to be a mess if it is not easy to fix. I still cannot even grasp the
> reality that vm-X-disk-Y is in any way the primary identifier in linstor. I
> still hope that the GH statement was incorrect or misleading.
>
> Before any patch could be thought of the linstor developers should give
> the users at least a workaround how to fix this by hand. In the 10 year
> doing clusters with DRBD it is the first time that I have the need to
> rename a resource. It is truly a corner case but an IMHO important one.
> The positive resonance here shows that I am not the only one with this
> particular problem.
>
> Proxmox for instance also states that (swapping VM devices) this is a
> corner case, and that they do not have a Button for it. But in the same
> instant they point to a documented workaround where the problem can be
> solved by editing some config files. This is IMHO really enough to deal
> with a corner case.
>
> Even If I had to shut down my VM to fix the resource name it would be a
> doable workaround. If you take into account the time to do the alternative
> which is copying a terabyte of email storage from one resource to an other
> simply because you cannot change the resource name, even shutting down a VM
> to rename a resource by hand gets some appeal.
>
>
> I am quite disappointed by linbit in the last years. DRBD was and still is
> a top notch performance, a really good and reliable product, which I would
> miss tremendously if it would vanish. But after the dumping of
>
> drbdmanage, the DRBD-Proxmox struggle and the introduction of linstore,
> working with DRBD9 has become a real pain.
>
> I never thought I would, but I think I will have my eyes open in the
> future to look for alternatives.
>
>
> Cheers,
>
> Volker
>
> --
> =========================================================
> inqbus Scientific Computing Dr. Volker Jaenisch
> Hungerbichlweg 3 <https://www.google.com/maps/search/Hungerbichlweg+3?entry=gmail&source=g> +49 (8860) 9222 7 92
> 86977 Burggen https://inqbus.de
> =========================================================
>
> _______________________________________________
> Star us on GITHUB: https://github.com/LINBIT
> drbd-user mailing list
> drbd-user@lists.linbit.com
> https://lists.linbit.com/mailman/listinfo/drbd-user
>