Re: [pve-devel] [PATCH] Improvement for pve-installation

A general (technical) remark: your edits seem to not have been based on current master, but the patch is. So this either requires a cleanup on/after applying or a v2 ;) There are two affected/reverted changes in pve-installation.adoc: - all the recent 'text' to `text` conversions are reverted in

Re: [pve-devel] student question about ha "restricted" option

>>Yes, Dietmar recalls correctly, nofailback does what your students expect. >>The restricted version is for controlling failover. Normally all nodes >>which are not already group members are added to the group with -1 priority >>(group member nodes can have minimum 0 as priority). This allows

Re: [pve-devel] pve-manager and disk IO monitoring

iostats are coming from qemu. what is the output of monitor "info blockstats" for the vm where you don't have stats ? - Mail original - De: "datanom.net" À: "pve-devel" Envoyé: Mercredi 28 Septembre 2016 22:46:25 Objet: [pve-devel]

Re: [pve-devel] pve-manager and disk IO monitoring

On Wed, 28 Sep 2016 23:37:40 +0200 Michael Rasmussen wrote: > My assumption seems to be wrong. Rather it seems that disk IO is not > monitored if disk type is scsi. virtio seems to work fine. > Or more precisely: Disk type: scsi Storage: zfs over iscsi (libiscsi) does not

Re: [pve-devel] pve-manager and disk IO monitoring

On Wed, 28 Sep 2016 22:46:25 +0200 Michael Rasmussen wrote: > Hi all, > > I have for some time wondering why disk IO graphs is showing no IO for > some VM's. I think I have found the cause. It seems that Disk IO is > only monitored on the first disk and I tend to split OS and

Re: [pve-devel] Two-Node HA

On Wed, Sep 28, 2016 at 6:30 PM, Michael Rasmussen wrote: > If you search the forum you will find a step guide for using a rpi as third > node. Yes, I know that. ___ pve-devel mailing list pve-devel@pve.proxmox.com

[pve-devel] [PATCH] Improvement for pve-installation

From: fritz Signed-off-by: fritz --- local-zfs.adoc| 1 + pve-installation.adoc | 125 ++ 2 files changed, 67 insertions(+), 59 deletions(-) diff --git a/local-zfs.adoc b/local-zfs.adoc

Re: [pve-devel] Two-Node HA

If you search the forum you will find a step guide for using a rpi as third node. On September 28, 2016 5:53:05 PM GMT+02:00, Andreas Steinel wrote: >Hi Thomas, > >Thank you for your time and your answer. > >I wonder why e.g. an Oracle Real Application Cluster (RAC) works

Re: [pve-devel] Two-Node HA

Hi Thomas, Thank you for your time and your answer. I wonder why e.g. an Oracle Real Application Cluster (RAC) works so well with a 2 node in a HA setup. We deployed 50+ clusters in the last years and never had a split-brain-like situation. Rolling-updates, as well as occasional host crashes are

Re: [pve-devel] student question about ha "restricted" option

On 28.09.2016 17:22, Dietmar Maurer wrote: 3 nodes: kvm1,kvm2,kvm3 we have a ha group , with kvm1 && kvm2, with a vm in this group. Restricted option is disable. We are trying to live migrate the vm to kvm3. The vm is migrated back to kvm1/2. Students expected that without restricted

Re: [pve-devel] [PATCH manager] Minor refactor for #1115 (reload grid after template download)

applied ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] student question about ha "restricted" option

> 3 nodes: kvm1,kvm2,kvm3 > > we have a ha group , with kvm1 && kvm2, with a vm in this group. Restricted > option is disable. > > > We are trying to live migrate the vm to kvm3. The vm is migrated back to > kvm1/2. > > Students expected that without restricted option, the vm keep running

[pve-devel] student question about ha "restricted" option

Hi, we are currently testing HA in our current week training. Students have a question about restricted option. config: 3 nodes: kvm1,kvm2,kvm3 we have a ha group , with kvm1 && kvm2, with a vm in this group. Restricted option is disable. We are trying to live migrate the vm to kvm3.

Re: [pve-devel] Two-Node HA

Hi, QDisks are not ideal and those itself will probably not supported by Proxmox VE, also I would really love top see the term "two node HA" vanish, as its only marketing talk and is technically simply not possible (sadly basic rules of our universe make it impossible), they call a setup with

[pve-devel] Two-Node HA

Hi, I'd like to ask if there are any plans to use e.g. the shared storage as a quorum/voting disk like the oracle grid infrastructure uses it to get a two node ha cluster (for almost a decade). This obviously only works for NAS or SAN storage. Best, Andreas

[pve-devel] [PATCH storage] fix #1122: correctly create LUNs for linked clones

