> Is possible add in /etc/default/sheepdog a new variable IPINTERFACE, then in
> /etc/init.d/sheepdog:
>
> - Verify if this new variable is set
> - Append in DAEMON_ARGS "-b $IPINTERFACE"
>
> Is useful to move sheepdog on a separeted high speed nic.
see
https://git.proxmox.com/?p=pve-sheepdog.g
Hi,
I was a little off this last week,
I'm currently working on livemigration+storage migration at the same time
(because I'll need it in some months, migration vms to a new datacenter with
new storage).
I think I'll have a first beta for rfc in 1 or 2 weeks.
Alexandre.
_
applied, thanks
> -Original Message-
> From: pve-devel-boun...@pve.proxmox.com [mailto:pve-devel-
> boun...@pve.proxmox.com] On Behalf Of Stefan Priebe
> Sent: Mittwoch, 09. Oktober 2013 09:24
> To: pve-devel@pve.proxmox.com
> Subject: [pve-devel] [PATCH] use a calculated interval for upda
applied, thanks.
> -Original Message-
> From: pve-devel-boun...@pve.proxmox.com [mailto:pve-devel-
> boun...@pve.proxmox.com] On Behalf Of m...@datanom.net
> Sent: Sonntag, 13. Oktober 2013 01:52
> To: pve-devel@pve.proxmox.com
> Subject: [pve-devel] [PATCH] Fixes bug in calculating pool s
> And BTW. the two plugins did use the same syntax but never the less the error
> was displayed. If you study the code in SectionConfig.pm it does not care
> whether the syntax is identical or not it merely checks whether a property has
> been defined or not.
> 'die "duplicate property" if defined(
On Sun, 13 Oct 2013 11:01:27 +0200
Michael Rasmussen wrote:
> It was just something I bump into while developing the ZFSPlugin. When
> configuring the plugin you need to enter a block size which I naturally
> named 'blocksize' but the NexentaPlugin also needing this info and this
> plugin also na
On Sun, 13 Oct 2013 06:51:06 +
Dietmar Maurer wrote:
>
> What property/plugin do you talk about?
>
It was just something I bump into while developing the ZFSPlugin. When
configuring the plugin you need to enter a block size which I naturally
named 'blocksize' but the NexentaPlugin also need
