added a screenshot:
https://git.proxmox.com/?p=pve-docs.git;a=commitdiff;h=4dbeb548bf90537388b52d3d52bda4783d8d5e0f
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
This can be used to mask out some nodes from the node selector.
Signed-off-by: Thomas Lamprecht
---
changes since v1:
* use ExtJS filter, simplifies code quite a bit
www/manager6/form/NodeSelector.js | 11 +++
1 file changed, 11 insertions(+)
diff --git a/www/manager6/form/NodeSelecto
applied, but moved into "Container Settings" Section.
Or was there a reason to put it into "Backup/Restore"?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Wouldn't it be simpler if we define a filter function?
> On November 17, 2016 at 3:00 PM Thomas Lamprecht
> wrote:
>
>
> This can be used to mask out some nodes from the node selector.
>
> Signed-off-by: Thomas Lamprecht
> ---
>
> this will be used in the next patch
>
> www/manager6/form/N
applied
I wonder if we can use something similar in PVE::API2Client?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Signed-off-by: Dominik Csapak
---
www/manager6/window/Backup.js | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/www/manager6/window/Backup.js b/www/manager6/window/Backup.js
index f7b30d5..033c199 100644
--- a/www/manager6/window/Backup.js
+++ b/www/manager6/window/Backup.js
@
---
www/manager6/Utils.js | 3 ++-
www/manager6/qemu/OSTypeEdit.js | 5 +
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/www/manager6/Utils.js b/www/manager6/Utils.js
index c824b97..8d5a598 100644
--- a/www/manager6/Utils.js
+++ b/www/manager6/Utils.js
@@ -63,7 +63,8 @
All special flags for Windows 8 and Windows 2012 (win8 type)
are kept the same , since we set flags based on checking if
/^win(\d+)$/ is greater than 6 or 7
---
PVE/QemuServer.pm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index d228
The following add Win2016 as an OS to choose in
the wizard, grouping it with Windows10.
Qemu flags for Windows 10 and 2016 are the same
as Windows8, this separate type is mainly
for ease of use and clarity in the UI.
Maybe should we remove at some point Linux 2.4
and Windows 2000 from the wizard
As we cannot migrate to the source node do not show it in the
migration window's node selector.
Fixes #1049 partly
Signed-off-by: Thomas Lamprecht
---
www/manager6/window/Migrate.js | 1 +
1 file changed, 1 insertion(+)
diff --git a/www/manager6/window/Migrate.js b/www/manager6/window/Migrate.
This can be used to mask out some nodes from the node selector.
Signed-off-by: Thomas Lamprecht
---
this will be used in the next patch
www/manager6/form/NodeSelector.js | 28 +++-
1 file changed, 27 insertions(+), 1 deletion(-)
diff --git a/www/manager6/form/NodeSelec
Add the sshkeyscan command which connects to all online nodes and
gets their IP on the given network. Those IPs will be used as hosts
for ssh-keyscan to gather the public keys of the nodes.
The collected public keys will then be added to our known_hosts file
in /etc/pve . On the addition we remove
On 11/16/2016 08:39 PM, Phil Kauffman wrote:
I have done some light testing of this and it doesn't seem to work
quite right yet.
Things I have done.
- dist-upgrade on both machines and reboot.
- able to ssh to and from both machines on alternate network without a
password
- Migration works whe
when forwarding an API request to the responsible node,
only accept the certificate that this node should have
according to the contents of the cluster file system.
to limit performance issues, cache certificate fingerprint
on first request for each node, and only regenerate cache
(at most once pe
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
pvestatd already depends on PVE::LXC and this way we can
use it at startup without having to import pvestatd.
Additionally: provide a way to get a new set of cores for a
not-yet started container.
---
src/PVE/LXC.pm | 135 +
1 file changed,
---
PVE/Service/pvestatd.pm | 120 +---
1 file changed, 1 insertion(+), 119 deletions(-)
diff --git a/PVE/Service/pvestatd.pm b/PVE/Service/pvestatd.pm
index 3774833..860d97a 100755
--- a/PVE/Service/pvestatd.pm
+++ b/PVE/Service/pvestatd.pm
@@ -222,124
Otherwise we run with all cores until pvestatd's rebalancing
takes effect, and the container could race to prevent this
from working.
---
src/PVE/LXC.pm | 12
1 file changed, 12 insertions(+)
diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm
index 598dff5..6421e2a 100644
--- a/src/PVE/LXC
don't drop the next current cpu after finishing a range
---
src/PVE/CpuSet.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/PVE/CpuSet.pm b/src/PVE/CpuSet.pm
index 753b3cd..7293d9b 100644
--- a/src/PVE/CpuSet.pm
+++ b/src/PVE/CpuSet.pm
@@ -165,7 +165,7 @@ sub short_string
---
pve-storage-glusterfs.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pve-storage-glusterfs.adoc b/pve-storage-glusterfs.adoc
index f12884a..af4b857 100644
--- a/pve-storage-glusterfs.adoc
+++ b/pve-storage-glusterfs.adoc
@@ -7,7 +7,7 @@ endif::wiki[]
Storage pool t
Mostly imported from Wiki
---
pct.adoc | 31 +++
1 file changed, 31 insertions(+)
diff --git a/pct.adoc b/pct.adoc
index 67abec1..1c27878 100644
--- a/pct.adoc
+++ b/pct.adoc
@@ -574,6 +574,37 @@ individually
* Redistribute backed up files according to new mount point
Hi all,
We just want to inform you that Linbit changed the License
for their 'drbdmanage' toolkit.
The commit messages says ("Philipp Reisner"):
--
basically we do not want that others (who have not contributed to the
development) act as parasites in our support business
-
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> Am 17.11.2016 um 07:33 schrieb Dietmar Maurer:
> > AFAIK we only protect base volumes, and we 'unprotect' that in the code.
> > So what is the purpose of this patch?
> >
>
> good question ;-) I just remember that i had this situation where i did
> clones from snapshots which results in protecte
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
32 matches
Mail list logo