--- PVE/Storage/ZFSPlugin.pm | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/PVE/Storage/ZFSPlugin.pm b/PVE/Storage/ZFSPlugin.pm index 6ed3dc9..ca25402 100644 --- a/PVE/Storage/ZFSPlugin.pm +++ b/PVE/Storage/ZFSPlugin.pm @@ -260,10 +260,13 @@ sub create_base { sub

[pve-devel] [PATCH v3 storage 1/4] move SMART error handling into get_disks

because we never ever want to die in get_disks because of a single disk, but the nodes/xyz/disks/smart API path is allowed to fail if a disk device is unsupported by smartctl or something else goes wrong. --- PVE/API2/Disks.pm | 2 ++ PVE/Diskmanage.pm | 69

[pve-devel] [PATCH v3 storage 3/4] disks: parse smart attributes using RE

--- PVE/Diskmanage.pm | 23 --- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/PVE/Diskmanage.pm b/PVE/Diskmanage.pm index edc0ea8..bcd3883 100644 --- a/PVE/Diskmanage.pm +++ b/PVE/Diskmanage.pm @@ -81,19 +81,20 @@ sub get_smart_data { $returncode =

[pve-devel] [PATCH v3 storage 2/4] disks: use smartctl -H -A

to only list SMART health and attributes, instead of "smartctl -a", which prints "all SMART information" --- PVE/Diskmanage.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/PVE/Diskmanage.pm b/PVE/Diskmanage.pm index 5909d73..edc0ea8 100644 --- a/PVE/Diskmanage.pm +++

[pve-devel] [PATCH v3 storage 0/4] improve SMART handling

this patch series partly fix #1123 and #1126: - no longer fail completely as soon as one NVME (or other unsupported) device is installed - limit smartctl commands to what we actually want - stricter matching for (ATA) attribute list output further todos: - investigate backport of smartmontools

[pve-devel] [PATCH v3 storage 4/4] disks: fix typo

--- PVE/API2/Disks.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/PVE/API2/Disks.pm b/PVE/API2/Disks.pm index d7030f8..3be6873 100644 --- a/PVE/API2/Disks.pm +++ b/PVE/API2/Disks.pm @@ -138,7 +138,7 @@ __PACKAGE__->register_method ({ $result =

Re: [pve-devel] [RFC manager] When adding a new hard disk, use the most used controller as suggested value

On 09/22/2016 02:09 PM, Dietmar Maurer wrote: > I would not change the order when displaying the list. Just select > the default ... > the clist we sort here is actually only used for setting the value of the comboBox, we call setValue() on the first element of the list further down

[pve-devel] [PATCH manager] Minor refactor for #1115 (reload grid after template download)

Move the listener to the new window declaration to make it clear this listener is not bound to the current component --- www/manager6/storage/ContentView.js | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/www/manager6/storage/ContentView.js

[pve-devel] [PATCH qemu-server] Avoid to parse empty property string.

Check if string exists before you try to parse it. --- PVE/QemuServer.pm | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm index dbd85a0..c7547d4 100644 --- a/PVE/QemuServer.pm +++ b/PVE/QemuServer.pm @@ -2797,8 +2797,9 @@ sub

Re: [pve-devel] tap && veth interfaces on host have ipv6 allocated

On Wed, Sep 28, 2016 at 08:38:38AM +0200, Wolfgang Bumiller wrote: > On Tue, Sep 27, 2016 at 03:11:50PM +0200, Wolfgang Bumiller wrote: > > On Tue, Sep 27, 2016 at 02:54:47PM +0200, Alexandre DERUMIER wrote: > > > Hi, > > > > > > we have just notice during the training, > > > that tap && veth

Re: [pve-devel] tap && veth interfaces on host have ipv6 allocated

Thanks wolfgang >>I've been wondering whether there are any good uses for them. (I used >>them a couple of times for testing when working on ipv6 initially but >>have since had them disabled.) >>So it's probably better to just remove them upon creation in >>veth_create() and tap_create()

Re: [pve-devel] tap && veth interfaces on host have ipv6 allocated

On Tue, Sep 27, 2016 at 03:11:50PM +0200, Wolfgang Bumiller wrote: > On Tue, Sep 27, 2016 at 02:54:47PM +0200, Alexandre DERUMIER wrote: > > Hi, > > > > we have just notice during the training, > > that tap && veth interfaces on host have ipv6 addresses allocated. > > See >

Re: [pve-devel] [PATCH manager 1/2] Ceph/Monitor: sort monitors after name

applied ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] [PATCH manager 2/2] Ceph/Monitor: set name column witdh to 100px

applied ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] [RFC manager] Makefile: fix distclean target

looks reasonable to me - applied. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel