Portál AbcLinuxu, 1. května 2025 07:12
8.6.2016 13:13
Ruža Becelin | skóre: 40
| blog: RuzaBecelinBlog
Díky za vhodný výraz.
Kolik zvládne Pacemaker nodů? Kdesi jsem četl, že omezení měly mít hlavně starší verze corosyncu. Každopádně na netu jsem narazil na mail (z r. 2012) kde psali, že je to dané tím, kolik strojů zvládne vzájemně komunikovat. A to je věc corosyncu. Ten prý reálně testovali na 32 nodovém clusteru a pro vyšší počet nodů doporučovali udělat menší clustery (viz).
A narazil jsem také na mail člověka, který chtěl sestavit 80 nodový cluster a narazil na limit corosyncu - 64 nodů (viz)
Druhý pokus o aktualizaci jsem spojil s přechodem na cephNějaký zápisek o tomhle bude?
Zrovna nedávno jsem si s tím zoušel hrát taky a byl to docela porod.
8.6.2016 07:25
9.6.2016 15:58
# pcs resource describe ocf:heartbeat:VirtualDomain
ocf:heartbeat:VirtualDomain - Manages virtual domains through the libvirt virtualization framework
Resource agent for a virtual domain (a.k.a. domU, virtual machine,
virtual environment etc., depending on context) managed by libvirtd.
Resource options:
config (required): Absolute path to the libvirt configuration file, for this virtual domain.
hypervisor: Hypervisor URI to connect to. See the libvirt documentation for details on supported URI formats. The default is system
dependent. Determine the system's default uri by running 'virsh --quiet uri'.
force_stop: Always forcefully shut down ("destroy") the domain on stop. The default behavior is to resort to a forceful shutdown only
after a graceful shutdown attempt has failed. You should only set this to true if your virtual domain (or your
virtualization backend) does not support graceful shutdown.
migration_transport: Transport used to connect to the remote hypervisor while migrating. Please refer to the libvirt documentation
for details on transports available. If this parameter is omitted, the resource will use libvirt's default
transport to connect to the remote hypervisor.
migration_network_suffix: Use a dedicated migration network. The migration URI is composed by adding this parameters value to the end
of the node name. If the node name happens to be an FQDN (as opposed to an unqualified host name), insert
the suffix immediately prior to the first period (.) in the FQDN. At the moment Qemu/KVM and Xen migration
via a dedicated network is supported. Note: Be sure this composed host name is locally resolveable and the
associated IP is reachable through the favored network.
monitor_scripts: To additionally monitor services within the virtual domain, add this parameter with a list of scripts to monitor.
Note: when monitor scripts are used, the start and migrate_from operations will complete only when all monitor
scripts have completed successfully. Be sure to set the timeout of these operations to accommodate this delay.
autoset_utilization_cpu: If set true, the agent will detect the number of domainU's vCPUs from virsh, and put it into the CPU
utilization of the resource when the monitor is executed.
autoset_utilization_hv_memory: If set true, the agent will detect the number of *Max memory* from virsh, and put it into the
hv_memory utilization of the resource when the monitor is executed.
migrateport: This port will be used in the qemu migrateuri. If unset, the port will be a random highport.
snapshot: Path to the snapshot directory where the virtual machine image will be stored. When this parameter is set, the virtual
machine's RAM state will be saved to a file in the snapshot directory when stopped. If on start a state file is present for
the domain, the domain will be restored to the same state it was in right before it stopped last. This option is
incompatible with the 'force_stop' option.
Díky,
Ondra
Tiskni
Sdílej:
ISSN 1214-1267, (c) 1999-2007 Stickfish s.r.o.