- ovsint port mtu need to be set with ""ovs-vsctl set mtu-request"
- update mtu on already existing interfaces (fwbr,fwln,tap,veth)
if existing tap|veth interface is replugged on a different mtu bridge
---
src/PVE/Network.pm | 30 --
1 file changed, 20 insertions(+),
a forum user have reported strange bug with ovs + mtu9000 when
switching between 2 ovs bridge with different mtu. (1500 vs 9000)
https://forum.proxmox.com/threads/ovs-problem-with-mtu-9000-on-vms-assigned-to-vmbr0.105172/
I have found 2 bugs:
1) ovsint port mtu need to be set with ""ovs-vsctl
Sorry, wrong bug. Should be 3886.
___
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
for mon, mds and osd: ok-to-stop
mon: ok-to-rm
osd: safe-to-destroy
Signed-off-by: Aaron Lauterer
---
I added the OSD safe-to-destroy endpoint even though I have no immediate
use for it as of now. But plan to include it in the OSD panel once I
have an idea how to do so in a sensible manner.
The main motivation behind this series is to leverage several safety
checks that Ceph has to make sure it is ok to stop or destroy a service.
For this to work, the librados2-perl needs to be adapted as the Ceph API
will return a non-zero return value and will also present a human readable
Check if stopping of a service (OSD, MON, MDS) will be problematic for
Ceph. The warning still allows the user to proceed.
Ceph also has a check if the destruction of a MON is okay, so let's use
it.
Instead of the common OK button, label it with `Stop OSD` and so forth
to hopefully reduce the
In some situations, we do not want to abort if the Ceph API returns an
error (ret != 0). We also want to be able to access all the retured
values from the Ceph API (return code, status, data).
One such situation can be the 'osd ok-to-stop' call where Ceph will
return a non zero code if it is not
If an OSD is removed during the wrong conditions, it could lead to
blocked IO or worst case data loss.
Check against global flags that limit the capabilities of Ceph to heal
itself (norebalance, norecover, noout) and if there are degraded
objects.
Unfortunately, the 'safe-to-destroy' API
Signed-off-by: Aaron Lauterer
---
thanks @Dominik who realized that we did not free this buffer in all
situations.
RADOS.xs | 4
1 file changed, 4 insertions(+)
diff --git a/RADOS.xs b/RADOS.xs
index 7eca024..1eb0b5a 100644
--- a/RADOS.xs
+++ b/RADOS.xs
@@ -145,6 +145,10 @@ CODE:
With the changes in librados2-perl, we need to make sure to call it in
scalar context.
Signed-off-by: Aaron Lauterer
---
This needs to be released in combination with the previous changes (2/6)
in librados2-perl to not break OSD removal!
PVE/API2/Ceph/OSD.pm | 2 +-
1 file changed, 1
The backups in the 'Backups' table in Storages are now initially
sorted by column 'Name' ascending.
Previously, they were first sorted by 'vmid' descending, then by date
descending. This was unintuitive as 'vmid' doesn't exist as column
in the GUI, and only 'Date' displayed a sorting arrow.
Perl's automatic conversion can lead to integers being converted to
strings, for example by matching it in a regex.
To make sure we always return an integer in the API call, add an
explicit cast to integer.
Signed-off-by: Mira Limbeck
Reviewed-by: Fabian Ebner
---
v3:
- fixed style nits
-
`qemu-img info --output=json` returns the size and used values as integers in
the JSON format, but the regex match converts them to strings.
As we know they only contain digits, we can simply cast them back to integers
after the regex.
The API requires them to be integers.
Signed-off-by: Mira
13 matches
Mail list logo
