{"id":53611,"date":"2019-12-06T00:00:00","date_gmt":"2019-12-05T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/legko-i-neprinuzhdenno-deploim-prilozheniya-na-tarantool-cartridge-chast-1"},"modified":"2020-02-18T14:01:32","modified_gmt":"2020-02-18T11:01:32","slug":"legko-i-neprinuzhdenno-deploim-prilozheniya-na-tarantool-cartridge-chast-1","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/legko-i-neprinuzhdenno-deploim-prilozheniya-na-tarantool-cartridge-chast-1","title":{"rendered":"Snadno a bez n\u00e1mahy deployujeme aplikace na Tarantool Cartridge (\u010d\u00e1st 1)","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Snadno a bez n\u00e1mahy deployujeme aplikace na Tarantool Cartridge (\u010d\u00e1st 1)\" src=\"\/wp-content\/uploads\/2019\/12\/0493b6c8d60253352bc971b216e9b63e.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p>Ji\u017e jsme hovo\u0159ili o <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/mailru\/blog\/465503\/\">Tarantool Cartridge<\/a><\/noindex>, kter\u00fd umo\u017e\u0148uje vyv\u00edjet distribuovan\u00e9 aplikace a balit je. U\u017e zb\u00fdv\u00e1 jen m\u00e1lo: nau\u010dit se tyto aplikace nasazovat a spravovat. Nebojte se, na v\u0161e jsme mysleli! Shrom\u00e1\u017edili jsme v\u0161echny osv\u011bd\u010den\u00e9 postupy pro pr\u00e1ci s Tarantool Cartridge a napsali <noindex><a rel=\"nofollow\" href=\"https:\/\/galaxy.ansible.com\/tarantool\/cartridge\">ansible-rol\u00edch<\/a><\/noindex>, kter\u00e1 nainstaluje bal\u00edk na servery, spust\u00ed instance, spoj\u00ed je do clusteru, nastav\u00ed autorizaci, p\u0159iprav\u00ed vshard, zapne automatick\u00fd failover a propatche clusterovou konfiguraci.<\/p>\n<p><\/p>\n<p>Zaj\u00edmav\u00e9? Tak poj\u010fte d\u00e1l, v\u0161echno v\u00e1m pov\u00edme a uk\u00e1\u017eeme.<\/p>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h1 id=\"nachnem-s-primera\">Za\u010dn\u011bme s p\u0159\u00edkladem<\/h1>\n<p><\/p>\n<p>Pod\u00edv\u00e1me se pouze na \u010d\u00e1st funkcionality na\u0161\u00ed role. \u00dapln\u00fd popis v\u0161ech jej\u00edch funkc\u00ed a vstupn\u00edch parametr\u016f v\u017edy najdete v <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/tarantool\/ansible-cartridge#ansible-role-tarantool-cartridge\">dokumentaci<\/a><\/noindex>. Ale lep\u0161\u00ed jednou zkusit, ne\u017e stokr\u00e1t vid\u011bt, tak si dejme mal\u00e9 nasazen\u00ed aplikace.<\/p>\n<p><\/p>\n<p>Tarantool Cartridge m\u00e1 <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/tarantool\/cartridge-cli\/tree\/master\/examples\/getting-started-app#application-example-based-on-tarantool-cartridge\">tutori\u00e1l<\/a><\/noindex> p\u0159\u00edklad pro vytvo\u0159en\u00ed mal\u00e9 Cartridge aplikace, kter\u00e1 uchov\u00e1v\u00e1 informace o bankovn\u00edch klientech a jejich \u00fa\u010dtech, a tak\u00e9 poskytuje API pro spr\u00e1vu dat p\u0159es HTTP. V aplikaci jsou pops\u00e1ny dv\u011b mo\u017en\u00e9 role: <code>api<\/code> a <code>\u00falo\u017ei\u0161t\u011b<\/code>, kter\u00e9 mohou b\u00fdt p\u0159i\u0159azeny instanc\u00edm.<\/p>\n<p><\/p>\n<p>Samotn\u00fd Cartridge nenazna\u010duje, jak spou\u0161t\u011bt procesy, pouze umo\u017e\u0148uje konfiguraci ji\u017e spu\u0161t\u011bn\u00fdch instanc\u00ed. Ostatn\u00ed mus\u00ed u\u017eivatel ud\u011blat s\u00e1m: rozlo\u017eit konfigura\u010dn\u00ed soubory, spustit slu\u017eby a nastavit topologii. Ale nebudeme se t\u00edm v\u0161\u00edm zab\u00fdvat, to za n\u00e1s ud\u011bl\u00e1 Ansible.<\/p>\n<p><\/p>\n<h3 id=\"ot-slov-k-delu\">Od slov k \u010din\u016fm<\/h3>\n<p><\/p>\n<p>Tak tedy, nasad\u00edme na\u0161i aplikaci na dva virtu\u00e1ln\u00ed stroje a nastav\u00edme jednoduchou topologii:<\/p>\n<p><\/p>\n<ul>\n<li>Replika set <code>app-1<\/code> bude realizovat roli <code>api<\/code>, kter\u00e1 zahrnuje roli <code>vshard-router<\/code>. Tady bude pouze jedna instance.<\/li>\n<li>Replika set <code>storage-1<\/code> realizuje roli <code>\u00falo\u017ei\u0161t\u011b<\/code> (a z\u00e1rove\u0148 <code>vshard-storage<\/code>), sem p\u0159id\u00e1me dv\u011b instance z r\u016fzn\u00fdch stroj\u016f.<\/li>\n<\/ul>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Snadno a bez n\u00e1mahy deployujeme aplikace na Tarantool Cartridge (\u010d\u00e1st 1)\" src=\"\/wp-content\/uploads\/2019\/12\/62d20050e2d7a6358002ecd758222f1f.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p>Pro spu\u0161t\u011bn\u00ed p\u0159\u00edkladu budeme pot\u0159ebovat <noindex><a rel=\"nofollow\" href=\"https:\/\/www.vagrantup.com\/\">Vagrant<\/a><\/noindex> a <noindex><a rel=\"nofollow\" href=\"https:\/\/www.ansible.com\">Ansible<\/a><\/noindex> (verze 2.8 nebo star\u0161\u00ed).<\/p>\n<p><\/p>\n<p>Samotn\u00e1 role se nach\u00e1z\u00ed v <noindex><a rel=\"nofollow\" href=\"https:\/\/galaxy.ansible.com\/docs\/\">Ansible Galaxy<\/a><\/noindex>. To je takov\u00fd repozit\u00e1\u0159, kter\u00fd umo\u017e\u0148uje sd\u00edlen\u00ed vlastn\u00edch znalost\u00ed a pou\u017e\u00edv\u00e1n\u00ed hotov\u00fdch rol\u00ed.<\/p>\n<p><\/p>\n<p>Naklonujeme repozit\u00e1\u0159 s p\u0159\u00edkladem:<\/p>\n<p><\/p>\n<pre><code class=\"bash\">$ git clone https:\/\/github.com\/dokshina\/deploy-tarantool-cartridge-app.git\n$ cd deploy-tarantool-cartridge-app &amp;&amp; git checkout 1.0.0<\/code><\/pre>\n<p><\/p>\n<p>Zved\u00e1me virtu\u00e1ln\u00ed stroje:<\/p>\n<p><\/p>\n<pre><code class=\"bash\">$ vagrant up<\/code><\/pre>\n<p><\/p>\n<p>Nainstalujeme ansible-rol na Tarantool Cartridge:<\/p>\n<p><\/p>\n<pre><code class=\"bash\">$ ansible-galaxy install tarantool.cartridge,1.0.1<\/code><\/pre>\n<p><\/p>\n<p>Spou\u0161t\u00edme nainstalovanou roli:<\/p>\n<p><\/p>\n<pre><code class=\"bash\">$ ansible-playbook -i hosts.yml playbook.yml<\/code><\/pre>\n<p><\/p>\n<p>\u010cek\u00e1me na dokon\u010den\u00ed spu\u0161t\u011bn\u00ed playbooku, p\u0159ejdeme na <noindex><a rel=\"nofollow\" href=\"http:\/\/localhost:8181\/admin\/cluster\/dashboard\">http:\/\/localhost:8181\/admin\/cluster\/dashboard<\/a><\/noindex> a u\u017e\u00edv\u00e1me si v\u00fdsledek:<\/p>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Snadno a bez n\u00e1mahy deployujeme aplikace na Tarantool Cartridge (\u010d\u00e1st 1)\" src=\"\/wp-content\/uploads\/2019\/12\/6563ddf2f2bfc85714f327c8d6b2d1c4.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p>M\u016f\u017eeme p\u0159en\u00e1\u0161et data. Skv\u011bl\u00e9, \u017ee?<\/p>\n<p><\/p>\n<p>A te\u010f se pod\u00edvejme, jak s t\u00edm pracovat, a z\u00e1rove\u0148 p\u0159id\u00e1me dal\u0161\u00ed replikaset do topologie.<\/p>\n<p><\/p>\n<h3 id=\"nachinaem-razbiratsya\">Za\u010d\u00edn\u00e1me se zab\u00fdvat<\/h3>\n<p><\/p>\n<p>Tak co se vlastn\u011b stalo?<\/p>\n<p><\/p>\n<p>Vytvo\u0159ili jsme dv\u011b virtu\u00e1ln\u00ed stroje a spustili ansible playbook, kter\u00fd nastavil n\u00e1\u0161 klastr. Pod\u00edvejme se na obsah souboru <code>playbook.yml<\/code>:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">---\n- name: Nasadit mou aplikaci Tarantool Cartridge\n  hosts: all\n  become: true\n  become_user: root\n  tasks:\n  - name: Importovat roli Tarantool Cartridge\n    import_role:\n      name: tarantool.cartridge<\/code><\/pre>\n<p><\/p>\n<p>Zde se nic zaj\u00edmav\u00e9ho ned\u011bje, spou\u0161t\u00edme ansible roli, kter\u00e1 se jmenuje <code>tarantool.cartridge<\/code>.<\/p>\n<p><\/p>\n<p>V\u0161echno d\u016fle\u017eit\u00e9 (a to, konkr\u00e9tn\u011b, konfigurace klastru) se nach\u00e1z\u00ed v <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.ansible.com\/ansible\/latest\/user_guide\/intro_inventory.html\">invent\u00e1\u0159<\/a><\/noindex>- souboru <code>hosts.yml<\/code>:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">---\nall:\n  vars:\n    # b\u011b\u017en\u00e9 prom\u011bnn\u00e9 klastru\n    cartridge_app_name: getting-started-app\n    cartridge_package_path: .\/getting-started-app-1.0.0-0.rpm  # cesta k bal\u00ed\u010dku\n\n    cartridge_cluster_cookie: app-default-cookie  # cluster cookie\n\n    # b\u011b\u017en\u00e9 mo\u017enosti ssh\n    ansible_ssh_private_key_file: ~\/.vagrant.d\/insecure_private_key\n    ansible_ssh_common_args: '-o IdentitiesOnly=yes -o UserKnownHostsFile=\/dev\/null -o StrictHostKeyChecking=no'\n\n  # INSTANCI\n  hosts:\n    storage-1:\n      config:\n        advertise_uri: '172.19.0.2:3301'\n        http_port: 8181\n\n    app-1:\n      config:\n        advertise_uri: '172.19.0.3:3301'\n        http_port: 8182\n\n    storage-1-replica:\n      config:\n        advertise_uri: '172.19.0.3:3302'\n        http_port: 8183\n\n  children:\n    # SKUPINOV\u00c9 INSTANCI PODLE STROJ\u016e\n    host1:\n      vars:\n        # p\u0159ipojovac\u00ed mo\u017enosti prvn\u00edho stroje\n        ansible_host: 172.19.0.2\n        ansible_user: vagrant\n\n      hosts:  # instance, kter\u00e9 budou spu\u0161t\u011bny na prvn\u00edm stroji\n        storage-1:\n\n    host2:\n      vars:\n        # p\u0159ipojovac\u00ed mo\u017enosti druh\u00e9ho stroje\n        ansible_host: 172.19.0.3\n        ansible_user: vagrant\n\n      hosts:  # instance, kter\u00e9 budou spu\u0161t\u011bny na druh\u00e9m stroji\n        app-1:\n        storage-1-replica:\n\n    # SKUPINOV\u00c9 INSTANCI PODLE REPLIKOV\u00ddCH SATOV\n    replicaset_app_1:\n      vars:  # konfigurace replikov\u00e9ho sadu\n        replicaset_alias: app-1\n        failover_priority:\n          - app-1  # v\u016fdce\n        roles:\n          - 'api'\n\n      hosts:  # instance replikov\u00e9ho sadu\n        app-1:\n\n    replicaset_storage_1:\n      vars:  # konfigurace replikov\u00e9ho sadu\n        replicaset_alias: storage-1\n        weight: 3\n        failover_priority:\n          - storage-1  # v\u016fdce\n          - storage-1-replica\n        roles:\n          - 'storage'\n\n      hosts:   # instance replikov\u00e9ho sadu\n        storage-1:\n        storage-1-replica:<\/code><\/pre>\n<p><\/p>\n<p>V\u0161echno, co pot\u0159ebujeme, je nau\u010dit se ovl\u00e1dat instance a replikov\u00e9 sady, zm\u011bnou obsahu tohoto souboru. D\u00e1le do n\u011bj budeme p\u0159id\u00e1vat nov\u00e9 sekce. Abychom se neztratili, kam je p\u0159id\u00e1vat, m\u016f\u017eete nahl\u00e9dnout do fin\u00e1ln\u00ed verze tohoto souboru, <code>hosts.updated.yml<\/code>, kter\u00fd se nach\u00e1z\u00ed v repozit\u00e1\u0159i s p\u0159\u00edkladem.<\/p>\n<p><\/p>\n<h3 id=\"upravlenie-instansami\">Spr\u00e1va instanc\u00ed<\/h3>\n<p><\/p>\n<p>V pojmech Ansible je ka\u017ed\u00e1 instance - to je host (nepl\u00e9st s fyzick\u00fdm serverem), tj. uzel infrastruktury, kter\u00fdm Ansible bude spravovat. Pro ka\u017ed\u00e9ho hostitele m\u016f\u017eeme specifikovat parametry p\u0159ipojen\u00ed (takov\u00e9, jako je <code>ansible_host<\/code> a <code>ansible_user<\/code>), a tak\u00e9 konfiguraci instance. Popis instanc\u00ed naleznete v sekci <code>hosts<\/code>.<\/p>\n<p><\/p>\n<p>Zva\u017eme konfiguraci instance <code>storage-1<\/code>:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">all:\n  vars:\n    ...\n\n  # INSTAN\u010cN\u00cd\n  hosts:\n    storage-1:\n      config:\n        advertise_uri: '172.19.0.2:3301'\n        http_port: 8181\n\n  ...<\/code><\/pre>\n<p><\/p>\n<p>V prom\u011bnn\u00e9 <code>config<\/code> uvedli jsme parametry instance \u2014 <code>advertise URI<\/code> a <code>HTTP port<\/code>.<br \/>\nN\u00ed\u017ee jsou parametry instanc\u00ed <code>app-1<\/code> a <code>storage-1-replica<\/code>.<\/p>\n<p><\/p>\n<p>Mus\u00edme Ansible sd\u011blit parametry p\u0159ipojen\u00ed pro ka\u017edou instanci. Zd\u00e1 se logick\u00e9 slou\u010dit instance do skupin podle virtu\u00e1ln\u00edch stroj\u016f. K tomu byly instance slou\u010deny do skupin <code>host1<\/code> a <code>host2<\/code>, a v ka\u017ed\u00e9 skupin\u011b v sekci <code>vars<\/code> jsou uvedeny hodnoty <code>ansible_host<\/code> a <code>ansible_user<\/code> pro jeden virtu\u00e1ln\u00ed stroj. A v sekci <code>hosts<\/code> \u2014 host\u00e9 (tak\u00e9 instance), kter\u00e9 pat\u0159\u00ed do t\u00e9to skupiny:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">all:\n  vars:\n    ...\n  hosts:\n    ...\n  children:\n    # SKUPINOV\u00c9 INSTANCI PODLE STROJ\u016e\n    host1:\n      vars:\n        # mo\u017enosti p\u0159ipojen\u00ed prvn\u00edho stroje\n        ansible_host: 172.19.0.2\n        ansible_user: vagrant\n       hosts:  # instance, kter\u00e9 budou spu\u0161t\u011bny na prvn\u00edm stroji\n        storage-1:\n\n     host2:\n      vars:\n        # mo\u017enosti p\u0159ipojen\u00ed druh\u00e9ho stroje\n        ansible_host: 172.19.0.3\n        ansible_user: vagrant\n       hosts:  # instance, kter\u00e9 budou spu\u0161t\u011bny na druh\u00e9m stroji\n        app-1:\n        storage-1-replica:<\/code><\/pre>\n<p><\/p>\n<p>Za\u010d\u00edn\u00e1me m\u011bnit <code>hosts.yml<\/code>. P\u0159id\u00e1me je\u0161t\u011b dv\u011b instance, <code>storage-2-replica<\/code> na prvn\u00edm virtu\u00e1ln\u00edm stroji a <code>storage-2<\/code> na druh\u00e9m:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">all:\n  vars:\n    ...\n\n  # INSTAN\u010cN\u00cd\n  hosts:\n    ...\n    storage-2:  # &lt;==\n      config:\n        advertise_uri: '172.19.0.3:3303'\n        http_port: 8184\n\n    storage-2-replica:  # &lt;==\n      config:\n        advertise_uri: '172.19.0.2:3302'\n        http_port: 8185\n\n  children:\n    # SKUPINOV\u00c9 INSTANCI PODLE STROJ\u016e\n    host1:\n      vars:\n        ...\n      hosts:  # instance, kter\u00e9 budou spu\u0161t\u011bny na prvn\u00edm stroji\n        storage-1:\n        storage-2-replica:  # &lt;==\n\n    host2:\n      vars:\n        ...\n      hosts:  # instance, kter\u00e9 budou spu\u0161t\u011bny na druh\u00e9m stroji\n        app-1:\n        storage-1-replica:\n        storage-2:  # &lt;==\n  ...<\/code><\/pre>\n<p><\/p>\n<p>Spou\u0161t\u00edme ansible-playbook:<\/p>\n<p><\/p>\n<pre><code class=\"bash\">$ ansible-playbook -i hosts.yml \n                   --limit storage-2,storage-2-replica \n                   playbook.yml<\/code><\/pre>\n<p><\/p>\n<p>V\u0161imn\u011bte si mo\u017enosti <code>--limit<\/code>. Proto\u017ee ka\u017ed\u00e1 instance clusteru je host v terminologii Ansible, m\u016f\u017eeme jasn\u011b uv\u00e1d\u011bt, kter\u00e9 instance by m\u011bly b\u00fdt nakonfigurov\u00e1ny p\u0159i spu\u0161t\u011bn\u00ed playbooku.<\/p>\n<p><\/p>\n<p>Znovu se p\u0159ihla\u0161ujeme do Web UI <noindex><a rel=\"nofollow\" href=\"http:\/\/localhost:8181\/admin\/cluster\/dashboard\">http:\/\/localhost:8181\/admin\/cluster\/dashboard<\/a><\/noindex> a sledujeme na\u0161e nov\u00e9 instance:<\/p>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Snadno a bez n\u00e1mahy deployujeme aplikace na Tarantool Cartridge (\u010d\u00e1st 1)\" src=\"\/wp-content\/uploads\/2019\/12\/6181c359e4e5ec4adaee8737600a27e4.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p>Nenech\u00e1me se zastavit a osvoj\u00edme si spr\u00e1vu topologie.<\/p>\n<p><\/p>\n<h3 id=\"upravlenie-topologiey\">Spr\u00e1va topologie<\/h3>\n<p><\/p>\n<p>Slou\u010d\u00edme na\u0161e nov\u00e9 instance do replikaset <code>storage-2<\/code>. P\u0159id\u00e1me novou skupinu <code>replicaset_storage_2<\/code> a pop\u00ed\u0161eme v jej\u00edch prom\u011bnn\u00fdch parametry replikasetu podle vzoru <code>replicaset_storage_1<\/code>. V sekci <code>hosts<\/code> ur\u010d\u00edme, kter\u00e9 instance budou do t\u00e9to skupiny pat\u0159it (tedy n\u00e1\u0161 replikaset):<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">---\nall:\n  vars:\n    ...\n  hosts:\n    ...\n  children:\n    ...\n    # SKUPINY INSTANC\u00cd ROZD\u011aLEN\u00c9 PODLE REPLIKOV\u00ddCH SAD\n    ...\n    replicaset_storage_2:  # &lt;==\n      vars:  # konfigurace replikov\u00e9 sady\n        replicaset_alias: storage-2\n        weight: 2\n        failover_priority:\n          - storage-2\n          - storage-2-replica\n        roles:\n          - &#039;storage&#039;\n\n      hosts:   # instance replikov\u00e9 sady\n        storage-2:\n        storage-2-replica:<\/code><\/pre>\n<p><\/p>\n<p>Znovu spou\u0161t\u00edme playbook:<\/p>\n<p><\/p>\n<pre><code class=\"bash\">$ ansible-playbook -i hosts.yml \n                   --limit replicaset_storage_2 \n                   --tags cartridge-replicasets \n                   playbook.yml<\/code><\/pre>\n<p><\/p>\n<p>V parametru <code>--limit<\/code> jsme tentokr\u00e1t p\u0159edali n\u00e1zev skupiny, kter\u00e1 odpov\u00edd\u00e1 na\u0161\u00ed replikov\u00e9 sad\u011b.<\/p>\n<p><\/p>\n<p>Poj\u010fme se pod\u00edvat na mo\u017enost <code>tags<\/code>.<\/p>\n<p><\/p>\n<p>Na\u0161e role postupn\u011b prov\u00e1d\u00ed r\u016fzn\u00e9 \u00fakoly, kter\u00e9 jsou ozna\u010deny n\u00e1sleduj\u00edc\u00edmi tagy:<\/p>\n<p><\/p>\n<ul>\n<li><code>cartridge-instances<\/code>: spr\u00e1va instanc\u00ed (nastaven\u00ed, p\u0159ipojen\u00ed k membership);<\/li>\n<li><code>cartridge-replicasets<\/code>: spr\u00e1va topologie (spr\u00e1va replikov\u00fdch sad a nevratn\u00e9 odstra\u0148ov\u00e1n\u00ed (expel) instanc\u00ed z clusteru);<\/li>\n<li><code>cartridge-config<\/code>: spr\u00e1va ostatn\u00edch parametr\u016f clusteru (vshard bootstrapping, re\u017eim automatick\u00e9ho failoveru, parametry autorizace a konfigurace aplikace).<\/li>\n<\/ul>\n<p><\/p>\n<p>M\u016f\u017eeme jasn\u011b ur\u010dit, kterou \u010d\u00e1st pr\u00e1ce chceme prov\u00e9st, a role p\u0159esko\u010d\u00ed prov\u00e1d\u011bn\u00ed ostatn\u00edch \u00fakol\u016f. V na\u0161em p\u0159\u00edpad\u011b chceme pracovat pouze s topologi\u00ed, proto jsme uvedli <code>cartridge-replicasets<\/code>.<\/p>\n<p><\/p>\n<p>Poj\u010fme vyhodnotit v\u00fdsledek na\u0161ich snah. Najdeme novou replikovou sadu na <noindex><a rel=\"nofollow\" href=\"http:\/\/localhost:8181\/admin\/cluster\/dashboard\">http:\/\/localhost:8181\/admin\/cluster\/dashboard<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Snadno a bez n\u00e1mahy deployujeme aplikace na Tarantool Cartridge (\u010d\u00e1st 1)\" src=\"\/wp-content\/uploads\/2019\/12\/20da99480df519b1ee239cd81f67b786.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p>Hur\u00e1!<\/p>\n<p><\/p>\n<p>Experimentujte se zm\u011bnami konfigurace instanc\u00ed a replikov\u00fdch sad a sledujte, jak se m\u011bn\u00ed topologie clusteru. M\u016f\u017eete vyzkou\u0161et r\u016fzn\u00e9 provozn\u00ed sc\u00e9n\u00e1\u0159e, nap\u0159\u00edklad, <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.ansible.com\/ansible\/latest\/user_guide\/playbooks_delegation.html#rolling-update-batch-size\">rolling update<\/a><\/noindex> nebo zv\u00fd\u0161en\u00ed <code>memtx_memory<\/code>. Role se to pokus\u00ed ud\u011blat bez restartu instance, aby se sn\u00ed\u017eil mo\u017en\u00fd downtime va\u0161\u00ed aplikace.<\/p>\n<p><\/p>\n<p>Nezapome\u0148te spustit <code>vagrant halt<\/code>, abyste zastavili virtu\u00e1ln\u00ed stroje, kdy\u017e s nimi skon\u010d\u00edte.<\/p>\n<p><\/p>\n<h1 id=\"a-chto-pod-kapotom\">A co se d\u011bje uvnit\u0159?<\/h1>\n<p><\/p>\n<p>Zde podrobn\u011bji pop\u00ed\u0161u, co se d\u011blo uvnit\u0159 ansible role b\u011bhem na\u0161ich experiment\u016f.<\/p>\n<p><\/p>\n<p>Pod\u00edvejme se krok za krokem na nasazen\u00ed aplikace Cartridge.<\/p>\n<p><\/p>\n<h3 id=\"ustanovka-paketa-i-start-instansov\">Instalace bal\u00ed\u010dku a spu\u0161t\u011bn\u00ed instanc\u00ed<\/h3>\n<p><\/p>\n<p>Nejprve je t\u0159eba doru\u010dit bal\u00ed\u010dek na server a nainstalovat ho. Nyn\u00ed role um\u00ed pracovat s RPM a DEB bal\u00ed\u010dky.<\/p>\n<p><\/p>\n<p>Pot\u00e9 spust\u00edme instance. Tady je to velmi jednoduch\u00e9: ka\u017ed\u00e1 instance je samostatn\u00fd <code>systemd<\/code>-slu\u017eba. Popisuji na p\u0159\u00edkladu:<\/p>\n<p><\/p>\n<pre><code class=\"bash\">$ systemctl start myapp@storage-1<\/code><\/pre>\n<p><\/p>\n<p>Tento p\u0159\u00edkaz spust\u00ed instanci <code>storage-1<\/code> aplikace <code>myapp<\/code>. Spu\u0161t\u011bn\u00e1 instance bude hledat svou <noindex><a rel=\"nofollow\" href=\"https:\/\/www.tarantool.io\/ru\/doc\/2.2\/book\/cartridge\/cartridge_dev\/#configuring-instances\">konfiguraci<\/a><\/noindex> v <code>\/etc\/tarantool\/conf.d\/<\/code>. Logy instance lze zobrazit pomoc\u00ed <code>journald<\/code>.<\/p>\n<p><\/p>\n<p>Unit souboru <code>\/etc\/systemd\/system\/myapp@.sevice<\/code> pro systemd slu\u017ebu budou doru\u010deny spolu s bal\u00ed\u010dkem.<\/p>\n<p><\/p>\n<p>V Ansible jsou vestav\u011bn\u00e9 moduly pro instalaci bal\u00ed\u010dk\u016f a spr\u00e1vu systemd slu\u017eeb, zde jsme nevymysleli nic nov\u00e9ho.<\/p>\n<p><\/p>\n<h3 id=\"nastroyka-topologii-klastera\">Nastaven\u00ed topologie clustera<\/h3>\n<p><\/p>\n<p>A tady za\u010d\u00edn\u00e1 to nejzaj\u00edmav\u011bj\u0161\u00ed. Souhlas\u00edte, bylo by divn\u00e9 se obracet na speci\u00e1ln\u00ed ansible roli pro instalaci bal\u00ed\u010dk\u016f a spou\u0161t\u011bn\u00ed <code>systemd<\/code>-slu\u017eeb.<\/p>\n<p><\/p>\n<p>Cluster lze nastavit ru\u010dn\u011b:<\/p>\n<p><\/p>\n<ul>\n<li>Prvn\u00ed mo\u017enost: otev\u0159ete Web UI a klikn\u011bte na tla\u010d\u00edtka. Pro jednor\u00e1zov\u00e9 spu\u0161t\u011bn\u00ed n\u011bkolika instanc\u00ed to bude zcela vyhovovat.<\/li>\n<li>Druh\u00e1 mo\u017enost: m\u016f\u017eete vyu\u017e\u00edt GraphQl API. Zde u\u017e m\u016f\u017eete n\u011bco automatizovat, nap\u0159\u00edklad napsat skript v Pythonu.<\/li>\n<li>T\u0159et\u00ed mo\u017enost (pro siln\u00e9 du\u0161e): p\u0159ihlaste se na server, p\u0159ipojte se k jedn\u00e9 z instanc\u00ed pomoc\u00ed <code>tarantoolctl connect<\/code> a prove\u010fte v\u0161echny pot\u0159ebn\u00e9 manipulace s Lua modulem <code>cartridge<\/code>.<\/li>\n<\/ul>\n<p><\/p>\n<p>Hlavn\u00edm c\u00edlem na\u0161eho vyn\u00e1lezu je ud\u011blat za v\u00e1s pr\u00e1v\u011b tu nejobt\u00ed\u017en\u011bj\u0161\u00ed \u010d\u00e1st pr\u00e1ce.<\/p>\n<p><\/p>\n<p>Ansible umo\u017e\u0148uje napsat sv\u016fj modul a pou\u017e\u00edvat ho v roli. Na\u0161e role pou\u017e\u00edv\u00e1 takov\u00e9 moduly pro spr\u00e1vu r\u016fzn\u00fdch komponent\u016f clustera.<\/p>\n<p><\/p>\n<p>Jak to funguje? Pop\u00ed\u0161ete po\u017eadovan\u00fd stav clustera v deklarativn\u00edm konfigu a role poskytuje ka\u017ed\u00e9mu modulu jeho sekci konfigurace. Modul z\u00edsk\u00e1 aktu\u00e1ln\u00ed stav clustera a porovn\u00e1 ho s t\u00edm, co dostal na vstupu. Pot\u00e9 je prost\u0159ednictv\u00edm socketu jedn\u00e9 z instanc\u00ed spu\u0161t\u011bn k\u00f3d, kter\u00fd p\u0159ivede cluster do po\u017eadovan\u00e9ho stavu.<\/p>\n<p><\/p>\n<h1 id=\"itogi\">Z\u00e1v\u011bry<\/h1>\n<p><\/p>\n<p>Dnes jsme v\u00e1m uk\u00e1zali, jak nasadit va\u0161i aplikaci na Tarantool Cartridge a nastavit jednoduchou topologii. K tomu jsme pou\u017eili Ansible \u2013 mocn\u00fd n\u00e1stroj, kter\u00fd se vyzna\u010duje jednoduchost\u00ed pou\u017eit\u00ed a umo\u017e\u0148uje z\u00e1rove\u0148 konfigurovat mno\u017estv\u00ed uzl\u016f infrastruktury (v na\u0161em p\u0159\u00edpad\u011b to jsou instance clustera).<\/p>\n<p><\/p>\n<p>V\u00fd\u0161e jsme se zam\u011b\u0159ili na jeden z mnoha zp\u016fsob\u016f popisu konfigurace clustera pomoc\u00ed Ansible. Jakmile si uv\u011bdom\u00edte, \u017ee jste p\u0159ipraveni j\u00edt d\u00e1l, prostudujte si <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.ansible.com\/ansible\/latest\/user_guide\/playbooks_best_practices.html\">best practices<\/a><\/noindex> pro psan\u00ed playbook\u016f. Mo\u017en\u00e1 pro v\u00e1s bude pohodln\u011bj\u0161\u00ed spravovat topologii pomoc\u00ed <code>group_vars<\/code> a <code>host_vars<\/code>.<\/p>\n<p><\/p>\n<p>Brzy v\u00e1m uk\u00e1\u017eeme, jak bezv return delet v\u00fdsti \u017er\u00e1 vzan studnestinstence z topologie, bootstrapovat vshard, spravovat re\u017eim automatick\u00e9ho failoveru, nastavovat autorizaci a patchovat konfigura clustera. A zat\u00edm si m\u016f\u017eete samostatn\u011b prostudovat. <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/tarantool\/ansible-cartridge#ansible-role-tarantool-cartridge\">dokumentaci<\/a><\/noindex> a experimentovat se zm\u011bnou parametr\u016f clusteru.<\/p>\n<p><\/p>\n<p>Pokud n\u011bco nefunguje, ur\u010dit\u011b <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/tarantool\/ansible-cartridge\/issues\/new\">n\u00e1s informujte<\/a><\/noindex> o probl\u00e9mu. Rychle to vy\u0159e\u0161\u00edme!<\/p>\n<p>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/mailru\/blog\/478710\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041c\u044b \u0443\u0436\u0435 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u043b\u0438 \u043f\u0440\u043e Tarantool Cartridge, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0440\u0430\u0437\u0440\u0430\u0431\u0430\u0442\u044b\u0432\u0430\u0442\u044c \u0440\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u043d\u044b\u0435 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f \u0438 \u043f\u0430\u043a\u043e\u0432\u0430\u0442\u044c \u0438\u0445. \u041e\u0441\u0442\u0430\u043b\u043e\u0441\u044c \u0432\u0441\u0435\u0433\u043e \u043d\u0438\u0447\u0435\u0433\u043e: \u043d\u0430\u0443\u0447\u0438\u0442\u044c\u0441\u044f \u0434\u0435\u043f\u043b\u043e\u0438\u0442\u044c \u044d\u0442\u0438 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f \u0438 \u0443\u043f\u0440\u0430\u0432\u043b\u044f\u0442\u044c \u0438\u043c\u0438. \u041d\u0435 \u0431\u0435\u0441\u043f\u043e\u043a\u043e\u0439\u0442\u0435\u0441\u044c, \u043c\u044b \u0432\u0441\u0451 \u043f\u0440\u0435\u0434\u0443\u0441\u043c\u043e\u0442\u0440\u0435\u043b\u0438! \u041c\u044b \u0441\u043e\u0431\u0440\u0430\u043b\u0438 \u0432\u043c\u0435\u0441\u0442\u0435 \u0432\u0441\u0435 best practices \u043f\u043e \u0440\u0430\u0431\u043e\u0442\u0435 \u0441 Tarantool Cartridge \u0438 \u043d\u0430\u043f\u0438\u0441\u0430\u043b\u0438 ansible-\u0440\u043e\u043b\u044c, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u0440\u0430\u0437\u043b\u043e\u0436\u0438\u0442 \u043f\u0430\u043a\u0435\u0442 \u043d\u0430 \u0441\u0435\u0440\u0432\u0435\u0440\u044b, \u0441\u0442\u0430\u0440\u0442\u0430\u043d\u0435\u0442 \u0438\u043d\u0441\u0442\u0430\u043d\u0441\u044b, \u043e\u0431\u044a\u0435\u0434\u0438\u043d\u0438\u0442 \u0438\u0445 \u0432 \u043a\u043b\u0430\u0441\u0442\u0435\u0440, \u043d\u0430\u0441\u0442\u0440\u043e\u0438\u0442 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-53611","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.3 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041c\u044b \u0443\u0436\u0435.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/legko-i-neprinuzhdenno-deploim-prilozheniya-na-tarantool-cartridge-chast-1\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.3\" \/>\n\t\t<meta property=\"og:locale\" content=\"cs_CZ\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041b\u0435\u0433\u043a\u043e \u0438 \u043d\u0435\u043f\u0440\u0438\u043d\u0443\u0436\u0434\u0435\u043d\u043d\u043e \u0434\u0435\u043f\u043b\u043e\u0438\u043c \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f \u043d\u0430 Tarantool Cartridge (\u0447\u0430\u0441\u0442\u044c 1) | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041c\u044b \u0443\u0436\u0435.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/legko-i-neprinuzhdenno-deploim-prilozheniya-na-tarantool-cartridge-chast-1\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-12-05T21:00:00+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-02-18T11:01:32+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47 Snadno a bez n\u00e1mahy nasazujeme aplikace na Tarantool Cartridge (\u010d\u00e1st 1) | ProHoster","description":"U\u017e jsme.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/legko-i-neprinuzhdenno-deploim-prilozheniya-na-tarantool-cartridge-chast-1","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"cs_CZ","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041b\u0435\u0433\u043a\u043e \u0438 \u043d\u0435\u043f\u0440\u0438\u043d\u0443\u0436\u0434\u0435\u043d\u043d\u043e \u0434\u0435\u043f\u043b\u043e\u0438\u043c \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f \u043d\u0430 Tarantool Cartridge (\u0447\u0430\u0441\u0442\u044c 1) | ProHoster","og:description":"\u041c\u044b \u0443\u0436\u0435.","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/legko-i-neprinuzhdenno-deploim-prilozheniya-na-tarantool-cartridge-chast-1","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-12-05T21:00:00+00:00","article:modified_time":"2020-02-18T11:01:32+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"53611","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-24 08:06:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 20:22:49","updated":"2026-01-24 08:06:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/53611","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=53611"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/53611\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=53611"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=53611"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=53611"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}