> Great thanks. Is there any reason why we don't use the existing pmxcfs for
> that path as well?
Yes. pmxcfs is stored in RAM (on all nodes), so you do not want to store many
large files there. Besides, the number and size of files is limited (hard
limits).
IMHO, it makes no sense to distribute
Great thanks. Is there any reason why we don't use the existing pmxcfs for that
path as well?
Stefan
Excuse my typo sent from my mobile phone.
> Am 11.03.2017 um 08:28 schrieb Dietmar Maurer :
>
>
>
>> On March 10, 2017 at 9:24 PM Stefan Priebe - Profihost AG
>> wrote:
>>
>>
>>
>> Am 10.
> On March 10, 2017 at 9:24 PM Stefan Priebe - Profihost AG
> wrote:
>
>
>
> Am 10.03.2017 um 21:20 schrieb Dietmar Maurer:
> >> Sure. Great. So there's no problem if all files got shared between
> >> nodes?
> >
> > Sorry, but I never tested that.
> >
> >> I've never looked at the code for
> I wonder if it is possible to have unique serial numbers computed and
> assigned for each disk?
We do not compute that automatically, but you can set the 'serial' attribute
manually (see "man qm.conf").
___
pve-devel mailing list
pve-devel@pve.proxmox
Hi all,
I have just consulted some kernel devs on the illumos developer list
because running omnios in a vm had problems when more disks was
present. It is problem related to that proxmox does not assign unique
serial numbers to disks and when I add a unique serial number to every
disk all disks a
> Sure. Great. So there's no problem if all files got shared between
> nodes?
Sorry, but I never tested that.
> I've never looked at the code for the active and index files...
I guess you would need some cluster wide locking, or use separate
directories for each node...
__
Am 10.03.2017 um 21:20 schrieb Dietmar Maurer:
>> Sure. Great. So there's no problem if all files got shared between
>> nodes?
>
> Sorry, but I never tested that.
>
>> I've never looked at the code for the active and index files...
>
> I guess you would need some cluster wide locking, or use s
Am 10.03.2017 um 20:54 schrieb Dietmar Maurer:
>> Is there any reason to no run /var/log/pve on ocfs2? So that it is
>> shared over all nodes?
>
> never tried. But I guess it is no problem as long as ocfs2 works (cluster
> quorate).
Sure. Great. So there's no problem if all files got shared betw
> Is there any reason to no run /var/log/pve on ocfs2? So that it is
> shared over all nodes?
never tried. But I guess it is no problem as long as ocfs2 works (cluster
quorate).
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com
Hello,
i don't like that i don't have a complete task history of a VM after
migration.
Is there any reason to no run /var/log/pve on ocfs2? So that it is
shared over all nodes?
Greets,
Stefan
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://
thanks for review. V4 sent.
Stefan
Am 10.03.2017 um 10:20 schrieb Thomas Lamprecht:
> small comment inline,
>
> On 03/09/2017 08:17 PM, Stefan Priebe wrote:
>> This allows us to use management software for files inside of /etc/pve.
>> f.e. saltstack which rely on being able to set uid,gid and ch
This allows us to use management software for files inside of /etc/pve.
f.e. saltstack which rely on being able to set uid,gid and chmod
Reviewed-by: Thomas Lamprecht
Signed-off-by: Stefan Priebe
---
data/src/pmxcfs.c | 34 +-
1 file changed, 33 insertions(+), 1
both patches to stable-4 and master
On Fri, Mar 10, 2017 at 11:25:40AM +0100, Wolfgang Bumiller wrote:
> This reverts commit ff867097e8a5ea1ab6ff1d5cbc381a4212c37254.
> ---
> This won't work and the lxc-wait only hid the fact that it is still
> a race condition: lxc sends the STOPPED state before
Fabian Grünbichler (4):
add fwlist for 4.10.1-1 kernel
update to Ubuntu-4.10.0-13.15
bump version to 5.0-2, bump ABI to 4.10.1-2-pve
buildsys: update make upload target for stretch
changelog.Debian|8 +
proxmox-ve/changelog.Debian |6 +
Makefile|
Signed-off-by: Fabian Grünbichler
---
changelog.Debian| 8
proxmox-ve/changelog.Debian | 6 ++
Makefile| 4 ++--
3 files changed, 16 insertions(+), 2 deletions(-)
diff --git a/changelog.Debian b/changelog.Debian
index 78666ab..92dcca7 100644
--- a/cha
Signed-off-by: Fabian Grünbichler
---
Makefile | 2 +-
ubuntu-zesty.tgz | Bin 154304050 -> 154345001 bytes
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index e301a48..3a58403 100644
--- a/Makefile
+++ b/Makefile
@@ -125,7 +125,7 @@ ${VIRTUAL_HDR_DEB}
Signed-off-by: Fabian Grünbichler
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 94057c0..0caa632 100644
--- a/Makefile
+++ b/Makefile
@@ -442,7 +442,7 @@ ${FW_DEB} fw: control.firmware linux-firmware.git/WHENCE
dvb-firmware.git/README
Signed-off-by: Fabian Grünbichler
---
debian/control.in | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/debian/control.in b/debian/control.in
index 4b1b8ff..fc01616 100644
--- a/debian/control.in
+++ b/debian/control.in
@@ -7,7 +7,10 @@ Build-Depends: debhelper (>= 7),
Signed-off-by: Fabian Grünbichler
---
Makefile | 4 ++--
debian/changelog | 10 ++
2 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/Makefile b/Makefile
index 4719feb..2b3fa07 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
PACKAGE=pve-cluster
-PKGVER=4.0
-PKG
Fabian Grünbichler (3):
update corosync dependencies
buildsys: update make upload target for stretch
bump version to 5.0-1
Makefile | 6 +++---
debian/control.in | 7 +--
debian/changelog | 10 ++
3 files changed, 18 insertions(+), 5 deletions(-)
--
2.1.4
___
Signed-off-by: Fabian Grünbichler
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 1875159..4719feb 100644
--- a/Makefile
+++ b/Makefile
@@ -35,7 +35,7 @@ ${DEB}:
.PHONY: upload
upload: ${DEB} ${DBG_DEB}
- tar cf - ${DEB} ${DBG_D
2017-03-10 8:57 GMT+01:00 Thomas Lamprecht :
> But you always could make those two servers a cluster, even if the have no
> shared resources like stroages or such, if it's possible to do this in your
> setup.
Any drawbacks by creating a two node cluster where quorum would never reached?
Last time
Signed-off-by: Fabian Grünbichler
---
changelog.Debian | 6 ++
Makefile | 4 ++--
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/changelog.Debian b/changelog.Debian
index d46cd85..9133be1 100644
--- a/changelog.Debian
+++ b/changelog.Debian
@@ -1,3 +1,9 @@
+criu (2.11.
Signed-off-by: Fabian Grünbichler
---
Makefile | 2 +-
criu.tgz | Bin 815301 -> 856048 bytes
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 3665eab..929415a 100644
--- a/Makefile
+++ b/Makefile
@@ -31,7 +31,7 @@ $(DEB1): $(SRCTAR)
.PHONY: download
down
Signed-off-by: Fabian Grünbichler
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 8fbf65c..08d06f8 100644
--- a/Makefile
+++ b/Makefile
@@ -25,7 +25,7 @@ $(DEB1): $(SRCTAR)
mv ${SRCDIR}/debian/changelog ${SRCDIR}/debian/changelog.
our old packaing was very minimalistic anyway.
Fabian Grünbichler (6):
bump RELEASE to 5.0
buildsys: use repoman for uploads
switch to Debians packaging as base
adapt Makefile for new packaging
buildsys: remove fakeroot from dpkg-buildpackage
bump version to 2.11.1-1~bpo90
changelog.
Signed-off-by: Fabian Grünbichler
---
changelog.Debian | 17 +
Makefile | 5 +++--
debian/changelog | 17 -
debian/compat| 1 -
debian/control | 43 ---
debian/copyright | 26 --
debian
Signed-off-by: Fabian Grünbichler
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 10b4008..ee6631a 100644
--- a/Makefile
+++ b/Makefile
@@ -1,4 +1,4 @@
-RELEASE=4.0
+RELEASE=5.0
PACKAGE=criu
PKGVER=2.10
--
2.1.4
___
Signed-off-by: Fabian Grünbichler
---
Makefile | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/Makefile b/Makefile
index ee6631a..3665eab 100644
--- a/Makefile
+++ b/Makefile
@@ -37,14 +37,7 @@ download:
.PHONY: upload
upload: ${DEBS}
- umount /pve/${RELEASE}
Since the STOPPED state is set before cgroup cleanup we need
a better way to restart a container: We now install an
ExecStopPost snippet into the lxc@.service which when
encountering a reboot trigger file
(/var/lib/lxc/$vmid/reboot) performs a systemctl restart.
---
debian/triggers| 1
This reverts commit ff867097e8a5ea1ab6ff1d5cbc381a4212c37254.
---
This won't work and the lxc-wait only hid the fact that it is still
a race condition: lxc sends the STOPPED state before doing cgroup
cleanups...
src/lxc-pve-poststop-hook | 35 ++-
1 file changed, 2
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Signed-off-by: Fabian Grünbichler
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 195b06a..8648a55 100644
--- a/Makefile
+++ b/Makefile
@@ -84,4 +84,4 @@ distclean: clean
.PHONY: upload
upload: ${DEBS}
- tar -cf - ${DEBS} | ssh
Signed-off-by: Fabian Grünbichler
---
Makefile | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/Makefile b/Makefile
index 8648a55..efb2707 100644
--- a/Makefile
+++ b/Makefile
@@ -27,14 +27,7 @@ zfs-zed_${ZFSPKGVER}_amd64.deb \
zfs-initramfs_${ZFS
Signed-off-by: Fabian Grünbichler
---
spl-changelog.Debian | 6 ++
zfs-changelog.Debian | 10 ++
Makefile | 6 +++---
3 files changed, 19 insertions(+), 3 deletions(-)
diff --git a/spl-changelog.Debian b/spl-changelog.Debian
index 17f038d..7a3e177 100644
--- a/spl-chang
Signed-off-by: Fabian Grünbichler
---
...Undo-python-changes-until-PVE-5.0-release.patch | 174 ---
...0001-remove-DKMS-modules-and-dracut-build.patch | 242 +
...ort-with-d-dev-disk-by-id-in-scan-service.patch | 29 +++
...0002-remove-DKMS-modules-and-dracut-buil
and drop the no longer needed transitional stuff
Fabian Grünbichler (4):
buildsys: update make upload target for stretch
drop patches no longer needed for stretch
buildsys: no longer build transitional packages
bump versions to -pve16~bpo90/pve-9~bpo90
spl-changelog.Debian
seems to work nicely, if we encounter issues during the PVE 5.0 alpha
phase we can always revert to our old packaging.
On Wed, Mar 08, 2017 at 02:22:04PM +0100, Fabian Grünbichler wrote:
> this patch series would switch the corosync packaging to be based on Debian
> Stretch's. the corosync version
Tested with upgrade jessie -> stretch with two node cluster, also tested
qdevices configured.
Had just the expected small quorum loss with a duration of < 1 second
when the upgrade process restarted corosync.
PVE 4.4 node and PVE 5.0 (git) node lives happily together, as expected.
So, looks go
+
+if (user == 0 && group == cfs.gid)
If we do not change either group or user chmod uses `-1` for that
parameter.
So something like this:
// we get -1 if no change should be made
if ((user == 0 || user == -1) && (group == cfs.gid || group ==
-1))
should be done here,
small comment inline,
On 03/09/2017 08:17 PM, Stefan Priebe wrote:
This allows us to use management software for files inside of /etc/pve.
f.e. saltstack which rely on being able to set uid,gid and chmod
Signed-off-by: Stefan Priebe
---
data/src/pmxcfs.c | 33
Hi Stefan
On 03/09/2017 08:15 PM, Stefan Priebe - Profihost AG wrote:
Hello Thomas,
Am 09.03.2017 um 18:09 schrieb Thomas Lamprecht:
On 03/09/2017 05:26 PM, Stefan Priebe wrote:
This allows us to use management software for files inside of /etc/pve.
f.e. saltstack which rely on being able t
extjs cannot "convert" and id from other fields, so the ids in the
diffstore and the realstore are different and we re-add every element on
every update
to mitigate this, we generate the id (which is "uid:hostname") in the
backend, and simply use it in the frontend
Signed-off-by: Dominik Csapak
both for stable-4 and master
On Wed, Mar 01, 2017 at 12:03:40PM +0100, Dominik Csapak wrote:
> or else the removal of such templates (with rootfs size 0) fails
>
> Signed-off-by: Dominik Csapak
> ---
> PVE/Storage/Plugin.pm | 12 ++--
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
44 matches
Mail list logo
