18
0
Fork 0

On utilise des IPv4 en 192.0.2.0/24 (RFC5737)

This commit is contained in:
Gregory Colpart 2016-12-29 02:18:28 +01:00
parent 452cd64b26
commit 464569d1c8
4 changed files with 17 additions and 17 deletions

View File

@ -84,10 +84,10 @@ resource r0 {
meta-disk internal; meta-disk internal;
} }
on tic { on tic {
address 192.168.0.1:7788; address 192.0.2.1:7788;
} }
on tac { on tac {
address 192.168.0.2:7788; address 192.0.2.2:7788;
} }
} }
~~~ ~~~
@ -139,10 +139,10 @@ resource r0 {
meta-disk internal; meta-disk internal;
} }
on tic { on tic {
address 192.168.0.1:7788; address 192.0.2.1:7788;
} }
on tac { on tac {
address 192.168.0.2:7788; address 192.0.2.2:7788;
} }
} }
~~~ ~~~
@ -166,14 +166,14 @@ Configurer OCFS dans /etc/ocfs2/cluster.conf
~~~ ~~~
node: node:
ip_port = 7777 ip_port = 7777
ip_address = 192.168.0.1 ip_address = 192.0.2.1
number = 0 number = 0
name = kvm1 name = kvm1
cluster = ocfs2 cluster = ocfs2
node: node:
ip_port = 7777 ip_port = 7777
ip_address = 192.168.0.2 ip_address = 192.0.2.2
number = 1 number = 1
name = kvm2 name = kvm2
cluster = ocfs2 cluster = ocfs2

View File

@ -331,9 +331,9 @@ Si l'on coupe le master, un autre est élu :
~~~ ~~~
[INFO ][o.e.d.z.ZenDiscovery ] [bar2] master_left [{bar0}{4Tt8FlV4TG2Hf_1T4EayQg}{5nbXw3F5RWCWjUSiRzv9DA}{192.0.2.42}{192.0.2.42:9300}], reason [shut_down] [INFO ][o.e.d.z.ZenDiscovery ] [bar2] master_left [{bar0}{4Tt8FlV4TG2Hf_1T4EayQg}{5nbXw3F5RWCWjUSiRzv9DA}{192.0.2.42}{192.0.2.42:9300}], reason [shut_down]
[WARN ][o.e.d.z.ZenDiscovery ] [bar2] master left (reason = shut_down), current nodes: {{bar2}{5wUhAI79SsyY-DKv4va26Q}{_VQTiZXxTCi2KIsijyQBpg}{192.0.2.42}{192.0.2.42:9302},{bar1}{_jwXmQsAQEyseSOc4pG2IA}{_pQMtkFLSTe3p-eDHMkalw}{192.0.2.42}{192.0.2.42:9301},} [WARN ][o.e.d.z.ZenDiscovery ] [bar2] master left (reason = shut_down), current nodes: {{bar2}{5wUhAI79SsyY-DKv4va26Q}{_VQTiZXxTCi2KIsijyQBpg}{192.0.2.42}{192.0.2.42:9302},{bar1}{_jwXmQsAQEyseSOc4pG2IA}{_pQMtkFLSTe3p-eDHMkalw}{192.0.2.42}{192.0.2.42:9301},}
[INFO ][o.e.c.s.ClusterService ] [bar2] removed {{bar0}{4Tt8FlV4TG2Hf_1T4EayQg}{5nbXw3F5RWCWjUSiRzv9DA}{192.168.0.133}{192.168.0.133:9300},}, reason: master_failed ({bar0}{4Tt8FlV4TG2Hf_1T4EayQg}{5nbXw3F5RWCWjUSiRzv9DA}{192.0.2.42}{192.0.2.42:9300}) [INFO ][o.e.c.s.ClusterService ] [bar2] removed {{bar0}{4Tt8FlV4TG2Hf_1T4EayQg}{5nbXw3F5RWCWjUSiRzv9DA}{192.0.2.133}{192.0.2.133:9300},}, reason: master_failed ({bar0}{4Tt8FlV4TG2Hf_1T4EayQg}{5nbXw3F5RWCWjUSiRzv9DA}{192.0.2.42}{192.0.2.42:9300})
[INFO ][o.e.c.r.a.AllocationService] [bar2] Cluster health status changed from [GREEN] to [YELLOW] (reason: [removed dead nodes on election]). [INFO ][o.e.c.r.a.AllocationService] [bar2] Cluster health status changed from [GREEN] to [YELLOW] (reason: [removed dead nodes on election]).
[INFO ][o.e.c.s.ClusterService ] [bar2] new_master {bar2}{5wUhAI79SsyY-DKv4va26Q}{_VQTiZXxTCi2KIsijyQBpg}{192.168.0.133}{192.168.0.133:9302}, reason: zen-disco-elected-as-master ([0] nodes joined) [INFO ][o.e.c.s.ClusterService ] [bar2] new_master {bar2}{5wUhAI79SsyY-DKv4va26Q}{_VQTiZXxTCi2KIsijyQBpg}{192.0.2.133}{192.0.2.133:9302}, reason: zen-disco-elected-as-master ([0] nodes joined)
[INFO ][o.e.c.r.DelayedAllocationService] [bar2] scheduling reroute for delayed shards in [59.8s] (2 delayed shards) [INFO ][o.e.c.r.DelayedAllocationService] [bar2] scheduling reroute for delayed shards in [59.8s] (2 delayed shards)
[INFO ][o.e.c.r.a.AllocationService] [bar2] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.monitoring-es-2-2016.11.06][0]] ...]). [INFO ][o.e.c.r.a.AllocationService] [bar2] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.monitoring-es-2-2016.11.06][0]] ...]).
~~~ ~~~
@ -572,4 +572,4 @@ for index in ${indices}; do
# echo Delete ${index} # echo Delete ${index}
curl -XDELETE http://127.0.0.1:9200/${index} curl -XDELETE http://127.0.0.1:9200/${index}
done done
~~~ ~~~

