You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 21
Next »
Configuration
The inventory may define these hosts:
observers
: Set of hosts to observe the cluster (only the first is considering)
eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IlRoaWJhdWx0IFBFWVBFTFVUIiwib3V0cHV0VHlwZSI6ImJsb2NrIiwibGFzdE1vZGlmaWVyTmFtZSI6IlRoaWJhdWx0IFBFWVBFTFVUIiwibGFuZ3VhZ2UiOiJlbiIsImRpYWdyYW1EaXNwbGF5TmFtZSI6IiIsInNGaWxlSWQiOiIiLCJhdHRJZCI6IjY1ODA3ODY1IiwiZGlhZ3JhbU5hbWUiOiJjbHVzdGVyLWNvbmYiLCJhc3BlY3QiOiIiLCJsaW5rcyI6ImF1dG8iLCJjZW9OYW1lIjoiSGlnaCBhdmFpbGFiaWxpdHkgKHdpdGggY29yb3N5bmMvcGFjZW1ha2VyKSIsInRic3R5bGUiOiJ0b3AiLCJjYW5Db21tZW50IjpmYWxzZSwiZGlhZ3JhbVVybCI6IiIsImNzdkZpbGVVcmwiOiIiLCJib3JkZXIiOnRydWUsIm1heFNjYWxlIjoiMSIsIm93bmluZ1BhZ2VJZCI6NjU4MDYyODUsImVkaXRhYmxlIjpmYWxzZSwiY2VvSWQiOjY4NjUyODE3LCJwYWdlSWQiOiIiLCJsYm94Ijp0cnVlLCJzZXJ2ZXJDb25maWciOnsiZW1haWxwcmV2aWV3IjoiMSJ9LCJvZHJpdmVJZCI6IiIsInJldmlzaW9uIjowLCJtYWNyb0lkIjoiMzZmYjExZDItMzZmYS00ZTA0LTlhNjQtZjlkMDk5OThlMWY2IiwicHJldmlld05hbWUiOiJjbHVzdGVyLWNvbmYucG5nIiwibGljZW5zZVN0YXR1cyI6Ik9LIiwic2VydmljZSI6IiIsImlzVGVtcGxhdGUiOiIiLCJ3aWR0aCI6IjY4MSIsInNpbXBsZVZpZXdlciI6ZmFsc2UsImxhc3RNb2RpZmllZCI6MTY4NTAyMTEzNjc4NywiZXhjZWVkUGFnZVdpZHRoIjpmYWxzZSwib0NsaWVudElkIjoiIn0=
N to N redundancy
All nodes in the cluster have an access to a shared storage via ceph (more details here). With it, the cluster is in N to N redundancy mode.
- Corosync will provides messaging and membership services.
- Pacemaker will manage the cluster (synchronize resources between each node).
eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IlRoaWJhdWx0IFBFWVBFTFVUIiwib3V0cHV0VHlwZSI6ImJsb2NrIiwibGFzdE1vZGlmaWVyTmFtZSI6IlRoaWJhdWx0IFBFWVBFTFVUIiwibGFuZ3VhZ2UiOiJlbiIsImRpYWdyYW1EaXNwbGF5TmFtZSI6IiIsInNGaWxlSWQiOiIiLCJhdHRJZCI6IjY4NjQ5NjgwIiwiZGlhZ3JhbU5hbWUiOiJuLXRvLW4tcmVkdW5kYW5jeSIsImFzcGVjdCI6IiIsImxpbmtzIjoiYXV0byIsImNlb05hbWUiOiJIaWdoIGF2YWlsYWJpbGl0eSAod2l0aCBjb3Jvc3luYy9wYWNlbWFrZXIpIiwidGJzdHlsZSI6InRvcCIsImNhbkNvbW1lbnQiOmZhbHNlLCJkaWFncmFtVXJsIjoiIiwiY3N2RmlsZVVybCI6IiIsImJvcmRlciI6dHJ1ZSwibWF4U2NhbGUiOiIxIiwib3duaW5nUGFnZUlkIjo2NTgxODU0NiwiZWRpdGFibGUiOmZhbHNlLCJjZW9JZCI6Njg2NTI4MTcsInBhZ2VJZCI6IiIsImxib3giOnRydWUsInNlcnZlckNvbmZpZyI6eyJlbWFpbHByZXZpZXciOiIxIn0sIm9kcml2ZUlkIjoiIiwicmV2aXNpb24iOjEsIm1hY3JvSWQiOiI3N2Y4ZTE4Ny00NTQ3LTQ5NmMtODIzNS0wZmViMzVkMDIxOWQiLCJwcmV2aWV3TmFtZSI6Im4tdG8tbi1yZWR1bmRhbmN5LnBuZyIsImxpY2Vuc2VTdGF0dXMiOiJPSyIsInNlcnZpY2UiOiIiLCJpc1RlbXBsYXRlIjoiIiwid2lkdGgiOiI0MDEiLCJzaW1wbGVWaWV3ZXIiOmZhbHNlLCJsYXN0TW9kaWZpZWQiOjE2ODcyNDgyMTgxMzQsImV4Y2VlZFBhZ2VXaWR0aCI6ZmFsc2UsIm9DbGllbnRJZCI6IiJ9
More details on pacemaker here and corosync here.
libvirt
To use pacemaker like
The vm_manager project is an high-level interface of pacemaker and ceph to manage the VM like a resource. He is installed during the installation step and provides the vm-mgr
command.
Sub-command
All sub-commands has -n
, --name
required option to specify which resource should be used.
add_colocation
: Adds a colocation constraints between resources
clone
: Creates a copy of the VM
create
: Generates a new resource from a VM
create_snapshot
: Creates a snapshot of a resource
disable
: Stops and removes the resource on the cluster
enable
: Adds and starts the resource on the cluster
get_metadata
: Gets a metadata of a resource
list
: Lists all resources
list_metadata
: Lists all keys of a resource
list_snapshots
: Lists all created snapshots
purge
: Deletes all snapshots of a resource
remove
: Removes the resource
remove_snapshot
: Removes a snapshot of a resource
rollback
: Rollbacks to a snapshot for a resource
set_metadata
: Sets a metadata of a resource
start
: Start a resource
status
: Gets the status of a resource
stop
: Stops a resource
Resources status
Undefined
:Disabled
:Failed
:Started
:Starting
:Stopping
:Stopped
:
Manage VM
Add VM in the cluster:
vm-mgr create --name NAME --xml /path/to/configuration.xml --image /path/to/disk.qcow2 --disable --force --enable-live-migration --migration-user virtu --migrate-to-timeout 180
Check the execution of the resource:
Get the status of the resource:
vm-mgr status --name NAME
Delete VM in the cluster:
vm-mgr remove --name NAME