We *have* operated largely under the understanding that not all Proxmox
sysadmins will fully understand the process that each command goes through
before they invoke it. A sanity check to ensure the directory can be
manipulated before starting the cluster join would be in keeping with that
approac
On Wed, 12 Nov 2014 05:36:40 +
Dietmar Maurer wrote:
> > 5) initial cluster joining starts which at some point involves restarting
> > pve-
> > cluster. when pve-cluster restarts the running initial cluster joining
> > process halts
> > since pve-cluster is not able to remount pve filesyste
> However as always I'm thinking about how to integrate it with Proxmox. It's
> not
> very handy to login for terminal and fire one of these. First I was thinking
> about
> adding possibility to define hooks per-VM. Hook could be a simple script to
> execute on machine up or down (there's somethi
I think we should add apis like
qm storage add storeid:xxx
qm storage del storeid:xxx
for this.
I have begin to do some block migration, seem to works fine.
I'm currently improving it to allow to migrate to different
storageid/storagetype.
Also I'm doing some tests with ndb server to copy un
Ok, Great!
Thanks for testing.
(@cc pve-devel)
- Mail transféré -
De: "Andrew Thrift"
À: "Alexandre DERUMIER"
Envoyé: Mercredi 12 Novembre 2014 05:10:40
Objet: Re: [pve-devel] [PATCH] rbd : free_image : retry if rbd has watchers
Hi Alexandre,
Initial testing looks promising.
> 5) initial cluster joining starts which at some point involves restarting pve-
> cluster. when pve-cluster restarts the running initial cluster joining
> process halts
> since pve-cluster is not able to remount pve filesystem since we block remount
> as our current directory is the mount point f
I'd still like to see settings for default migration targets, possibly a
list instead of a single entry (so there are fallbacks in case the first
node is inaccessible), on a per-VM basis. Per-node defaults would probably
also be useful, too - if nothing else, they might pre-select the node in
the
On Tue, 11 Nov 2014 21:22:51 -0500
Eric Blevins wrote:
> I use DRBD on many nodes. The DRBD storage is marked as shared and
> accessible to only the two nodes that have access to the volume.
>
> If maintenance mode does not take the storage accessibility into account
> migrations would fail.
>
I think number 4 is nice... As Andrew said...
2014-11-12 0:22 GMT-02:00 Eric Blevins :
> I use DRBD on many nodes. The DRBD storage is marked as shared and
> accessible to only the two nodes that have access to the volume.
>
> If maintenance mode does not take the storage accessibility into accou
I use DRBD on many nodes. The DRBD storage is marked as shared and
accessible to only the two nodes that have access to the volume.
If maintenance mode does not take the storage accessibility into account
migrations would fail.
Eric
On Nov 11, 2014 1:43 AM, "Michael Rasmussen" wrote:
> On Tue,
On Tue, 11 Nov 2014 23:46:54 +0100
Michael Rasmussen wrote:
> Hi Dietmar,
>
> Found a bug this evening which results in a broken cluster.
>
Created in bugzilla as https://bugzilla.proxmox.com/show_bug.cgi?id=578
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael rasmussen
Hi Dietmar,
Found a bug this evening which results in a broken cluster.
Howto replicate bug:
We assume an existing cluster exist on node pve122.
1) Create a fresh proxmox node. Lets call it pve123
2) login to this node as root
3) cd /etc/pve
4) pvecm add pve122
5) initial cluster joining starts
> Sorry, I was to fast happy,
>
> behind a new start of the firewall, all the same, Containers with IPv6
> firewall
> activated, and the firewall cant start!
>
> Sorry, I have test to fast!
What version do you test exactly? Latest version from git?
_
Dietmar is currently merging ipv6 patches into pve-firewall git.
I don't think packages are already available in pvetest repository.
Better to disable firewall on this containers, are currently firewall don't
generate any ipv6 rules
- Mail original -
De: "Detlef Bracker"
À: pve-de
Sorry, I was to fast happy,
behind a new start of the firewall, all the same, Containers with IPv6
firewall activated, and the firewall cant start!
Sorry, I have test to fast!
Regards
Detlef
signature.asc
Description: OpenPGP digital signature
_
Dear all,
we have download now the new updates of proxmox and have test now again the
firewall and we are happy, that the bug is now resolved!
So we will test more about the security of the firewall and so on!
Many thanks to all they are involved with this!
Detlef
signature.asc
Description:
I have my fancy home setup with VGA passthrough for Windows VM running
custom kernel with i915 arbiter and acs patches, but to make it shutter
free when playing games I have to PIN vCPUs to physical CPU cores.
Currently I have two scripts which have to be run after VM start (you only
require to run
17 matches
Mail list logo
