[pve-devel] [PATCH v2 manager] Add Ceph, iscsi and more disk and zfs information to pvereport

2019-04-03 Thread Friedrich Ramberger
Following items added to pvereport: * more details about disks * iscsi information * more zfs information * ceph information (only when ceph.conf exists) When running from command line now report progress is shown at the console (STDERR) --- v2: avoid whitespace errors in the patch PVE/Repo

[pve-devel] [PATCH manager] Add Ceph, iscsi and more disk and zfs information to pvereport

2019-03-28 Thread Friedrich Ramberger
Following items added to pvereport: * more details about disks * iscsi information * more zfs information * ceph information (only when ceph.conf exists) When running from command line now report progress is shown at the console (STDERR) --- PVE/Report.pm | 18 +++--- 1 file changed

[pve-devel] [PATCH manager] Signed-off-by: Friedrich Ramberger

2019-03-21 Thread Friedrich Ramberger
Following items added to pvereport: * more details about disks * iscsi information * lvm physical volume scan (pvs) * more zfs information * ceph information (only when ceph.conf exists) When running from command line now report progress is shown at the console (STDERR) --- PVE/Report.pm |

[pve-devel] [PATCH pve-docs] Precise certificate generation

2019-01-23 Thread Friedrich Ramberger
Signed-off-by: Friedrich Ramberger --- certificate-managment.adoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/certificate-managment.adoc b/certificate-managment.adoc index 3eabee8..7970f61 100644 --- a/certificate-managment.adoc +++ b/certificate-managment.adoc

Re: [pve-devel] [PATCH manager] fix #2058: show correct pool for external ceph clusters

2019-01-18 Thread Friedrich Ramberger
Patch works fine - thx! > On January 18, 2019 at 2:09 PM Dominik Csapak wrote: > > > instead of having two inputfields and displayfields (where only one gets the > correct value), have two inputfileds but one displayfield when we need it > > Signed-off-by: Dominik Csapak > --- > www/manager6

[pve-devel] [PATCH docs] New chapter "Hyper-converged Infrastructure" with Proxmox ceph server

2017-06-20 Thread Friedrich Ramberger
ctice information it is not obsolete yet. A combined source for both Wiki and Administration Guide will be made later. Signed-off-by: Friedrich Ramberger --- ceph-server.adoc| 138 hyper-converged-infrastructure.adoc |

[pve-devel] [PATCH docs] More details in introduction about CD-ROM

2016-11-02 Thread Friedrich Ramberger
Signed-off-by: Friedrich Ramberger --- pve-installation.adoc | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/pve-installation.adoc b/pve-installation.adoc index a309061..ce11c93 100644 --- a/pve-installation.adoc +++ b/pve-installation.adoc @@ -32,11 +32,11

[pve-devel] USB device assignment

2015-01-16 Thread Friedrich Ramberger
Hello, The new article https://pve.proxmox.com/wiki/USB_Devices_in_Virtual_Machines documents how to handle USB devices for VMs. There are 2 items I could not clarify satisfactorily: * how can the usb3 driver xhci be integrated into /usr/share/qemu-server/pve-usb.cfg in order to avoid an "a

Re: [pve-devel] FYI: news from the OpenVZ project

2014-12-27 Thread Friedrich Ramberger
Sounds good - remains the question: what means "early" (2015), not Jan 1st probably, it may last another few months -Original Message- From: pve-devel [mailto:pve-devel-boun...@pve.proxmox.com] On Behalf Of Michael Rasmussen Sent: Samstag, 27. Dezember 2014 13:30 To: pve-devel@pve.pro

Re: [pve-devel] idea: new section 'sysrules' inside vmid.fw

2014-09-04 Thread Friedrich Ramberger
See comment below -Original Message- From: pve-devel [mailto:pve-devel-boun...@pve.proxmox.com] On Behalf Of Michael Rasmussen Sent: Donnerstag, 04. September 2014 20:10 To: pve-devel@pve.proxmox.com Subject: Re: [pve-devel] idea: new section 'sysrules' inside vmid.fw On Thu, 4 Sep 2014

Re: [pve-devel] idea: new section 'sysrules' inside vmid.fw

2014-09-04 Thread Friedrich Ramberger
A good one - I guess the "rules" (without "sys") are "userrules" then (= managed by user-permission level) - maybe we can use this term in the config-file too (in order to make it more transparent) like [userrules] But, of course, which term tuo use it is neither essential nor important