View File

@ -171,7 +171,7 @@ du préfixe, ici 64. Ce qui donne par exemple :
Pour la passerelle il faut éditer le fichier /etc/mygate et ajouter Pour la passerelle il faut éditer le fichier /etc/mygate et ajouter
une ou plusieurs passerelles (IPv4 et IPv6) : une ou plusieurs passerelles (IPv4 et IPv6) :
192.168.0.1 192.0.2.1
2001:db8:42::1 2001:db8:42::1
#### Configuration (temporaire) en ligne de commande #### Configuration (temporaire) en ligne de commande

View File

@ -543,11 +543,11 @@ Et l'on peut configurer avec un réseau NAT avec `virt-manager` ou `virsh net-cr
<interface dev='eth0'/> <interface dev='eth0'/>
</forward> </forward>
<bridge name='virbr0' stp='on' delay='0'/> <bridge name='virbr0' stp='on' delay='0'/>
<mac address='52:54:00:06:2e:8c'/> <mac address='52:54:00:de:ad:41'/>
<domain name='nat0'/> <domain name='nat0'/>
<ip address='192.168.100.1' netmask='255.255.255.0'> <ip address='192.0.2.1' netmask='255.255.255.0'>
<dhcp> <dhcp>
<range start='192.168.100.128' end='192.168.100.254'/> <range start='192.0.2.128' end='192.0.2.254'/>
</dhcp> </dhcp>
</ip> </ip>
</network> </network>
@ -575,8 +575,8 @@ Vous pouvez ainsi lancer votre KVM ainsi (on lance un CD-ROM d'OpenBSD dans notr
# kvm -hda routeur0.qcow2 -cdrom cd48.iso -boot d -m 384 -k fr -net nic,macaddr=52:54:00:de:ad:42,model=e1000 -net tap,vlan=0,ifname=tap0 # kvm -hda routeur0.qcow2 -cdrom cd48.iso -boot d -m 384 -k fr -net nic,macaddr=52:54:00:de:ad:42,model=e1000 -net tap,vlan=0,ifname=tap0
~~~ ~~~
Une fois démarré, attribuez l'IP 10.0.0.1/24 à l'interface tap0 sur votre portable. Une fois démarré, attribuez l'IP 192.0.2.1/24 à l'interface tap0 sur votre portable.
Dans vos machines virtuelles, prenez une adresse IP dans la plage 10.0.0.0/24 et indiquez 10.0.0.1 comme route par défaut. Dans vos machines virtuelles, prenez une adresse IP dans la plage 192.0.2.0/24 et indiquez 192.0.2.1 comme route par défaut.
Normalement, c'est tout ! Normalement, c'est tout !
@ -899,7 +899,7 @@ Pour rappatrier une VM _test_ depuis l'hyperviseur _foo_ :
Si l'on a plusieurs interfaces réseau sur l'hyperviseur (par exemple un réseau dédié entre les hyperviseurs), il faut l'indiquer à *libvirtd* sinon il tente de passer par l'interface principale : Si l'on a plusieurs interfaces réseau sur l'hyperviseur (par exemple un réseau dédié entre les hyperviseurs), il faut l'indiquer à *libvirtd* sinon il tente de passer par l'interface principale :
~~~ ~~~
# virsh migrate --live --unsafe test qemu+ssh://192.168.0.2/system tcp://192.168.0.2/ # virsh migrate --live --unsafe test qemu+ssh://192.0.2.2/system tcp://192.0.2.2/
Migration: [100 %] Migration: [100 %]
~~~ ~~~
@ -1020,7 +1020,7 @@ Pour ne pas avoir besoin de redémarrer une VM pour retirer une interface, on pe
# virsh dumpxml <vm-name> # virsh dumpxml <vm-name>
[…] […]
<interface type='bridge'> <interface type='bridge'>
<mac address='52:54:00:xx:xx:xx'/> <mac address='52:54:00:de:ad:43'/>
<source bridge='br2'/> <source bridge='br2'/>
<target dev='vnet7'/> <target dev='vnet7'/>
<model type='virtio'/> <model type='virtio'/>