Users might not even know that the option or the issue it addresses
exist.
Expose the option in the UI and expand on the "why" in the
documentation.
Motivated by a recent forum post:
https://forum.proxmox.com/threads/137734/
manager:
Fiona Ebner (1):
ui: lvm: expose saferemove setting
It can be security-relevant in some environments. The LVM storage
documentation can be reached via the "Help" button and contains a few
more details.
Signed-off-by: Fiona Ebner
---
www/manager6/storage/LVMEdit.js | 10 ++
1 file changed, 10 insertions(+)
diff --git
mentioning why zeroing-out might be necessary.
Signed-off-by: Fiona Ebner
---
pve-storage-lvm.adoc | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/pve-storage-lvm.adoc b/pve-storage-lvm.adoc
index 917d8fb..cff5d3e 100644
--- a/pve-storage-lvm.adoc
+++
with this the title is now completely visible when the column is
expanded, even if it's originally too narrow.
Suggested-by: Thomas Lamprecht
Signed-off-by: Dominik Csapak
---
changes from v1:
* wrap the text in the column, instead of duplicating it in the expanded
body
thanks @thomas for
The strings were hard to translate and required some tricks like passing
'Ceph ' as an argument. The `/main` part was also removed to simplify
the flow and UX.
Suggested-by: Dietmar Maurer
Signed-off-by: Maximiliano Sandoval
---
src/node/APTRepositories.js | 20 +---
1 file
Am 07/12/2023 um 12:01 schrieb Dominik Csapak:
> this has the advantage that the title is now completely visible when the
> column is too narrow when expanded, although it is duplicated (since
> it's already contained in the non expanded row) even if the original
> value may be cutoff.
>
>
this has the advantage that the title is now completely visible when the
column is too narrow when expanded, although it is duplicated (since
it's already contained in the non expanded row) even if the original
value may be cutoff.
Signed-off-by: Dominik Csapak
---
not sure about this, because
for base images we call the volume_import of the parent plugin and pass
it as vm-image instead of base-image, then convert it back as base-image
Signed-off-by: Hannes Duerr
---
src/PVE/Storage/LvmThinPlugin.pm | 60
1 file changed, 60 insertions(+)
diff --git
During migration, the volume names may change if the name is already in
use at the target location. We therefore want to save the original names
before the migration so that we can clean up the original volumes
afterwards.
Signed-off-by: Hannes Duerr
---
PVE/QemuMigrate.pm | 5 +++--
1 file
if a base-image is to be migrated to a lvm-thin storage, a new
vm-image is allocated on the target side, then the data is written
and afterwards the image is converted to a base-image
qemu-server:
Hannes Duerr (1):
migration: secure and use source volume names for cleanup
xgettext is a robust tool to extract translatable strings from source
code.
Using msgcat for concatenating pot files is not recommended, hence we
also switch to xgettext. It also added garbage when there were comments.
What do we get for free:
- It de-escapes strings. there are 3 cases in our
Note that N/A is already translatable in other places.
Signed-off-by: Maximiliano Sandoval
---
Differences from v2:
- Translate the invalid subscription key message, this string is also in two
more places in pve-manager. This will be the content of a following patch.
- Do not translate
12 matches
Mail list logo
