On 09/25/2017 07:05 AM, Dietmar Maurer wrote:
+ sub {
+ my ($res) = @_;
+ my $longest = 0;
+ foreach my $role(map($_->{roleid}, @$res)) {
+ my $len = length $role;
+ $longest = $len if $len > $longest;
+ }
+ $lo
On Mon, Sep 25, 2017 at 10:13:29AM +0200, Thomas Lamprecht wrote:
> On 09/25/2017 07:05 AM, Dietmar Maurer wrote:
> >
> > > + sub {
> > > + my ($res) = @_;
> > > + my $longest = 0;
> > > + foreach my $role(map($_->{roleid}, @$res)) {
> > > + my $len = length $role;
> > > +
We extract them from the json data by first deleting all
quotes, then deleting everything up to their entries, then
everything after the next comma. If the entry is at the end
there's no comma, instead there are closing braces, so we
need to strip away these as well.
---
it's no fun when scripts er
---
spice-example-sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/spice-example-sh b/spice-example-sh
index cc7c6b7f..6fe5c1f5 100755
--- a/spice-example-sh
+++ b/spice-example-sh
@@ -59,7 +59,7 @@ fi
NODE="${NODE%%\.*}"
-DATA="$(curl -f -s -S -k -d "username=$USERNAME&
---
avoids pain
spice-example-sh | 46 +++---
1 file changed, 23 insertions(+), 23 deletions(-)
diff --git a/spice-example-sh b/spice-example-sh
index 62192f3e..1d8bdc49 100755
--- a/spice-example-sh
+++ b/spice-example-sh
@@ -22,10 +22,10 @@ USERNAME=""
On Mon, Sep 25, 2017 at 07:05:03AM +0200, Dietmar Maurer wrote:
> comments inline
>
> > Use the existing 'index' API call from PVE::API2::Role to produce a
> > tidy list of all available roles and their associated privileges.
> > ---
> > Concerns #1502 but doesn't fix it completely.
> > PVE/CLI/p
comments inline
On 09/22/2017 04:32 PM, Alwin Antreich wrote:
Signed-off-by: Alwin Antreich
---
PVE/CLI/pveum.pm | 21 +
1 file changed, 21 insertions(+)
diff --git a/PVE/CLI/pveum.pm b/PVE/CLI/pveum.pm
index aef7089..0426cfb 100755
--- a/PVE/CLI/pveum.pm
+++ b/PVE/CLI/p
comments inline
On 09/22/2017 04:32 PM, Alwin Antreich wrote:
Signed-off-by: Alwin Antreich
---
PVE/CLI/pveum.pm | 12
1 file changed, 12 insertions(+)
diff --git a/PVE/CLI/pveum.pm b/PVE/CLI/pveum.pm
index 0426cfb..7a4930f 100755
--- a/PVE/CLI/pveum.pm
+++ b/PVE/CLI/pveum.pm
@
In addition to Thomas' reply:
On Fri, Sep 22, 2017 at 04:32:29PM +0200, Alwin Antreich wrote:
> Signed-off-by: Alwin Antreich
> ---
> PVE/CLI/pveum.pm | 21 +
> 1 file changed, 21 insertions(+)
>
> diff --git a/PVE/CLI/pveum.pm b/PVE/CLI/pveum.pm
> index aef7089..0426cfb 100
On 09/22/2017 04:32 PM, Alwin Antreich wrote:
Signed-off-by: Alwin Antreich
---
PVE/CLI/pveum.pm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/PVE/CLI/pveum.pm b/PVE/CLI/pveum.pm
index 7a4930f..d960437 100755
--- a/PVE/CLI/pveum.pm
+++ b/PVE/CLI/pveum.pm
@@ -50,7 +50
applied series
On Wed, Sep 13, 2017 at 04:10:20PM +0200, Emmanuel Kasper wrote:
> bumping this after the topic has been brough in forum:
> https://forum.proxmox.com/threads/procedure-to-import-vmware-ova-to-proxmox-5-0-23-with-zfs-vm-store.36779/#post-180321
>
> changes since V7:
> rebase on mast
applied series
On Fri, Sep 22, 2017 at 02:20:21PM +0200, Thomas Lamprecht wrote:
> Mostly a resend of v2 which was part of a bigger series.
> Rebased on current master.
> 'PVE.qemu.OSTypeEdit: declare static' patch is new.
> As Emmanuel showed real use for the bigger size of the wizad and I had
>
besides the cleanup purpose this fixes an actual problem, perls POSIX
module has the following caveat:
`Everything is exported by default (with a handful of exceptions).
This is an unfortunate backwards compatibility feature and its use is
strongly discouraged. You should either prevent the export
>>there might be some yet undiscovered incompatibility when mixing versions like
>>that (there are other ceph libraries with reverse-dependencies to
>>consider as well)
But proxmox 5.0 ceph-server only support luminous, right ?
so, I think it shouldn't be a problem ?
and from client side, librbd
applied
On Mon, Sep 25, 2017 at 02:39:43PM +0200, Thomas Lamprecht wrote:
> besides the cleanup purpose this fixes an actual problem, perls POSIX
> module has the following caveat:
>
> `Everything is exported by default (with a handful of exceptions).
> This is an unfortunate backwards compatibil
We allow uppercase characters in snapshot names.
pvesm import and export must allow uppercase characters too.
[PATCH V2]
Use JSON schema instead of hardcoding.
[PATCH V3 pve-storage]
Correct typo.
[PATCH V4]
Make base snapshot more specific.
[PATCH V5]
Merge pve-lxc-snapshot-name and pve-snapsh
---
PVE/CLI/pvesm.pm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/PVE/CLI/pvesm.pm b/PVE/CLI/pvesm.pm
index 9455595..57d10f4 100755
--- a/PVE/CLI/pvesm.pm
+++ b/PVE/CLI/pvesm.pm
@@ -183,7 +183,7 @@ __PACKAGE__->register_method ({
base => {
des
This format was two time declared in PVE::LXC::Config and PVE::QemuServer.
---
src/PVE/JSONSchema.pm | 17 +
1 file changed, 17 insertions(+)
diff --git a/src/PVE/JSONSchema.pm b/src/PVE/JSONSchema.pm
index 3295599..5b1d59e 100644
--- a/src/PVE/JSONSchema.pm
+++ b/src/PVE/JSONSche
A base snapshot can be a replication snapshot or a normal snapshot.
Normal snapshots use the format configid.
---
src/PVE/JSONSchema.pm | 13 +
1 file changed, 13 insertions(+)
diff --git a/src/PVE/JSONSchema.pm b/src/PVE/JSONSchema.pm
index 5b1d59e..fdf8119 100644
--- a/src/PVE/JSONS
---
PVE/QemuServer.pm | 6 --
1 file changed, 6 deletions(-)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index 2b6fda9..bd4f6cd 100644
--- a/PVE/QemuServer.pm
+++ b/PVE/QemuServer.pm
@@ -62,12 +62,6 @@ PVE::JSONSchema::register_standard_option('pve-qm-stateuri',
{
optional => 1,
Rename pve-lxc-snapshot-name to pve-snapshot-name to have a unified name schema.
---
src/PVE/API2/LXC.pm | 4 ++--
src/PVE/API2/LXC/Snapshot.pm | 12 ++--
src/PVE/LXC/Config.pm| 6 --
3 files changed, 8 insertions(+), 14 deletions(-)
diff --git a/src/PVE/API2/LXC.pm
On Mon, Sep 25, 2017 at 03:10:11PM +0200, Alexandre DERUMIER wrote:
> >>there might be some yet undiscovered incompatibility when mixing versions
> >>like
> >>that (there are other ceph libraries with reverse-dependencies to
> >>consider as well)
>
> But proxmox 5.0 ceph-server only support lumin
On 09/14/2017 02:39 PM, Philip Abernethy wrote:
Using the nodename in $mailto is not correct and can lead to mails not
forwarding in restrictive mail server configurations.
Also changes $mailfrom to 'root' instead of 'root@localhost', which
results in postfix appending the proper FQDN there, too.
applied
On Thu, Sep 14, 2017 at 02:39:33PM +0200, Philip Abernethy wrote:
> Using the nodename in $mailto is not correct and can lead to mails not
> forwarding in restrictive mail server configurations.
> Also changes $mailfrom to 'root' instead of 'root@localhost', which
> results in postfix appe
applied
On Tue, Sep 19, 2017 at 12:01:15PM +0200, Wolfgang Link wrote:
> The jobid is already parsed by the file parser.
> ---
> PVE/API2/Replication.pm | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/PVE/API2/Replication.pm b/PVE/API2/Replication.pm
> index 15499508..f396615d 100644
>
>>but for other use cases, we don't (yet?) have that limitation. e.g.,
>>running a radosgw (which is a client from Ceph's perspective) or just
>>rbd access to an external cluster is supported using Jewel as well.
mmm, I don't have thinked about radosgw.
>>if we move librbd1, we'd have to move
>>Maybe it is possible to detect this at runtime ?
mmm,I find some old threads and discuss about this case
https://patchwork.ozlabs.org/patch/235271/
seem that qemu don't support dynamic linking, that's why it don't work with old
lib
if qemu is build with newer lib.
so maybe maintain a pve-qem
On Mon, Sep 25, 2017 at 10:19:50AM +0200, Philip Abernethy wrote:
> On Mon, Sep 25, 2017 at 10:13:29AM +0200, Thomas Lamprecht wrote:
> > On 09/25/2017 07:05 AM, Dietmar Maurer wrote:
> > >
> > > > + sub {
> > > > + my ($res) = @_;
> > > > + my $longest = 0;
> > > > +
28 matches
Mail list logo
