> > Both works:
> > 10.1.2.1/24 == 10.1.2.0/24 == 10.1.2.128/24
> >
> > /24 tells us that the last 8 bit are irrelevant and masked away, at least in
> > this case, ip-tools can handle it just fine :)
>
> After thinking about it a bit I do think using .0 is a more consistent
> and sane choice for
On Tue, Nov 29, 2016 at 04:44:30PM +0100, Thomas Lamprecht wrote:
> Hi,
>
>
> On 11/29/2016 04:34 PM, Alexandre DERUMIER wrote:
> >Hi,
> >
> >+
> >>>+Here we want to use the 10.1.2.1/24 network as migration network.
> >>>+migration: secure,network=10.1.2.1/24
> >I think the network is:
> >
>
bit are irrelevant and masked away, at
least in this case, ip-tools can handle it just fine :)
?
- Mail original -
De: "Thomas Lamprecht" <t.lampre...@proxmox.com>
À: "pve-devel" <pve-devel@pve.proxmox.com>
Envoyé: Mardi 29 Novembre 2016 10:56:05
Obj
e-devel@pve.proxmox.com>
Envoyé: Mardi 29 Novembre 2016 10:56:05
Objet: [pve-devel] [PATCH docs] add migration settings documentation
Signed-off-by: Thomas Lamprecht <t.lampre...@proxmox.com>
---
pvecm seemed like a reasonable place for this. migrations make only sense in
clustered s
Signed-off-by: Thomas Lamprecht
---
pvecm seemed like a reasonable place for this. migrations make only sense in
clustered setups, the settings are in the pve-cluster package
(datacenter.cfg), but I'm naturally open for suggestions about better places.
pvecm.adoc | 98